https://github.com/gullerya/just-test
Test framework to run JavaScript (client) tests
https://github.com/gullerya/just-test
Last synced: about 1 month ago
JSON representation
Test framework to run JavaScript (client) tests
- Host: GitHub
- URL: https://github.com/gullerya/just-test
- Owner: gullerya
- License: mit
- Created: 2014-12-02T10:19:55.000Z (over 10 years ago)
- Default Branch: main
- Last Pushed: 2023-12-31T22:23:11.000Z (over 1 year ago)
- Last Synced: 2025-04-22T10:43:29.332Z (about 1 month ago)
- Language: JavaScript
- Size: 1.18 MB
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 5
-
Metadata Files:
- Readme: readme.md
- Funding: .github/FUNDING.yml
- License: license
Awesome Lists containing this project
README
[](https://www.npmjs.com/package/@gullerya/just-test)
[](https://opensource.org/licenses/MIT)[](https://github.com/gullerya/just-test/actions/workflows/quality.yml)
[](https://codecov.io/gh/gullerya/just-test)[](https://www.codacy.com/app/gullerya/just-test)
# Summary
`just-test` is an all-JS platforms oriented test runner strongly opinionated towards testing libraries, frameworks and components.
TODO
#### Highlights:
- running tests in __browser__, no server needed, import/link your code (static files) and just test, literally __TDD__ oriented
- __re-running__ any test in browser ad-hoc - convenient for debugging and developing on the fly
- friendly __UI__ on top of the page of the tests, allows immediatelly observe the behavior of the code and the test
- running tests from __NodeJS__ via headless browser (chromium, firefox, webkit) to run in __CI/CD automation__
- generating __test results__ report (types: __xUnit__)
- collecting __coverage__ and generating report (types: __lcov__)
- flexible yet simple ability to run tests in __sync__ as well as __async__ (default) manner
- in general, a lot of attention was paid to create __simple and usable__ framework even for a not-so-simple cases, like asynchronous tests etc> Attention: the doc below is still in construction, more updates and detailed one will be published very soon!!!
> Meanwhile, the best way to actually see how the library should be used is it look onto its own tests in `tests` folder, and for CI/CD case - `travis.yml` is a good start.# CI readiness
TODO - move to features
* run your tests in CI in the following browsers: Chromium (covering all based upon), Firefox, WebKit
* test report types: `xUnit`
* coverage report types: `lcov`# Examples
TODO
# API
TODO