Release QA (fleetd):1.59.0

[AndreyKizimenko]

Goal

Easy-to-follow test steps for manually checking the fleetd agent and the bundled osquery (osqueryd) prior to a release.

How to check off: Tick the checkbox in each Progress list as a test passes. GitHub tracks completion ("X of Y tasks") at the top of the issue. The tables below each list hold the step instructions and expected results for reference. For a failure, leave the box unchecked and record the details under Notes.

Important reference data

1. fleetctl preview setup
2. Testing TUF
3. fleetd auto-update n+1 test guide

Release versioning

Includes updates to:

• Orbit: True / False : v1.xx.x > v1.xx.x
• Desktop: True / False : v1.xx.x > v1.xx.x
• osquery: True / False : v1.xx.x > v1.xx.x
• Android: True / False : v1.xx.x > v1.xx.x

Smoke tests

Smoke tests are limited to core functionality and serve as a pre-release final review. If smoke
tests are failing, a release cannot proceed.

Setup: Before running, build a new fleetd from the release candidate branch as needed for Orbit and Desktop (e.g. rc-minor-fleet-v4.80.0). Do not build from main — it is a moving target and changes from future releases may already be merged.

fleetd

Prerequisites

1. Local instance is running and up to date with the target release branch.
2. fleetd is built from the release candidate branch (e.g. rc-minor-fleet-v4.xx.0), not main.
3. Hosts enrolled for macOS, Windows, and Linux.

Progress

• Enrollment & versions
• Fleet Desktop / My device page
• Scripts
• Software
• Auto-updates disabled
• Auto-update n+1
• Self-healing

Test name	Step instructions	Expected result
Enrollment & versions	Verify hosts enroll and report correct component versions.	Hosts can enroll and report the correct version of fleetd (Orbit, osquery, Fleet Desktop) on macOS, Windows, and Linux. Refetching host vitals completes and returns updated information.
Fleet Desktop / My device page	Verify all sections of the end user's My device page load and display correctly.	Clicking the Fleet desktop item, then "My device" successfully loads the My device page. All tabs/sections of the "My device" page (e.g. About, Software, Activity) are populated correctly and as expected. Self-service software items are visible and accessible under the Software tab. Styling and padding appears correct across all sections.
Scripts	Verify script execution via Orbit.	From Host details (macOS, Windows, & Linux) run a script that should PASS, verify. From Host details (macOS, Windows, & Linux) run a script that should FAIL, verify. Verify script results display correctly in Activity feed.
Software	Verify software install via Orbit.	From Host details (macOS, Windows, & Linux) run an install that should PASS, verify. From My Device (macOS, Windows, & Linux) software tab should have self-service items available, verify. Verify software installs display correctly in Activity feed.
Self-healing	Verify Orbit restarts automatically after being stopped.	Stop or kill the Orbit process on a macOS, Windows, and Linux host. Wait and confirm the Orbit process restarts automatically without manual intervention. Confirm the host remains enrolled and visible in Fleet after the restart.
Auto-updates disabled	Verify that fleetd works when the installer package is built with --disable-updates.	Generate package with fleetctl package [...] --updates-disabled. Install packages on macOS, Windows, and Linux. Smoke test Orbit and Fleet Desktop functionality, and osquery tables.
Auto-update n+1	Verify the agent successfully auto-updates to the new release.	Conduct the fleetd auto-update n+1 test. Agent successfully auto-updates. QA certifies new release by commenting in issue.

osquery

Progress

• osquery version
• Live query (report) flow
• osquery tables
• Scheduled queries & log destination
• Packs flow

Test name	Step instructions	Expected result
osquery version	Verify the bundled osquery version.	Host details page reports the expected osqueryd version on macOS, Windows, and Linux, matching the version listed in Release versioning above.
Live query (report) flow	Run a live query against enrolled hosts.	A live query (e.g. SELECT * FROM osquery_info;) runs manually and returns results from macOS, Windows, and Linux hosts. Syntax errors result in error messaging.
osquery tables	Verify common osquery tables return data on each platform.	Query platform-relevant tables (e.g. system_info, os_version, users, processes) and confirm results are populated on macOS, Windows, and Linux.
Scheduled queries & log destination	Verify scheduled query execution and result logging.	Scheduled queries run on host machines and results are logged. osquery result and status logs are successfully sent to the configured log destination (Filesystem or external).
Packs flow	Verify management, operation, and logging of ["2017 packs"](https://fleetdm.com/handbook/company/why-this-way#why-does-fleet-support-query-packs).	Packs successfully run on host machines after migrations. New Packs can be created. Packs can be edited and deleted. Packs results information is logged.

Android

Progress

• App deployment
• Setup experience software
• Software available in Google Play
• Certificate delivery
• Certificate display in app
• Debug mode
• Unenrollment

Test name	Step instructions	Expected result
App deployment	Verify the Fleet Android app is deployed to the device.	The Fleet Android app gets deployed on the device.
Setup experience software	Verify setup experience software is pre-installed during enrollment.	Setup experience software gets pre-installed during the enrollment.
Software available in Google Play	Verify newly added software is available to the end user.	Newly added software is available in Google Play.
Certificate delivery	Verify certificates can be delivered to the device.	Certificates can be delivered.
Certificate display in app	Verify certificates are displayed correctly within the Fleet Android app.	Certificates are displayed correctly within the Fleet Android app.
Debug mode	Verify debug mode can be accessed from the app.	Debug mode can be accessed by tapping the app version 10 times.
Unenrollment	Verify an Android device can be unenrolled from Fleet.	Unenroll the device from the Fleet UI. Confirm the device is removed from the host list in Fleet. Confirm the Fleet Android app is no longer managed on the device.

Notes

What has not been tested:

Include any notes on whether issues should block release or not as needed: