JSystem Demo

Applicable for version 3.x of JSystem.

What will you find in this paper?

This paper will guide you in installing and running the JSystem demo. If you would like to know what JSystem is all about, this is the right place to start.

The demo kit will demonstrate the following capabilities of JSystem solution:

1. Build & run tests scenario
2. View & analyze results
3. Publish results and reports
4. Test writing, run & debug

Download and install

Below are the steps for installing JSystem:

1. You should have Java (JRE) in version 1.4.x installed on your machine. (download java).
2. Download jsystem + demo pack.
3. Unzip the jsystem_demo.zip file.
4. Use run.bat in the root of the extracted directory to launch the application.

Build & run tests scenario

If for some reason you were unable to see the main window:

1. Try to set JAVA_HOME system property to the location of your 1.4.x java installation.
2. Refer to the installation guide for more details.

What do I see in the main window?

1. upper task bar - is used to run the scenario - , stop scenario execution - , reload tests - , view tests execution log - , select the setup to run the test on, change the tests class directory - and more.
2. scenario panel - on the left side of the application you will see the scenario panel. The scenario panel includes the scenario task bar, the scenario table and the scenario progress bar.
3. tests tree tab - on the right side of the application main window you will see the tests tree tab.

Run a test

Select the testBridging from the tests tree, use the big left arrow - to insert the test to the scenario. Press the run button - . Wait for the test execution to end (around 14 sec).

View & analyze results

Use the report button - to view the execution results. The report you can see is the HtmlReport output. The html page contain 3 frames:

1. Package frame - on the upper left side you will see the package frame. In this frame you will see a list of all the tests packages that was run in the scenario. In our case you will see traffic.tests.
2. Tests frame - on the lower left side you will see the tests frame. The test you have just run is visible here.
3. Main frame - on the right side is the main frame.

1. Hierarchy - 4 types of layers: package, test, test step, step derail-down.
2. Summary report - include some brief information/statistics.
3. Javadoc - extract javadoc from the tests code to the test report.
4. Test code - show the test code in the report.
5. Online status - the report is update online and you can view the test results during the test execution.

Test writing, run & debug

Following is a test code example:

The test is written in Java and it's a JSystem test, It extends (JUnit). The test works with 2 SystemObject, the first is the device under test and the second is a traffic generator (AQUA traffic package include single interface to all the common traffic generator like: Ixia, SmartBits and Agilent N2X). Because it's a JUnit test you can use your favorite Java SDK to edit run and debug the test. As part of AQUA methodology, the test spikes in the QA engineer language and it's very simple and readable. In the test you can see 3 types of operations:

1. System object configuration.
2. Analyzing - every configuration operation can follow an analyzing operation that will work on the last configuration operation.
3. Reports.

The test as all the power of programing language like Java, but it try to be as simple and clear as possible. You will rarely find if statement in the test code. All the complexity is hidden in the SystemObject layer.

You can use setter/getter methods in the test.

The test setter method will automatically appear as a parameter to the test. The person who run the scenario can change the test behavior using the runner GUI.

When selecting a test from the scenario screen, the 'Test Info' tab can give additional information, test documentation as written in the test source and test parameters.

Publish results and reports

The full AQUA solution include a centralize reports server. The report server is J2EE base application that include database. The install and use of the reporting server is out of the scope of this demo. In this section I will briefly explain the use of the reports server. For more information about the reports server contact info@aquasw.com.

After running a scenario the next step is to publish the results to a main server. This process include the following steps:

1. Editing the reports results. Add remarks, delete tests and change tests status.
2. Add additional information about the scenario execution like the version of the device under test and more...
3. Send the results to the server.
4. Access and analyze the result by all the people in your organization.

Following is a screen-shot of the reports main window: