Closed greenkeeper[bot] closed 5 years ago
After pinning to 2.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
ava was updated from 2.3.0
to 2.4.0
.Your tests are still failing with this version. Compare changes
t.try()
assertionsThanks 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: #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!
Thank you @jeremenichelli, @jamesgeorge007, @dongjae93, @qlonik and @tryzniak. We couldn't have done this without you!
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.
The new version differs by 24 commits.
05f077e
2.4.0
ca4eff7
Bump dependencies
67e4dea
Update endpoint testing recipe to focus on the concept, not libraries
4fdb02d
Implement experimental t.try() assertion
782c2d8
Run some tests on Travis still
4c890d9
Add OpenCollective link to README
03c1509
Groundwork to support experimental features
0a5c933
Remove unnecessary flag from tap invocation
e598c30
Detect whether error source is on a different drive (on Windows)
fb0c536
Fix serialize-error tests on Windows with GitHub Actions
53d7fe1
Allow some fixtures to pass linting when XO is installed without lockfile
11771ba
Run CI using GitHub Actions
5538bdc
Replace an indexOf() by includes()
49b202f
Add shared variables & asynchronous tests to common pitfalls
1c81c4b
2.3.0
There are 24 commits in total.
See the full diff
devDependency
ava was updated from 3.3.0
to 3.4.0
.Your tests are still failing with this version. Compare changes
t.try()
assertionThe new t.try()
allows you to try assertions without causing the test to fail:
test('do the thing', async t => {
const attempt = () => t.try(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.
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 @stavalfiava.config.js
files once again work with our @ava/typescript
package f4d4edd@types/node
7a1dacftest.cb()
is used with asynchronous functions or observables f5a8c2b @toddkcarlsonjsdom-global
instead of browser-env
3f9c616 @ScrumSee v3.3.0...v3.4.0 for all changes.
The new version differs by 109 commits.
8630636
3.4.0
12ba7bc
Ship t.try() without requiring opt-in
f4d4edd
Evaluate ava.config.js scripts in current context
8831f54
Improve detection of ESM support
d0e2161
Support undefined as second argument to t.throws and t.throwsAsync
324e45f
Document t.try()
(#2251)
da52e5f
Bump dependencies
55a3649
Ensure t.try() assigns unique titles when multiple implementations are passed
7ee3a0e
Prefix attempt titles with that of parent test
a69e4f2
Bump dependencies
7a1dacf
Remove @types/node reference
3f9c616
Update Vue recipe to use JSDom rather than browser-env
f5a8c2b
Improve error message when test.cb()
is used with promises
c166e05
3.3.0
362b6f9
Upgrade @ava/babel
There are 109 commits in total.
See the full diff
devDependency
ava was updated from 3.4.0
to 3.5.0
.Your tests are still failing with this version. Compare changes
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 v3.4.0...v3.5.0 for all changes. Spoiler alert: it's just this one
devDependency
ava was updated from 3.5.0
to 3.5.1
.Your tests are still failing with this version. Compare changes
The devDependency ava was updated from
2.1.0
to2.2.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
ava is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/noyobo/img-spriter-transform/builds/555963615?utm_source=github_status&utm_medium=notification)).Release Notes for 2.2.0
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. 2dae2bfBug fixes
We're now faking the new
hasColors()
method for better compatibility with Node.js 12. d399797Node.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.
Commits
The new version differs by 9 commits.
2451484
2.2.0
e528ad2
Bump dependencies
2dae2bf
Implement --config flag
58b2350
Disable deprecation warnings in reporter tests
d399797
Fake
hasColors()
in worker processes90acbb9
Stop testing Node.js 11, remove from engines entry
533ee4b
Link to VSCode debugging recipe
dc91725
Fix grammar in readme
851316f
Remove Flow references
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: