-
Notifications
You must be signed in to change notification settings - Fork 7
Team‐1 Testing Plan
This wiki page outlines the testing procedures followed by team 1 in order to write robust code.
-
Where possible, every new class should have a set of unit tests which aim to have complete code coverage. In the case where this is not possible, this step may be skipped.
-
Actually running the program and testing the new feature manually. While this may not test every edge case quickly, it ensures the new code does not break the build and performs the intended functionality.
-
Create a PR for major changes to the team's feature branch. With at least 2 additional reviewers, it is less likely any bugs or code quality issues will be merged in undetected.
While there are a few instances that step 1 cannot be completed, continuing with steps 2 and 3 ensure the team maintains a high code quality.