Tests that require a login

This article applies to: UserTesting 

On this page:

• About tests that require a login
• Managing participant login strategies
• Best practices for unmoderated tests

About tests that require a login

• When your test material is password-protected, each participant will need to log in.
• Consider if:
  • All participants can use the same password
  • You need to change the password after the test to maintain security
  • Participants need their own unique password 

Managing participant login strategies

Here are four strategies to manage unique logins effectively:

Run one session at a time

• Launch a Live Conversation session or a recorded test for one participant at a time.
• After each session, reset the account or edit the credentials before moving on to the next participant.
• This approach ensures all data is consolidated in one place but may extend the time needed to complete the testing.

Conduct multiple one-person tests

• Create a separate test for each participant.
• Start by creating the initial test, then make copies for additional participants, updating the login credentials in each copy.
• This method allows all participants to complete the test simultaneously, speeding up the process, though it does spread your data across multiple tests.

Use a tracking sheet

• Provide participants with access to an editable online spreadsheet or document containing the available login credentials.
• Instruct them to mark the credentials they use, ensuring others know which ones are still available.
• For mobile tests, participants will need the Google Sheets app to make edits.

Implement a login generator

• Create a tool that automatically assigns the next available credentials to each new participant.
• This method is efficient and reduces errors but may require engineering support to develop, depending on your resources.
  
  
   

Best practices for unmoderated tests

For unmoderated tests, we recommend providing login credentials in a dedicated task instead of only in the scenario text. This makes credentials easier for participants to reference and reduces the chance they’ll be missed.

Recommended flow

1. Use the scenario to explain the context of the test.
2. Add a separate task before the login step with:
   • Username/email
   • Password
   • Any additional login instructions
3. Ask participants to confirm they successfully logged in before continuing.

Example

Scenario: 
Imagine you are reviewing your recent account activity in your online bankinig portal.

Task:
Please log in using the credentials below:

• Username: testuser01@example.com
• Password: ExamplePassword123

Additional considerations

• Update shared passwords after the test ends.
• For unique credentials, consider using a tracking sheet or login generator.

Related content