Skip to content

Commit a892610

Browse files
Apply suggestions from code review
Co-authored-by: Marcel Ribeiro-Dantas <[email protected]>
1 parent 0c3f82b commit a892610

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/side_quests/nf-test.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ There are lots of different types of tests we can write:
2121
2. **Workflow-level tests**: For a single workflow
2222
3. **Pipeline-level tests**: For the pipeline as a whole
2323
4. **Performance tests**: For the speed and efficiency of the pipeline
24-
5. **Stress tests**: To identify the limits of the pipeline
24+
5. **Stress tests**: Assessing the pipeline's performance under extreme conditions to determine its limits
2525

2626
Testing individual processes is analogous to unit tests in other languages. Testing the workflow or the entire pipeline is analogous to what's called integration tests in other languages, where we test the interactions of the components.
2727

@@ -127,7 +127,7 @@ Wrote pipeline test file '/workspaces/training/side-quests/nf-test/tests/main.nf
127127
SUCCESS: Generated 1 test files.
128128
```
129129

130-
This will create a `tests` directory with a `main.nf.test` and a `nextflow.config` file. This is our pipeline level test file. If you run `tree tests/` you should see something like this:
130+
This will create a `main.nf.test` file within the `tests` directory. This is our pipeline level test file. If you run `tree tests/` you should see something like this:
131131

132132
```console title="Test directory contents"
133133
tests/

0 commit comments

Comments
 (0)