Test Management in Telerik Developer Edition

5 posts, 0 answers
  1. Sriram
    Sriram avatar
    4 posts
    Member since:
    Dec 2010

    Posted 04 Jan 2011 Link to this post

    Currently, Web UI Test Studio - Developer Edition has the capability to integrate with Team Foundation Server to achieve project maintenance in the Centralized Repository. But, If we check out two different tests by two different resources - How the embedding/check-in process happens in terms of upgrading the element explorer, coding libraries & other build components?

    Our project Module is really high (which we planned to automate more then 30000 manual steps). Also, please suggest can Telerik will support such a huge lines of code can be contained within 1 single project? Suggest/Comment on Performance Issues (if anything may affect this scenario).

    Regards,
    Sriram
  2. Cody
    Admin
    Cody avatar
    3360 posts

    Posted 06 Jan 2011 Link to this post

    Hello Sriram,

    See if this brand new KB article answers your questions regarding our Element Repository. Please don't hesitate to ask if I was unable to address all of your questions.

    We have many customers that have hundreds of tests contained within a single project. You may start to see performance issues if you get to thousands of tests within the same project simply because of the element merge process I explain in the KB article. I recommend you break up your test modules into very high level categories of functionality and have one test project for each category. For performance reasons it would be good to limit each test project to less then 1000 tests.

    Otherwise we will fully support you in your test module creation efforts.

    Regards,
    Cody
    the Telerik team
    Interested in Agile Testing? Check out Telerik TV for a recording of Automated Testing in the Agile Environment
  3. Phuong
    Phuong avatar
    6 posts
    Member since:
    Dec 2010

    Posted 04 Aug 2011 Link to this post

    Hi Cody,

    Would you please explain more detail of “performance reasons” that you mentioned above. Does it mean that it may affect the automated tests execution?
  4. Cody
    Admin
    Cody avatar
    3360 posts

    Posted 05 Aug 2011 Link to this post

    Hi Phuong,

    No, the performance issues I mentioned are not related to the automated tests execution. I am referring to the amount of time it will take Test Studio to merge elements in the Element Repository. This merge happens:

    - When you open a test project
    - Add an element to the repository, usually happens when you record a new test step
    - Delete an element from the repository, either manually selecting an element and deleting it, or deleting a test step that results in an element being removed from the repository

    That's where you'll see performance issues if the number of elements it contains grows excessively large.

    I hope that adequately answers your question.

    All the best,
    Cody
    the Telerik team
    Vote for Telerik Test Studio at the Annual Automation Honors Voting!
  5. Phuong
    Phuong avatar
    6 posts
    Member since:
    Dec 2010

    Posted 09 Aug 2011 Link to this post

    Hi Cody,

    Thank you for the helpful information.


    Best regards,
Back to Top
  Cast Your Vote at DevPro Connections! Cast Your Vote at  Win IT Pro Connections!