Comment on page
The TestResults.io designer is an extension to Visual Studio which allows you to create and execute test cases during your test automation development cycle.
The TestResults.io designer was created in order to help software developers and testers in designing robust and easy to maintain test models. The Designer together with the TestResults.io engine allows you to build a test model based on the images and text displayed on the Subject Under Test (SUT). Any step which is being done in a manual test case can be easily replaced by a step created with TestResults.io
Keep in mind that the Designer is not a capture and replay tool and does require basic C# coding skills in order to create your test model and write your test cases.
The Designer contains of several modules which will allow you to create test cases and test models fast and efficiently. The bottom line is that it is an extension to Visual Studio. Therefore, you can benefit from all advantages of object oriented programming as well as all .net libraries.
The Designer will generate a lot of the required code for you, but you will still need to write code for some tasks. The designer will help you to prepare what you need in order to do so. The flow presents itself as follows:
The Test Case as well as the Test Model are developed locally on the test / automation engineers PC. The execution of the test case (hosting) is done locally however the test case itself is executed on the desired dedicated test environment.
Once the test case (and/or test model) are developed and proven to work locally, the user can upload the test case directly from the Designer to the Portal and afterwards control the execution of the test case from the Portal. The files which are uploaded to the Portal from the Designer are called containers.
The TestResults.io engine allows you to identify objects on the screen in two different ways:
The designer allows you to take images of the UI controls in the Subject Under Test. Those images are afterwards used within the code you write so that you can interact or observe the SUT. The details of taking images and coding will be presented in the next chapters however from a high level overview it looks as follows.
- We take an image with the Designer e.g.
- We reference the image within the test case/test model code e.g.
- There are also more advanced options which will be a part of the next chapters like
Keep in mind that the Designer doesn't limit you to the TestResults.io visual engine. You can can use other frameworks to interact with your SUT (e.g. Selenium) or test your application through API calls.
Whenever you cannot use the Image Recognition you can use the Text Search (OCR Search) to identify objects of the SUT. Following the Google Search button example it would look as follows:
The next chapters will also show you the details of how to effectively search for text.