The system should cover all the previous use cases.
Please, follow this mockup.
You should provide a workout log that works looks this mock, but remmember this is a mock and we are open to new ideas on how it should work.
- You must implement a workout log using React. If you want, you can also use Redux to manage app's state.
- You don't need a backend, you can implement only in the browser using memory or local storage. But it would be very good if the app consume an API.
- You should write tests
- Host the source code as a private git repositotry at bitbucket.org
- The design is important but the UX is more important.
- You can surprise us but never forget the four main features.
- The final application provides a README file with instructions on how to run it? And how to run the tests?
- The solution works as it should be?
- All tasks were delivered? The applicant made something beyond the expected?
- Is the code easy to read?
- The code uses the common conventions of the used language?
- Did the applicant comprehended the problem as a whole?
- Did he structure/model the solution accordingly?
- The structure/architecture of the final application makes sense?
- The right tools for the solution were used? Or the applicant used a fork to have soup?
- Do you feel that the user was committed to deliver something really good?
- If you were asked to implement more features on the delivered application, would you rather keep the code or forget it and start the whole thing from scratch?
- The tests really describe the solution?
- Does he or she care about literate tests?
- Try to identify if the applicant did use of TDD/BDD.
- Look the repository log and check if the commits are tiny, with a well described purpose.