test: ignore expected console error and improve test #274
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wjhsf
approved these changes
Jul 1, 2024
| it('exports refreshApex method returning a promise', () => { | ||
| expect(refreshApex()).resolves.toEqual(undefined); | ||
| expect(refreshApex()).not.toBeUndefined(); | ||
| expect(refreshApex().then).toEqual(expect.any(Function)); // should be a thenable (promise) |
Contributor
There was a problem hiding this comment.
Why a thenable rather than instance of Promise?
Contributor
Author
There was a problem hiding this comment.
Old habit? I guess my mind is still stuck in the days when Promises weren't supported everywhere.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This removes an annoying error message in the test (which is totally expected) and also improves the tests for apex methods returning a promise.