Closed greenkeeper[bot] closed 6 years ago
coveralls
commented
7 years ago Coverage remained the same at 100.0% when pulling 0bea2d31787a8e33281c4621ad3f4650b0cfb7ce on greenkeeper/ava-0.22.0 into 5b49bcb765132c01da709837c110db1fa303eb40 on master.
greenkeeper[bot]
commented
7 years ago Update to this version instead 🚀
NODE_ENV=test AVA will now set process.env.NODE_ENV to 'test', as long as the NODE_ENV environment variable has not already been set. 42e7c74
Snapshots are stored alongside your test files. This is great when your test file is executed directly but say if you're using TypeScript to precompile your test file AVA would store the snapshots in your build directory. In this release, if source maps are available, AVA determines the original test file location and uses that to store the snapshots.
You can also specify where snapshots are stored through the snapshotLocation option in the package.json file. 7fadc34
--match='*' now matches all tests, including those without a title. 1df502d
2 in CI environments 3f81fc4Bluebird.longStackTraces(). If you're using Bluebird you may want to call this yourself using a require script. ebf78b3 61101d9t.log() is now supported in the Flow and TypeScript type definitions 64b7755t.title is now supported in the TypeScript type definitions 3c8b1bet.snapshot() now has a better Flow type definition ded7ab8We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
The new version differs by 30 commits.
3b81e2c 0.23.03f81fc4 Limit concurrency to 2 in a CI environment1cb9d4f Adjust NODE_PATH test to fix linting issue1ea758f Only display timestamp in verbose logger if watch mode is active (#1557)c72f4f2 Include anonymous functions in stacktraces (#1508)eebf26e Add Awesome mentioned badgef43d5ae Recipe instructions for making jQuery available in browser (#1543)68ce4b8 Update tsconfig.json docs link in the TS recipe837b0dd Fix TypeScript recipe typo (#1549)2349316 Update package-lock with changes in #1407bb91862 Version warning when local version is behind (#1407)42e7c74 Set NODE_ENV to to 'test' if not already set (#1523)64b7755 Add t.log() for Flow and TypeScript (#1538)8955e15 Lint test fixturesfa4f73c Update to npm@5.4.2There are 30 commits in total.
See the full diff
greenkeeper[bot]
commented
6 years ago Update to this version instead 🚀
This is a pretty small release, but a great one if you're solely developing for Node.js 8.3 or above.
You can now use object rest/spread properties in test files without any further Babel configuration. Note that if you're running tests on older versions of Node.js you'll still need to add the relevant Babel plugins, since this new language feature has not yet reached stage 4. 37c9122
t.is() values are deeply equal but not the same c41b2afWe welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
The new version differs by 12 commits.
e401bd1 0.24.08141395 Churn and dedupe package-lockf2979a3 Bump dependenciesefc3b31 Code style tweakscb1c3f7 Fix documentation of snapshotDir optionc41b2af Provide feedback when t.is() values are deeply equal but not the same1cd3a04 Don't run before and after hooks when all tests are skippedf98a881 Document how to title macros when using TypeScriptb3c4090 Fix broken link in contributing guide37c9122 Include syntax-object-rest-spread in default Babel options for Node.js >= 8.3.0035fd31 Verify package-lock when linting37e8b49 Use babel-generator to regenerate enhanced assertion statementsSee the full diff
greenkeeper[bot]
commented
6 years ago Update to this version instead 🚀
The new version differs by 15 commits.
a051d3e 0.25.04f896c2 Make t.log() behave more like console.log()f00f3c4 Don't set Error.stackTraceLimit in worker processesc2b42ec Mention #1319 as a pitfallbcb77fc Recommend skipFiles for VSCode debuggingcd8c91b Add more clarification for different Babel config in .babelrc.md (#1642)947f207 Update code-excerpt to ^2.1.14a13966 Debug serially in the "Debugging tests with VS Code" recipe (#1634)aaddc37 Use absolute source map paths in precompiled files72c53be support @std/esm (#1618)29e5dfd Add TS types for t.snapshot(content, options)c1faf95 Fix typo in precompiling-with-webpack.md (#1625)4e8f827 Switch time-require to @ladjs/time-require965cbc6 Use supertap to generate TAP output (#1610)4124d77 Update npm, test Node.js 9, detect package-lock churn in CI (#1601)See the full diff
Version 0.22.0 of ava just got published.
The version 0.22.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ava. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
0.22.0There's but a few commits in this release, but we've made a big change to how AVA manages its test workers 👩🏼🔬👨🏼🏭👨🏿🚀👨🏻⚕️👩🏽💼.
Highlights
Default concurrency
We now cap the number of concurrent workers to the number of CPU cores on your machine. Previously AVA started workers for each test file, so if you had many test files this could actually bring things to a halt. 465fcec
You can still customize the concurrency by setting the
concurrencyoption in AVA'spackage.jsonconfiguration, or by passing the--concurrencyflag. We've also beefed up input validation on that flag. b6eef5aUnfortunately this does change how
test.only()behaves. AVA can no longer guarantee that normal tests won't run. For now, if you want to usetest.only(), you should run tests from just that file. We have an open issue to add an--onlyflag, which will ensure that AVA runs just thetest.only()tests. If you'd like to help us with that please head on over to #1472.t.log()We've also added
t.log(), which lets you print a log message contextually alongside the test result, instead of immediately printing it tostdoutlikeconsole.log. 14f7095Miscellaneous
t.notThrows()example has been clarified 57f5007All changes
v0.21.0...v0.22.0Thanks
Get involved
We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.
Commits
The new version differs by 10 commits.
dd9e8b20.22.0b6eef5aFail hard when--concurrencyis set to invalid values (#1478)57f5007Fix typo int.notThrowsexample (#1486)d8c21a6Update debugging with webstorm recipe (#1483)14f7095Implement t.log() (#1452)e28be05Fixed makeApp() in endpoint testing recipe (#1479)465fcecLimit concurrency to the number of CPU cores (#1467)4eea226Use --verbose when testing CLI output (#1477)a0d5b37Simplify readme avatar URLs31b1380Add tests for improper-usage-messages (#1462)See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: