Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(test) SPIKE Row Level Security testing #516

Open
andrewrisse opened this issue May 15, 2024 · 1 comment
Open

chore(test) SPIKE Row Level Security testing #516

andrewrisse opened this issue May 15, 2024 · 1 comment
Labels
tech-debt 💳 Not a feature, but still necessary

Comments

@andrewrisse
Copy link
Contributor

Spike into how we can test our Postgres Row Level Security rules. The LF API will set most of the rules, but the frontend will also have some of it's own (ex. avatar storage uploading, not API related, but handled by Sveltekit backend).

It can sometimes be difficult to test these rules with browser based End-To-End (Playwright) tests because there's no way to get yourself into some of these edge cases with the UI. Example- I maliciously try to delete another user's Assistant.

We may required a different E2E testing tool (like Postman) to test the RLS rules.

Additional context

These tests should be integrated into the workflow, but may not necessarily have to be associated with just the UI or just the API.

@andrewrisse andrewrisse added the tech-debt 💳 Not a feature, but still necessary label May 15, 2024
@andrewrisse andrewrisse added this to the v0.8.0 milestone May 15, 2024
@CollectiveUnicorn
Copy link
Contributor

CollectiveUnicorn commented May 17, 2024

Here's how I was tackling it from the API side of things: #533 maybe it'll help if you haven't already started this.

@barronstone barronstone changed the title SPIKE Row Level Security testing chore(test) SPIKE Row Level Security testing May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-debt 💳 Not a feature, but still necessary
Projects
None yet
Development

No branches or pull requests

3 participants