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.
Add testRigor End-to-End Tests and CI Integration
This PR introduces a new set of end-to-end (E2E) tests powered by testRigor.
Example of a run with the tests included on this pull request:
https://app.testrigor.com/test-suites/fZ9vEeN353zJeAWRu/runs/FWZ69SPqpXrhqW9wP
Requirements for this PR to be merged:
Include the environment variable/secret SUITE_ID and CI_TOKEN into the upstream repository.
This can be done by:
Set up a new Open Source account for OrangeHRM
ORANGEHRM_TEST_SUITE_ID
presented on the test suite URL as a repository variable in GitHubORANGEHRM_AUTH_TOKEN
from the fieldauth-token
on the CI/CD Integration tab ( /ci or click the "CI/CD Integration" button )ORANGEHRM_AUTH_TOKEN
as a repository secret in GitHubOR
I can share the token for the current suite used to test this pull request with OrangeHRM manteiners.
Why testRigor?
Open Source projects thrive when contributors can easily verify changes and ensure nothing breaks. testRigor offers advantages that are particularly valuable for a community-driven project like OrangeHRM:
Natural language test cases: Anyone can contribute automated tests without any language-specific coding skills, broadening the contributor base and allowing a higher test coverage.
Reduced maintenance overhead: Tests are resilient to UI changes, lowering the cost of keeping the suite up to date.
Cross-platform coverage: Support across different environments and setups such as mobile, desktop and web.
Faster feedback loop: Catch issues earlier in PRs and maintain higher project stability.