Conversation
…uct-ID and associat… (#123) * changes to update nhsd-application-id to NHSE-Product-ID and associated MV and NBS product ids * datahelper fix..dont convert to lower!
* initial push * initial push * nbs files * All TCs NBS RSV TCs and some amendments to the NHS numbers of the COVID scenarios * All TCs NBS RSV TCs and some amendments to the NHS numbers of the COVID scenarios
allow the consumer mapping config in preprod
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v4...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: adam-wallernhs1 <176666249+adam-wallernhs1@users.noreply.github.com>
Bumps [npm](https://github.com/npm/cli) from 11.6.2 to 11.6.3. - [Release notes](https://github.com/npm/cli/releases) - [Changelog](https://github.com/npm/cli/blob/latest/CHANGELOG.md) - [Commits](npm/cli@v11.6.2...v11.6.3) --- updated-dependencies: - dependency-name: npm dependency-version: 11.6.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: adam-wallernhs1 <176666249+adam-wallernhs1@users.noreply.github.com>
Bumps [asdf-vm/actions](https://github.com/asdf-vm/actions) from 4.0.0 to 4.0.1. - [Release notes](https://github.com/asdf-vm/actions/releases) - [Changelog](https://github.com/asdf-vm/actions/blob/master/CHANGELOG.md) - [Commits](asdf-vm/actions@1902764...b7bcd02) --- updated-dependencies: - dependency-name: asdf-vm/actions dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: eddalmond1 <102675624+eddalmond1@users.noreply.github.com>
| name: Performance Tests | ||
|
|
||
| concurrency: | ||
| group: ${{ github.workflow }} |
There was a problem hiding this comment.
Are we only ever planning to run these tests in preprod? I ask this because if we wanted to run tests in multiple environments at the same time then this concurrency setting would prevent this.
520eac5 to
a08befd
Compare
* Upgrade: [dependabot] - bump boto3 from 1.40.50 to 1.40.62 Bumps [boto3](https://github.com/boto/boto3) from 1.40.50 to 1.40.62. - [Release notes](https://github.com/boto/boto3/releases) - [Commits](boto/boto3@1.40.50...1.40.62) --- updated-dependencies: - dependency-name: boto3 dependency-version: 1.40.62 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> * bugfix - trying to fix ci/cd by pinning node version * bugfix - forcing npm version via make command * bugfix - regenerated lockfile locally * removing unneeded pin --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Edd Almond <102675624+eddalmond1@users.noreply.github.com>
* multiple iterations in a single config * updated the My Vaccines RSV config to v1.2 at their request
… after test runs (#130) * updated make file to include the upload of the integration test configs added the locations of the current int test configs in test_config.py updated upload_configs_to_s3 to allow full file paths in the arguments so the above could be passed * updated make file to include the upload of the integration test configs added the locations of the current int test configs in test_config.py updated upload_configs_to_s3 to allow full file paths in the arguments so the above could be passed * updated make file to include the upload of the integration test configs added the locations of the current int test configs in test_config.py updated upload_configs_to_s3 to allow full file paths in the arguments so the above could be passed * updated the My Vaccines RSV config to v1.2 at their request
Signed-off-by: Karthikeyannhs <174426205+Karthikeyannhs@users.noreply.github.com>
| required: true | ||
| default: "dev" | ||
| github_tag: | ||
| description: 'The github tag to run the test pack from' |
There was a problem hiding this comment.
I'm a bit conflicted on if we should allow performance tests to be run from a different branch to main. Main has at least some sort of version tagging that we could refer back to that would help us identify exactly which version of the performance tests yielded a given result. I guess if you kept the branch around you could still do that but usually we delete branches after merging.
| ref: ${{ inputs.github_tag }} | ||
|
|
||
| # using git commit sha for version of action to ensure we have stable version | ||
| - name: Install asdf |
There was a problem hiding this comment.
Are we using more than just python in this repo - or more specifically in this workflow? If not it might be simpler to just install python directly here
| "tests/performance_tests/locust.py", | ||
| "--headless", | ||
| "-u", | ||
| "10", |
There was a problem hiding this comment.
could we potentially expose these variables - particularly spawn rate and total users - to the workflow dispatch action? We could obviously impose limits on it but would allow us to run different types of tests without changing the code
Summary
Remove items from this list if they are not relevant. Remove this line once this has been done
Details
Add any summary information of what is in the change. Remove this line if you have nothing to add.
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.