Linking imbus TestBench and the Robot Framework

The Robot Framework is a generic open source framework for the test automation of acceptance tests. It uses the keyword-driven approach to testing and can be adapted to any test object by using external libraries. With the test adapter (special iTEP wrapper) developed by imbus, the framework from the TestBench can be used very easily. Combining these tools, both of which are very well established in the market, enables the user to implement a highly transparent and intuitive application scenario for the task of test automation.

Workflow

The test cases are created after the relevant keyword library is imported into the TestBench. The keywords in these libraries are nested in professional interactions so that the test designer automatically creates an easily maintainable repository for the task-related test procedures. These tests can therefore deal with a variety of interfaces (GUI, SQL, WEB service, file system, etc.). The test cases performed are later compiled using an appropriate filter in an executable sequence and exported in XML format. These exported test specification are then, using the iTEP, converted into the input format consistent with the Robot Framework (extension: .robot); an iTEP wrapper specially developed by imbus is used for this.

This iTEP wrapper carries out syntax checks during this transformation process and is therefore able to immediately recognise possible specification errors. As an extension of checking the syntax, the option of a dry run is provided by the GUI of the iTEP wrapper. This option facilitates the complete check of the test suites generated, including a review of the complete installation of all necessary components on the relevant system. 

Because all the information required to perform the tests are provided validated in the file system at the same time, the actual implementation can then be started with all available options (use of RIDE, activating via Jenkins plugin or via the simple activation by Batch).

The results after the test run are also parsed with the created iTEP wrapper, producing a TestBench-compliant XML log file. After importing this file, all the results of the implementation are available in the TestBench; this includes any external files (e.g. screenshorts in the event of an error) created during the test procedure.

Conclusion

The combination of these two tools into a seamless tool chain allows a test team to dynamically respond to challenges in short release cycles. At the same time however, the tool chain meets all the requirements which may arise in the context of tests with extended documentation obligations or special traceabilty evidence.

For existing Robot Framework users, there is the option to embed the "island solution of test automation" in a professional tool for test management and thus to transfer in the desired coexistence to the equally necessary manual test cases. Both the creation of test cases as well as the determination of the sequence of their implementation then take place in a very clear hierarchical structure using drag and drop. In addition, the user is provided the options of role-based task distribution, filtering, reporting and version updates within the TestBench for all the project's test cases.

For existing TestBench customers, the integration of the Robot Framework results in an interesting approach to a cost-effective solution in the context of any test automation requirements. Since many suitable libraries already exist for many common tasks and, in addition, any keyword libraries can be created in Python or Java (for adaptations in the context of .net applications, the Remote Library can be used), the gateway to test automation is now wide open for the TestBench user…

Contact show/hide Contact show/hide

Ihr Ansprechpartner bei imbus

Mr. Dierk Engelhardt