due Tuesday, October 2
- Jinzhong: A Testing Function to ensure links in *.md are accessible
- Wenhe: Add ReLU function and test
- James: Add timer funtion and test
- Jiwon: Add randInt, factorize and 3D distance check functions and test
- Guillermo: Add fahrenheit2Celcius function and three tests: first broken and then fixed.
- emma: Add iThink function and test
- Nico: Add Fisher-Yates array shuffle algorithm and test
- Lin: Add repeatAction function and test
- Alice: Testing for myLove function (and many failures D:)
- Vince: Add power function
- Luna: My test
Note that this assignment can be completed any number of ways. The idea is to experiment with unit tests and continuous integration. You do not need to set up your own continuous integration or write a new test. For documentation, you may link below to a pull request, GitHub repository, or blog/medium post.
- Follow these video tutorials:
- Try one or more of the following:
- Submit a pull request to UnitTestingCI that breaks one of the tests. Can you then edit the request with a fix so that the test passes? (Now, thanks to #64 as an alternative, you can also try breaking/fixing the tests here on this repo!)
- Add a new test to UnitTestingCI. Does it pass? For reference, here is the Jest testing documentation.
- Fork the UnitTestingCI and set up continous integration with CircleCI on your own account. This video on how to set up CircleCI will help.
The Playground repository also has continuous integration enabled with TravisCI and testing with Mocha and Chai. If you'd like to try writing some tests for the Playground or experimenting with breaking the existing tests this is also an option.
Here are some resources for the above:
- Egghead: Setting up Unit Testing with Mocha and Chai
- Egghead: Unit Testing with Mocha and Chai
- Egghead: Automatically running tests before commits with ghooks
You are welcome to set up unit testing and/or continuous integration in a new GitHub repository or contribute a test to another open source project.