Automations allow you to run tests without user interaction on remote computers. You can perform such tests as often as needed, for example, after a successful build or on a daily basis.
Integrate QAComplete tests with various testing tools to track results using the features provided by the Test Library. You can automatically run necessary tests and collect results for full tracking of your testing coverage and progress.
Supported automated testing tools
- SmartBear TestComplete
- SmartBear ReadyAPI
- SmartBear SoapUI OS
- Selenium Webdriver for the following unit testing frameworks:
|Note:||Starting from the 10.50 version, TestComplete supports integration with Selenium tests. In TestComplete, you can run Selenium tests created with JUnit, TestNG, NUnit, PyUnit, Ruby Test::Unit, and PHPUnit frameworks. Add these tests to the TestComplete project, then integrate the project with QAComplete.|
How the test automation works
The test automation mechanism in QAComplete works in the following way:
In your automated testing tool, you create tests that will perform the needed actions to test your application or feature.
You pack the automated test files into a .zip archive. These can be stored in a shared network folder or on a separate website.
Note: It is also possible to attach files directly to the test item in the Test Library.
You install and configure the Test Agent on the computers that you will use to preform automated tests.
You associate the automated tests with tests in the Test Library.
(Optional) You create schedules to run tests at the time specified.
During the scheduled run time or when you request the test to run, the Test Agent performs the following actions on the host:
- Connecting to the QAComplete web service;
- Fetching the automated test files;
- Launching the testing tool on the host;
- Performing the test.
Tip: You can configure the Test Agent to log out of Windows while closing any open applications, then log back in with the specific credentials. It is also possible to check if a user on the host machine is currently logged in to avoid the logout routine.