Please see the 6 tests I wrote for my project. The test cases I wrote is highlighted in the link and is wrapped with "START RON'S TEST CASES" and "END RON'S TEST CASES" comments. Here I tested my own feature checking if the course check qualification is working as expected. All test cases passed after testing.
Test cases:
- test_minors_of_APS360()
- test_certificates_of_APS360()
- test_majors_of_APS360()
- test_minors_of_wrong_course_codes()
- test_certificates_of_wrong_course_codes()
- test_majors_of_wrong_course_codes()
- Able to make sure that the new changes did not affect your old testcases, if old testcases fail this makes it easier to debug
- Able to achieve high test coverage of the code
- Forces your code to be more modular
- When submitting a pull request and you include what your test cases are and how they have passed makes it easier for others to quickly understand what the new changes are doing
- Can catch small mistakes instantly
- Testing becomes automated, no longer need to manually test everything by clicking through everything
- Able to be refactored easily, since every new feature is throuogly unit tested
- Development becomes much slower because you always need to write the test first before jumping into developing
- Requires more brainpower to come up with the test instead of writing the code immediately
- Sometimes it is difficult / tedious to write tests depending on what the program is doing
- Even the written test cannot catch all errors, manually testing extensively usually will gurantee the user would not see any weird errors
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent