When I updated the Supabase auth implementation some months ago I accidentally introduced some regression, can't even remember now. But, to not risk doing the same thing next time I (or someone else) updated a provider I added the "Basic sanity checks". It made it easy to scan the list of all the providers and see that all the checks still passed.
Now that all the providers are on different pages and, on each page, the checks are scrolled out of view, I'm starting to question the value of the checks.
Ideally these "basic sanity checks" would be basic tests in the code instead. Or e2e tests run as CI-test on GitHub.
Is this possible to implement? Maybe as cypress tests?
When I updated the Supabase auth implementation some months ago I accidentally introduced some regression, can't even remember now. But, to not risk doing the same thing next time I (or someone else) updated a provider I added the "Basic sanity checks". It made it easy to scan the list of all the providers and see that all the checks still passed.
Now that all the providers are on different pages and, on each page, the checks are scrolled out of view, I'm starting to question the value of the checks.
Ideally these "basic sanity checks" would be basic tests in the code instead. Or e2e tests run as CI-test on GitHub.
Is this possible to implement? Maybe as cypress tests?