Tests "disappear" after changing config files #30
Comments
|
@colindembovsky |
|
Here are the steps I follow:
Here's the log file: |
|
@colindembovsky |
|
No problem - it's a minor annoyance, since we don't change the config files too frequently. Just wanted you to know about this issue. Keep up the great work! 😄 |
MortenHoustonLudvigsen
added a commit
that referenced
this issue
Apr 3, 2015
|
@colindembovsky |
|
Thank you Morten. When I previously updated the Karma Test Adapter, I tried configuring to run Chrome, IE and Phantom at the same time and when I did, both IE and Chrome opened multiple instances like issue 23. At the time I was behind on a deadline, so I just uninstalled KTA and ran Karma from powershell. I just installed KTA 1.1.3 and have toggled the Disabled property a number of times and it only created one instance of each IE and Chrome. Then I close the solution and reopened it. Chrome was connected and IE was disconnected. I refreshed IE and then it connected and Chrome disconnected. Each time I toggled the disconnected browser, the connected browser would disconnect. If I run IE alone, it seems to work. If I run Chrome alone it works. The latter is my most common scenario. Karma Test Adapter is constantly improving and is now at a place where I can keep it running and recommend it to my co-workers. I’ll keep you posted of any issues. Respectfully, David C From: Morten Houston Ludvigsen [mailto:[email protected]] @cResultshttps://github.com/cResults — |
|
Thanks Morten The test discovery works great now even after changing config files! I still seem to have an issue with Chrome - it launches, then the tests run (and report back to VS), but the Chrome window stays open, even though I have singleRun set to true. Closing the Chrome window causes another Chrome window to pop up (Karma thinks that the browser has crashed and tried to re-run the tests). However, I'm mostly running my CI tests using PhantomJS, so this isn't a huge problem. Keep up the great work! |
|
@colindembovsky |
|
@colindembovsky |
|
@cResults |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A small issue - when changing either the karma config file or the test adapter json config file, the tests "disappear" - seems the test runner gets into some strange state. Restarting VS fixes the issue - but every time we change the config file we need to restart VS for test discovery to work.
The text was updated successfully, but these errors were encountered: