From 5ef68b382045893a07cb8f1a0d9224c30f4903dc Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Mon, 10 Jun 2024 16:53:13 -0400 Subject: [PATCH] Release QA issue template - Add section for testing the [default migration workflow](https://fleetdm.com/docs/using-fleet/mdm-migration-guide#default-workflow) for macOS hosts. Discussed w/ @georgekarrv that we may have caught the following bug if we were testing the migration workflow each release: #19512 We also thought it was a good idea to make this part of release QA in case the flow breaks w/ a never version of macOS. --- .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 66d6bd14e3ea..339341500f43 100644 --- a/.github/ISSUE_TEMPLATE/release-qa.md +++ b/.github/ISSUE_TEMPLATE/release-qa.md @@ -99,6 +99,12 @@ Smoke tests are limited to core functionality and serve as a pre-release final r 3. Verify able to run MDM commands on both macOS and Windows hosts from the CLI. pass/fail +MDM migration flowVerify MDM enrollments, run MDM commands + +1. Turn off MDM on an ADE-eligible macOS host and verify that the native, "Device Enrollment" macOS notification appears. +2. Follow the "Turn on MDM" instructions and verify that MDM is turned on. +pass/fail + ScriptsVerify script library and execution 1. Verify able to run a script on all host types from CLI.