Sergey Simonchik

This issue is similar to https://github.com/karma-runner/karma/issues/2317, but it's targeting "karma run" and can be still reproduced with the latest released karma 1.7.0.

@johnjbarton Agree, the app-under-test code contributes a significant part here. Can it be reduced if only needed part the app-under-test code is delivered to browser? For example, using `require`/`import`? Other...

>Why are you not running npm.exe? I'm using WebStorm and it runs npm commands with explicitly specified interpreter, e.g. `C:\Program Files\Nodist\bin\node.exe C:\Program Files\Nodist\npm\bin\npm-cli.js info karma` Looks like it's caused by...

Seems the change is pretty harmless. @johnjbarton What do you think?

This issue also affects running single test in project generated with `vue init webpack my-project` command (https://youtrack.jetbrains.com/issue/WEB-32918). Please review PR: https://github.com/karma-runner/karma-mocha/pull/206 //cc @maksimr

@rprichard Any idea how it can be workarounded? What if console windows height is always kept the same (say 1000 rows)?

@rprichard Do you plan to implement it in winpty?

Thanks, currently, the value last passed to `winpty_set_size` is used: https://github.com/JetBrains/pty4j/commit/3f0fbce33ce0c2231f84feae28b09abd50fd6fe8#diff-385b08a79e19a17a08ef52bc324383f9 Do you mean that it's impossible to retrieve the window size or it's just not implemented yet, but possible?

@SimenB IntelliJ/Fleet both run Jest tests using Jest CLI. It appears that we're not currently interested in it.

This caused https://youtrack.jetbrains.com/issue/WEB-51467. A workaround will be added in WebStorm 2021.3.2: `test.todo` will be fetched from `onTestFileResult` events, but it happens too late, when the whole test file is done....