Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 52

Update smoke-tests.md (#15004)

Browse source 
Adding MDM-specific smoke tests to pre-release smoke testing.
This commit is contained in:
Sabrina Coy 2023-11-10 14:33:46 -05:00 committed by GitHub
parent a0d5d55dfa
commit b3f5c17796
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
.github/ISSUE_TEMPLATE/smoke-tests.md vendored
View file

@ -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
</td><td>pass/fail</td></tr>
<tr><td>MDM Smoke Tests</td><td>Verify MDM enrollments, run commands, and script execution</td><td>
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.
</td><td>pass/fail</td></tr>
<tr><td>Migration Test</td><td>Verify Fleet can migrate to the next version with no issues.</td><td>
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.
</td><td>pass/fail</td></tr>
<tr><td>Release blockers</td><td>Verify there are no outstanding release blocking tickets.</td><td>
1. Check [this](https://github.com/fleetdm/fleet/labels/~release%20blocker) filter to view all open `~release blocker` tickets.