Skip to content
Snippets Groups Projects

Update QA specs for Run Pipeline form

Merged Mireya Andres requested to merge update-run-pipeline-qa into master
All threads resolved!

What does this MR do and why?

Updates QA tests to address the following issues:

Screenshots or screen recordings

N/A

How to set up and validate locally

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Mireya Andres

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Mireya Andres changed milestone to %15.6

    changed milestone to %15.6

  • assigned to @mgandres

  • 1 Message
    :book: CHANGELOG missing:

    If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog.

    If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message.

    If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

    Reviewer roulette

    Changes that require review have been detected!

    Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

    Category Reviewer Maintainer
    QA Harsha Muralidhar current availability (@hmuralidhar) (UTC+5.5, 2.5 hours behind @mgandres) Maintainer review is optional for QA
    test for spec/features/* Sam Figueroa current availability (@sam.figueroa) (UTC+0, 8 hours behind @mgandres) Maintainer review is optional for test for spec/features/*

    To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

    To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

    Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

    If needed, you can retry the :repeat: danger-review job that generated this comment.

    Generated by :no_entry_sign: Danger

  • Allure report

    allure-report-publisher generated test report!

    e2e-review-qa: :white_check_mark: test report for 40aee6a0

    expand test summary
    +-----------------------------------------------------------------------------------------+
    |                                     suites summary                                      |
    +------------------------------------+--------+--------+---------+-------+-------+--------+
    |                                    | passed | failed | skipped | flaky | total | result |
    +------------------------------------+--------+--------+---------+-------+-------+--------+
    | Manage                             | 43     | 0      | 3       | 0     | 46    | ✅     |
    | Plan                               | 49     | 0      | 1       | 0     | 50    | ✅     |
    | Govern                             | 10     | 0      | 5       | 0     | 15    | ✅     |
    | Create                             | 28     | 0      | 1       | 0     | 29    | ✅     |
    | Configure                          | 0      | 0      | 1       | 0     | 1     | ➖     |
    | Verify                             | 12     | 0      | 1       | 0     | 13    | ✅     |
    | Feature flag handler sanity checks | 9      | 0      | 0       | 0     | 9     | ✅     |
    | Version sanity check               | 0      | 0      | 1       | 0     | 1     | ➖     |
    | Package                            | 0      | 0      | 1       | 0     | 1     | ➖     |
    +------------------------------------+--------+--------+---------+-------+-------+--------+
    | Total                              | 151    | 0      | 14      | 0     | 165   | ✅     |
    +------------------------------------+--------+--------+---------+-------+-------+--------+

    e2e-package-and-test: :x: test report for 40aee6a0

    expand test summary
    +---------------------------------------------------------------------------+
    |                              suites summary                               |
    +----------------------+--------+--------+---------+-------+-------+--------+
    |                      | passed | failed | skipped | flaky | total | result |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Plan                 | 312    | 0      | 0       | 0     | 312   | ✅     |
    | Verify               | 219    | 0      | 42      | 0     | 261   | ✅     |
    | Create               | 822    | 1      | 27      | 0     | 850   | ❌     |
    | Manage               | 364    | 0      | 65      | 0     | 429   | ✅     |
    | Package              | 144    | 0      | 37      | 0     | 181   | ✅     |
    | Govern               | 209    | 0      | 0       | 0     | 209   | ✅     |
    | Configure            | 1      | 0      | 15      | 0     | 16    | ✅     |
    | Analytics            | 11     | 0      | 0       | 0     | 11    | ✅     |
    | Fulfillment          | 10     | 0      | 75      | 0     | 85    | ✅     |
    | GitLab Metrics       | 2      | 0      | 1       | 0     | 3     | ✅     |
    | ModelOps             | 0      | 0      | 5       | 0     | 5     | ➖     |
    | Systems              | 3      | 0      | 0       | 0     | 3     | ✅     |
    | Release              | 25     | 0      | 0       | 0     | 25    | ✅     |
    | Data Stores          | 12     | 0      | 1       | 0     | 13    | ✅     |
    | Secure               | 34     | 1      | 5       | 0     | 40    | ❌     |
    | Version sanity check | 0      | 0      | 7       | 0     | 7     | ➖     |
    +----------------------+--------+--------+---------+-------+-------+--------+
    | Total                | 2168   | 2      | 280     | 0     | 2450  | ❌     |
    +----------------------+--------+--------+---------+-------+-------+--------+
  • Mireya Andres added 102 commits

    added 102 commits

    Compare with previous version

  • Mireya Andres added 1 commit

    added 1 commit

    • 78473c06 - Update QA specs for Run Pipeline form

    Compare with previous version

  • Mireya Andres changed the description

    changed the description

  • Mireya Andres
  • Mireya Andres requested review from @treagitlab

    requested review from @treagitlab

  • Tiffany Rea
  • Mireya Andres added 1 commit

    added 1 commit

    • 3edf1bb4 - Link testcases and change FF scope to :project

    Compare with previous version

  • Mireya Andres added 1 commit

    added 1 commit

    • d3f1a212 - Link testcases and change FF scope to :project

    Compare with previous version

  • Mireya Andres added 1 commit

    added 1 commit

    • 211c3da4 - Link testcases and change FF scope to :project

    Compare with previous version

  • Mireya Andres added 1 commit

    added 1 commit

    • 6056b661 - Cosmetic touchup to keep code style consistent

    Compare with previous version

  • mentioned in issue #381233 (closed)

  • Mireya Andres added 1364 commits

    added 1364 commits

    • 6056b661...5693766d - 1360 commits from branch master
    • 25fb583d - Update QA specs for Run Pipeline form
    • d028f1b9 - Link testcases and change FF scope to :project
    • 9cf429ff - Cosmetic touchup to keep code style consistent
    • b5f38b10 - Link issue to discuss how to deal with cache implementation

    Compare with previous version

  • Tiffany Rea approved this merge request

    approved this merge request

  • :wave: @treagitlab, thanks for approving this merge request.

    This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.

    For more info, please refer to the following links:

  • 🤖 GitLab Bot 🤖 added 1 deleted label

    added 1 deleted label

  • Tiffany Rea requested review from @chloeliu

    requested review from @chloeliu

  • mentioned in issue #363660 (closed)

  • Chloe Liu
  • Chloe Liu
  • Chloe Liu
  • Chloe Liu
  • Chloe Liu
  • Chloe Liu
  • Chloe Liu removed review request for @chloeliu

    removed review request for @chloeliu

  • Mireya Andres added 432 commits

    added 432 commits

    • b5f38b10...acaed280 - 427 commits from branch master
    • c5fd8570 - Update QA specs for Run Pipeline form
    • d9b47958 - Link testcases and change FF scope to :project
    • c223d735 - Cosmetic touchup to keep code style consistent
    • 75722edf - Link issue to discuss how to deal with cache implementation
    • 40aee6a0 - Disable FF in before block when testing with FF disabled context

    Compare with previous version

  • Mireya Andres requested review from @chloeliu

    requested review from @chloeliu

  • Chloe Liu approved this merge request

    approved this merge request

  • Chloe Liu resolved all threads

    resolved all threads

  • merged

  • @chloeliu, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline finished more than 2 hours ago, you should:

    1. Ensure the merge request is not in Draft status.
    2. Start a pipeline (especially important for Community contribution merge requests).
    3. Set the merge request to merge when pipeline succeeds.

    This is a guideline, not a rule. Please consider replying to this comment for transparency.

    This message was generated automatically. You're welcome to improve it.

  • Chloe Liu mentioned in commit a11d41aa

    mentioned in commit a11d41aa

  • mentioned in issue #372310 (closed)

  • added workflowstaging label and removed workflowcanary label

  • mentioned in issue #375552 (closed)

  • Rémy Coutable mentioned in merge request !104379 (merged)

    mentioned in merge request !104379 (merged)

  • mentioned in issue #378250 (closed)

  • mentioned in issue #378249 (closed)

  • Please register or sign in to reply
    Loading