Adding Acceptance Tests
ADR: osdu/platform/ci-cd-pipelines#49
- Created a new module
register-acceptance-test - Copy over core test cases to new project
- Made test classes
finalforbidding overrides. - Decouple provider modules from a core-test module. (By moving the refactored module to a new folder)
- Added a common, standards-based configuration for token issuing. (OIDC and direct token injection)
- Added new
acceptancejob.
Edited by Rustam Lotsmanenko (EPAM)
Merge request reports
Activity
changed milestone to %M25 - Release 0.28
added MRTesting Platform Standardization labels
requested review from @Rustam_Lotsmanenko
assigned to @vihar.mamania
added 5 commits
-
7bb867b2...4d0f8d67 - 2 commits from branch
master - bd421f9b - Adding Acceptance Tests
- 3305bf9a - Adding Acceptance Tests
- 3d47aa50 - Updating README.md
Toggle commit list-
7bb867b2...4d0f8d67 - 2 commits from branch
- Resolved by Lauren Datz
Can we please link the associated ADR? Is it this one? osdu/platform/ci-cd-pipelines#49
- Last reply by Rustam Lotsmanenko (EPAM)
- Resolved by Vihar Mamania
Hello, could we alter the token naming to the following format? AWS would propose the following changes: rename ADMIN_TOKEN=>PRIVILEGED_USER_TOKEN and rename NO_ACCESS_TOKEN=>NO_ACCESS_USER_TOKEN. This would be consistent with the token naming convention as in the following services: os-storage, os-secret, os-legal, os-file, os-entitlements. Example with storage: storage!952 (diffs)
- Last reply by Vihar Mamania
reset approvals from @wbevans_ms by pushing to the branch
Please register or sign in to reply