Here are some notes from my attempt at debugging this (using node --inspect-brk ./node_modules/.bin/ember electron:test).
The "Browser exited unexpectedly" message is coming from testem, which is getting launched by ember-electron calling test-runner.js which calls electron-forge's start.
Not knowing how to just build the test files and manually launch electron/electron-forge, I set a breakpoint to pause the debugger when ember-cli logs "An error occurred running..." then started a separate process to run
electron tmp/class-tests_dist-0pryoyEl.tmp tmp/class-tests_dist-0pryoyEl.tmp/ember/tests/index.html?hidepassed=__amp__testemId=5511 http://localhost:7357/
where those arguments are buildDir, testemUrl, and testPageUrl, and I think they match what electron-forge is using. When I call this with electron v1.8.2 it launches and stays running, but when I run it with electron v2.0.0-beta.1 it runs and terminates before I see the window. Running with DEBUG=* doesn't appear to show anything interesting/unusual (output stops before test runner executes, apparently) except that it is quiet with the working 1.x version and prints a few messages from electron-compile with the failing 2.x one. (I built for 2.x and switched between electron versions w/o rebuilding by calling /home/user/.nvm/versions/node/v8.9.4/lib/node_modules/electron/dist/electron (globally installed) or node_modules/electron/dist/electron (locally installed) -- since there are no native addons I don't think this is causing any problems, especially since the same bug happens when I rebuild the whole project). I put a console.log statement at the end of the app.ready callback. When running in 1.x I see that line and then the process stays running until I close the window or Ctrl-C. When running the 2.x version, I see the same log line followed immediately by a Segmentation fault :bomb: