Skip to content

Commit dc23014

Browse files
authored
adding screenshots.
1 parent c46ff27 commit dc23014

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

contributor_docs/unit_testing.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -188,6 +188,11 @@ Here are the conventions and best practices that p5.js uses for unit tests which
188188

189189
The most straightforward way to run the tests is by using the `npm test` command in your terminal. However, `npm test` usually takes a long time to run simply because of the large number of test cases p5.js has. We don’t need to run `npm test` over and over after each change. As soon as we save our code, we can see in the browser or terminal whether the tests pass or not.
190190

191+
This screenshot shows how the test executes on the website and in the terminal.
192+
193+
<img src="./images/unit-visual-test.png" width="300" alt="Web test" /> | <img src="./images/unit-visual-test-terminal.png" width="250" alt="Terminal test" />
194+
195+
191196
- You can also mark certain test suites to be skipped or be the only suite that is run with the `.skip` and `.only` syntax.
192197

193198
```js

0 commit comments

Comments
 (0)