forked from jedireza/drywall
-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Drywall needs a testing suite #3
Labels
Comments
trystant
pushed a commit
that referenced
this issue
Sep 1, 2015
Added supertest and mocha for "Unit" testing (AKA end to end testing) The test suite is invoked with the command "npm test" - package.json - Added a "test" command which maps to an invocation of mocha with the specified directory, in this case "test": "NODE_ENV=test mocha specs". - specs/index-spec.js - Initial spec created that maps to the web application home page.
trystant
pushed a commit
that referenced
this issue
Sep 1, 2015
Setting up a Travis server for this project Runs for node.js and io.js for now
trystant
pushed a commit
that referenced
this issue
Sep 1, 2015
Changed the copy on the 'it' function for the specs/index-spec.js
trystant
pushed a commit
that referenced
this issue
Sep 1, 2015
Changed the YML syntax of the YAML file
trystant
pushed a commit
that referenced
this issue
Sep 1, 2015
npm install added to the before_script attribute to make sure that the NPM script is installed properly.
trystant
pushed a commit
that referenced
this issue
Sep 1, 2015
- .travis.yml - Removed the 'before_script' line since it is not used - README.md - Added a "Testing" section which describes how testing works at a high level and how to invoke the command
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I plan on using the testing strategy I used on the Red Cross project; mocha and Supertest to do "Unit" Testing. I'm familiar with it as end-to-end testing, but having that suite will be helpful. The second stage will be to have that testing suite up and running on Travis or another Continuous Integration server.
The text was updated successfully, but these errors were encountered: