https://github.com/xta/unit-test-js-demo
unit test your JS & use it in your browser
https://github.com/xta/unit-test-js-demo
Last synced: about 1 year ago
JSON representation
unit test your JS & use it in your browser
- Host: GitHub
- URL: https://github.com/xta/unit-test-js-demo
- Owner: xta
- Created: 2014-07-19T18:58:10.000Z (almost 12 years ago)
- Default Branch: master
- Last Pushed: 2014-07-20T14:44:33.000Z (almost 12 years ago)
- Last Synced: 2024-10-13T00:22:51.890Z (over 1 year ago)
- Language: JavaScript
- Homepage: http://xta.github.io/unit-test-js-demo/
- Size: 4.63 MB
- Stars: 1
- Watchers: 2
- Forks: 6
- Open Issues: 0
-
Metadata Files:
- Readme: Readme.md
Awesome Lists containing this project
README
# Unit Test JS demo
a simple demo with Jasmine, Browserify, and Gulp on NodeJS
### Why?
I want to unit test my JS libraries AND use it in my browser.
### Walkthrough Guide
Read the [blog post](http://www.rexfeng.com/blog/2014/07/how-to-unit-test-your-js-and-use-it-in-the-browser/) that walks through this repo to add GulpJS, gulp-jasmine, and browserify.
### Dev
// Run default task to run specs and generate minified JS
gulp
### Questions
Why did you include the `node_modules` dir?
* Per the [npm-faq](https://www.npmjs.org/doc/faq.html#Should-I-check-my-node_modules-folder-into-git), "Check `node_modules` into git for things you deploy, such as **websites** and apps."
Why did you not include the [*insert task here*] Gulp task? Why did you organize your folders that way? Why didn't you include more test cases?
* This demo is intended as an easy to understand example of using Gulp + Jasmine + Browserify together. This demo is not a production ready project.
### License
MIT