You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to run tests through karma in IE11 and open browser window with width 1200 and height 800 pixels. But after searching on internet I haven't found a solution how to do it.
As I know IE11 can not be started from command line with size options passed in. (Chrome can do it!)
As workaround I use next code that I put on the start of my test suite's code (executes one time before running all tests): window.resizeTo(1200, 800);
It yields me a desired result when I start karma in --no-single-run mode (config property singleRun = false). In that case when I click DEBUG button new browser window is opened and resized when resizeTo() is invoked. Tests are success.
But when I start karma in --single-run mode this workaround doesn't work! And IE11 window doesn't resized. And tests were failed!
Please, tell me how to run tests in IE11 with my window dimensions?
I want to run tests through karma in IE11 and open browser window with width 1200 and height 800 pixels. But after searching on internet I haven't found a solution how to do it.
As I know IE11 can not be started from command line with size options passed in. (Chrome can do it!)
As workaround I use next code that I put on the start of my test suite's code (executes one time before running all tests):
window.resizeTo(1200, 800);
It yields me a desired result when I start karma in
--no-single-run
mode (config propertysingleRun = false
). In that case when I click DEBUG button new browser window is opened and resized whenresizeTo()
is invoked. Tests are success.But when I start karma in
--single-run
mode this workaround doesn't work! And IE11 window doesn't resized. And tests were failed!Please, tell me how to run tests in IE11 with my window dimensions?
OS: Windows 7 64x
Karma version: 1.6.0
karma-ie-launcher version: 1.0.0
NodeJs version: 6.9.2
The text was updated successfully, but these errors were encountered: