When collaborating between TestRail and Ranorex Studio, align ownership and workflows to avoid duplicated cases, conflicting mappings, and inconsistent run reporting.
Best practice
TestRail is a test management tool, while Ranorex Studio is a test automation tool. To leverage both effectively:
- One team manages test planning in TestRail (manual vs automated, suites, runs/plans).
- Another team automates in Ranorex Studio, importing the tests that are designated as automated and adapting structure as needed.
Test runs can be initiated by either team (or via CI). The most important success factor is communication and coordination.
Source control + TestRail integration
Designate one owner to coordinate import/export/synchronization. Otherwise, teams can accidentally create duplicates or break mappings.
Recommended 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.
- Team members make changes to the solution and check them in.
- Before synchronizing with TestRail, make sure everyone has the latest version.
- Synchronize and commit again.
YAML Connection Credentials collaboration
If your team uses TestRail.yaml:
- Store non-secret settings in the YAML file (URL, project ID, suite/run IDs, proxy settings).
- Store credentials securely (environment variables / secret store in CI).
- Agree on who maintains the YAML schema and when it can change (to avoid breaking builds).
High-volume automation
For large suites, parallel execution, or frequent evidence uploads:
- Be aware of TestRail Cloud API rate limits (e.g., 180 req/min Professional, 300 Enterprise).
- Coordinate heavy CI runs to avoid throttling bursts across teams/tools.