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 have a karma already launched with a browser attached, karma start --run-once=false. Using karma-jasmine adapter.
I run:
karma run -- --grep=foo
karma run
I expect the first one to run just matching "foo" and the second to run all the tests.
Actual behavior
The second one just runs the "grep=foo" tests.
I went in and added logging in the entrypoints of the karma-jasmine adapter, and I see that window.__karma__.config still has args: ['--grep=foo'] on the second run.
Since it doesn't look like karma-jasmine ever sets this value, this seems like a bug in karma itself rather than in the framework adapter. Karma is not clearing window.__karma__ between runs.
Enviroment Details
Karma version (output of karma --version): 1.2.0
Relevant part of your karma.config.js file N/A
Steps to reproduce the behaviour
Described above
The text was updated successfully, but these errors were encountered:
Expected behavior
I have a karma already launched with a browser attached,
karma start --run-once=false
. Usingkarma-jasmine
adapter.I run:
I expect the first one to run just matching "foo" and the second to run all the tests.
Actual behavior
The second one just runs the "grep=foo" tests.
I went in and added logging in the entrypoints of the karma-jasmine adapter, and I see that
window.__karma__.config
still hasargs: ['--grep=foo']
on the second run.Since it doesn't look like karma-jasmine ever sets this value, this seems like a bug in karma itself rather than in the framework adapter. Karma is not clearing
window.__karma__
between runs.Enviroment Details
karma --version
): 1.2.0karma.config.js
file N/ASteps to reproduce the behaviour
Described above
The text was updated successfully, but these errors were encountered: