The latest Telerik Test Studio release is out, and all the new features are driven by our mission – to turn QAs into superheroes.
The team's focus for this release is to make test execution even more stable and test failure analysis even easier.
Let’s not lose any more time - let's dive into all the new features.
We all have seen situations where tests fail for random reasons – synchronization issues, temporary machine slowness, an unexpected dialog or error that has nothing to do with our application under test, etc. All these situations usually produce false-negative results. First of all, these failures interrupt our nightly run, and then we lose time identifying whether the failure is due to an application bug or script issue. In most of these cases if you just re-run the failed test case it will pass. But doing this manually would consume time and your overall automation suite result remains failing.
We have solved that problem with the automatic re-run of failed tests inside a test list. Once the option is enabled, all the tests that fail during a test list run will be automatically re-run, and that info will be displayed in the generated result.
If all reruns pass, the overall test list status is “Pass.” Just to be sure that no issue is missed, there is an indication that there were initially failing tests though.
Analyzing the reason a test failed can sometimes be very time consuming, even when the failing issue is easy to spot. Both running the scenario manually or re-running the automated test can take time, especially if we have a long test with many steps. So, even if the issue is easily discoverable you may need to wait for some time to reproduce it, which is boring and unproductive.
For these cases we added the screen recording feature. When enabled it will record, depending on what you prefer, either all the execution or only failing tests. Once the result is ready you can open the video and see what led to the failure and what really happened.
You can see this in action in the video below.
We’ve heard from many automation engineers that keeping the user session on a machine is a challenge. When you want to validate real actions or desktop commands on your application’s UI, you need to have an active UI session on the machine. And this active session usually gets disconnected due to some machine/domain settings or other rules.
We added an option to the Execution client to keep the active session so that all UI tests run unattended and seamlessly. You just need to open Test Studio Test Runner and enable the option.
There is a new verification step that checks if and what JS errors there are on your website. If there are any expected errors, you can exclude them from the verification, so it does not fail because of them.
Browsers are constantly evolving. They come with multiple official releases per year and even more updates. Some of these updates change the UI structure of the whole browser. This impacts how Test Studio handles dialog and notification windows. As a result, after breaking changes like these are introduced by the browsers, Test Studio should be updated accordingly.
The good news is that for such cases we don’t need to put a whole release out and the user doesn’t need to upgrade to this newer version of the Test Studio application anymore. From Test Studio R3 2018 onwards, anyone with the latest major release will be able to download a very lightweight patch directly inside Test Studio’s UI whenever a browser releases a breaking change. This patch is a minor one that does not upgrade the whole application, nor your projects. It holds no risk for your project, tests and Test Studio stability.
For a full list of everything new in Test Studio, feel free to check out the updated release notes.
To explore the features of Test Studio R3 2018, download the free, full-featured trial (no credit card required).
Iliyan is a Product Manager for Telerik Testing Solutions, including Test Studio and Mobile Testing. Ten years ago he started as a game tester, because he loves video games, and eventually he realized that breaking software is fun. He believes that a good Quality Assurance Engineer should be involved in all phases of the software development process.
Now as a Product Manager Iliyan has a new mission—to unburden the QA engineer from the test automation problems and to make the tester's workday a more pleasant one.
Subscribe to be the first to get our expert-written articles and tutorials for developers!