Update dependency ava to v3 - autoclosed #6

renovate · 2020-02-08T22:56:27Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ava (source)	`^2.1.0` -> `^3.0.0`

Release Notes

avajs/ava

`v3.15.0`

Compare Source

Automatic snapshot file removal

When you stop using snapshots in a test file, the next time you run ava --update-snapshots we'll remove the left-over snapshot files. Thanks @ninevra! 4f093ab

TAP improvements

@tymfear has been on a roll improving our TAP reporter. t.log() output is now compliant with the spec 99ab93a. Tests that did not run due to timeouts are now reported 98595da.

Next-generation configuration

AVA 4 will add full support for ESM configuration files as well as allowing you to have asynchronous factory functions a2f2614. If you're using Node.js 12 or later you can opt-in to these features in AVA 3 by enabling the nextGenConfig experiment. Say in an ava.config.mjs file:

export default {
	nonSemVerExperiments: {
		nextGenConfig: true
	},
	files: ['unit-tests/**/*]
};

This also allows you to pass an .mjs file using the --config argument.

With this experiment enabled, AVA will no longer have special treatment for ava.config.js files. Instead AVA follows Node.js' behavior, so if you've set "type": "module" you must use ESM, and otherwise you must use CommonJS.

You mustn't have an ava.config.mjs file next to an ava.config.js or ava.config.cjs file.

See avajs/ava@v3.14.0...v3.15.0 for all changes.

`v3.14.0`

Compare Source

Snapshot ordering

With this release, snapshot files are now ordered based on test declaration, not completion. This makes it easier to compare the human-readable reports to your test file, and also stops the .snap from changing when the reports themselves don't. You'll want to rebuild snapshots after upgrading to this release to isolate any changes. Thanks @ninevra! e66b54c

Shared workers

We’ve been working on making AVA more extensible. One major step on this path is our new shared worker support: run code in the main process, communicate with test workers and influence execution. Find out more in our shared workers recipe.

See avajs/ava@v3.13.0...v3.14.0 for all changes.

`v3.13.0`

Compare Source

t.passed can now be used in tests and teardown functions. Thanks @tymfear! 900dc6d
In AVA 4, you'll no longer be able to pass null as the expectation for t.throws() & t.throwsAsync(). You can opt in to this early by enabling the disableNullExpectations experiment. Thanks @JSimoni42! f328a69
The Enzyme recipe has been updated. Thanks @jonathansamines! db5d2c3
The TypeScript recipe has been updated. Thanks @SephReed! a3379fa

See avajs/ava@v3.12.1...v3.13.0 for all changes.

`v3.12.1`

Compare Source

Configure how AVA loads test files

Normally, AVA loads all files as CommonJS, except for mjs files and if you've configured "type": "module" in your package.json.

As an experiment, you can now configure how AVA loads other file extensions. This is useful if you want to use Node.js' experimental loaders feature. Read more in our documentation. Thank you @macarie for working on this! 5c9dbb9

Comparison bugfix

There was a bug in our comparison library which meant that negative-index properties on lists were not compared. This was fixed in a patch release, which will definitely be installed when you install AVA 3.12. Your tests may have been passing, even though they should have been failing. They'll fail now. Snapshots may also be different, causing tests to fail.

All changes

See avajs/ava@v3.11.1...v3.12.1 for all changes.

Thank you @AnthumChris for making sure our ESM example used ESM syntax (20bc781).

`v3.12.0`

Compare Source

`v3.11.1`

Compare Source

This release fixes corrupted output of the default reporter when test or program code writes to standard out. 5ddc9fd

Also, thanks to @jonathansamines we've taken another step to using AVA to test AVA. 1150991

See avajs/ava@v3.11.0...v3.11.1 for all changes.

`v3.11.0`

Compare Source

New `t.like()` assertion

Thanks to @futpib we now have a t.like() assertion 19c4f35:

In the following example, the map property of value must be deeply equal to that of selector. However nested.qux is ignored, because it's not in selector.

t.like({
	map: new Map([['foo', 'bar']]),
	nested: {
		baz: 'thud',
		qux: 'quux'
	}
}, {
	map: new Map([['foo', 'bar']]),
	nested: {
		baz: 'thud',
	}
})

Read more in the t.like() assertion documentation.

This assertion was previously introduced as an experiment.

VSCode 1.47 debugging improvements

You can now debug tests using the new JavaScript Debug Terminal in VSCode 1.47. We've updated our debugging recipe accordingly. Thank you @connor4312 for the documentation updates and your work on VSCode! bc39bcc

All changes

See avajs/ava@v3.10.1...v3.11.0 for all changes.

`v3.10.1`

Compare Source

It's time for another AVA release 🎉

Restricting when you can update snapshots

When executing a subset of tests, through --match or or .only() or .skip(), you can no longer also update snapshots. This prevents you from accidentally deleting snapshots. Thank you @bunysae for putting this together. f72fab4

If you are skipping a test that you can't immediately fix, but you still need to update snapshots, use .failing() instead.

Support for message strings in `t.timeout()` calls

Thanks to @jonathansamines you can now provide a message string when using t.timeout(). This can be useful if your test depends on some other setup that may not have been completed: ca8ea45

test('foo', t => {
	t.timeout(100, 'make sure database has started');
	// Write your assertions here
});

`t.try()` does not work in hooks

t.try() has never worked in hooks, but thanks to @okyantoro it now fails properly instead of crashing. d01db61

`t.snapshot()` does not really work in hooks either

t.snapshot() sort of works in hooks, but we'll be removing this in AVA 4. You can opt in to this behavior by enabling the disableSnapshotsInHooks experiment. Again thank you @okyantoro d01db61.

Fixed TypeScript definition for `t.like()`

The experimental t.like() assertion should now work better with TypeScript.

New experiments!

Thanks to @futpib we now have an experimental t.like() assertion 19c4f35:

In the following example, the map property of value must be deeply equal to that of selector. However nested.qux is ignored, because it's not in selector.

t.like({
	map: new Map([['foo', 'bar']]),
	nested: {
		baz: 'thud',
		qux: 'quux'
	}
}, {
	map: new Map([['foo', 'bar']]),
	nested: {
		baz: 'thud',
	}
})

Read more in the t.like() assertion documentation and let us know what you think.

@yjpa7145 has contributed an experiment to reverse the order in which t.teardown() functions are run, so that the last registered function is called first 952a017. This will be the behavior in AVA 4.

To enable both these experiments update your AVA configuration:

package.json:

{
	"ava": {
		"nonSemVerExperiments": {
			"likeAssertion": true,
			"reverseTeardowns": true
		}
	}
}

ava.config.js:

export default {
	nonSemVerExperiments: {
		likeAssertion: true,
		reverseTeardowns: true
	}
}

Reporter changes

@Michael55555 has helped us combine our reporter code into a single file b3866b6. We've also made some other tweaks and improvements baaf99a. Let us know if anything seems amiss.

Improved diffs

@bunysae made it so that missing or extraneous objects in diffs are printed with extra depth https://github.com/concordancejs/concordance/pull/62.

Farewell Node.js 13

Node.js 13 has reached end-of-life. Per our support statement we have removed it from our test matrix and supported version list.

All changes

See avajs/ava@v3.8.2...v3.9.0 for all changes. Thank you @paulrobertlloyd and @Autre31415 for contributing documentation improvements.

`v3.8.2`

Compare Source

Fix bad dependency fd92b4a
Use configured depth limit for diffs in assertion failures, thanks @bunysae! a5385a4

`v3.8.1`

Compare Source

Node.js 14 support

Great news, this is a feature heavy release!

First off, though, AVA now officially supports Node.js 14. Thank you @zackschuster! 2e7c76b

Run tests at specific line numbers

AVA can now run tests at specific line numbers! 🎉

Given the following test file:

test.js

1: test('unicorn', t => {
2:   t.pass();
3: });
4:
5: test('rainbow', t => {
6:  t.fail();
7: });

Running npx ava test.js:2 for would run the unicorn test. In fact you could use any line number between 1 and 3.

This feature is only available from the command line. It won't work if you use tools like ts-node/register or @babel/register, and it does not currently work with @ava/babel and @ava/typescript. See https://github.com/avajs/ava/issues/2473.

Thank you @ulken for your hard work and patience to get this shipped. 1222ce9

Test-specific teardown functions

Sometimes tests have side-effects you want to clean up. @ulken has implemented t.teardown() which lets you register teardown functions within your test. They'll run once your test has finished, even if it failed: 75cbc3b

test('read file', t => {
	fs.writeFileSync('file.txt', '👋');
	t.teardown(() => fs.unlinkSync('file.txt');

	// Run assertions
});

Node.js internal in stack traces

Thanks to @bunysae, stack traces now include Node.js internals. Previously we removed them because we wanted you to focus on your own code, but quite often they do provide context. Now they're displayed, but somewhat dimmed. 9a9351d

Watch mode with the default reporter

Watch mode with the default reporter once again accepts key input. Thanks @pcdevil! 59c227d

ICYMI

afterEach() and afterEach.always() hooks can now determine whether the test passed. Thank you @bunysae for contributing this! 8f312c0

test('passes', t => t.pass());

test.afterEach(t => {
	if (t.passed) {
		// Do something because the test passed
	} else {
		// Do something because the test failed
	}
});

If you've ever wanted to save some files along with AVA's snapshots, you can now determine the directory path by accessing test.meta.snapshotDirectory. Thank you @ulken! cb5f9f7

All changes

See avajs/ava@v3.7.1...v3.8.1 for all changes.

`v3.8.0`

Compare Source

`v3.7.1`

Compare Source

Support parallel runs that do not need to run test files, courtesy of @micaelmbagira 26c8326

`v3.7.0`

Compare Source

If you've ever wanted to save some files along with AVA's snapshots, you can now determine the directory path by accessing test.meta.snapshotDirectory. Thank you @ulken ! cb5f9f7

See avajs/ava@v3.6.0...v3.7.0 for all changes.

`v3.6.0`

Compare Source

afterEach() and afterEach.always() hooks can now determine whether the test passed. Thank you @bunysae for contributing this! 8f312c0:

test('passes', t => t.pass());

test.afterEach(t => {
	if (t.passed) {
		// Do something because the test passed
	} else {
		// Do something because the test failed
	}
});

@mbiesiad has diligently translated our documentation to Polish. Thank you @kekuu for reviewing.

Also thank you @timgates42 for fixing a typo in our documentation. ede4f32

See avajs/ava@v3.5.0...v3.6.0 for all changes.

`v3.5.2`

Compare Source

`v3.5.1`

Compare Source

`v3.5.0`

Compare Source

When using ava debug, you can now specify the address or hostname the inspector is available through by using the --host option. Thanks to @DYefimov for contributing this! 13d6651

See avajs/ava@v3.4.0...v3.5.0 for all changes. Spoiler alert: it's just this one 😉

`v3.4.0`

Compare Source

Introducing the `t.try()` assertion

The new t.try() allows you to try assertions without causing the test to fail:

test('do the thing', async t => {
  const attempt = () => t.try(async tt => {
    const result = await getResult()
    // getResult() can be flaky and sometimes throws :(
    tt.is(result, 'expected')
  })
  
  const firstAttempt = await attempt()
  if (firstAttempt.passed) return firstAttempt.commit()
  
  t.log('Retrying (just once)')
  firstAttempt.discard()
  const secondAttempt = await attempt()
  secondAttempt.commit()
})

You can use any test implementation with t.try(), including (arrays of) macros. You can decide what to do with attempts. You can even run attempts concurrently, so long as they don't use snapshot assertions.

This is great building block for handling all kinds of advanced test scenarios. We can't wait to see what you'll do with it! Find out more in the assertion documentation.

This feature was previously behind an experimental flag. That flag has now been removed. If you have enabled the flag you'll have to update your AVA config. Also note that as of this release, attempt titles are always prefixed with the title of the parent test 7ee3a0e.

Once again, thank you @qlonik for contributing this new assertion.

In case you missed it: ESM support

As of the 3.3.0 release, AVA can load ESM test files! Check our updated ES Modules recipe for details.

Our ESM support is still incomplete. Progress is tracked in the ESM support project. Join us, won't you?

Other changes

The t.throws() and t.throwsAsync() assertions can now be called with undefined as the second argument. Previously, if you wanted to set an assertion message but did not want to provide any expectations for the thrown error you had to pass null. That's still allowed, of course. d0e2161 @stavalfi
ava.config.js files once again work with our @ava/typescript package f4d4edd
Our TypeScript definition no longer references @types/node 7a1dacf
We've improved the error message shown when test.cb() is used with asynchronous functions or observables f5a8c2b @toddkcarlson
The Vue recipe has been updated to use jsdom-global instead of browser-env 3f9c616 @Scrum
@fisker optimized how we detect ESM support 8831f54

See avajs/ava@v3.3.0...v3.4.0 for all changes.

`v3.3.0`

Compare Source

AVA can now load ESM test files! 🎉Thank you @arlac77 for making this happen. Check our updated ES Modules recipe for details.

Our ESM support is still incomplete. Progress is tracked in the ESM support project. Join us, won't you?

Other changes

See avajs/ava@v3.2.0...v3.3.0 for all changes.

`v3.2.0`

Compare Source

This release improves the integration with the new [@ava/typescript][@ava/typescript] package, which allows AVA to load pre-compiled TypeScript files.

First, install the new [@ava/typescript][@ava/typescript] package:

npm install --save-dev @&#8203;ava/typescript@^1.1

Now let's assume your TypeScript files are in a src directory, output to a build directory. Configure AVA like so:

ava.config.js file:

export default {
  typescript: {
    rewritePaths: {
      'src/': 'build/'
    }
  }
}

Compile your TypeScript files and run your tests! Or, to run a specific test file, run npx ava src/test.ts.

For more examples see the [@ava/typescript][@ava/typescript] package.

As exciting as this is, it's still early days. We need your help improving our TypeScript support. Check out the open issues.

Other changes

See avajs/ava@v3.1.0...v3.2.0 for all changes.

`v3.1.0`

Compare Source

AVA can now load pre-compiled TypeScript files!

First, install the new [@ava/typescript][@ava/typescript] package:

npm install --save-dev @&#8203;ava/typescript

Now let's assume your TypeScript files are in a src directory, output to a build directory. Configure AVA like so:

ava.config.js file:

export default {
  typescript: {
    rewritePaths: {
      'src/': 'build/'
    }
  }
}

Compile your TypeScript files and run your tests! Or, to run a specific test file, run npx ava src/test.ts.

For more examples see the [@ava/typescript][@ava/typescript] package.

As exciting as this is, it's still early days. We need your help improving our TypeScript support. Check out the open issues.

Other changes

Thanks to @jhechtf for fixing our TypeScript recipe after the changes in AVA 3.0 91a0086

See avajs/ava@v3.0.0...v3.1.0 for all changes.

`v3.0.0`

Compare Source

We're proud to introduce AVA 3! 🚀

When we began AVA, JavaScript was very different. Most syntax you find familiar today was not supported by Node.js. Instead we relied on Babel to support that syntax before it made its way to Node.js itself.

These days most new stage-4 syntax is adopted quickly. It's often not necessary to transpile anything. Therefore we're removing our built-in Babel support from AVA itself.

Without Babel you'll have to resort to using require() functions in your JavaScript files. But, you say, Node.js 13 supports ECMAScript Modules!

Well, we're getting there. For a start, AVA now also looks for .cjs files. And .mjs files are recognized too, but can't be loaded just yet. This also impacts ava.config.js files. If you'd like to help out delivering full .mjs support check out the issues in the ESM support project.

Removing Babel allowed us to simplify how test files are selected. Likely non-test files, inside "fixture" or "helper" directories are ignored. The same for files that are inside an underscore-prefixed directory. We've made some other breaking changes in this area so please do read the full release notes.

You can again pass glob patterns on the CLI. However these now filter the test files that AVA already selected based on the configuration. In other words you can't run files that wouldn't be run by invoking npx ava.

AVA now interrupts your tests if there's no progress for 10 seconds. Use the timeout configuration or --timeout CLI option to change this.

New features

Built-in debug mode

You can now debug individual test files using the V8 Inspector:

npx ava debug test.js

Connect to the debugger with Chrome DevTools. Or set up a debugger in VSCode.

Configurable Node.js arguments

You can now configure the arguments passed to Node.js itself when AVA starts its worker processes. Use the nodeArguments configuration or combine with the --node-arguments CLI option.

All breaking changes

Supported Node.js versions

We now support Node.js 10, 12 and 13. The minimal versions are 10.18.0, 12.14.0 and 13.5.0 respectively.

Removing Babel

Utilize Babel with AVA by installing our @ava/babel package and then enabling Babel by setting babel: true in the AVA configuration. Having this as a separate package means it can evolve independently.

The compileEnhancements setting has been moved into the babel configuration. Consequently, the t.assert() assertion will only print its detailed information when you use Babel. And we won't be able to catch typical mistakes with t.throws() as well as we could before.

The ava/stage-4 preset is now available from @ava/babel/stage-4. Our old @ava/babel-preset-transform-test-files and @ava/babel-preset-stage-4 packages are no longer maintained and not installed with AVA itself.

ECMAScript Module Support

AVA now also looks for .cjs and .mjs test files. That said, .mjs files cannot be loaded just yet.

Also, when you add "type": "module" , AVA would really like to treat .js files as ECMAScript Modules, but can't just yet.

Similarly,ava.config.cjs configuration files are now supported. ava.config.mjs files not just yet.

With AVA 2, we loaded ava.config.js files using the esm package. To avoid confusion between the different module formats we now only support export default statements. No import, no __filename. Configuration files that have dependencies should be written as a .cjs file for now.

Configuration files can only have .cjs, .js and .mjs extensions.

The remaining work is tracked in the ESM support project.

File selection

When you use the default configuration AVA will no longer select files matching the following glob patterns:

**/__tests__/**/__helper__/**/*
**/__tests__/**/__helpers__/**/*
**/__tests__/**/__fixture__/**/*
**/__tests__/**/__fixtures__/**/*
**/test/**/helper/**/*
**/test/**/helpers/**/*
**/test/**/fixture/**/*
**/test/**/fixtures/**/*
**/tests/**/helper/**/*
**/tests/**/helpers/**/*
**/tests/**/fixture/**/*
**/tests/**/fixtures/**/*

Additionally, when a file has a parent directory that starts with a single underscore, it can never be a test file.

test.js files are only selected if they're next to the package.json file, or inside top-level src and source directories.

We've removed the configuration of helpers. Previously, files selected by the helpers glob patterns were never considered test files. Now that this configuration is no longer supported you'll need to ensure the files patterns exclude your helper files. If you're using Babel, you can configure the compilation of additional files .

The sources configuration has also been removed. Instead, use the ignoredByWatcher configuration. Changes to files matched by these glob patterns will not cause the watcher to rerun tests.

Negated sources patterns must be used without the negation in ignoredByWatcher:

 export default {
-  sources: ['!examples/**/*']
+  ignoredByWatcher: ['examples/**/*']
 }

CLI changes

Internally we've replaced meow by yargs. We're not expecting things to break because of this, but you never know.

Resetting the cache

The --reset-cache argument has been replaced by a proper reset-cache command:

npx ava reset-cache

File selection (again!)

AVA again accepts glob patterns via the CLI:

npx ava '**/api/**/*'

The way this work is that AVA first finds all test files, according to the configuration, and then filters to select just the files that also match the glob patterns passed via the CLI.

You can still pass paths to specific files:

npx ava src/api/test/my-api-test.js

However unlike with AVA 2, you can no longer specify test files that aren't already selected by AVA's configuration.

`t.throws()` and `t.throwsAsync()` assertions

The second argument passed to these assertions must now be an expectation object. You can no longer pass the expected constructor, error message or regular expression.

Other breaking changes

Support for old esm versions has been removed.
We've set a default test timeout of 10 seconds. This means that if no test results are received for 10 seconds, AVA forces its worker processes to quit.
The NODE_PATH environment variable is no longer rewritten to ensure values are absolute paths.
AVA longer fakes the TTY in worker processes.

Other changes

We've simplified how we identify observables. Any object returned by a test implementation that has a subscribe function is assumed to be an observable. AVA's type definition has been updated accordingly.
The TAP reporter now reports hook failures as test failures.
We've added an example of module path mapping to our TypeScript recipe.
We've added a Selenium WebDriver JS recipe.

All changes

Thanks

Thank you @tymfear, @HeathNaylor, @grnch, @alexdrans, @MoppetX, @jimmywarting, @micaelmbagira, @aptester, @theashraf, @sramam and @maximelkin. We couldn't have done this without you!

`v2.4.0`

Compare Source

Experimental `t.try()` assertions

Thanks to the amazing work and patience of @qlonik we're shipping a new assertion! t.try() lets you perform assertions and decide whether to commit or discard their outcome. All kinds of interesting things can be built on top of this, from fuzzy testers to new test interfaces and more.

We're excited to get this out there, but it's not quite done yet. For now you have to opt in to this new feature. Being opt-in, we may make changes (breaking ones even!) until we feel this is stable.

To opt in, configure AVA with the following:

package.json:

{
  "ava": {
    "nonSemVerExperiments": {
      "tryAssertion": true
    }
  }
}

ava.config.js:

export default {
	nonSemVerExperiments: {
		tryAssertion: true
	}
};

We'd love to hear your feedback. Please join us in this issue: https://github.com/avajs/ava/issues/2250

Also, if you're looking to help out with the remaining issues so that we can ship this without the opt-in, have a look at this project: https://github.com/orgs/avajs/projects/1

Thanks again @qlonik!

Other changes

We've added the common pitfall of sharing variables across asynchronous tests 49b202f
We've updated the endpoint testing recipe to focus on the concept, not specific libraries 67e4dea

All changes

v2.3.0...v2.4.0

Thanks

Thank you @jeremenichelli, @jamesgeorge007, @dongjae93, @qlonik and @tryzniak. 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.

`v2.3.0`

Compare Source

Changes

We've fixed some bugs to improve watch mode. ffa62ce 9e8d28f
AVA now prints an error when it receives non-existent test files on the command line. f01d05f
When using the TAP reporter, remaining tests are now included in failed test count. Failed hooks are no longer treated as test failures, and logs are printed. 8628976
Internal errors that may occur for some edge cases are now printed. b27cb8d
TTY in the worker processes should follow the new APIs in Node.js 12.7.0 (when used with those Node.js versions). 7dcb473
AVA now handles stage-4 syntax like dynamic import, and stage-3 syntax like BigInt, numeric separators and class properties that are supported by V8. 9baca8c
AVA now supports dynamic import through our stage-4 preset.
AVA now uses import-local@^3.0.2 which fixes issues with Lerna projects.
For our TypeScript users, we've changed the default type of t.context to unknown, in line with TypeScript's changes in their 3.5 release. 2fc7d56

All changes

v2.2.0...v2.3.0

Thanks

Thank you @MarchWorks, @yovasx2 and @bobthekingofegypt. 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.

`v2.2.0`

Compare Source

Enhancements

You can now specify an alternative config file, using the --config CLI argument. This is useful if you want to run unit tests separately from integration tests, since you can have a config file specific to your integration tests which specifies different glob patterns. 2dae2bf

Bug fixes

We're now faking the new hasColors() method for better compatibility with Node.js 12. d399797

Node.js 11

We've removed Node.js 11 from our test matrix. You should upgrade to Node.js 12. 90acbb9

All changes

v2.1.0...v2.2.0

Thanks

Thank you @langri-sha, @keyspress, @cdaringe and @okyantoro. 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.

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Update dependency ava to v3

86204d2

renovate bot changed the title ~~Update dependency ava to v3~~ Update dependency ava to v3 - autoclosed Mar 7, 2022

renovate bot closed this Mar 7, 2022

renovate bot deleted the renovate/ava-3.x branch March 7, 2022 16:19

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency ava to v3 - autoclosed #6

Update dependency ava to v3 - autoclosed #6

renovate bot commented Feb 8, 2020 •

edited

Update dependency ava to v3 - autoclosed #6

Update dependency ava to v3 - autoclosed #6

Conversation

renovate bot commented Feb 8, 2020 • edited

Release Notes

Automatic snapshot file removal

TAP improvements

Next-generation configuration

Snapshot ordering

Shared workers

Configure how AVA loads test files

Comparison bugfix

All changes

New t.like() assertion

VSCode 1.47 debugging improvements

All changes

It's time for another AVA release 🎉

Restricting when you can update snapshots

Support for message strings in t.timeout() calls

t.try() does not work in hooks

t.snapshot() does not really work in hooks either

Fixed TypeScript definition for t.like()

All changes

New experiments!

Reporter changes

Improved diffs

Farewell Node.js 13

All changes

Node.js 14 support

Run tests at specific line numbers

Test-specific teardown functions

Node.js internal in stack traces

Watch mode with the default reporter

ICYMI

All changes

Introducing the t.try() assertion

In case you missed it: ESM support

Other changes

Other changes

Other changes

Other changes

We're proud to introduce AVA 3! 🚀

New features

Built-in debug mode

Configurable Node.js arguments

All breaking changes

Supported Node.js versions

Removing Babel

ECMAScript Module Support

File selection

CLI changes

Resetting the cache

File selection (again!)

t.throws() and t.throwsAsync() assertions

Other breaking changes

Other changes

All changes

Thanks

Experimental t.try() assertions

Other changes

All changes

Thanks

Get involved

Changes

All changes

Thanks

Get involved

Enhancements

Bug fixes

Node.js 11

All changes

Thanks

Get involved

Configuration

renovate bot commented Feb 8, 2020 •

edited

New `t.like()` assertion

Support for message strings in `t.timeout()` calls

`t.try()` does not work in hooks

`t.snapshot()` does not really work in hooks either

Fixed TypeScript definition for `t.like()`

Introducing the `t.try()` assertion

`t.throws()` and `t.throwsAsync()` assertions

Experimental `t.try()` assertions