How is eValid organized on my machine/server?
I mean, how does eValid organize all of the scripts and results and other stuff?
Also any documentation references would be helpful.
This can be daunting if you have a lot of tests that are complicated BevLin.
Here is the lead page that explains the design: http://e-valid.com/Products/Documentati ... rules.html
The basic principle is this: you have a test project that is organized into groups of tests, and individual tests that are given names.
Project >> Group >> Test
A good rule of thumb is to have a test activity that involves 10 projects each with 10 groups of tests, and each test has 10 individual scripts.
That's 1000 test overall.
That's enough for most of our users.
-- eValid Support