From 27d8f8ee4bbd7f1ae44ef9aed85f72ec0f339b87 Mon Sep 17 00:00:00 2001 From: Janis Watts <184028114+jmwatts@users.noreply.github.com> Date: Sat, 8 Feb 2025 23:17:57 -0600 Subject: [PATCH] Update release-qa.md with load test expectations (#26181) --- .github/ISSUE_TEMPLATE/release-qa.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/release-qa.md b/.github/ISSUE_TEMPLATE/release-qa.md index 7c13dcf3d3..dce9a641d8 100644 --- a/.github/ISSUE_TEMPLATE/release-qa.md +++ b/.github/ISSUE_TEMPLATE/release-qa.md @@ -197,6 +197,12 @@ Using the migration scripts located in fleet/test/upgrade/ 1. Check [this](https://github.com/fleetdm/fleet/labels/~release%20blocker) filter to view all open `~release blocker` tickets. 2. If any are found raise an alarm in the `#help-engineering` and `#g-mdm` (or `#g-endpoint-ops`) channels. +pass/fail +Load TestsVerify all load test metrics are within acceptable range on final build of RC. + +1. Check [this Google doc](https://docs.google.com/document/d/1V6QtFzcGDsLnn2PIvGin74DAxdAN_3likjxSssOMMQI/edit?tab=t.0#heading=h.15acjob4ji20) to review load test key metrics and checks. +2. After all expected changes have been merged to the RC branch, set up a load test environment and allow it at least 24hrs of run time. +3. Record metrics in [this spreadsheet](https://docs.google.com/spreadsheets/d/1FOF0ykFVoZ7DJSTfrveip0olfyRQsY9oT1uXCCZmuKc/edit?usp=drive_link) for the load test run. pass/fail