Improve debug cycle about karma-chrome-launcher HOT 9 OPEN

It is also useful to be able to setup and save Workspace settings across multiple invocations. It would be nice to be able to selectively inject saved DevTools settings into a fresh profile, but I'm not aware of any mechanism to do so. A brute force approach is to pass the --user-data-dir flag to a custom launcher:

    browsers: ['Chrome'],

    customLaunchers: {
      Chrome_DevTools_Saved_Prefs: {
        base: 'Chrome',
        flags: ['--user-data-dir=./tests/config/.chrome_dev_user']
      }
    }

Then:

karma start --browsers Chrome_DevTools_Saved_Prefs

This will allow you to reuse the profile and takes care of steps 4-7 (breakpoints are also preserved). When you want to test using a fresh profile, use the default Chrome launcher or wipe the user-data-dir.

from karma-chrome-launcher.

What is working for us is:

browsers: [
  'Chrome'
],
customLaunchers: {
  Chrome_DevTools_Saved_Prefs: {
    base: 'Chrome',
    flags: ['--auto-open-devtools-for-tabs']
  }
},

from karma-chrome-launcher.

+1
Too many steps to take to debug...

from karma-chrome-launcher.

Looks like Chrome will soon remember DevTools position/docked state in incognito mode, so there may be some opportunities to have karma remember it debug DevTools settings (http://crbug.com/376788#c45)

from karma-chrome-launcher.

It seems this planned to land in Chrome 44 stable. So lets see how much improvement that brings.
If you have any ideas what we could do from the karma side, I'm very open to suggestions.

from karma-chrome-launcher.

I think that making it open a new tab in the currently focused window (instead of a new instance and a new profile) is good enough.

Why isn't that the default behavior?

from karma-chrome-launcher.

It appears that the Chrome fix has landed and, while it does apply to an incognito window, it doesn't apply to the new window that karma-chrome-launcher opens.

from karma-chrome-launcher.

The Jetbrains karma runner is happy to use any currently subscribed browser window...if a browser is at localhost:9876 it just runs in that however it's set. Otherwise it launches one if instructed to.

That is the correct behavior as we can control the exact context if we want rather than being forced to cope with a vanilla one or edit config settings down in the bowels. But I don't always want to run Jetbrains and they have their own debugger problems. I want chrome debugger with my own extensions.

This is a very important piece of code and it really shouldn't be abandoned like this.

from karma-chrome-launcher.

@ltvolks That was exactly the answer I was looking for, even now in April 2017. Thank you! :)

from karma-chrome-launcher.