gitlab-org--gitlab-foss/doc/ci/test_cases/index.md

3.1 KiB

stage group info description type
Plan Certify To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments Test cases in GitLab can help your teams create testing scenarios in their existing development platform. reference

Test Cases (ULTIMATE)

Test cases in GitLab can help your teams create testing scenarios in their existing development platform.

This can help the Implementation and Testing teams collaborate, because they no longer have to use external test planning tools, which require additional overhead, context switching, and expense.

Create a test case

To create a test case in a GitLab project:

  1. Navigate to CI/CD > Test Cases.
  2. Select the New test case button. You are taken to the new test case form. Here you can enter the new case's title, description, attach a file, and assign labels.
  3. Select the Submit test case button. You are taken to view the new test case.

View a test case

You can view all test cases in the project in the Test Cases list. Filter the issue list with a search query, including labels or the test case's title.

Test case list page

To view a test case:

  1. In a project, navigate to CI/CD > Test Cases.
  2. Select the title of the test case you want to view. You are taken to the test case page.

An example test case page

Archive a test case

When you want to stop using a test case, you can archive it. You can reopen an archived test case later.

To archive a test case, on the test case's page, select the Archive test case button.

To view archived test cases:

  1. Navigate to CI/CD > Test Cases.
  2. Select Archived.

Reopen an archived test case

If you decide to start using an archived test case again, you can reopen it.

To reopen an archived test case, on the test case's page, select the Reopen test case button.

Enable or disable Test Cases (ULTIMATE ONLY)

The GitLab Test Cases feature is under development but ready for production use. It is deployed behind a feature flag that is enabled by default. GitLab administrators with access to the GitLab Rails console can opt to disable it.

To enable it:

Feature.enable(:quality_test_cases, Project.find_by_full_path('<project_path>'))

To disable it:

Feature.disable(:quality_test_cases, Project.find_by_full_path('<project_path>'))