testee does not exit if using a config

[tracer99]

On all of our projects that are now on CanJS5/DoneJS3 testee no longer exits on completion of tests.

I've setup a bone stock donejs3 app with the only modification being the use of a config file for tests. The single tests completes successfully but testee does not exit.

https://github.com/tracer99/testee-exit

Platforms tested:
NodeJS 8 through 12
Debian Stable & old-stable
WSL & WSL2 (Debian Stable)
OSX

Note: The tests for testee itself exhibit this exact issue.

[cherifGsoul]

This happens when Chrome is closed but there's a google-chrome process still hangs in the background when some extensions need to be run even if Chrome is closed.

The fix should be done on launchpad by:

• Disable installed extensions and other services in default args
• Use separate Chrome profile for each launch
• Make a cleanup after killing each Chrome instance

Running the tests after killing all the running background instances closes the running instance.

[tracer99]

hah. so this prompted me to look at more chrome command line switches. --bwsi seems to do the trick.

"Indicates that the browser is in "browse without sign-in" (Guest session) mode. Should completely disable extensions, sync and bookmarks. " from https://peter.sh/experiments/chromium-command-line-switches/

[tracer99]

Sadly, this stopped working. I have no idea what changes but --bwsi does nothing now.

Note this happens for Firefox as well. The only way I can have the tests run and exit properly is by not passing in any arguments. Then it work every time.

[cherifGsoul]

@tracer99 you can add clean options to make sure browser will exit:

"browsers": [
        {
            "clean": true,
            "browser": "chrome",
            "args": [
                "--headless"
            ]
        }
    ]