Mock browser document in integration test
How can I mock standard whole browser's window on client? I want entirely new object same as window which would provide work with location and DOM but would not render into actual displayed window. There is JSDOM which works on server, but I would like the possibility on client. I'm using Meteor with Mocha.
I came up with solution to call window.open() and use returned value, but it comes with problems with pop-blocker and I guess it's pretty slow.
javascript testing meteor mocha integration-testing
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
add a comment |
How can I mock standard whole browser's window on client? I want entirely new object same as window which would provide work with location and DOM but would not render into actual displayed window. There is JSDOM which works on server, but I would like the possibility on client. I'm using Meteor with Mocha.
I came up with solution to call window.open() and use returned value, but it comes with problems with pop-blocker and I guess it's pretty slow.
javascript testing meteor mocha integration-testing
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
"Pretty slow" should be a minor concern when doing integration tests. Validity and integrity are way more important. Why would you need to mock the entire DOM from the window object (with all it's functionality)?
– Jankapunkt
Nov 15 '18 at 19:09
Just to be sure that it works as in native window. I would like to rather make new instance same as window, not create object that resembles existing window object.
– Márius Rak
Nov 15 '18 at 19:21
add a comment |
How can I mock standard whole browser's window on client? I want entirely new object same as window which would provide work with location and DOM but would not render into actual displayed window. There is JSDOM which works on server, but I would like the possibility on client. I'm using Meteor with Mocha.
I came up with solution to call window.open() and use returned value, but it comes with problems with pop-blocker and I guess it's pretty slow.
javascript testing meteor mocha integration-testing
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
How can I mock standard whole browser's window on client? I want entirely new object same as window which would provide work with location and DOM but would not render into actual displayed window. There is JSDOM which works on server, but I would like the possibility on client. I'm using Meteor with Mocha.
I came up with solution to call window.open() and use returned value, but it comes with problems with pop-blocker and I guess it's pretty slow.
javascript testing meteor mocha integration-testing
javascript testing meteor mocha integration-testing
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
edited Nov 15 '18 at 17:12
Márius Rak
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
asked Nov 15 '18 at 16:42
Márius RakMárius Rak
2261420
2261420
"Pretty slow" should be a minor concern when doing integration tests. Validity and integrity are way more important. Why would you need to mock the entire DOM from the window object (with all it's functionality)?
– Jankapunkt
Nov 15 '18 at 19:09
Just to be sure that it works as in native window. I would like to rather make new instance same as window, not create object that resembles existing window object.
– Márius Rak
Nov 15 '18 at 19:21
add a comment |
"Pretty slow" should be a minor concern when doing integration tests. Validity and integrity are way more important. Why would you need to mock the entire DOM from the window object (with all it's functionality)?
– Jankapunkt
Nov 15 '18 at 19:09
Just to be sure that it works as in native window. I would like to rather make new instance same as window, not create object that resembles existing window object.
– Márius Rak
Nov 15 '18 at 19:21
"Pretty slow" should be a minor concern when doing integration tests. Validity and integrity are way more important. Why would you need to mock the entire DOM from the window object (with all it's functionality)?
– Jankapunkt
Nov 15 '18 at 19:09
"Pretty slow" should be a minor concern when doing integration tests. Validity and integrity are way more important. Why would you need to mock the entire DOM from the window object (with all it's functionality)?
– Jankapunkt
Nov 15 '18 at 19:09
Just to be sure that it works as in native window. I would like to rather make new instance same as window, not create object that resembles existing window object.
– Márius Rak
Nov 15 '18 at 19:21
Just to be sure that it works as in native window. I would like to rather make new instance same as window, not create object that resembles existing window object.
– Márius Rak
Nov 15 '18 at 19:21
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%2f53324105%2fmock-browser-document-in-integration-test%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%2f53324105%2fmock-browser-document-in-integration-test%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
"Pretty slow" should be a minor concern when doing integration tests. Validity and integrity are way more important. Why would you need to mock the entire DOM from the window object (with all it's functionality)?
– Jankapunkt
Nov 15 '18 at 19:09
Just to be sure that it works as in native window. I would like to rather make new instance same as window, not create object that resembles existing window object.
– Márius Rak
Nov 15 '18 at 19:21