Challenge Overview
Cloud Hub has been building our web application with Node and React, and we would like to add some test coverage to our web application. After doing some initial research we want to setup our testing with Karma and Mocha. We want to setup test coverage on a couple of pages during the initial challenge.
Requirements
1. Add test coverage with Karma and Mocha
2. Add covearge to table and nav components only, currently 12 components.
Great article on Karma and Mocha: https://www.toptal.com/react/how-react-components-make-ui-testing-easy
2. Provide your code and documentation in a single zip file. Please include a git patch for easier integration of changes.
3. The bulk of your documentation should be in the Readme.md and you should assume that this will be open source so make sure you cover all the steps to set up, If you have specific information that should not be included in a public readme (like links to your video) put them in a file called submission.txt and they will be omitted from the project if it is open sourced.
4. Provide a quick video of your solution in action (feel free to annotate your video if you are not comfortable with spoken English or don’t like the sound of your own voice). Video may be private on youtube or added to the submission files. Your video can skip the setup of your environment, linting and tests. We are interested to see the new functionality of the app in the video.
Requirements
1. Add test coverage with Karma and Mocha
2. Add covearge to table and nav components only, currently 12 components.
Great article on Karma and Mocha: https://www.toptal.com/react/how-react-components-make-ui-testing-easy
Final Submission Guidelines
1. Any additions or modifications to the code project pass on "npm run lint" and "npm run test".2. Provide your code and documentation in a single zip file. Please include a git patch for easier integration of changes.
3. The bulk of your documentation should be in the Readme.md and you should assume that this will be open source so make sure you cover all the steps to set up, If you have specific information that should not be included in a public readme (like links to your video) put them in a file called submission.txt and they will be omitted from the project if it is open sourced.
4. Provide a quick video of your solution in action (feel free to annotate your video if you are not comfortable with spoken English or don’t like the sound of your own voice). Video may be private on youtube or added to the submission files. Your video can skip the setup of your environment, linting and tests. We are interested to see the new functionality of the app in the video.