You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/side_quests/nf-test.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ There are lots of different types of tests we can write:
21
21
2.**Workflow-level tests**: For a single workflow
22
22
3.**Pipeline-level tests**: For the pipeline as a whole
23
23
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
25
25
26
26
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.
27
27
@@ -127,7 +127,7 @@ Wrote pipeline test file '/workspaces/training/side-quests/nf-test/tests/main.nf
127
127
SUCCESS: Generated 1 test files.
128
128
```
129
129
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:
0 commit comments