Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

For background see

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLIO-3218
.

...

The setup-users.feature in the folio-integration-tests repo is run before every integration testing sub-project, since most integration tests need an authenticated user. Two routes from mod-login are used by the setup-users.feature: authn/credentials (to create the test user) and authn/login (to login the test user). However, this existing usage of these /authn routes isn't really designed to test mod-login directly. Because of this mod-login is a good candidate for its own integration-style tests. Routes like authn/reset-password and authn/update should have their own integration test coverage (since they currently do not have coverage), and routes like authn/credentials and authn/login should be used to test with user credential creation and updating.

A flow like the following would represent a complete set of integration tests for mod-login:

  1. Create a new user and give that new user credentials by calling authn/credentials
  2. Log in the new test user with authn/login
  3. Reset the user's password with authn/reset-password
  4. Login using the new password
  5. Update the user's username with authn/update
  6. Login using the new username
  7. Delete the new user and ensure that deletion succeeded