Applications nowadays have different ways to approach. For example, your application comes in the following flavors.
With the automated-testing tools around Test Workbench , you can test the different interfaces through a single test as part of a use case. Unlike most other tools for automated testing, Test Workbench can test the same function that you access through different clients.
Different clients, same function
Let’s take Team Concert as an example. Team Concert comes in different clients. You can work in the following clients.
In these clients, you can create records, edit records, save information, and other things. Through all clients, the application server receives the information that you entered and commits that information into the database. That’s why you say that saving data on the different clients is one use case. Of course, you want to test the same function on the different clients.
Quick not dirty
For continuous engineering, you need continuous testing. Test early, test often and test automated are the buzz words for the technological and cultural change that you need to strive for. Besides a robust and maintainable test automation framework, also a well thought approach to discover defects might help reducing time for troubleshooting in finding the root cause.
If something unexpected occurs in all clients, you might bump into a defect in your server’s business logic. If you see something unexpected only in one client, that client might be suffering a defect.
In our example of Rational Team Concert, all clients would show something when the server fails to commit changes to the database. If only one client shows unchanged data, only that client is likely the root cause of the failure.
When you put the tests of the different clients into a single test, you see where to look for the root cause when anything goes wrong.
Let’s test two different clients
Let me explain by example. The application under test is Team Concert. Team Concert comes in a thin client, a browser, and a thick client, an Eclipse environment. I want to test the creation of a new record, a work item.
In Test Workbench , you can merge different tests into a single test. Test Workbench calls such test a compound test. Here compound means composed or consisting of parts. In this example, we test the Rational Team Concert in through the following interfaces.
Good to go
First, install Functional Tester v9.1 and Test Workbench Web UI Tester v9.1 in the same Eclipse shell. Of course, both products are in the same architecture, either 32 bit or 64 bit.
Now, you got a single test that runs in both clients. First, the Functional Tester script in the Eclipse client. Then, the Test Workbench test against the Chrome browser.
In the video, you can see how you build a compound test and how to run that compound test.
If you want to try yourself, you can download Functional Tester and Test Workbench Web UI Tester for free.
In short, you can use a Test Workbench compound test to compose a test that consist of two tests against different clients and that test the same function. This compound test might be convenient to help you finding the root cause when something goes wrong.
If you’d like to share your experience with compound tests or share your thoughts, leave a comment here or follow me on Twitter @gunangwaney.
Gunang Waney works as a product specialist of the Rational Testing tools. He is passionate about communicating technical knowledge and making things work for customers. Gunang graduated from Utrecht University, The Netherlands with an MSc degree and works in Amsterdam, The Netherlands. When he can escape from his computer, he spends time with his family.