Now it is time to test the code you have added. Since there will be a variety of codebase structures across the entire class, the specific requirements for this stage are minimal. But you must, as a group, write tests for each of the implemented functions/features that you added in the previous phase. These tests should be integrated into the existing test suite from the template codebase. You should document these in either the testing/README.md file or with comments in the test files themselves. After this, another group member should review your tests and make sure they are correct and complete. Create a subdirectory called reviews inside the testing directory and document the review process there. Each group member should create their own file in this directory with their name as the filename. In this file, document which tests you reviewed, when you reviewed them, and any comments or concerns you have about them.
Everything in your codebase should be tested by the end of this project, but it is likely that the implementations you had hoped to finish by now still need some work. Test the features you can, and keep coding! This iterative, complicated process is a part of software development. Reach out to the TAs if you're struggling with implementations.
- On Canvas, submit the following:
- the URL to your group's repository