EPIC Goal

As we are supporting the LDAP plugin to ingest users, we need to test all functionality of this plugin extensively to ensure the plugin is reliable for customer use.

Background/Feature Origin

There are many customers currently using this plugin to ingest users, but it is not well tested by RHDH.

Why is this important?

Having good automated test coverage ensures we catch regressions early before they reach customers. 

Manual testing also helps us build a deeper understanding of the plugin, enabling us to efficiently support when issues arise.

User Scenarios

Changes in plugin behaviour are caught in automated tests before customers experience issues. 

Dependencies (internal and external)

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>