Skip to content

Conversation

@mepr1
Copy link

@mepr1 mepr1 commented May 14, 2025

Description

New POM for the diagnostic test outcome page

Context

Allowing for the locators in this page to be reused

Type of changes

  • [ x] Refactoring (non-breaking change)
  • [x ] 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

  • [ x] I am familiar with the contributing guidelines
  • [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) 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.

@mepr1 mepr1 requested a review from a team May 14, 2025 12:09
@mepr1 mepr1 added the enhancement New feature or request label May 14, 2025
…tcome-page

# Conflicts:
#	tests/smokescreen/test_compartment_6.py
@sonarqubecloud
Copy link

@mepr1 mepr1 merged commit 7f5f78a into main May 14, 2025
10 checks passed
@mepr1 mepr1 deleted the feature/BCSS-20477-c6-pom-diagnostic-test-outcome-page branch May 14, 2025 16:39
Andyg79 pushed a commit that referenced this pull request May 14, 2025
<!-- markdownlint-disable-next-line first-line-heading -->
## Description

New POM for the  diagnostic test outcome page

## Context
Allowing for the locators in this page to be reused

## Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [ x] Refactoring (non-breaking change)
- [x ] 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.

---------

Co-authored-by: Dave Harding <35965578+davethepunkyone@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants