Releases: japa/core
Fixing skip in CI
- chore(package): update dependencies d83c47c
Dropping support for Node 8&9
Moving forward, Japa support Node.js 10.15.3
and above. It was required to keep the dependencies up to date and free from vulnerabilities.
Big bang re-write 🎉
Japa 2.0 is out with a Big Bang re-write. The end-user API is more or less same. However, the core has been moved to Typescript and is smaller, and faster than earlier.
Big wins
-
Moved to Typescript. Which means, now you can enjoy autocomplete when writing tests.
-
The core is simpler, leaner and marginally faster than the older versions.
-
In-built support to run multiple test files, without any CLI.
Improvements
-
The flow of tests and hooks is more streamlined and explained here.
-
Now tests relying on
done
callback, can also use theawait
keyword.test('process one job at a time', async (assert, done) => { queue.on('job', (data) => { assert.deepEqual(data, {}) done() }) await queue.run() })
-
Better support for
grep
. Earlier it has to be a substring of the test title. Now you can defineRegExp
too.const { configure } = require('japa') configure({ grep: 'users' }) // or regex like string configure({ grep: 'user(s)?' }) // even regex configure({ grep: /user(s)?/ })
Breaking changes
- The need of japa-cli has been removed. We recommend using a
master test file
and configure the tests using the configure method. - Calling
test.timeout
at a global level doesn't work anymore and again theconfigure
method can be used to define the global timeout for all the tests. - The module
japa/cli
has been removed. This was used by the CLI to interact with the Japa core and hence is not required. - The structure of
japa/api
has been changed too.
First Version
The first version with all the goodness