fleet/server/mdm/android/tests
Jahziel Villasana-Espinoza eb87048714
34376 android sw gitops (#36595)
<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** Resolves #34376

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.

- [x] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)

## Testing

- [x] Added/updated automated tests
- [x] Where appropriate, [automated tests simulate multiple hosts and
test for host
isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing)
(updates to one hosts's records do not affect another)
- [x] QA'd all new/changed functionality manually

## New Fleet configuration settings

If you didn't check the box above, follow this checklist for
GitOps-enabled settings:

- [x] Verified that the setting is exported via `fleetctl
generate-gitops`
- [x] Verified that the setting is cleared on the server if it is not
supplied in a YAML file (or that it is documented as being optional)
2025-12-05 20:01:57 -05:00
..
enterprise Reduce API Android usage (#36209) 2025-11-25 09:39:06 -03:00
http.go Replace home-made SAML implementation with https://github.com/crewjam/saml (#28486) 2025-07-07 15:13:46 -03:00
integration_software_test.go Android software ingestion (#33826) 2025-10-08 10:24:38 -04:00
README.md Added GET enterprise API endpoint. (#26555) 2025-02-26 10:47:05 -06:00
testing_utils.go 34376 android sw gitops (#36595) 2025-12-05 20:01:57 -05:00

This package contains API Android tests with the real Android service and Android MySQL database.

We use testify Suite to run these tests. Since testify Suite does not support parallel execution, we put each test in their own package/directory. This allows these tests to run in parallel because each package is a separate compile unit. If you create a large test, please put it in a separate file within the same Suite/package.