Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Correct npm script usage in DEVELOPMENT.md #1032

Merged
merged 1 commit into from
Oct 7, 2016
Merged

Correct npm script usage in DEVELOPMENT.md #1032

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The local development environment requires both Node.js and Ruby, along with the

You can now try out the unit test suite by running:

npm test:unit
npm run test:unit

Karma also provides a local server so you can just visit a url from any browser to run the test suite, instead of launching one from the command line. Webpack also provides a server to dynamically build and serve the latest copy of the source code. Jekyll does the same for the documentation site.

Expand All @@ -30,15 +30,15 @@ All four services can be run with a single command thanks to [foreman](http://dd

While Quill features an extensive javascript test suite, which you can run with:

npm test:unit
npm run test:unit

However some functionality can only be tested with webdriver. To set up or update webdriver run:

npm webdriver:update

Once webdriver is installed, you can run the test suite with

npm test:functional
npm run test:functional


### Workflow
Expand Down