You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- markdownlint-disable-next-line first-line-heading -->
## Description
<!-- Describe your changes in detail. -->
Refactoring users.json to include the organisation for the primary key,
e.g. - "Hub Manager State Registered at BCS01"
## Context
This makes it easier to identify exactly which user is being used per
test.
<!-- Why is this change required? What problem does it solve? -->
## Type of changes
This was done followed by Kate comments during playwright demo and it
will be helpful to recognise the users when we add more.
<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->
- [x ] Refactoring (non-breaking change)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)
## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ x] I am familiar with the [contributing
guidelines](https://github.com/nhs-england-tools/playwright-python-blueprint/blob/main/CONTRIBUTING.md)
- [x ] I have followed the code style of the project
- [ ] I have added tests to cover my changes (where appropriate)
- [ ] I have updated the documentation accordingly
- [ ] This PR is a result of pair or mob programming
---
## Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others
privacy, we kindly ask you to NOT including [PII (Personal Identifiable
Information) / PID (Personal Identifiable
Data)](https://digital.nhs.uk/data-and-information/keeping-data-safe-and-benefitting-the-public)
or any other sensitive data in this PR (Pull Request) and the codebase
changes. We will remove any PR that do contain any sensitive
information. We really appreciate your cooperation in this matter.
- [x ] I confirm that neither PII/PID nor sensitive data are included in
this PR and the codebase changes.
It then checks that the status of the subject is as expected using the subject screening summary page
47
47
Then it process two batches performing checks on the subjects to ensure they always have the correct event status
48
48
"""
49
-
UserTools.user_login(page, "Hub Manager State Registered")
49
+
UserTools.user_login(page, "Hub Manager State Registered at BCS01")
50
50
51
51
# Find data , separate it into normal and abnormal, Add results to the test records in the KIT_QUEUE table (i.e. mimic receiving results from the middleware)
0 commit comments