This is a Starter Kit for my future Test-Driven Development projects.
The master branch is a general and very basic branch, while each branch under addition is a different configuration that could be used for a different kind of project.
These branches should always be rebased on master, so that a project using eg. TypeScript could be easily forked from this repository then have its addition/TypeScript branch merged on master. (The rest of the addition branches could be deleted if not needed.)
By default, de build folder is served locally with gulp-connect.
JavaScript files and their unit tests correspond. If either of them is changed, tests should run and will run automatically.
The unit tests are written in Jasmine and ran with Karma in a headless PhantomJS browser.
First, fork this repository and find the branches you need
git branch --all
All additional branches should be under addition Merge the branch you need to master
git merge addition/<your-selected-branch> master
And finally, create your dev branch and run the serve task
git checkout -b dev
gulp serve
Code!
Note: While using gulp serve, file changes like add, change and delete will be handled automatically. The webserver will be reloaded and the unit tests will be ran again.
The MIT License (MIT) Copyright (c) 2016 Peter Seprus
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.