Features in the current release
A new Swing runner that enables you to manage your test suites/scenarios, execute scenarios, view and publish reports.
Enables you to define a tree of fixtures, every fixture with setUp, tearDown and failTearDown methods. The fixture represent a configuration of you setup. Every test that extends SystemTestCase can set the fixture it should work on top of. When a test is executed the framework will navigate to the fixture that was set by the test. The framework remembers the current position in the fixture tree. If two tests run on top of the same fixture, and they are both executed as part of a suite one after the other, the framework will navigate to position fixture tree for the first test. Afterwards no fixture tree navigation will be needed for the second. As part of this feature a fixture manager UI is available. You can navigate the fixture tree manually.
You can run and debug your tests directly from your Java SDK environment. If you are using Eclipse or any other Java SDK you can use there existing integration with JUnit to run JSystem tests.
Enables extendable detail reporting service. Now it is possible to log positive events from your tests and API's. A hierarchical HTML view of the results is available. You can use it to track complex functional/system tests. You can extend it by writing you own reporting layer.
A layer that enables a test to run on different setups. It can be seen as a way to send parameters to tests.
A convention to represent the setup/system you are working on with a single object. The steps in the tests will be operations on the setup/system object.
An expendable methodology able to analyze the test step result. You can analyze text output (String), database output (ResultSet) and more.
For more details please refer to the user Manual .
When defining setters method in your tests, the scenario builder will allow you to set the parameter value. The parameters values are saved into the scenario file.
You can manage test scenarios from the Scenario Builder GUI, Save them to the source control directory, set parameters to tests and more...
If you documented your test using javadoc the documentation will be shown in the Html and other reports.
Enhanced ability to define tasks that will be executed parallel to the test, collect information and in some cases can fail the test.