Fix false positive when using chai-as-promised #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The issue
When we use both chai-as-promised and chai-xml, chai-xml inhibits the behavior of chai-as-promised with the
eventually
keyword.eventually
has to be used in a return statement so we can test the promise result.Steps to reproduce
npm install
Actual Result
Expected result
(You can comment
chai.use(require("chai-xml"));
inindex-spec.js
to see the expected result)Explanation of the patch
Simply use the return statement to make a clean by-pass to other hooks.