Proposal: semi automated QA

[0x4007]

We can consider making a CI script to test all of the functions on every commit similar to how @web4er does manual QA.

Perhaps this GitHub action can open a new issue and do a routine. Perhaps it can also tag the title with the commit hash so that it is easier to identify which commit the tests correspond to.

context: #621 (review)

Task list

• Automated QA: End-to-end tests #633
• Automated QA: Unit tests with mocked github events #634
• Automated QA: Unit tests with other mocked infrastructure dependencies like logger, database, etc #635

[web4er]

A minimum goal to start would be some end-to-end tests that run all commands and check their responses.

A lengthy goal would be to also include unit tests with mocked github events and other mocked infrastructure dependencies like logger, database, etc leading to the possibility of high coverage and test-driven development style.

It wouldn't be just CI step, yarn test will also help developers to get quick feedback if they broke something with new changes.

[rndquu]

@web4er Could you elaborate on the difference between these 2 issues: #634 and #635?

From my point of view they're basically the same because implementing #634 implies mocking 3rd party dependencies (logger, supabase DB, etc...) so I don't really understand why we need this issue. Perhaps we should close this one?

[0x4007]

It was just to break apart the project into two phases.

The first being the essentials, the second being basically everything else.