Why do you have things broken down into Project\Group\Test?

How to use eValid to support regression testing.

Why do you have things broken down into Project\Group\Test?

Postby index9 » Wed Sep 30, 2009 4:15 pm

Why do you have things broken down into Project\Group\Test all the time?
Where does that come from?
index9
 
Posts: 10
Joined: Wed Aug 26, 2009 3:32 pm

Re: Why do you have things broken down into Project\Group\Test?

Postby eValid » Thu Oct 08, 2009 5:37 am

index9 wrote:Why do you have things broken down into Project\Group\Test all the time?
Where does that come from?


Long experience in organizing suites of tests have shown us that in 99.99% of the cases you tend to group tests of a similar nature into a test "Group", and that you then tend to group a collection of Groups into a Project.

Think 100 tests in a Group and 100 Groups in a Project and you have a reasonably efficient way to partition what otherwise would be 100 * 100 = 10,000 tests.

Of course in practice you probably really would have 10 groups of 100 tests or 100 groups of ten tests.

So the answer is that this is a judgement call that keeps your tests organized
and in a way also prevents you from having "too many" tests in a project.

Our goal was about 1,000 tests in a test suite and over the years we've found it quite workable to have just the three layers: Project :: Group :: Test.

The eValid Team
eValid
 
Posts: 2076
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to Regression Testing

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons