forum.e-valid.com

The way you have put the eValid Manager (eV.Manager) together suggests you have a design target in mind for the size of the test suite? Do you?

Issaca wrote:The way you have put the eValid Manager (eV.Manager) together suggests you have a design target in mind for the size of the test suite? Do you?

Our engineers found, after years of experience, that few test suites ever grew to over 500 tests. So the design point for the eV.Manager engine was 1,000 tests.

The nominal structure is one big project made up of 10 sub-projects each consisting of 10 groups of 10 tests per group. And that yields a total of 1,000 test nodes.

Of course there are variations on this. But the planning has largely held firm and the reality seems to support this nominal structure. We have heard of some test groups with 100 tests, and some project with many more than 10 major sub-groups, but when that happens eV.Manager can still handle the load.

Another way of looking at is in terms of total test suite execution time. If you have 1,000 tests and they take 1-2 minutes each to run and validate,
then you have a suite of tests that will take 1K to 2K minutes, which is 16.6 to 33.3 hours. In other words, over a day!

So, when your test suite is that large, you probably split it in parts that can run on different machines automatically.

eValid Manager Team