You can publish your existing Qualitia test cases that are linked to TFS/Azure DevOps tests.

Only the test cases linked with TFS/AzureDevOps tests are available for publishing. After you publish the test cases, the current state of such test case(s) is saved to Qualitia server.

In order to do publish, you must first link Qualitia test cases to TFS/Azure DevOps tests.

Best Practices

Link a test case with TFS/Azure DevOps test.
Once the test case is completed in Qualitia and ready for execution, Publish such test cases from the Execute section.
If you make any changes after publishing a test case, Publish such test cases again.
If the test case is no more required to be integrated with TFS, unlink the test case.
Changes in environment variables do not affect the Publish status of test cases. Before executing test cases using build or release cycles, ensure you republish the test cases from the Execute section (Integration Status) which are published earlier. It is to ensure the TFS/Azure DevOps has the latest set of test cases before execution.

To Publish Qualitia Test cases for TFS/Azure DevOps test execution:

On the Execution tab, navigate to Integration Status.
You can filter the test cases based on the test Scenario they belong to along with Test Case Link Status, and Test Case Publish Status.
Select the test case(s) to publish.
Click Publish.
You can publish test cases that are linked with the TFS/Azure DevOps tests.
Use the Link / Unlink button to map or unmap the test cases to TFS/Azure DevOps tests.
For more information on this, refer to the Linking Qualitia test cases to TFS/Azure DevOps tests section.
Publish Statuses
- Not Published - When a test case is linked with TFS/Azure DevOps test, its publish status is set to Not Published. These test cases will not be executed from TFS/Azure DevOps.
- Published - When the latest version of a test case is published to Qualitia, the publish status is set to Published. The test case version in Qualitia (which is the same as version published to Qualitia server) will be executed from TFS/Azure DevOps.
  Only published test cases will be executed as a build or release cycle from the TFS/Azure DevOps.
- Updates not Published - When a test case is modified after publishing it, the publish status is set to Updates not Published. In such event, the latest version of the test case is not available with Qualitia server.
  To make the latest version available for execution, you must publish the test case again. TFS/Azure DevOps will use the last published version of the test case (which may not be the same as version visible in Qualitia). Changes made to the test cases after publishing do not affect its execution from release/build pipelines.

Once you publish the test case, Qualitia saves the latest updated version to Qualitia server. Also, the status of such test cases is updated to and is displayed in a pop-up screen.

In case you update any of the existing environment variables from the published test cases, you must republish such test cases to TFS/Azure DevOps for execution through the build or release pipelines. Updates in environment variables do not take effect unless you republish the test case.

In TFS/Azure DevOps:

Once you publish any test case from Qualitia automation studio, the status of the test in TFS/Azure DevOps is marked as Automated.

To view the status of the test case in TFS/Azure DevOps:

In TFS/Azure DevOps, select the test suite.
In the Automation Status column, the status will be updated to Automated.
Open this test case and in the steps section, you will find the status as Automated.
This means this test case is successfully linked to Qualitia automated test case.

4. Open this test case and in the steps section, you will find the status as Automated.

This means this test case is successfully linked to Qualitia automated test case. You can now trigger execution of this test case as a build or release cycle from the TFS/Azure DevOps.

Browser not supported