Forum Discussion

rlounsbury's avatar
rlounsbury
Occasional Contributor
14 years ago

Project Suite Sizing

We are in the process of setting up TestComplete tests for a large web application.  The application consists of 60 WAR files with 700+ JSPs; we anticipate that there will eventually be between 700 and 1000 test scripts for the application.  We are looking for guidance on how we should set up the TestComplete environment for this test set.  Should we have a single test suite with separate projects for each WAR, or should we have separate suites for each WAR and make projects within the suites as necessary?



We anticipate that there will be a couple of the WARs that will have scripts that are used by many other tests.  (E.G. the tests to login/logout will be needed by all other tests.)  



In particular, we are concerned about the performance of running a large number of tests.  We anticipate running these tests as part of a nightly automated build.  We are using version 8.0 of TestComplete.



Any input would be appreciated.



Thanks in advance,



Ron L

3 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    I would recommend, as much as possible, utilizing libraries of code and Script Extensions to reduce the amount of code and tests that you have to write and maintain.



    I would also investigate implementing some sort of data driven/table driven testing where the tests are not in the projects themselves but are stored in some sort of data table file (like a CSV or Excel sheet).  Then, when you run your tests, your framework will read the test parameters from the files, execute the tests, and iterate through the files.  This will greatly reduce the amount of script repetition and re-use in your projects and increase your maintainability and portability of your tests.



    I would HIGHLY recommend reading Linda G. Hayes book "The Automated Testing Handbook".  While it is not tool specific nor does it describe details script code, it lays out some high-level concepts that work VERY well in creating a maintainable and efficient automated testing framework.



    http://www.softwaretestpro.com/Item/4772/The-Automated-Testing-Handbook/Automation-Quality-Assurance-Test-and-QA-Technology-Testing
  • rlounsbury's avatar
    rlounsbury
    Occasional Contributor
    14 years ago
    Robert



    Thank you for your response, I will take a look at the book you suggest.  We are planning on using data-driven testing; our concern is simply that with the large number of pages in our application, we will have a large number of tests - even if we use libraries, etc.  Are there guidelines for how many projects may be included in a suite and how many tests may included in a project without significantly impacting the performance?



    Thank you,

    Ron L
  • YMinaev's avatar
    YMinaev
    Icon for Staff rankStaff
    14 years ago
    Hi,



    There's no built-in limitation of the number of projects or test. This greatly depends on your system resources. It is impossible to say anything specific "in general".