Testing Guideline

Testing Strategy

This is to still be agreed on as of writing this

Testing your code is crucial for ensuring its reliability and functionality.

Generally when testing we'd like to see:

• that everything meets the requirements that guided its design and development
• it responds correctly to different kinds of inputs
• performs its functions within a resonable amount of time
• is usable enough (for time being)
• can be installed and run in its intended envs

Testing our own Platform

yarn test 

Or to run the tests without the e2e running:

yarn backstage-cli repo test

If it works

git add --all
git commit -m "ADD: <What has been added>"

git push

And then at your GitHub for https://github.com/codeuniversity/code-idp click Create pull request.

Integrating Testing into CI/CD

• Automated Test Execution: All commits to branches trigger automated unit and integration tests to ensure new changes meet baseline quality before code review.
• Test Review as Part of Code Review: During pull requests, reviewers also have to check the over the tests. Are the new features sufficiently covered? Can any tests be improved or extended?
• Test Coverage Improvement: Review test coverage reports as a team to identify areas where coverage can be improved. This can help us maintain and enhance the robustness of our repo.