Project

General

Profile

Feature #41820

mgr/dashboard: Move QA tests to support running the rados/dashboard QA tests in isolation

Added by Lenz Grimmer 7 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
dashboard/qa
Target version:
% Done:

0%

Source:
Tags:
Backport:
nautilus
Reviewed:
Affected Versions:
Pull request ID:

Description

Currently, the dashboard tests are located in qa/suites/rados/mgr/tasks/dashboard.yaml. In order to make it possible to run the tests in isolation (e.g. using the option -s rados/dashboard), these test should be moved further "upwards" (see the clt-weekly-minutes from 2019-08-21 for the notes)


Related issues

Copied to mgr - Backport #42562: nautilus: mgr/dashboard: Move QA tests to support running the rados/dashboard QA tests in isolation Resolved

History

#1 Updated by Laura Paduano 7 months ago

Lenz Grimmer wrote:

Currently, the dashboard tests are located in qa/suites/rados/mgr/tasks/dashboard.yaml. In order to make it possible to run the tests in isolation (e.g. using the option -s rados/dashboard), these test should be moved further "upwards" (see the clt-weekly-minutes from 2019-08-21 for the notes)

For running dashboard-only tests in Teuthology we have the "--filter dashboard" option, not sure if that is meant with "isolated" or if the "-s" option is something different though).

Edit: Ah, I guess -s rados/dashboard is the same as we use now, only with mgr ("--suite rados/mgr").

#2 Updated by Nathan Cutler 7 months ago

  • Status changed from New to In Progress
  • Assignee set to Nathan Cutler

#3 Updated by Nathan Cutler 7 months ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 30434

#4 Updated by Nathan Cutler 5 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to nautilus

#5 Updated by Nathan Cutler 5 months ago

  • Copied to Backport #42562: nautilus: mgr/dashboard: Move QA tests to support running the rados/dashboard QA tests in isolation added

#6 Updated by Nathan Cutler 5 months ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF