iTORX has been designed to be easy to follow and easy to use, it is configurable, and, of course, it fits to the special requirements of software testing.

The interaction method makes the imbus TestBench a powerful tool for test specification. This is complemented by the imbus Test assistant for Online and Remote eXecution (iTORX), which is integrated in the imbus TestBench. iTORX is a versatile and carefully thought-out assistant for specification previews and manual test execution.

Down to the smallest detail: iTORX links your defects not only with the respective test case, but with the test step that actually triggered the defect. That means you are always able to pinpoint the exact point in the test where the defect occurred.

If an external defect management system is connected, all defect information will, of course, be synchronized with the external system.

iTORX reliably guides the tester through the manual test execution in a way that is  easy to follow, and helps him to record test results quickly and exactly. In addition, iTORX can be called up during the specification process, and provides the test designer with a detailed preview of the specified test.

iTORX has been designed to be easy to follow and easy to use, it is configurable, and, of course, it fits to the special requirements of software testing. Carefully thought-out details make it easier for the user to do his daily work. Some examples:

  • Besides the main window, there are a number of detail windows that can be hidden when not required. All the windows can be arranged in any way on the screen, and can be moved individually or together.
  • If an unopened window contains relevant information, then this is signaled optically in the main window, and the window can be opened with a single click.
  • For navigation during the test and the input of the most important test results, it is sufficient to use the keyboard; of course, all elements can also be operated using the mouse.
  • Result values, such as “PASS” and “FAIL”, are propagated in the test tree from lower-ordered to higher-ordered elements – in accordance with a tried and tested status model.

Versioning

This might also be of interest to you