iValidator A test framework to help you with your development.
Download

iValidator Ranking & Summary

iValidator Tags

Test Tester test framework scenario Micro Test Framework Declarative Test Framework test framework add-on test-driven development test automation framework scenario automation complex environment test development test load test framework performance test framework thread test framework test development framework

iValidator Description

iValidator is a Java framework designed to help you with the automation of scenario and integration tests in complex environments. Main features: Complex Test Scenarios iValidator enables hierarchic and sequential test structures concurrently. The control of the test processes is on the lines of modern job scheduling systems. The complete test context and test history are available for control means. Parameters for the components (test, setups, checkups, and teardowns) are supplied from the outside (Inversion of Control Pattern). Extensive Control Mechanisms Control elements in the xml description of the test scenarios can be used to define whether test should run sequentially or in parallel. They also control the behaviour depending on errors in individual tests or test suites, e.g. abortion of the complete test, continuation with the next test level with or without reinitialization, etc. Reusability of Unit Tests So-called unit tests form the base level of the test system. These are test classes implemented in Java that inherit all the necessary funtionality to be used within the framework. The test funtionality has to be coded, parameters are supplied through the xml description. The unit tests constitute self-contained developer tests. Wrapping of the SuT Technical Interfaces with Adapters Adapters are used to wrap the access to the system under test (SuT) and other external systems. Adapters decrease the complexity and costs for maintaining the testing system, beacuse they limit the number of places needed to be updated in case of interface modifications in the SuT or in the external systems. Flexibility The test parameters are defined in the xml description. If necessary parameters for unit tests and lower level test suites can be overwritten when they are imbedded in further test hierarchy levels. The strict separation of the actual test classes from the parameters and the definition of the test flow provides great flexibility. Initialization of the Test Environment The initialisation and clearance of the test environment is done by setup and teardown classes. Like the test classes the parameters can be provided in the xml description and the setups and teardowns can be reused. Setups and teardowns can be applied at all test levels. Validation, Reporting, Logging iValidator separates the test execution from the validation of the results. Special checkup classes validate the results and thus allow a context-dependent evaluation within various scenarios. Example: A test runs successfully, viewed by itself it is okay. But within a test scenario with an invalid previous login this is to be assessed as an error. The test results are reported in xml. The structure of the report reflects exactly the hierarchic structure of the test configuration and thus provides a clear presentation even for complex, deeply layered scenarios. iValidator uses and extends Log4J to log relevant information, e.g. configuration, test initialization data and state, information about every test step and its state, test result with state and statisitics, detailed information for error tracking (stack traces). System Independence The iValidator test framework is by no means limited to the test automation of Java based systems. By the use of so-called adapters any system can be tested. Systems that are necessary for the execution of the test scenarios but not test relevant in themselves can be simulated with mock objects. Support of all Test Levels Because of its structure iValidator supports all test levels: developer tests integration tests acceptance tests JUnit Support We are able to run JUnit tests within the iValidator framework. This includes invoking the setup and teardown methods of the JUnit test classes. The results of the JUnit tests can be used for the control of the test flows along the same lines as the iValidator test cases. This allows you to reuse existing unittests for the integration test. Eclipse Plug-In To simplify the handling of iValidator we offer an Eclipse Plug-In. Now the test execution and the display of the results can be integrated seamlessly into your IDE. Ant Task By providing iValidator as an Ant Task, test runs can easily be integrated into the build and deployment process. Flexible Interfaces for Test Descriptions The framework allows to read test descriptions from any source (e.g. databases or Excel sheets). Accordingly the results of the testruns can be written to any target. Available implementations for the test descriptions are at the moment: XML-Descriptor-Repository Available implementations for the reports are: XML-Report-Repository Swing-Report-Repository

iValidator Related Software