Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

[Unit Test Failure] Not all Test Windows are closed even when tests succeed #3219

Closed
redmunds opened this issue Mar 22, 2013 · 5 comments
Closed
Assignees
Milestone

Comments

@redmunds
Copy link
Contributor

When I run the Live Development Integration tests, they report "Complete. No failures.", but 2 test windows are left open. Both Mac and Windows.

I am seeing the same with the UpdateNotification tests, so this doesn't seem to be caused by recent Live Development changes.

@redmunds
Copy link
Contributor Author

I'll run git bisect to see if I can find the change that broke it.

@redmunds
Copy link
Contributor Author

This was introduced by this change: #3153

Assigning to @RaymondLim

@ghost ghost assigned RaymondLim Mar 22, 2013
@njx
Copy link
Contributor

njx commented Mar 22, 2013

Interesting. I bet this breaks the tests because some tests probably leave unsaved changes; in the past, we would just go ahead and close the window due to #3152, which turns out to be what you want for tests, but not for the real product :) Maybe we should just change SpecRunner.closeTestWindow() to make it so it can force the window to close even if there are unsaved changes (would probably have to add some internal API in Brackets to allow this).

@peterflynn
Copy link
Member

FBNC @redmunds since the fix has been merged

@ghost ghost assigned redmunds Mar 22, 2013
@redmunds
Copy link
Contributor Author

Confirmed. Closing.

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

No branches or pull requests

4 participants