This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request updates dependency ava from version
0.18.1
to0.18.2
Changelog
0.18.2 / 2017-02-18
`flow check` is easily taking 30 seconds on my development machine,
presumably it's checking too many files. Move the .flowconfig into
the flow-types test directory and only include the index.js.flow file
to improve check speed.
Fixes #1233. Our assertions don't call toJSON(), so we shouldn't use
it either when displaying actual and expected values.
This allows errors from the exit logic to propagate to the runner.
Errors that occur inside the runner are treated as uncaught exceptions.
This prevents them from being swallowed in the promise chain, causing
the test to hang.
Fixes #1270.
Don't show code excerpts for dependencies or code outside the project
directory. Determine where the source lives when serializing the error.
Then, when excerpting the code, bail if it lives outside the project
or is a dependency.
We no longer rewrite paths. Mentioning future uses seems unnecessary. What's left is implicitly covered elsewhere.
The watcher would break if logger.finish() threw an exception. Instead
rethrow this error (which causes the process to exit).
Tests don't need to be ended when a promise is returned.
Test plans are not necessary if all assertions occur within the returned
promise chain. Exceptions will still fail the test.
This makes it easier to inspect the code coverage during development.
Stub process.stderr.write(), rather than just spying on it. Otherwise
'resultresult' gets written to the stderr while the tests run.
We're ending up compiling all helper-like files in AVA's test/
directory, which is unnecessary.
directory of the user's project.
process.cwd() in the code even though it's never actually used.
Closes #1003.
Closes #1224.
This adds flow-bin, adds it to the test running script, and adds some regression tests based on prior issues.
In an immediate proof of value (and proof of my own prior sloppiness) it spotted an issue that #1219 sought to fix and did not do so. Fix included along with test.
Instead of double-defining each of these, define them once while using overloading.
Also took some liberties to improve the definition. Specifically, ava doesn't care what values these throwing functions return, but doesn't produce a return value.
Fixes #1148