This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
The current working directory in test files changed (BREAKING)
We made the hard decision of changing the current working directory (process.cwd()) in test files to be the same directory as package.json. It was previously the same as __dirname (the directory of the test file). Having process.cwd() equal __dirnamefelt like a good idea at the time, but as the popularity of AVA grew, people started hitting issues with it.
This affects users that have test files in a sub-folder and are using relative paths. If you have your test files in the same directory as package.json, you're fine.
The fix is to wrap all relative paths in path.join(__dirname, 'relative-path') to make them absolute.
Here's an example of what needs changing. The below file and unicorn.txt are both in ./test/.
The next minor version of AVA, 0.18.0, will drop support Node.js 0.10 and 0.12. We'll continue fixing critical issues for this version until the end of the year. Time to upgrade if you haven't. (Discussion: #1051)
Highlights
We now have a script to automatically migrate from tape to AVA.
Reduced transpilation on Node.js >=4. AVA now only transpile what's needed for Node.js 4 when on it or higher, which should result in better performance and stacktraces. 4025d81
Removed the --require CLI flag. Configure it in package.json instead. 17119bc
Switched to lodash.isEqual for deep equality checking (t.deepEqual() & t.notDeepEqual()). This might make your test fail if our previous deep equality check was too loose. 8856684
Improvements to the test failure output. e4f90e0 (We're currently working on many more improvements in this area. Stay tuned.)
Correctly cleanup stacktraces on Node.js 6 and higher. 26bcab0
Removed t.doesNotThrow() as it was renamed to t.notThrows(). It was deprecated far back in AVA 0.12.0. e448798
Deprecated t.error() alias for t.ifError(). It will be removed in AVA 1.0.0. Just use t.ifError(). 28bb0d5(We have an automatic migration script if you're using t.error())
Ensures test files load correct AVA installation. This means you can now run AVA with an absolute path and it will still use the local AVA installation at that path if available. 3ea2ba1
Added support for debugging tests with WebStorm and added a recipe. c268c8d
Hello lovely humans,
ava just published its new version 0.17.0.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
The current working directory in test files changed (BREAKING)
We made the hard decision of changing the current working directory (
process.cwd()) in test files to be the same directory as package.json. It was previously the same as__dirname(the directory of the test file). Havingprocess.cwd()equal__dirnamefelt like a good idea at the time, but as the popularity of AVA grew, people started hitting issues with it.This affects users that have test files in a sub-folder and are using relative paths. If you have your test files in the same directory as package.json, you're fine.
The fix is to wrap all relative paths in
path.join(__dirname, 'relative-path')to make them absolute.Here's an example of what needs changing. The below file and
unicorn.txtare both in./test/.Let us know if anything is unclear or if you're having problems.
Commit: 476c653
Node.js version support
The next minor version of AVA, 0.18.0, will drop support Node.js 0.10 and 0.12. We'll continue fixing critical issues for this version until the end of the year. Time to upgrade if you haven't. (Discussion: #1051)
Highlights
--requireCLI flag. Configure it in package.json instead. 17119bclodash.isEqualfor deep equality checking (t.deepEqual()&t.notDeepEqual()). This might make your test fail if our previous deep equality check was too loose. 8856684power-assert. 24a38act.doesNotThrow()as it was renamed tot.notThrows(). It was deprecated far back in AVA 0.12.0. e448798t.error()alias fort.ifError(). It will be removed in AVA 1.0.0. Just uset.ifError(). 28bb0d5 (We have an automatic migration script if you're usingt.error())All Changes
v0.16.0...v0.17.0
The new version differs by 51 commits .
b24495d0.17.0056f227bump dev dependencies and make XO happy26bcab0temp fix for Node.js internal stack traces showing2d04763Add docs for test parameter need to be namedt(#1096)59254b7Use current working directory if nopackage.json(#1044)3c3a6d8add XO badgee0a170bSpeed up CI (#1076)257b34dUpgrade XO (#1080)3ea2ba1Ensure test files load correct AVA installation (#1085)476c653Change the current working directory of tests to be the same directory as package.json (#1074)1b214beclean up caching precompiler (#1077)6165a23linting: turn off theno-use-extend-nativerulee10338eUpdate readme.md (#1075)dae3a44make XO happyc258d03Fix link to configuration in readme (#1073)There are 51 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade