Create an expectation before starting callback-based work, fulfill it in the completion handler, then wait with a finite timeout: ```swift func testCompletionIsCalled() { let expectation = expectation(description: "completion called") client.fetch { result in XCTAssertEqual(try? result.get().id, 42) expectation.fulfill() } wait(for: [expectation], timeout: 2.0) } ``` Use `async throws` tests with `try await` for async APIs instead of blocking. Every expectation needs a reasonable timeout so a...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill swift-testing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Swift Testing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-swift-testing-d43c335c)More formats (shields.io, HTML) on the badges page.
Create an expectation before starting callback-based work, fulfill it in the completion handler, then wait with a finite timeout:
```swift
func testCompletionIsCalled() {
let expectation = expectation(description: "completion called")
client.fetch { result in
XCTAssertEqual(try? result.get().id, 42)
expectation.fulfill()
}
wait(for: [expectation], timeout: 2.0)
}
```
Use `async throws` tests with `try await` for async APIs instead of blocking. Every expectation needs a reasonable timeout so a broken callback cannot hang CI.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
