Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: run k6 tests regardless if previous jobs skipped #665

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

arealmaas
Copy link
Collaborator

Description

  • To ensure the tests are run regardless of if the previous jobs have been skipped, we add the same logic as for deploying apps.
  • Ensure tests are run only if backend code has been changes

Related Issue(s)

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)
  • Relevant automated test added (if you find this hard, leave it and we'll help out)

Documentation

  • Documentation is updated (either in docs-directory, Altinnpedia or a separate linked PR in altinn-studio-docs., if applicable)

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@arealmaas arealmaas merged commit 9713ea7 into main Apr 22, 2024
14 checks passed
@arealmaas arealmaas deleted the ci/run-k6-tests-regardless-of-skipped-jobs branch April 22, 2024 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants