E2E programmable test

[wildan3105]

To enhance the application's robustness and increase confidence. Priority of tests:

1. E2E (might require 3rd party tools): evaluate the application as a whole. possible dependency: redis, serp API, twitter API
2. integration test: checks how different parts of your application work together.
3. unit test: smallest test for each unit.

While unit tests serve a purpose in isolating and validating individual components, the true value and confidence in application functionality stem from robust integration and e2e testing strategies

[wildan3105]

Documentation on how to setup redis on github action: https://docs.github.com/en/actions/using-containerized-services/creating-redis-service-containers

[wildan3105]

Still relevant but will be done in healthcheck:

• check if the response from serp API conform the interface (will need to update the serp API module first)
• send the report everyday (positive/negative)
• ensure match-fetcher partially use the same method as the healthcheck