diff --git a/.github/ISSUE_TEMPLATE/smoke-tests.md b/.github/ISSUE_TEMPLATE/smoke-tests.md index 127d7b1484..979e97fa00 100644 --- a/.github/ISSUE_TEMPLATE/smoke-tests.md +++ b/.github/ISSUE_TEMPLATE/smoke-tests.md @@ -7,7 +7,7 @@ assignees: '' --- -# Goal: easy-to-follow test steps for sanity checking a release manually +# Goal: easy-to-follow test steps for checking a release manually **Fleet version** (Head to the "My account" page in the Fleet UI or run `fleetctl version`): @@ -22,7 +22,7 @@ assignees: '' # Smoke Tests -Smoke tests are limited to core functionality and serve as a sanity test. If smoke tests are failing, a release cannot proceed. +Smoke tests are limited to core functionality and serve as a pre-release final review. If smoke tests are failing, a release cannot proceed. ## Prerequisites @@ -68,13 +68,22 @@ Smoke tests are limited to core functionality and serve as a sanity test. If smo 4. Warning and informational modals show when expected and make sense pass/fail +MDM Smoke TestsVerify MDM enrollments, run commands, and script execution + +1. Erase an ADE-eligible macOS host and verify able to complete auomated enrollment flow. +2. With Windows MDM turned On, enroll a Windows host and verify MDM is turned On for the host. +3. Verify able to run a script on all host types from CLI. +4. Verify scripts library upload/download/delete, run from Host details. +5. Verify able to run MDM commands on both macOS and Windows hosts from the CLI. +pass/fail + Migration TestVerify Fleet can migrate to the next version with no issues. Using the migration scripts located in fleet/test/upgrade/ 1. Run the upgrade_test.go script using the most recent stable version of Fleet and `main`. 2. Upgrade test returns an 'OK' response. pass/fail - + Release blockersVerify there are no outstanding release blocking tickets. 1. Check [this](https://github.com/fleetdm/fleet/labels/~release%20blocker) filter to view all open `~release blocker` tickets.