-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
Use Case
As a Node.js engineer
I want tests that report errors in a way that is easy to ascertain the root cause
So that I can determine if my feature/fix work as introduced a regression
User Impact
- None
Dependencies
- None
Unknowns
- Are the assertions in the tests accurate?
- Are the assertions adequately loose? Explain's responses are based on internals of the server version, it's generally meant for human consumption only.
Acceptance Criteria
Implementation Requirements
Do the following in separate commits since the syntax changes will likely have git mark the file as entirely new instead of a proper diff
- Change file extension from .js to .ts
- Accept linter prompted changes: require -> import
- Refactor callback tests to async / await
- Clean up redundant metadata
- Improve chai assertions:
- Ex. expect(something.key).to.be.array; -> expect(something).to.have.property('key').that.is.an.array;
Testing Requirements
- Existing CI must pass
Documentation Requirements
- None
Follow Up Requirements
- None
- is related to
-
NODE-5241 Introduce returnRawResult option in findAndModify family of methods
- Closed