|Conditional Statements and Loops||
We introduced four new nodes altering the test execution flow: Conditional Statements and Loops.
The If-Then-Else-node allows you to specify one or more test cases or test steps as a condition. Based upon the result of the condition nodes, either the "then" or the "else" branch will be entered and the containing nodes will be executed. The condition can also be negated.
The While-Do-node and the Do-While-Node will both repeat the test nodes inside the "do"-branch until the condition is no longer being met. In contrary to the While-Do-node, the Do-While-node checks the condition after each run through the "do"-branch. Therefore, the Do-While-node will always run at least once.
The Repeat-node repeats the nodes inside the "do"-branch for a specified amount of times.
Component name types are calculated and treated differently from this release onwards. The type becomes only decorative, so actions resulting in invalid component name types are allowed from now on, however, the user is warned before any action resulting in an invalid type. Component names with invalid type are decorated by error markers, just like component names which are mapped into a component which does not realize one of the actions which might be executed on the component name.
|Check actions with timeout parameter||
Most of the check actions do now have a timeout parameter. If there is a timeout value greater than 0 the check action is checking multiple times if the wanted status has occurred. If this did not happen until the timeout is reached the check is marked as check failed.
|Skipping test steps||
Test steps can now be skipped by changing the value of at least one parameter of a test step to '##jbskip##'.
|New navigation in HTML reports||
Similarly to the ITE, it is now possible to navigate between errors in an HTML report.
|Navigation between parents and childs||
To help navigating between Editors we have introduced double click on root Nodes of Test Case Editor's. This will activate a Editor in which the Test Case is referenced or if there are more than one such Editors open, you can choose one to activate in a dialog. Aswell if there is no such Editor open, you can choose a Test Case or Test Suite which references the Test Case, and open its Editor.
|Deletion of complete Trees||
We introduced a new feature in the Test Case Browser called Delete with Orphans. When tidying up a project, there are Test Cases that are no longer required or used. The Delete with Orphans feature allows you to show all Test Cases that would remain unused if a certain Test Case were deleted. It then offers you to delete the Test Case with all its remaining "Orphans
|Export JUnit reports||
When generating TestResult XML/HTML files from Test Results, the generated files will now include an additional lightweight JUnit report. You can define referenced Test Cases as "JUnitTestSuite" for the generation of the JUnit report.
Back to the top