Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following table explains how different components of Azure DevOps and Qualitia interact with each other.

Component

Roles Played in Different Stages

Azure DevOps

Association

  • Responds to Qualitia server using standard out of box APIs offered by Azure DevOps.

Execution

  • Configuration of build/release pipelines.

  • Agent pool configurations.

  • Initiate pipeline execution.

Result Publish

  • Host results of pipeline execution.

Azure DevOps Agent

Association

None

Execution

  • Executes of the jobs in the pipeline and the contained tasks.

  • Select Test Plan and Test Suite which contains Automated test cases and Suites in Azure DevOps projects.

Result Publish

  • Execution of the Publish Result task of Qualitia to publish results to Qualitia Server and Azure DevOps Test Runs.

  • Uses Qualitia Server APIs to publish result.

Qualitia Server

Association

  • Interacts with the Azure DevOps server to update Automation Status of Azure DevOps test cases.

Result Publish

  • Receives test case results directly from the Qualitia Client with the help of Qualitia APIs.

Qualitia Client

Association

  • Allows the authorized users to view Azure DevOps projects and associate projects and test cases.

Execution

  • Publishes the test case to Qualitia project repository. The published test case is used in the Azure DevOps pipeline execution.

Result Publish

  • Shows the status of Test cases executed through Azure DevOps pipeline in Real Time Reporting Portal.

Configuring Azure DevOps for Test Executions

...

Your Azure DevOps instance is now ready for Qualitia integration.

🔧 Got a problem? Let’s fix!

  1. Mobile test case execution is failing on ADO: To execute mobile test case successfully on ADO, you need to provide all the mobile capabilities manually.
    Here is the list of required capabilities in ADO Pipeline.

Capability Name

Values (As per execution needs)

MobilePlatform

Android

MobileBrowser

Chrome

MobileExecutionEnvironment

Local

AppiumServerURL

http://127.0.0.1:4723/

androidAppiumServerURL

http://127.0.0.1:4723/

android.platformName

android

android.browserName

chrome

android.appium:udid

emulator-5558

android.appium:deviceName

Pixel_3a_XL_API_34

android.appium:automationName

UiAutomator2

appiumOption

Custom/Automatic

androidAppiumOption

Custom/Automatic

Follow the below steps to add capabilities:

  1. Go to ADO.

  2. Edit the pipeline.

  3. Click three dots next to Enter environment variables.

  4. Add capabilities & their values from the above table.

  5. Click OK.

  6. Save the pipeline.

    image-20240919-073926.pngImage Added