Adobe plugins: engineering QA on real devices (macOS + Windows)

[juan-fdz-hawa]

Related user story

#45414

Task

End-to-end engineering QA of the Adobe plugins feature on real macOS and Windows devices, once the ingestion (#45414 sub-task 1), vulnerability-column (sub-task 2), frontend (sub-task 3), and docs (sub-task 4) work has merged. This is the final gate before the story moves to Awaiting QA.

Setup

• A macOS host and a Windows host, each enrolled in Fleet and running fleetd ≥ v1.56.0 (the release that ships the adobe_plugins table).
• Install Adobe Creative Cloud plus at least one CEP extension and one UXP extension (e.g. from Adobe Exchange) so both extension types appear. Note the plugin name, version, and vendor from each manifest for comparison.
• Optionally install a per-user extension and a system-wide extension to exercise both scopes.

Verify

• Inventory (Software page): each installed Adobe extension appears as a distinct software title with Type "Plugin (Adobe)", the Adobe-plugin icon, the correct version, and an accurate host count. Values match the extension manifests.
• Host details: the same extensions appear on the host's Software card with Type "Plugin (Adobe)" and the correct installed path(s).
• Both platforms: repeat on macOS and Windows; system-wide and per-user extensions both surface.
• Vulnerabilities column: every Adobe plugin row shows ---, because Adobe plugins are excluded from vulnerability scanning (Adobe plugins: exclude from vulnerability scanning #49061). Confirm no Adobe host-app CVE (Photoshop/Acrobat/etc.) is attributed to an extension row: SELECT * FROM software_cve sc JOIN software s ON s.id = sc.software_id WHERE s.source = 'adobe_plugins'; must return zero rows.
• Negative cases: a Linux host reports no adobe_plugins software; a host on an older fleetd without the table logs no query errors; a host with no Adobe plugins shows none.
• Cross-check against the Figma wireframe and the design-QA considerations list (docs/Contributing/guides/ui/design-qa-considerations.md).

Confirm the test plan on the parent story

Complete the parent story's test plan (core flow, UI, edge cases), then add the engineer confirmation comment to #45414.

Condition of satisfaction

• Adobe CEP and UXP extensions installed on real macOS and Windows hosts appear in Fleet inventory with Type "Plugin (Adobe)", the Adobe icon, correct version, and correct host count, on both the Software page and host details.
• The Vulnerabilities column shows --- for every Adobe plugin, with no Adobe host-app CVE attributed to an extension row.
• Linux hosts and hosts on pre-1.56.0 fleetd show no Adobe plugins and log no errors.
• All UI states match the Figma wireframe.
• The parent story (Software inventory: Add Adobe plugins #45414) test plan is completed and the engineer confirmation comment is posted.

[fleet-release]

Adobe plugins shine,
On Windows and macOS, aligned,
In Fleet's design, find peace.