Skip to main content

Create User Research Environment

Background

To aid in the on going user research surrounding the MRLPA paper identity check process in Sirius the user researchers require an ephemeral environment that is deployed using the mock providers so that all identity providers have the same matching data sets. Due to a limitation in the configurability of the various development/testing environments provided by the third party identity providers, we can’t get data that matches between them all for an end to end journey.

We can therefore choose to deploy the mock third party providers used for local development into AWS to give a consistent response state from those external parties. As the mocks are static we also need certain cases to be staged in Sirius and the LPA Store to allow the user journey flow to work. To achieve the Sirius side of this we are using the S3 Environment back up and restore process used for the Training Environments.

Deploying and Setting up the Environment

Creating the User Research Environment with Mocks

  • Run the Create Development Environment Jenkins Job as detailed below.
  • Make sure you select the environment as user-research and check the box that says Use Mock Services

Pick Environment

Select Env

Enable Mocks

Enable Mocks

  • Ensure the job runs successfully to completion.

Restore Sirius Data into the Environment

Restore User Research Environment

Manually Amend LPA Store Data to match Sirius Snapshot

This is currently still a manual step that is sometimes required depending on what prior research has occurred.

  • Log into the AWS Console
  • Switch to operator in the development LPA Store Account
  • Use the search to select DynamoDB in the Console
  • User Tables select deeds-development and then the option to Explore table items
  • Choose to search by Query
  • Enter M-BB4B-E7LX-98AX at the uid and click Run
  • In the results select the uid to open the record in the json editor
  • Expand the donor section
  • If there is an IdentityCheck key, select Remove, then Save and Close, if there is no IdentityCheck key you can just close Edit Deed Record
  • Switch to the changes-development table in the table list
  • Choose to search by Query
  • Enter M-BB4B-E7LX-98AX at the uid and click Run
  • If there is a DONOR_CONFIRM_IDENTITY record, click the tick box next to it and then select Actions and Delete Items, if there is no record you don’t need to do anything Find Changes Record Delete Changes Record
  • Press Delete to confirm when prompted
This page was last reviewed on 8 February 2022. It needs to be reviewed again on 8 March 2022 by the page owner #opg-sirius-develop .
This page was set to be reviewed before 8 March 2022 by the page owner #opg-sirius-develop. This might mean the content is out of date.