Breaking: [ELI-262] - Configure-CI/CD-pipeline-for-automated-e2e-testing#44
Merged
seansteberisal merged 54 commits intomainfrom Sep 26, 2025
Conversation
… the role from the role authed in gh actions
…-automated-e2e-testing
…-automated-e2e-testing
…pipeline-for-automated-e2e-testing' into feature/ELI-262-Configure-CI/CD-pipeline-for-automated-e2e-testing
…ss in the environment name. logging level INFO will output to the console by default environment variables once set in github have been removed the .env file is no longer needed and will not work The S3 process no longer uses a prefix, it appears it was not needed. credential_helper.py file deleted because it is no longer used
commented out continue-on-error: true not sure if we need this to fail the build because this is not Behave testing
…v or test Restoration of existing tags will also be included deletion of test_regression_tests.py and test_smoke_tests.py files
…-automated-e2e-testing
…-automated-e2e-testing # Conflicts: # poetry.lock
Contributor
|
This branch is work on a ticket in an NHS England JIRA Project. Here is a handy link to the ticket: |
update README.md remove template .env
…-automated-e2e-testing
removed make run-tests-old command removed unused CONSTANTS removed scope="session" from scenarios params fixture stopped calling delete_all_configs_from_s3() in scenarios params fixture
adam-wallernhs1
approved these changes
Sep 26, 2025
Collaborator
adam-wallernhs1
left a comment
There was a problem hiding this comment.
reviewed with Sean
adam-wallernhs1
approved these changes
Sep 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Details
This pull request includes:
Pull Request Naming
Pull requests should be named using the following format:
Tag can be one of:
Fix- for a bug fix. (Patch release)Update- either for a backwards-compatible enhancement or for a rule change that adds reported problems. (Patch release)New- implemented a new feature. (Minor release)Breaking- for a backwards-incompatible enhancement or feature. (Major release)Docs- changes to documentation only. (Patch release)Build- changes to build process only. (No release)Upgrade- for a dependency upgrade. (Patch release)Chore- for refactoring, adding tests, etc. (anything that isn't user-facing). (Patch release)If the current release is x.y.z then
Correct tagging is necessary for our automated versioning and release process (Release).
The description of your pull request will be used as the commit message for the merge, and also be included in the changelog. Please ensure that your title is sufficiently descriptive.
Rerunning Checks
If you need to rename your pull request, you can restart the checks by either:
git commit --allow-empty -m 'trigger build' git pushRerunning the checks from within the pull request will not use the updated title.