Skip to content

Commit ab7aa08

Browse files
committed
move browser testing section
explain in-browser testing as part of the existing unit testing section
1 parent 4c245c2 commit ab7aa08

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

developer_docs/README.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,14 @@ To run the unit tests, use Grunt.
5454
$ grunt
5555
```
5656

57+
Sometimes it is useful to run the tests in the browser instead of on the command line. To do this, first start the [connect](https://github.com/gruntjs/grunt-contrib-connect) server:
58+
59+
```
60+
$ npm run grunt connect -keepalive
61+
```
62+
63+
With the server running, you should be able to open test/test.html in your favorite web browser.
64+
5765
# Development Process
5866

5967
1. Install [node.js](http://nodejs.org/), which also automatically installs the [npm](https://www.npmjs.org) package manager.
@@ -127,12 +135,6 @@ This will build the p5.js library, generate the documentation files, run a web s
127135
npm run docs:dev
128136
```
129137

130-
## Running tests in the browser
131-
Sometimes it is useful to run tests in browser especially when trying to debug test failures. To run the tests in the browser:
132-
133-
1. Run the connect server. ```npm run grunt connect -keepalive```
134-
2. Open test/test.html in your favourite web browser.
135-
136138
# Repositories
137139

138140
* https://github.com/processing/p5.js - this repo contains the source code for the p5.js library, and the p5.dom.js addon library. The reference is also generated from this code, as the documentation and examples are located in the source code itself, maintained by Lauren McCarthy.

0 commit comments

Comments
 (0)