Overall, my testing strategy was to "cast a wide net" over my code. I rely on less but higher level tests eg. integration & e2e. Gives me max return on investment in a short amount of time.
If i had a bit more time i would look at testing my useAuth hook in isolation next.
As the app would scale, a more robust form management and validation library would make sense. eg. react-hook-forms & ZOD.
Also, setting up a solid CI&CD pipeline with husky, Cypress & Vitest with code coverage reports would probably be the next step I would do for this repo.
Since credentials are not sensitive for this API I am including them in the readme for user's convenience.
- username: tesonet
- pass: partyanimal
🧑💻 Preview Live Application Here
npm run devstarts development server.npm run buildruns build script.npm run testruns unit & integration test suite.npm run test:coverageruns the unit & integration test suite and generates a istanbul test coverage report.npm run test:e2estarts the server & runs the e2e test suite in headless mode. Exits when done.
