Skip to content

Commit 6970f54

Browse files
committed
docs: Document how to add new testing data
1 parent a730cb6 commit 6970f54

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

doc/content/docs/hacking_itk_wasm.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,14 @@ git clean -fdx
4141
npm run build:debug
4242
```
4343

44+
### Add test data
45+
46+
To prevent Git repository bloat, we add testing data through [CMake content links](https://blog.kitware.com/cmake-externaldata-using-large-files-with-distributed-version-control/) of [Content Identifiers (CIDs)](https://proto.school/anatomy-of-a-cid). To add new test data,
47+
48+
1. Upload the data and download its content link *.cid* file with the [CMake w3 ExternalData Upload Tool](https://cmake-w3-externaldata-upload.on.fleek.co/)
49+
2. Move the *.cid* file to *itk-wasm/test/Input/*
50+
3. Reference the content link with a `DATA{<path>}` call in *itk-wasm/test/CMakeLists.txt*.
51+
4452
### Contributing
4553

4654
We use [semantic-release](https://github.com/semantic-release/semantic-release) for handling the change log and version. Therefore, we recommend using the following command line when creating a commit:

0 commit comments

Comments
 (0)