SSO Button Gets Randomized IDs
Med.AuthLocators
Mission
- Incident
Randomized auth controls break smoke coverage exactly where release teams need confidence most: login
- Goal
Complete the SSO launch flow using resilient semantics rather than CSS or internal IDs
- Pass condition
Use the real SSO primary action, not troubleshoot or backup controls
What counts
- Use the real SSO primary action, not troubleshoot or backup controls
- Prove lifecycle completion with status text reaching done
- the workspace success panel appears after authentication
Constraints2 rules + 1 mutation note
Rules
- Do not rely on volatile token text or position-based selectors
- Do not treat the help panel as a completion signal
Mutation
- Primary label and slot can move between baseline and mutated variants
Hint 1
Action: Use the real SSO primary action, not troubleshoot or backup controls.
Hint 2
Assertion: Prove lifecycle completion with status text reaching done.
Hint 3
Assertion: Assert the workspace success panel appears after authentication.