Test users

Used by the application in automated processes

eRegulations has test users with different roles are used by the application, for example in a unit test. These users, and their properties, including whether they are active, should not be modified.

• root user (username is randomly generated; if doing any work with existing users and the name isn't clear, ask the dev team which one this is)

  • Group: EREGS_ADMIN
  • Active: checked
  • Staff status: checked
  • Superuser status: checked
  • How it is used by the application: to verify that it can detect administrative elements on the page, and to verify internal link and file behavior

• reader_user

  • Group: EREGS_READER
  • Active: checked
  • Staff status: checked
  • Superuser status: unchecked
  • How it is used by the application: to verify that it cannot detect administrative elements on the page

Used for manual testing by team members

To test functionality within eRegulations – for example, to ensure that an editor cannot access elements that only a manager should access – create (or activate, if one already exists) a user in that group and generate a new password for it. Use a password generator to make a secure password.

Use the change password screen within the Django admin to set a new password for the temporary user if it is an existing user. Log in with those credentials in a new session. Use that session to test the functionality in question for that user group.

Deactivate the user in the Django admin when testing is completed.