You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+136-1Lines changed: 136 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -139,6 +139,142 @@ void main() {
139
139
}
140
140
```
141
141
142
+
### Mocking Errors
143
+
144
+
You can simulate error scenarios by configuring an error trigger callback. This is useful for testing how your application handles various error conditions:
- The mock Supabase client does not know the table schema. This means that it does not know if the inserted mock data is a referenced table data, or just a array/JSON object. This could potentially return more data than you construct a mock data with more than one referenced table.
@@ -154,7 +290,6 @@ void main() {
154
290
- count and head requests are not supported.
155
291
- aggregate functions are not supported.
156
292
- Respect nullsFirst on ordering is not supported.
157
-
- rpc support is not supported.
158
293
- The errors thrown by the mock Supabase client is not the same as the actual Supabase client.
159
294
- The mock Supabase client does not support auth, realtime, storage, or calling edge functions.
160
295
- You can either mock those using libraries like [mockito](https://pub.dev/packages/mockito) or use the Supabase CLI to do a full integration testing. You could use our [GitHub actions](https://github.com/supabase/setup-cli) to do that.
0 commit comments