... | ... | @@ -39,7 +39,7 @@ If you want to contribute, you must learn about them. Otherwise, it's pure HTML5 |
|
|
|
|
|
## Code style
|
|
|
|
|
|
Please follow style defined into *.jsonhintrc* and call `npm run lint` before commiting.
|
|
|
Please follow style defined into *.jsonhintrc* and call `npm run lint` before committing.
|
|
|
|
|
|
## Unit and functional testing
|
|
|
|
... | ... | @@ -47,4 +47,6 @@ Tests use recent [jasmine library](http://jasmine.github.io/). |
|
|
|
|
|
Backend code has good coverage of unit and functional testing (using `request` library for API testing). Tests are located into *spec/backend*. Please take care of not breaking tests and adding pertinent ones. You can run backend testing with `npm run test`.
|
|
|
|
|
|
Web client is only functionally tested for common navigation scenarios. You can run frontend functional testing on a fresh mockup server connecting your browser to `http://localhost:8042/mypads/functest/`. Tests are located into *spec/frontend* and need to be inventoried into *spec/frontend/entry.js*. If you add or update a frontend functional test, you can rebuild the global file with `npm run functest:build` or you can watch for changes with `npm run functest:watch`. |
|
|
\ No newline at end of file |
|
|
Web client is only functionally tested for common navigation scenarios. You can run frontend functional testing on a fresh mockup server connecting your browser to `http://localhost:8042/mypads/functest/`. Tests are located into *spec/frontend* and need to be inventoried into *spec/frontend/entry.js*. If you add or update a frontend functional test, you can rebuild the global file with `npm run functest:build` or you can watch for changes with `npm run functest:watch`.
|
|
|
|
|
|
**All** frontend functional tests **have been broken** by MR !2 . A few have been adapted but a couple of days will be required to rewrite all. Contributions will be greatly appreciated here. |
|
|
\ No newline at end of file |