Before submitting your test, please review the requirements/guidelines belows. Note that the requirements are mandatory and if you do not satisfy them we won't review your code (we don't mean to be harsh but this is based on the minimum expectations that our hiring partners require when you submit code for tech tests).
- We use Hound CI to check for violations to our style guide. When you submit your Pull Request, please then check over and correct everything that Hound has sniffed out that is wrong with your code (unless you feel you really can't do anything to fix it). Once you've fixed Hound errors, push your code again and the Pull Request should update automatically.
- Make sure you have written your own README that briefly explains your approach to solving the challenge.
- If your code isn't finished it's not ideal but acceptable as long as you explain in your README where you got to and how you would plan to finish the challenge.
- All code must be written test-first - we're looking for 100% test coverage or as near as possible to that figure.
- Ensure all your tests are passing.
- Set up Travis CI on your own repo and add a status badge to your README showing that all tests are passing - and make sure it passes our own CI when you submit your PR.
- Ensure you've understood the specification and built the code according to the challenge guidelines.
- Read through Code Reviews :pill: to understand what we're looking for in your code.