Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extra launcher when running ember nw:test --server with Ember CLI 1.13.15 #54

Open
brzpegasus opened this issue Jan 23, 2016 · 5 comments
Labels

Comments

@brzpegasus
Copy link
Owner

When running ember nw:test --server, the testem UI shows two launchers instead of one. This happens upon upgrading to Ember CLI 1.13.15. It does not happen with Ember CLI 1.13.14 or below.

screen shot 2016-01-23 at 2 48 55 pm

@brzpegasus brzpegasus added the bug label Jan 23, 2016
@brzpegasus
Copy link
Owner Author

Clarification: This behavior is seen when upgrading Ember CLI in the consuming app, not in the addon.

@brzpegasus
Copy link
Owner Author

Pinpointed the issue to this specific commit in testem.

@felixrieseberg
Copy link

One thing that is worth pointing out: When @sedouard and I worked on the app that lead to some of the testing and Qunit code, we saw a bunch of testing wonkiness, but it ultimately still reports correctly.

(Just in case anyone looks at this and thinks that the feature is broken - it's just visually broken 😉)

@brzpegasus
Copy link
Owner Author

I cleaned up a lot of things with the testing command, so I'm not aware of any leftover testing wonkiness in particular (though I'd like to know if there are any). Having two launchers show up in the UI seems to be a result of Testem refactoring the code to consolidate Dev + CI modes. There used to be only one prior to upgrading Testem. Right now, the first tab never runs any tests and shouldn't be there. The 2nd tab is correct. It's not preventing users from getting to the results by focusing on the right tab, but still annoying =).

@felixrieseberg
Copy link

Nevermind then, if you cleaned it up it's probably all fine 😊When we initially worked on it, testem (interactive) would sometimes just be the grinch (and display things all over the place, have multiple launchers, launch nwjs repeatedly, etc), but the end results we're always correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants