https://github.com/radiergummi/clientside-javascript-test-boilerplate
Simple boilerplate to test clientside javascript code written in ES6, using PhantomJS, ES6 tests and modules
https://github.com/radiergummi/clientside-javascript-test-boilerplate
clientside javascript javascript-library phantomjs test-clientside-javascript
Last synced: 2 months ago
JSON representation
Simple boilerplate to test clientside javascript code written in ES6, using PhantomJS, ES6 tests and modules
- Host: GitHub
- URL: https://github.com/radiergummi/clientside-javascript-test-boilerplate
- Owner: Radiergummi
- License: apache-2.0
- Created: 2017-03-03T15:08:13.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2017-05-10T15:39:10.000Z (almost 8 years ago)
- Last Synced: 2024-12-28T16:46:44.630Z (4 months ago)
- Topics: clientside, javascript, javascript-library, phantomjs, test-clientside-javascript
- Language: JavaScript
- Size: 95.7 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# clientside-javascript-test-boilerplate
Simple boilerplate to test clientside javascript code written in ES6, using PhantomJS, ES6 tests and modules
## Features
- Test your ES6 client code
- Write your tests in ES6
- Use modules both in source and in tests
- Use multiple test files for easier file system structure
- Automatically spin up and shut down an HTTP server for AJAX call testing
- Emulate a browser event by attaching your library to the PhantomJS window object
- Automate your tests with TravisCI
## Why should I care?
This is a simple boilerplate to test your clientside code. When attempting to create tests for a client library I'm writing, I noticed all the hassles required to do so:
You don't want to perform tests manually in a graphical browser, especially if you want to be able to use CI environments like Travis. Therefore, you use PhantomJS, a glorious headless browser, running on the command line entirely. But oh, snap! It doesn't support ES6 yet. So you set out to use Babel to transpile your ES6 code for the tests, which you would do anyway. But oh, snap! Imports or require won't work here. So you again go google a bit, after all you don't want webpack for your tests, which would be overkill for a single library. You integrate Browserify to bundle your transpiled source code, but oh, snap! The tests won't work, because you made use of those nice ES6 features in your tests, too. So you repeat the whole process for your tests, and BAM! Another few hundred lines of code and several modules just for testing your freaking client side code.
But at last, you have plugged together exactly what I have already done for you in this repo.
## Instructions
1. Clone the repository
2. Run `npm install`
3. Place your library code at `src`
4. Place your tests in `test/specs/spec.js` and anything below `test/specs`
5. Run `npm test`