Mocha w/React Testing Library is not respecting expect(null).to.be.null within wait/waitForElement
I’m using the combination of Mocha and React Testing Library for acceptance testing (not my choice) and have a situation where I need to use wait
or waitForElement
to ultimately verify the absence of an element in the DOM. (Yes, as per React Testing Library’s documentation, I’m using getByTestId
to attempt this.) There are multiple asynchonous operations that include fetch requests which occur in rapid succession (e.g., the user logs in then clicks/selects some things before submitting a form, which causes another UI to render). After all of that, there’s my expect
, which is supposed to verify the absence of an element from within React Testing Library’s wait
. The problem is that I can neither resolve so much as expect(null).to.be.null
nor expect(null).to.not.be.null
from within wait
.
These fail:
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.be.null
})
})
})
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.not.be.null
})
})
})
What could I be doing wrong?
reactjs redux acceptance-testing react-testing-library
add a comment |
I’m using the combination of Mocha and React Testing Library for acceptance testing (not my choice) and have a situation where I need to use wait
or waitForElement
to ultimately verify the absence of an element in the DOM. (Yes, as per React Testing Library’s documentation, I’m using getByTestId
to attempt this.) There are multiple asynchonous operations that include fetch requests which occur in rapid succession (e.g., the user logs in then clicks/selects some things before submitting a form, which causes another UI to render). After all of that, there’s my expect
, which is supposed to verify the absence of an element from within React Testing Library’s wait
. The problem is that I can neither resolve so much as expect(null).to.be.null
nor expect(null).to.not.be.null
from within wait
.
These fail:
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.be.null
})
})
})
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.not.be.null
})
})
})
What could I be doing wrong?
reactjs redux acceptance-testing react-testing-library
Can you share a reproducible example in codesandbox or something similar?
– Gpx
Nov 20 '18 at 16:57
add a comment |
I’m using the combination of Mocha and React Testing Library for acceptance testing (not my choice) and have a situation where I need to use wait
or waitForElement
to ultimately verify the absence of an element in the DOM. (Yes, as per React Testing Library’s documentation, I’m using getByTestId
to attempt this.) There are multiple asynchonous operations that include fetch requests which occur in rapid succession (e.g., the user logs in then clicks/selects some things before submitting a form, which causes another UI to render). After all of that, there’s my expect
, which is supposed to verify the absence of an element from within React Testing Library’s wait
. The problem is that I can neither resolve so much as expect(null).to.be.null
nor expect(null).to.not.be.null
from within wait
.
These fail:
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.be.null
})
})
})
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.not.be.null
})
})
})
What could I be doing wrong?
reactjs redux acceptance-testing react-testing-library
I’m using the combination of Mocha and React Testing Library for acceptance testing (not my choice) and have a situation where I need to use wait
or waitForElement
to ultimately verify the absence of an element in the DOM. (Yes, as per React Testing Library’s documentation, I’m using getByTestId
to attempt this.) There are multiple asynchonous operations that include fetch requests which occur in rapid succession (e.g., the user logs in then clicks/selects some things before submitting a form, which causes another UI to render). After all of that, there’s my expect
, which is supposed to verify the absence of an element from within React Testing Library’s wait
. The problem is that I can neither resolve so much as expect(null).to.be.null
nor expect(null).to.not.be.null
from within wait
.
These fail:
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.be.null
})
})
})
describe(‘My app’, function () {
it(‘Does things’, async function () {
await wait(() => {
expect(null).to.not.be.null
})
})
})
What could I be doing wrong?
reactjs redux acceptance-testing react-testing-library
reactjs redux acceptance-testing react-testing-library
edited Nov 20 '18 at 16:28
Michael P.
asked Nov 20 '18 at 16:17
Michael P.Michael P.
473518
473518
Can you share a reproducible example in codesandbox or something similar?
– Gpx
Nov 20 '18 at 16:57
add a comment |
Can you share a reproducible example in codesandbox or something similar?
– Gpx
Nov 20 '18 at 16:57
Can you share a reproducible example in codesandbox or something similar?
– Gpx
Nov 20 '18 at 16:57
Can you share a reproducible example in codesandbox or something similar?
– Gpx
Nov 20 '18 at 16:57
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397186%2fmocha-w-react-testing-library-is-not-respecting-expectnull-to-be-null-within-w%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397186%2fmocha-w-react-testing-library-is-not-respecting-expectnull-to-be-null-within-w%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you share a reproducible example in codesandbox or something similar?
– Gpx
Nov 20 '18 at 16:57