Dragonnet dRisk - ReactJS Unit Tests

Challenge Objectives

• Add unit tests for components to our existing ReactJS based prototype code.

Challenge Context

• Please check the challenge in which the prototype was built to better understand how it works and what was in scope. One thing to pay attention to was we enforced using the Micro Frontend Framework.

Technology Stack

• ReactJS v16.8
• JTest
• Enzyme (optional)
• Redux
• Typescript
• HTML5
• CSS

Challenge Requirements

• You must unit test all the components in the code base, with a coverage of over 90%. This is considered a major requirement in the scorecard since unit testing is all this challenge is about.
• End-to-end testing is NOT in scope.
• Your submission must add a script (or command) to run the tests and generate a coverage report.
• No existing code should be modified and no existing features should be broken.
• There should be no linting errors or warnings with the unit tests code
• Production build of the prototype must not be broken

References
Here are a few quick references if unit testing is new to you:

• https://reactjs.org/docs/testing.html
• https://www.toptal.com/react/tdd-react-unit-testing-enzyme-jest
• https://blog.bitsrc.io/how-to-test-react-components-with-jest-and-enzyme-in-depth-145fcd06b90
• https://medium.com/codeclan/testing-react-with-jest-and-enzyme-20505fec4675

Final Submission Guidelines

Please submit a single zip file with the following:

• Full source code
• Updated / new build scripts to run the tests and generate coverage report
• Updated readme to reflect the changes done in this challenge (example: new details on how to run your tests and where to check the coverage report, how to run linting on the test code, etc.)