Skip to content

Update testing.md to refer to .xctest extension #30

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update testing.md to refer to .xctest extension #30

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9cc4b58
Update testing.md to refer to xctest extension
cobbal May 28, 2025
99519c3
Update testing.md
cobbal May 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions src/getting-started/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,13 +62,13 @@ using `SwiftPM`. After your tests are built, you can use a WASI-compatible host
[wasmtime](https://wasmtime.dev/) to run the test bundle:

```sh
$ wasmtime --dir . .build/wasm32-unknown-wasi/debug/ExamplePackageTests.wasm
$ wasmtime --dir . .build/wasm32-unknown-wasi/debug/ExamplePackageTests.xctest
```

(`--dir .` is used to allow XCTest to find `Bundle.main` resources placed alongside the executable file.)

As you can see, the produced test binary starts with the name of your package followed by
`PackageTests.wasm`. It is located in the `.build/debug` subdirectory, or in the `.build/release`
`PackageTests.xctest`. It is located in the `.build/debug` subdirectory, or in the `.build/release`
subdirectory when you build in release mode.

## Code coverage with `SwiftPM`
Expand All @@ -87,11 +87,11 @@ data will be stored in `default.profraw` file in the current directory. You can
and `llvm-cov` tools to generate a human-readable report:

```sh
$ wasmtime --dir . .build/wasm32-unknown-wasi/debug/ExamplePackageTests.wasm
$ wasmtime --dir . .build/wasm32-unknown-wasi/debug/ExamplePackageTests.xctest
$ llvm-profdata merge default.profraw -o default.profdata
$ llvm-cov show .build/wasm32-unknown-wasi/debug/ExamplePackageTests.wasm -instr-profile=default.profdata
$ llvm-cov show .build/wasm32-unknown-wasi/debug/ExamplePackageTests.xctest -instr-profile=default.profdata
# or generate an HTML report
$ llvm-cov show .build/wasm32-unknown-wasi/debug/ExamplePackageTests.wasm -instr-profile=default.profdata --format=html -o coverage
$ llvm-cov show .build/wasm32-unknown-wasi/debug/ExamplePackageTests.xctest -instr-profile=default.profdata --format=html -o coverage
$ open coverage/index.html
```

Expand Down