Triggering a test run

Important

This section includes information that is only applicable to Skyline employees.

In this tutorial, you will learn how to trigger a QAOps test run.

Expected duration: 15 minutes.

Prerequisites

• Access to https://qaops-sandbox.skyline.be. This "QAOps Sandbox Environment" environment should be used for every QAOps tutorial.

  Note

  Please contact support.boost@skyline.be to receive a username and password for access to the Sandbox system.

• dotnet 8.0 SDK is required, even if a higher SDK version is already installed.

Overview

• Step 1: Download, install, and verify the QAOps tool

• Step 2: Find the unique test and configuration identifiers

• Step 3: Create a token

• Step 4: Trigger the test run

• Step 5: Verify that the request was received

Step 1: Download, install, and verify the QAOps tool

1. Open a Command Prompt, Bash, or PowerShell window.

2. Check if you have nuget.org as a known NuGet source:

   dotnet nuget list source
   

3. Verify that the output contains nuget.org [Enabled].

   Note

   The first time you run a dotnet command on a computer, you will see a welcome message. The output of your command is displayed below that message.

4. If your sources do not contain nuget.org, add it with the following command. Otherwise, skip this step.

   dotnet nuget add source https://api.nuget.org/v3/index.json -n "nuget.org"
   

5. Install the QAOps tool:

   dotnet tool install skyline.dataminer.qaops --global
   

6. Verify that the tool is available:

   dataminer-qaops --help
   

   The command output will display a description of the tool and the available commands.

Note

If you see the exception "Unable to load the service index for source ...", one of your configured NuGet sources may be unreachable or may have expired credentials.

To continue this tutorial, you can temporarily remove the failing source and add it again later when needed:

dotnet nuget remove source "NameOfSource"

Step 2: Find the unique test and configuration identifiers

1. In the QAOps User app (i.e., the green QAOps app), go to the Configurations page.

2. Select Demo Configuration and Demo Test Suite.

3. Copy the configuration ID and save it in a text file.

4. Copy the test suite ID and save it in a text file.

Step 3: Create a token

1. In the QAOps User app, go to the Tokens page.

2. In the top-left corner, click Create Token .

3. Enter a name for the token.

4. Select the scope that matches the ".execute" scope for your chosen configuration.

5. Click Generate Token.

6. Wait until the token value is shown.

7. Copy the token value and save it in a text file.

   For production environments, use a key vault solution.

Step 4: Trigger the test run

1. Open a Command Prompt, Bash, or PowerShell window.

2. Run the following command, after replacing the placeholders as indicated below, making sure to keep the double quotes around the TOKEN value:

   dataminer-qaops test-run --token "TOKEN" -t TESTSUITE -c CONFIGURATION -tags MYNAME -san saqaopssandbox
   

   • TOKEN: The token value you copied earlier. Make sure this value is enclosed in double quotes.

   • TESTSUITE: The test suite ID you copied earlier.

   • CONFIGURATION: The configuration ID you copied earlier.

   • MYNAME: Your name, nickname, or another identifier that helps you find your request.

   Note

   For production systems, leave out the -san argument. This argument indicates to which QAOps System you want to send commands, in this case the QAOps Sandbox system. The default is the production QAOps system.

Step 5: Verify that the request was received

1. In the QAOps User app, go to the Overview page.

2. Locate your tag in the list.

3. Use the top filter to find your request more quickly.

4. Track the test run life cycle.

To view and interpret the test results, follow the tutorial Viewing test results tutorial.