Testing Strategy

Major Developments

• Testing setup
• CI/CD (at least the base architecture)

Pretty short log here - continuing on with the basic architecture setup. I shelved the push for new screens for now and decided to be proactive and set up testing. Shared monorepo sort of helps out with things, at least since everything is TypeScript. Utilizing @testing-library/react-native, so nothing out of the ordinary here. CI/CD we're just implementing standard flows through GitHub workflows, in order to automate tests on PRs/Merges.

Decisions

No major decisions here - testing-library was a simple choice, and the use of GitHub workflows was just the natural choice as I've used it in the past as well as already set up in GitHub.

I was refactoring some things as a few tests were retroactive - I'm trying not to do this as much as I can, and at least staying relatively close to the code when I write it (not strictly TDD, but not leaving out tests entirely).

Also made a choice to leave some things untested, focusing on schemas and some of the stats calculations - component testing and Supabase integration will come at a later date.

Next

Moving back to developing out the application itself. Will most likely target some simple actions (logging a dish, perhaps) and give "users" something to do.