In order to execute Qualitia test cases mapped to TFS/Azure DevOps tests in the build cycle, you need to configure the build cycle accordingly. Configuring build cycle includes adding a Visual Studio Test Task and configuring it for the build cycle.
Adding and Configuring Visual Studio Test Task
You must add and configure a visual studio test task to get all the required information from Qualitia and execute Qualitia test cases as a build cycle.
To add and configure Visual Studio Test Task:
- Launch TFS/Azure DevOps instance.
- Edit existing build cycle or create new build cycle.
- Add new Visual Studio Test Task and fill up the details as mentioned in the table below for the Test Selection section:
| Display Name | Enter the desired display name. |
|---|---|
| Test Selection | |
| Select tests using | Select the method using which you want to select Qualitia automated test cases for execution:
|
| Test Plan | Select a test plan containing test suites with Qualitia automated test cases |
| Test Suite | Select test suites containing Qualitia automated test cases. You can select more than one suites here. |
| Test Configuration | Select test configuration. |
| Search folder | This is the directory system will search for the test assemblies. This field comes pre-populated and should be same as the Path to save Qualitia Test Project settings set under Qualitia-Get Test Assembly task. For more information on updating value set under this variable, refer to TFS/Azude DevOps documentation. |
| Test mix contains UI tests | This option enables to run UI tests. This option has no significance with reference to Qualitia automated test cases and is deselected by default. For more information on configuring agent to run in interactive mode, refer to the TFS/Azure DevOps documentation. |
For executing Qualitia automated test cases as a build cycle, it is mandatory to fill up the information for these fields as mentioned in the table above. You may fill up the information in other sections like Execution options, Reporting options, and Control options, and so forth based on the project and build cycles requirements.
