Skip to content

Commit 0c0eee6

Browse files
committed
Prettier
1 parent ebe4b23 commit 0c0eee6

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/side_quests/nf-test.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,29 @@
11
# Side Quest: nf-test
22

33
Testing is a fundamental aspect of software development, and pipeline development is no exception. Being able to systematically verify that every component of your workflow behaves as intended is critical for:
4+
45
- Ensuring reproducibility
56
- Supporting long-term maintenance
67
- Accelerating the development process
78

89
Let's explore why testing is so important in pipeline development.
910

1011
Imagine you're building a new workflow. You start by gathering some test data that you know should produce valid results. As you develop, you:
12+
1113
1. Add the first process to your pipeline
1214
2. Connect it to your input data
1315
3. Run it to verify it works
1416
4. Move on to the next process
1517
5. Repeat until the pipeline is complete
1618

1719
This manual testing approach works initially, but quickly becomes challenging. For example, when you add a simple parameter like `--skip_process`, you now need to:
20+
1821
- Run the pipeline twice (once with and without the parameter)
1922
- Manually inspect outputs or log files to verify the process was actually skipped
2023
- Remember to repeat this verification every time you make changes
2124

2225
As your pipeline grows more complex, this manual testing becomes:
26+
2327
- Time-consuming
2428
- Error-prone
2529
- Difficult to track

0 commit comments

Comments
 (0)