Closed greenkeeper[bot] closed 6 years ago
Merging #191 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #191 +/- ##
=======================================
Coverage 92.94% 92.94%
=======================================
Files 9 9
Lines 241 241
=======================================
Hits 224 224
Misses 17 17
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update a16058f...4854d01. Read the comment docs.
Update to this version instead 🚀
This 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 be any
4a769f8test()
so macros are compatible with the latest flow-bin
e794e73We 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 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
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
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
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.0
3f81fc4
Limit concurrency to 2 in a CI environment
1cb9d4f
Adjust NODE_PATH test to fix linting issue
1ea758f
Only display timestamp in verbose logger if watch mode is active (#1557)
c72f4f2
Include anonymous functions in stacktraces (#1508)
eebf26e
Add Awesome mentioned badge
f43d5ae
Recipe instructions for making jQuery available in browser (#1543)
68ce4b8
Update tsconfig.json docs link in the TS recipe
837b0dd
Fix TypeScript recipe typo (#1549)
2349316
Update package-lock with changes in #1407
bb91862
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 fixtures
fa4f73c
Update to npm@5.4.2
There are 30 commits in total.
See the full diff
Version 0.20.0 of ava just got published.
The version 0.20.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.20.0Today’s release is very exciting. After adding magic assert and snapshot testing we found that these features sometimes disagreed with each other.
t.deepEqual()
would returnfalse
, yet AVA wouldn’t show a diff. Snapshot tests cared aboutSet
order butt.deepEqual()
didn’t. @novemberborn came to the realization that comparing and diffing object trees, and doing so over time with snapshots, are variations on the same problem. Thus he started ConcordanceJS, a new project that lets you compare, format, diff and serialize any JavaScript value. This AVA release reaps the fruits of his labor.Highlights
More magical asserts
Magic assert will now always show the difference between actual and expected values. If an unexpected error occurs it’ll print all (enumerable) properties of the error which can make it easier to debug your program.
More details of an object are printed, like the constructor name and the string tag. Buffers are hex-encoded with line breaks so they’re easy to read:
t.deepEqual()
improvementst.deepEqual()
andt.notDeepEqual()
now useconcordance
, rather thanlodash.isequal
. This changes what values AVA considers to be equal, making thet.deepEqual()
assertion more predictable. You can now trust that all aspects of your objects are compared.Object wrappers are no longer equal. The following assertion will now fail:
For
Map
andSet
objects to be equal, their elements must now be in the same order:With this release AVA will compare all enumerable properties of an object. For an array this means that the comparison considers not just the array elements. The following are no longer considered equal:
The same goes for
Map
andSet
objects, errors, and so forth:You used to be able to compare
Arguments
object to an object literal:Instead you must now use:
(Of course you can still compare
Arguments
objects to each other.)New in this release is the ability to compare React elements:
Snapshot improvements
Snapshots too now use
concordance
. This means values are compared with the snapshot according to the same rules ast.deepEqual()
, albeit with some minor differences:Argument
objects can only be compared toArgument
objectsNote that Node.js versions before 6.5 cannot infer names of all functions . AVA will pass a snapshot assertion if it determines the name information is unreliable.
AVA now saves two files when snapshotting. One, ending in the
.snap
extension, contains a compressed serialization of the expected value. The other is a readable Markdown file that contains the snapshot report. You should commit both to source control. The report file can be used to see what is in your snapshots and to compare snapshot changes over time.Try it out with our snapshot example! Or check out an example snapshot report.
The snapshot file location now follows your test layout. If you use a
test
folder, they’ll be placed intest/snapshots
. With__tests__
they’ll be placed in__tests__/__snapshots__
. And if you just have atest.js
in your project root the snapshot files will be written totest.js.snap
andtest.js.md
. You may have to manually remove old snapshot files after installing this new AVA version. ebd572aImproved snapshot support in watch mode
In watch mode, AVA now watches for changes to snapshot files. This is handy when you revert changes while the watcher is running. Snapshot files are correctly tracked as test dependencies, so the right tests are rerun. Typing
u
, followed byEnter
updates the snapshots in the tests that just ran. (And the watcher won’t rerun tests when snapshots are updated.) 87eef84 dbc78dc f507e36 50b60a1Node.js 8 support
AVA 0.19 already worked great with Node.js 8, and we’ve made it even better by removing unnecessary Babel transpilations in our
stage-4
preset. We’re now also forwarding the--inspect-brk
flag for debugging purposes. e456951 a868b02New and improved recipes
We’ve added new recipes and improved others:
browser-env
c01ac05Miscellaneous
--concurrency
without a value now causes AVA to exit with an error 8c35a1at.throws()
with a resolved promise now prints a helpful error message dfca2d9t.title
accessor has been documented. 549e99bAll changes
v0.19.1...v0.20.0
Thanks
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 63 commits.
854203a
0.20.0
652705b
Add more screenshot fixtures
9d3b1ba
Deep update of XO and its dependencies
8d09ba5
Link to ava-snapshot-example
2360256
Redo all of the screenshots
589489d
Meta tweaks
f507e36
Add command for updating snapshots in watch mode (#1413)
87eef84
Automatically watch for snapshot changes
a141033
concordance@2
f62c137
Update readme
0e82f8f
Add integration test for appending to an existing snapshot file
ebd572a
Determine snapshot directory by where the test is located
dbc78dc
Treat loaded snapshot files as test dependencies
50b60a1
Track snapshot files touched during test run, ignore in watcher
6d3c279
Include dirty sources in watcher debug output
There are 63 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: