• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / supabase-flutter / 27916391162 / 8
86%
main: 86%

Build:
DEFAULT BRANCH: main
Ran 21 Jun 2026 08:27PM UTC
Files 5
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Jun 2026 08:22PM UTC coverage: 93.013%. Remained the same
27916391162.8

push

github

web-flow
test: use proper matchers in tests (#1437)

## What kind of change does this PR introduce?

Test quality cleanup. No production code changes; only test files are
touched.

## What is the current behavior?

Several test suites used non-idiomatic assertions:

- boolean-literal expectations, e.g. `expect(x, true)` / `expect(x,
false)`
- equality checks done inside the actual argument, e.g. `expect(a == b,
true)`
- length-zero emptiness checks, e.g. `expect(x.length, 0)`
- exception assertions written as `try { await ...; fail('...'); } catch
(e) { expect(e, ...) }`

## What is the new behavior?

These are replaced with the proper matchers across all packages:

- `expect(x, isTrue)` / `expect(x, isFalse)`
- `expect(a, b)` / `expect(a, isNot(b))`
- `expect(x, isEmpty)`
- `expectLater(() => ..., throwsA(isA<T>().having((e) => e.field,
'field', value)))`

Approximate counts: ~47 boolean matchers, ~22 direct equality, ~8
emptiness, ~43 exception conversions across 22 test files in
functions_client, gotrue, postgrest, realtime_client, storage_client,
supabase, and supabase_flutter.

A few `fail()` calls were intentionally left in place because they are
not exception-testing patterns (one sits inside an `await for` stream
loop, two assert that a download succeeds after copy/move).

## How was the change verified?

- `dart analyze` / `flutter analyze` on every affected package's `test/`
directory: no issues.
- `dart format` on all changed files: already conformant.
- All mock-based suites pass. Server-dependent integration suites were
not run locally but analyze cleanly; the conversions are mechanical and
preserve assertion meaning.

426 of 458 relevant lines covered (93.01%)

2.1 hits per line

Source Files on job storage_client - 27916391162.8
  • Tree
  • List 5
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 27916391162
  • 623777b5 on github
  • Prev Job for on main (#27914112093.5)
  • Next Job for on main (#27945378487.7)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc