Currently there are no (web tests) for testing the state of particular an OIDC/Saml/oauth entity under different conditions. Below is a set-up of a matrix which test must at least be covered for SAML, oauth, and OIDC:
Protocol
Environment
Is published
Is excluded from push
Expected entity status
Should show connection request?
Should show client secret
Should display thank you page
Should display flash message
saml20
prod
yes
yes
requested
yes
no
yes
no
oidc10
prod
yes
yes
requested
yes
yes
yes
no
The idea is to let the PM\'s fill this test matrix. Making a formal statement about the expected behavior when editing, creating, publishing, client secret resetting an entity.
This matrix then can be used in an automated test to verify if the application actually adheres to this behavior. We should already have partial coverage of many of the cases that will end up in the matrix. But having full coverage will be beneficial from a regression point of view.
This issue is imported from pivotal - Originaly created at Feb 16, 2023 by sjaak2
The idea is to let the PM\'s fill this test matrix. Making a formal statement about the expected behavior when editing, creating, publishing, client secret resetting an entity.
This matrix then can be used in an automated test to verify if the application actually adheres to this behavior. We should already have partial coverage of many of the cases that will end up in the matrix. But having full coverage will be beneficial from a regression point of view.