https://capstone.cse.sc.edu/milestone/testing/

It's important to note that this milestone is due in two parts: Once on Sunday, January 31, and again on Monday, April 25th.

For this milestone, you will implement and run both unit and behavioral tests. You will likely use third-party libraries and tools for creating and running your unit tests. Typically, the official documentation for your platform will have a section on "Testing" which tells you how they recommend you do automated tests. You will also devise a method for automating some of this testing and making it part of your workflow.

The first part of the milestone requires you to research these testing tools, choose some, learn to use them, and create and add to your repo one simple unit and one behavior test to demonstrate your progress.

The second part, due at the end of the semester, requires you to have added multiple tests to your repo. You should add the unit tests as you write the code.

For the first deadline:

Have at least one unit and one behavioral test in your repo. Typically in a tests folder.
In your Readme.md file add a Testing section which lists
the commands/instructions one must type to run your tests
the directory (or filename regexep) where all your tests are located.
Once your tests are committed, create a git tag named v0.2 on the commit that marks the release: git tag v0.2
Push tags to GitHub: git push --tags.

For the final deadline:
Multiple unit tests (even if they are silly).
Multiple behavioral tests. Test the core functionality of the app.
In your Readme.md file add a Testing section which lists
the commands/instructions one must type to run your tests
the directory (or filename regexep) where all your tests are located
Add an Issue titled "Testing Video" to your repo and and put in there a video, or more, showing how the tests run. ( they don't have to pass)
Optionally, setup a continuous integration service, like travis to automatically run your tests.