ava changelog

Changelog History

Page 4

• v2.0.0-rc.1 Changes

  May 28, 2019

  🚀 ⚠️ If you're looking to upgrade from 1.4.1, make sure to read the Beta 1 and Beta 2 release notes.

  👌 Support for the new test & helper file selection in our ESLint plugin

  👕 AVA now exposes some methods to our ESLint plugin, allowing our plugin to support the new test & helper file selection. 51433be

  🔧 Configurable object printing depth

  AVA now uses the util.inspect.defaultOptions.depth option when printing objects. 98034fb

  All changes

  v2.0.0-beta.2...v2.0.0-rc.1

  Thanks

  Thank you @grnch. We couldn't have done this without you!

  Get involved

  We welcome new contributors. AVA is a friendly place to get started in open source. We have a great articleon getting started contributing and a comprehensive contributing guide.

• v2.0.0-beta.2 Changes

  May 19, 2019

  🚀 ⚠️ If you're looking to upgrade from 1.4.1, make sure to read the Beta 1 release notes.

  💥 Breaking changes

  • ⚡️ Test implementations may return observables. We've updated our TypeScript definition to require these to have a Symbol.observable function. c2d8218

  ✅ Test file and helper selection

  ✅ AVA now also selects files ending with .spec.js when looking for tests. 08e99e5

  You can now specify custom globs to select helper files:

  { "ava": { "helpers": ["\*\*/helpers/\*\*/\*"] } }
  

  🛠 Bugfixes

  • 👷 The dependency tracking in watch mode now respects custom require hooks you install in the worker processes. Thanks @lo1tuma! cb4c809
  • ✅ The TypeScript definition once again allows test.skip(macro) ba5cd80

  All changes

  v2.0.0-beta.1...v2.0.0-beta.2

  Thanks

  Thank you @StoneCypher, @LukasHechenberger, @lo1tuma, @htor and @alexisfontaine. We couldn't have done this without you!

  Get involved

  We welcome new contributors. AVA is a friendly place to get started in open source. We have a great articleon getting started contributing and a comprehensive contributing guide.

• v2.0.0-beta.1 Changes

  April 29, 2019

  💥 Breaking changes

  AVA now requires at least Node.js 8.9.4

  🚀 Per the Node.js release schedule, the 6.x releases reach end of live on April 30th. Consequently we've removed support in AVA. We are now testing with Node.js 12 though. 3a4afc6

  ✅ Test file and helper selection

  We've been working on simplifying how test files and helpers are selected. First off, the files option now only accepts glob patterns. If you configured it with directories before, please add /**/* to get the previous behavior.

  🔧 The files and sources options must now be arrays containing at least one pattern. It's no longer possible to override a default exclusion pattern, but we're looking at making these configurable separately.

  🚀 AVA used to treat all files inside a helpers directory as test helpers. Finding these files could be really slow, however, and it also meant you couldn't have tests inside a helpers directory. Instead we're going to let you specify glob patterns to find these helpers. That work hasn't landed yet. For now, if you have such helpers we'd advise to not upgrade to this release.

  ✅ Test files starting with an underscore are still recognized as helpers.

  ✅ Files inside fixtures directories are no longer ignored, and will now be treated as test files. The watcher now also watches ava.config.js files.

  The CLI now only takes file paths, not glob patterns.

  ⚡️ We'd like some help updating our ESLint plugin as well.

  Snapshots in CI

  ⚡️ When you run tests locally and add a new snapshot, AVA automatically updates the .snap file. However if you forget to commit this file and then run your CI tests, they won't fail because AVA quietly updates the .snap file, just like it does locally.

  🚀 With this release, AVA will fail the t.snapshot() assertion if it is run in CI and no snapshot could be found. 0804107

  Assertion messages must be strings

  👀 AVA now enforces assertion messages to be strings. The message is only used when the assertion fails, and non-string values may cause AVA to crash. You may see test failures if you were accidentally passing a non-string message. 49120aa

  Flow type definitions

  🚚 We've decided to remove the Flow type definitions from AVA itself. We don't have anybody to maintain them and consequently they've become a blocker when adding features to AVA. c633cf0

  We've set up a new repository from which we'll publish the definitions, but we need your help setting it up. If you use AVA and Flow, please join us in avajs/flow-typed#1.

  Other changes

  • We've added UntitledMacro and UntitledCbMacro types, for macro functions that will never have a .title function. Though really this just helped simplify the type definition. Thanks @qlonik! ebf4807

  All changes

  v1.4.1...v2.0.0-beta.1

  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.

• v1.4.1 Changes

  March 24, 2019

  Focusing power-assert

  AVA comes with power-assert built-in, giving you more descriptive assertion messages. However it's been confusing to understand which assertions come with power-assert. To address this we've added the new t.assert() assertion. It's now the only assertion that is power-assert enabled. The assertion passes if called with a truthy value. Consider this example:

  test('enhanced assertions', t =\> { const a = /foo/; const b = 'bar'; const c = 'baz'; t.assert(a.test(b) || b === c); });
  

  AVA will output: 6: const c = 'baz'; ✅ 7: t.assert(a.test(b) || b === c); 8: }); Value is not truthy: false ✅ a.test(b) || b === c => false b === c => false c => 'baz' b => 'bar' ✅ a.test(b) => false b => 'bar' a => /foo/

  ⚡️ Our ESLint plugin has been updated to support this new assertion. Many thanks to @eemed for implementing this! 9406470

  Watch mode

  🖨 Watch mode now prints the available commands. Thanks @KompKK! cd256ac

  🐛 Bug fixes

  • ✅ Filtered tests (when using --match, .skip() or .only()) are no longer included in the list of pending tests when timeouts occur or when you interrupt a test run. Thanks @vancouverwill! 23e302a
  • 👷 We're now shimming all TTY methods in the worker processes, thanks to @okyantoro. c1f6fdf

  📚 Documentation updates

  • ✅ We've added a note to say that, by default, AVA does not have a default test timeout. Thanks @amokmen! 99a10a1

  All changes

  v1.3.1...v1.4.1

  Thanks

  Thank you @eemed, @KompKK, @vancouverwill, @okyantoro and @amokmen. We couldn't have done this without you!

  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.

• v1.4.0

  March 24, 2019

• v1.3.1 Changes

  March 05, 2019

  🐛 Bug fixes

  • We've fixed a rather embarrasing bug with t.throws() and t.throwsAsync(). If you'd set a code expectation to a number we never actually checked that the thrown error had such a code! Thanks to @qlonik for both spotting and fixing this. 82daa5e
  • 📦 1.2.0 contained a regression which meant that if you faked clearTimeout(), you'd break AVA. That's now been fixed. 40f331c
  • Snapshot files are now recognized as source files, so if you're using watch mode and you delete one, AVA won't rerun all your test files. d066f6f

  🆕 New features

  You can now use require() in ava.config.js files to load non-ES modules. 334e15b

  All changes

  v1.2.1...v1.3.1

  Thanks

  🚀 Thank you @itaisteinherz, @jdalton, @kagawagao, @KompKK, @SleeplessByte, @Chrisyee22 and @qlonik for helping us with this release. We couldn't have done this without you!

  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.

• v1.3.0

  March 05, 2019

• « First
• ‹ Prev
• 1
• 2
• 3
• 4