Closed greenkeeper[bot] closed 7 years ago
Update to this version instead ๐
There's but a few commits in this release, but we've made a big change to how AVA manages its test workers ๐ฉ๐ผโ๐ฌ๐จ๐ผโ๐ญ๐จ๐ฟโ๐๐จ๐ปโโ๏ธ๐ฉ๐ฝโ๐ผ.
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 concurrency
option in AVA's package.json
configuration, or by passing the --concurrency
flag. We've also beefed up input validation on that flag. b6eef5a
Unfortunately this does change how test.only()
behaves. AVA can no longer guarantee that normal tests won't run. For now, if you want to use test.only()
, you should run tests from just that file. We have an open issue to add an --only
flag, which will ensure that AVA runs just the test.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 to stdout
like console.log
. 14f7095
t.notThrows()
example has been clarified 57f5007We 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 10 commits.
dd9e8b2
0.22.0
b6eef5a
Fail hard when --concurrency
is set to invalid values (#1478)
57f5007
Fix typo in t.notThrows
example (#1486)
d8c21a6
Update debugging with webstorm recipe (#1483)
14f7095
Implement t.log() (#1452)
e28be05
Fixed makeApp() in endpoint testing recipe (#1479)
465fcec
Limit concurrency to the number of CPU cores (#1467)
4eea226
Use --verbose when testing CLI output (#1477)
a0d5b37
Simplify readme avatar URLs
31b1380
Add tests for improper-usage-messages (#1462)
See the full diff
Version 0.21.0 of ava just got published.
The version 0.21.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.21.0This is primarily a bug fix release, but some features did sneak in:
npm
2b4e35dThis release includes the following patches:
t.deepEqual()
and magic assert diffs 9e4ee3fBuffer
APIs that are unavailable in Node.js releases older than 4.5 d0fc8c9t.throws()
promise return value to beany
4a769f8test()
so macros are compatible with the latestflow-bin
e794e73Thanks
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 17 commits.
a1afbe3
0.21.0
f9b865a
Update safe-buffer in package-lock.json
d0fc8c9
Avoid directly using newish Buffer APIs (#1448)
9e4ee3f
Upgrade concordance (#1450)
761f7f7
Update expected package.json version in readme (#1449)
e794e73
Resolve strict checking of function call arity (#1441)
1cbcb06
Revert "Handle package-lock.json churn"
8d981bf
Handle package-lock.json churn
c09462c
Assume npm 5.2.0 during development and CI
2b4e35d
Add an additional npm-based recipe for Jetbrains IDEs (#1444)
4a769f8
Update flow def for AssertContext.throws to match typescript def (#1443)
3f6e134
Include raw actual and expected objects in AssertionError (#1432)
0069a7e
Remove non-existent npm run script in maintaining.md (#1434)
e58e96e
Minor readme tweak (#1422)
5ae434a
Bump dependencies
There are 17 commits in total.
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: