JoshuaAndle
commented
1 year ago At least 3 automated tests written for each feature (which may be failing i.e. is commented out)
Use the process Dr. Greg demonstrated in class for test-driven web development for a use case. -7.5 points for each feature delivered where the commit history shows it was not developed using test-driven development, which means writing the test before the implementation code. See the test-driven web development class and class recording, and use your use cases! I will be strict about this for all code written after class on 11/22! Not recoverable by regrade because you can’t go back in time to use TDD. Do not squash your commits such that you can’t tell TDD was used. -7.5 points. If you did not use TDD, if I see a bug in your implementation that a simple test could have caught, -5 additional points.
At least some new HTML, React, CSS and Typescript code is present for each new feature. It is expected each feature will have at least 6 hours of development time total at a minimum and the code should be commensurate with that. So get help fast from your team if you get stuck!
(5 / 15 points each) For each feature developed, submit the mockup that was made first before implementing the feature. Put this in the 1-6 minute video, then show the feature as implemented/progressed on. There can be some changes from the mockup / don’t avoid improving the UI just to match the initial mockup.
It is best practice to make a simple UI mockup/sketch before implementing any UI more complicated than a single button or HTML element
Given the remaining time available, any easily correctible discrepancies between the documents and implemented code will be corrected, either by changing the code if called for, or preferably by changing the document.