Issue/482 supabase test framework

[johannesvedder]

• Fixes docker networks misbehaving
• Dumped study schema with postgres to verify it adheres to current version of supabase
  • Change table owners to postgres (fixes: https://github.com/orgs/supabase/discussions/9314)
• Provides the ability to test (supabase) postgresql functions and row level security with pgtap
• Requires the supabase CLI to be installed and can be initiated with npx supabase test db
• For manual testing,database/studyu_schema.sql has to be copied to docker/supabase/seed.sql. I didn't find a way to specify a different file for seeding
• depends on Bug: Study registry visibility issues #483

Todo:

• We could create a github actions pipeline for this if the current state is sufficient
  • https://2metz.fr/blog/use-pgtap-on-github-actions/

[jannis-baum]

How do we start the containers for local development now? The instructions in our contribution guide don't work anymore on this branch:

network studyu_network declared as external, but could not be found

[johannesvedder]

How do we start the containers for local development now? The instructions in our contribution guide don't work anymore on this branch:

network studyu_network declared as external, but could not be found

I ran into some issues with the current setup, that's why I changed the network config for the time being. This is an open issue: docker/compose#10797
Depending on how the compose issue gets resolved, I will adapt our network setup accordingly. For now you can create the network yourself (docker network create).

[jannis-baum]

Maybe we can mention that people might have to create the network manually for the time being until the issue is fixed? Just so that nobody gets confused with more people getting on the project now.

[johannesvedder]

Maybe we can mention that people might have to create the network manually for the time being until the issue is fixed? Just so that nobody gets confused with more people getting on the project now.

Yeah, I'll probably wait until progress happens with the compose issue and then do some changes on our side before merging this..

Edit: Let's just stay with our current setup for the moment and wait until the compose issue is closed.

[johannesvedder]

Update 27.07.

• Docker network will be created automatically, ignore warning for now until compose fix is ready (553320d)
• Created github actions pipeline (2359e90)
• Updated https://github.com/supabase/supabase/tree/master/docker (63100a4)

[jannis-baum]

Looks good! See 1 comment & we have to remember to also delete the supabase-test-framework-combined branch when it is no longer needed.

[johannesvedder]

How do we start the containers for local development now? The instructions in our contribution guide don't work anymore on this branch:

network studyu_network declared as external, but could not be found

Do you still encounter this message with the current version @jannis-baum? Shouldn't be the case anymore

[jannis-baum]

Do you still encounter this message with the current version @jannis-baum? Shouldn't be the case anymore

No, works fine! :)