Skip to content

Release QA template: progress checkboxes, drop pass/fail column, update loadtesting instructions#48312

Merged
AndreyKizimenko merged 2 commits into
mainfrom
release-qa-progress-checkboxes
Jun 29, 2026
Merged

Release QA template: progress checkboxes, drop pass/fail column, update loadtesting instructions#48312
AndreyKizimenko merged 2 commits into
mainfrom
release-qa-progress-checkboxes

Conversation

@AndreyKizimenko

@AndreyKizimenko AndreyKizimenko commented Jun 25, 2026

Copy link
Copy Markdown
Member

Related issue: N/A — internal release-QA issue template update

Description

Updates the Release QA issue template (.github/ISSUE_TEMPLATE/release-qa.md) to match the format already used by the Release QA - fleetd template:

  • Adds a "How to check off" note explaining that testers tick the per-section Progress checkboxes (so GitHub shows the "X of Y tasks" tracker), and record failures under Notes.
  • Adds a Progress checkbox list before each section table (Orchestration, MDM, Power to PC, Software, Security & Compliance, All product groups).
  • Drops the pass/fail column from every table (now 3 columns: Test name / Step instructions / Expected result) and removes the $Name placeholder example row.
  • Splits the single Load tests entry into Baseline loadtest and Migration loadtest rows (and matching checkboxes), and reworks both around the tools/loadtest/metrics/ tooling (see below).

No code or product behavior changes — issue template only.

New load test flow

Both load tests now use the tools/loadtest/metrics/ scripts — collect-metrics.sh (pulls CloudWatch metrics into a .json data file + .md synopsis) and compare-metrics.sh (diffs two runs and flags deltas ok / WARN / ALERT). Condition of satisfaction for each: collect → compare → post the comparison as an issue comment → open a PR with the run artifacts and record results in the metrics spreadsheet.

Baseline loadtest (compared against the previous release, n-1):

  1. Stand up a fresh RC environment (new instance, no data) and run it ~24h.
  2. Collect metrics under the baseline category.
  3. Compare against the previous release (n-1); post the comparison as an issue comment — deltas should be ok.
  4. Open a PR with the run artifacts (.json + .md) under runs/baseline/<workspace>/ and record metrics in the spreadsheet.

Migration loadtest (compared before vs. after the migration):

  1. Run a load test on the previous minor release (n-1); right before migrating, collect the last 2h.
  2. Migrate the environment to the RC (n).
  3. Wait ~2h, then collect the past 2h (symmetric window for an apples-to-apples diff).
  4. Compare post-migration vs. pre-migration; post the comparison as an issue comment — deltas should be ok.
  5. Open a PR with the run artifacts under runs/migration/<workspace>/ and record metrics in the spreadsheet.

Example result PRs this flow produces: #47794 (baseline), #47803 (migration).

Checklist for submitter

  • QA'd all new/changed functionality manually

Match the Release QA - fleetd template format:
- Add a "How to check off" note
- Add per-section Progress checkbox lists
- Drop the pass/fail column and the $Name placeholder row
- Split Load tests into Baseline loadtest and Migration loadtest
Replace the old Google-doc loadtest steps with the collect-metrics.sh /
compare-metrics.sh workflow:
- Baseline: collect under the baseline category, compare against n-1,
  post the comparison as an issue comment, then PR the run artifacts.
- Migration: collect the last 2h on n-1 pre-migration, migrate to the RC,
  wait ~2h, collect the past 2h, compare before vs. after, PR the artifacts.
Both steps link the collect/compare scripts and record results in the sheet.
@AndreyKizimenko AndreyKizimenko marked this pull request as ready for review June 25, 2026 21:49
@fleet-release fleet-release requested a review from ireedy June 25, 2026 21:49

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

Tip: disable this comment in your organization's Code Review settings.

@AndreyKizimenko AndreyKizimenko changed the title Release QA template: progress checkboxes, drop pass/fail column Release QA template: progress checkboxes, drop pass/fail column, update loadtesting instructions Jun 25, 2026
@AndreyKizimenko AndreyKizimenko removed the request for review from ireedy June 25, 2026 21:51
@fleet-release fleet-release requested a review from ireedy June 25, 2026 21:53
@AndreyKizimenko AndreyKizimenko removed the request for review from ireedy June 25, 2026 21:56

@chrstphr84 chrstphr84 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@AndreyKizimenko AndreyKizimenko merged commit 04db6de into main Jun 29, 2026
11 checks passed
@AndreyKizimenko AndreyKizimenko deleted the release-qa-progress-checkboxes branch June 29, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants