Nowadays, web visitors don't only consider the usefulness of a website but base their decision to stay or leave the site on the layout, design, and functionality. A significant portion of visitors abandon a website with poor functionality or confusing navigation,...
When collaborating between TestRail and Ranorex Studio, there are a couple of things you should consider.
In this chapter
Basic best practice
TestRail is a test management tool, while Ranorex Studio is a test automation tool. They serve similar, but ultimately different purposes. Based on this we recommend the following approach to leverage the advantages of both programs.
One team is responsible for planning and managing tests on TestRail. They designate what needs to be tested, which of the tests are manual/automated, and they plan test runs.
The other team works in Ranorex Studio. They import the tests designated as automated and automate them in Ranorex Studio. They adapt the structure of the TestRail suites to what makes sense in Ranorex Studio.
Test runs can be initiated by either team or by using Continuous Integration tools. What’s most important is communicating it to each other. This applies in general: Keep each other up to date. Let others know what you’re doing. Most collaboration pitfalls are rooted in a lack of communication.
Source control and TestRail integration in Ranorex Studio
When using source control and the TestRail integration, it’s important that you designate one person to coordinate and do the synchronizing. Otherwise you will end up with duplicated test cases in TestRail or worse.
Follow this workflow:
- Connect your solution to TestRail, i.e. carry out an import or export, depending on your starting point.
- Check in TestRail.trsd into your version control tool.
- People make changes to the solution and check them in.
- Before synchronizing with TestRail, make sure everyone has the latest version.
- Synchronize and check everything in again.
- Repeat from step 3.