Introduction| User Guide |
Target GroupThis document addresses test developers. Test developers are people that use the iValidator "as-is" to test a software. It explains all aspects to that aim. The guide is not meant for people that want to take an active part in the developement of iValidator itself or write their own repositories.Terms and DefinitionsThe test development with iValidator is two-staged. The first step is to implement units in Java. These should be design for reusability. The second step is to write test descriptions that put together test scenarios.A test description is executed by the TestRunner and is called test run. A test run can contain several test descriptions. During and after a test run the TestRunner provides the test results. The TestRunner receives the test descriptions from so-called descriptor repositories and writes the test results to so-called report repositories. Repositories are plugable and can easily be added to an existing iValidator installation. By default iValidator comes with a repository that reads test description from xml files and stores the test results in xml files. This xml-repository is described in this user guide. Index* Test Structure* Unit-Implementation * Adapter * Repositories * Configuration and TestRunner * Test descriptions in the xml-repository |