supabase / supabase-swift / 29819344692
84%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 96
Run time 1min
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
coverage: 83.583%. Remained the same
29819344692

push

github

web-flow 
test(storage): migrate StorageTests to Swift Testing, keep Mocker (Phase 3) (#1096)

* test(storage): migrate StorageTests to Swift Testing, keep Mocker

Same Phase 3 migration as #1096, but stays on Mocker for HTTP mocking
instead of Replay -- Replay isn't proven yet for all our cases, so we
stick with Mocker for now. StorageBucketAPITests/StorageFileAPITests
gain @Suite(.serialized) since Mocker's mock registry is process-global
and Swift Testing runs suites in parallel by default. Restores the
.snapshotRequest curl-body assertions for move/copy/remove instead of
Replay's custom JSON-body matcher, since Mocker already covers that.

Linear: SDK-1250

* fix(storage): clear Mocker registry per-test to prevent stub leakage

Mocker.mock(for:) matches the FIRST registered mock for a request, so
a stale stub from an earlier test could shadow a fresh one registered
for the same URL in a later test. Clear the registry at the top of
makeSUT() in both StorageBucketAPITests and StorageFileAPITests.

Since Mocker's registry is process-global, the two suites also can't
run concurrently *with each other* anymore (only .serialized within
each suite isn't enough) -- otherwise one suite's removeAll() could
wipe out mocks the other just registered. Nest both under a shared
StorageMockerTests(.serialized) namespace, since Swift Testing applies
.serialized recursively to nested suites.

Addresses review feedback on #1096.

8141 of 9740 relevant lines covered (83.58%)

38.65 hits per line

Jobs
ID Job ID Ran Files Coverage
1 29819344692.1 96
83.58
 GitHub Action Run
Source Files on build 29819344692