Context
You should not use an administrator account (a user with administrator system groups) when testing or participating in user processes or functional features.
Administrator accounts are designed for system configuration and administrative tasks. When used for functional testing or participating in user processes (for example, handling tickets or changing reservations), they can produce misleading or incorrect results because their permissions and behavior differ from those of regular users.
Why testing with an administrator account can cause issues
Administrator users typically have:
- Additional permissions and overrides
- Access to configuration and management functions
- Extended visibility of tasks or workflow options
- Different system behavior compared to regular users
As a result, workflows may behave differently than they would for a standard user. This can lead to inaccurate test outcomes and incorrectly reported issues.
Correct way to test user processes
When testing functional processes:
- Use a dedicated test user
- Take over an existing user account
- Ensure the account only has the access rights relevant to the scenario
This ensures:
- Accurate workflow behavior
- Correct page visibility
- Reliable validation of access
- Representative test results
Intended use of administrator accounts
Administrator accounts should only be used for:
- System configuration
- Module and workflow settings
- Data corrections
- Technical and administrative management
They are not intended for validating functional end-user processes.