My Certificate Find a Certificate About Certification QA Terminology Basics of Software Testing Basics of Test Automation QA Processes Overview Basics of testRigor BDD & SDD Web Testing Overview Mobile Testing Overview Native Desktop App Testing Overview API Testing Overview Click / Drag / Hover Entering Data Variables Validations Scrolls and Swipes Dealing with Dates and Times Dealing with Emails Working with Tables Conditional Sequences Cycles & Loops Reusable Rules SMS and Phone Calls Managing Multiple Environments Settings Integrations AI and Prompt Engineering AI-Driven Test Case Generation with testRigor Using AI Coding Agents with testRigor Final Exam

Generative AI-Based Testing Certification

Integrations

Integrations

An integration connects testRigor with another tool your team already uses. This allows testRigor to exchange information or trigger actions automatically.
For example, updating a test case in a test management system, creating a bug ticket, starting tests from a CI/CD pipeline, querying a database, or running tests on real devices.

All supported integrations can be found here (except for CI/CD systems, since testRigor supports most of them).

Test case management

Test case management tools help teams organize, track, and manage their testing activities. They provide a central place to manage test cases, assign them to team members, track their results across multiple test runs, and review testing history over time. This can help teams identify recurring failures and areas of an application that may be more likely to experience issues as new changes are introduced.

testRigor integrates with test case management systems by allowing test cases in testRigor to be linked with corresponding test cases in these systems. When a full retest is performed in testRigor, the results of linked test cases can also be updated automatically in the connected test case management system.

For example, if a test case managed in Zephyr is linked to an automated test in testRigor, running the test in testRigor can automatically update its status in Zephyr. This allows teams to keep their test results synchronized and manage both manual and automated testing from one central location.

testRigor integrates with TestRails, Zephyr, Azure DevOps, XRay, ReportPortal, and several other test case management tools.

Ticket issue creation

Issue tracking tools are used to record, assign, prioritize, and track bugs and other development work. testRigor can integrate with issue tracking systems so that problems discovered during testing can be connected to your team’s existing bug-tracking workflow.

Customers need to report their bugs so that developers are made aware of fixes that need to be made before merging a feature into production. These systems allow them to do that.
testRigor test fails → issue is created/reported → developer investigates → issue is tracked in Jira/Azure DevOps

For Jira, users can now assign values for custom fields. The name of the Jira field must be the one that starts with customfield_.

testRigor integrates with Jira, AzureDevops, PivotalTracker, and several other issue management tools.

CI/CD

CI/CD systems automate the process of building, testing, and releasing software. testRigor can be added to this process so automated tests run whenever appropriate. For example, after a new version of an application is built, we want our CI/CD to automatically run our assigned automated tests

Developer pushes code → application is built → CI/CD triggers testRigor → testRigor runs regression tests → pipeline continues if the required tests pass or stops if they fail.

Database testing

A database is a system used by applications to store and manage data. In general, directly accessing a database during testing is considered bad practice because it makes tests dependent on the application’s internal database structure, which can change over time.

However, direct database access can be useful in certain testing scenarios. For example, you may need to retrieve test data, verify that information was stored correctly, or access information that is difficult to obtain through the application’s user interface.

Database integrations should be configured in Settings before use, but these configurations can also be overridden through the command line when running tests as part of a CI/CD pipeline.

testRigor supports communicating with both SQL and NoSQL databases. When a database query returns data, testRigor automatically stores the resulting columns as variables that can be used later in the test.
For example, running the following command:

run sql query "select top 1 UserID, LastName, FirstName from Users;"

will run that SQL query in database that was configured in Settings, read the first row with the data and then create variables UserID, LastName, and FirstName automatically with the data from the row that had been read from the database, so you can later do validations like this:


check that stored value "LastName" itself contains "Doe"

testRigor supports querying MySQL, PostgreSQL, Microsoft SQL Server, Snowflake, MongoDB, Grid Gain, and more. If you need database access that is not listed here please contact testRigor support.

You can read more about database syntax here

Third-party infrastructure providers

testRigor’s testing capabilities are restricted to certain devices, relying on simulators and emulators. Some applications necessitate testing on actual devices.

Device farms are cloud services that provide access to a large collection of browsers and devices for testing. Through integrations with providers such as BrowserStack, testRigor tests can run on infrastructure provided by these services, including real devices when required. For example, you could use testRigor to run the same mobile test on multiple Android and iOS devices provided by a device farm without physically owning those devices.

testRigor communicates with these third-party providers through APIs, sending the actions required to execute the test on their infrastructure.

testRigor integrates with BrowserStack, Kobiton, SauceLabs, and several other test infrastructure providers.

Test your knowledge

Helps people to fly to Mars.
Enables testRigor to report issues.
To assign custom values for Jira fields.
Allows testRigor to set statuses of test cases in that test case management system.
Allows testRigor test cases to connect to real mobile devices.
To simulate different devices for testing.
To monitor the progress of test case plans.
To oversee release cycles, identifying bugs before they become public.
To report bugs directly to testRigor.
To create new test suites.
© testRigor. All rights reserved.