A read-only URL and Key for writing tests for pack...
# ideas-and-suggestions
k
A read-only URL and Key for writing tests for packages. Similar to Stripe, which has a test key and URL you can use to initiate a test checkout. This would be useful for making more standard tests for Supabase libraries without having to create a new project for each one, and worry about security etc for keys that may be public on GitHub.
The key and url would return Postgres and real-time data and auth tokens that appear and act real, but wouldn’t allow real writes
This might already exist but if it would be great to have
s
These are two different systems, there would be no way for Supabase to know your application structure or form if they made a universal testing system similar to that of Stripe
Note that in stripe you are testing a number of processes which are set in place, the requirements is already defined and you dont need to redefine them per project
s
Technically, with a new supabase-admin-test user (for example), it would be possible to set only
select
permissions for tables. However, this comes with it's own challenges, as Postgres would enforce those permissions at a level that is above the Supabase stack, so it would simply return a permission denied error. It's definitely a nice idea, but potentially beyond the scope of Supabase itself
k
I see both your points, I just looked at the JS repos to see how they were testing and it looks like they start an on-device instance of Supabase for testing. I’ll look at implementing that for tests in the Swift repos. Thanks!