How to use Access.Claims

Our native solution Access.Claims was developed to enable equal test account distribution among testers. Here we describe how to use it.

Uliana Kruk avatar
Written by Uliana Kruk
Updated over a week ago

What is Access.Claims?

Our native solution access.claims enables our testers to evenly distribute test accounts among themselves that they can use in your testing environment. The solution is meant to ensure that there is only one tester per test account in order to avoid any forced bugs associated with multiple users being active in the same test account.

Our customers can utilize this tool by creating a page with selectable login credentials, so that our testers can 'claim' an account for themselves.

In order to make use of access.claims, you can create a page, copy-paste credentials directly into the page (as we will see in the step-by-step instruction below), and then simply add the link into the test instructions.

Since April 2024 you can also select existing access pages directly in Test IO, when creating or editing a test cycle environment.

Create a new access page - Step-by-Step Instructions

1. Log into https://access.claims/ using the button “sign in with TEST IO”. If you are not logged in yet in the same browser, you will be asked to sign in with your Test IO login data.

Tip: We recommend you always sign in before creating a new page. This will give you the ability to later edit the pages you created and also to share them with your colleagues.

2. Under “New access page” you can create the page.

You will find some setting options:

  • A name will help you to differentiate between different pages.

  • Related TEST IO account dropdown allows you to assign the page to your company's TEST IO account, to share it with your team and to make it directly selectable from the test.io interface

    • All your colleagues with access to the same company TEST IO account will be able to use and adjust the page

    • The page will appear as option when you setup a new test in Test IO

    • The setting also adds extra security measures: Testers can only access this page, while they are doing work for your company's account.

  • For expiration period our recommendation is to set it to "never", so you can reuse the list in future tests without limits

3. Enter the credentials and other information you want to share with the testers.

  • Notes for optional general information about the credential usage is shared and visible to all testers entering the page

  • Credentials can be entered individually line by line. But also copied and pasted directly as a list from a spreadsheet to create multiple credentials as one.

    • On the right side of the website, you will find a short video showing how to copy data from an excel spreadsheet into the credentials field.

Each line of credentials is meant to be used by one tester at a time. Testers will see the credential text only after claiming a line for themselves.

4. After you copy-pasted the data from the excel file into the credentials field, the respective number of credentials will appear as a list (see the screenshot below).

As you can see in the video below, there is no need to create single fields for each credential. Just copy-paste the whole excel row + column selection into the 1st credential field.

5. On the right side you can copy the newly created Access.claims URL to be included in the test instructions of your next test cycle.

Tester Perspective

Testers that enter the access.claims page will see the page name, your notes, and the list of credential lines with hidden information. Each tester will have to claim one credential to be able to read and use it. The testers are asked to release their credential again, when they are done testing.

If you have any questions or need assistance, please do not hesitate to reach out to your dedicated Customer Success Manager or contact our team at [email protected].

Did this answer your question?