Features / Test environments
Create test identities for end-to-end automation and load testing with an explicit lifecycle and safe operational boundaries.
Explore the design intent, review practical decisions and validate exact behavior against your deployed configuration.
Why it matters
Test accounts can accumulate indefinitely, receive real notifications or accidentally gain privileged status if they share the production user model without clear classification.
Design intent
Enable test-user behavior deliberately, configure deletion timing and test email domains, and keep OTP retrieval available only through controlled administrative test mechanisms. Test users should not become administrators.
Worked scenario
A CI run creates a test identity under a designated domain, reads the test OTP through the supported administrative path and allows the identity to expire automatically.
Boundary to verify
Confirm enforcement at the relevant server, API, resource or operational decision point. A hidden button or an informative dashboard is not, by itself, an authorization control.
Practical path
Use these stages as a review guide. Exact settings and enforcement points depend on the configured deployment and connected systems.
Identify the actor, target resource and operation that test users is meant to govern.
Enable test-user behavior deliberately, configure deletion timing and test email domains, and keep OTP retrieval available only through controlled administrative test mechanisms. Test users should not become administrators.
A CI run creates a test identity under a designated domain, reads the test OTP through the supported administrative path and allows the identity to expire automatically. Also test the path that should be denied, deferred or sent for review.
Check that the resulting state is understandable and that the decision can be investigated later. For audit-enabled operations, confirm the relevant actor and context are captured.
Before rollout
A capability is easier to operate when ownership, failure behavior and verification are defined upfront.
This page describes a design approach based on WebFrolic’s documented product model. Verify feature availability and exact behavior in your environment before relying on it for a control requirement.
Related capabilities
Follow the related areas to understand how this capability fits within identity, access, lifecycle and operations.
Evaluate with your scenario
Share the identities, resource boundary and decision you want to test. The walkthrough can focus on the relevant behavior rather than a generic feature tour.
