You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a revisit of the previously closed issue #1078
I am working on a largish node application that uses AVA for testing framework, and a mix of native AVA assertions and chai assertions.
So here is my problem. Because of the mixed use of the assertions libraries, AVA is configured to not fail the tests that do not call native AVA assertion, but use chai's instead.
The configuration uses 'ava' section in package.json file.
Unfortunately when tests are run in Wallaby, it ignores this config and tests are failing for no reason.
We have updated Wallaby to allow you to set test runner options for Ava. The testFramework for Ava now provides an empty object { } (was previously undefined). You may set ava's options by setting the properties of the testFramework. Please update to the latest version of Wallaby core (v1.0.768) that includes this change. If Wallaby does not update automatically, you may force a core update.
Please note that the following properties will always be overridden by Wallaby: file, projectDir, updateSnapshots.
You may set failWithoutAssertions to false by modifying the testFramework in the setup function of your Wallaby.js configuration file (see example below).
Issue description or question
This is a revisit of the previously closed issue #1078
I am working on a largish node application that uses AVA for testing framework, and a mix of native AVA assertions and chai assertions.
So here is my problem. Because of the mixed use of the assertions libraries, AVA is configured to not fail the tests that do not call native AVA assertion, but use chai's instead.
The configuration uses 'ava' section in package.json file.
Unfortunately when tests are run in Wallaby, it ignores this config and tests are failing for no reason.
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: