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

Fix cleanup of jsdom environment #129

Merged
merged 1 commit into from
Dec 13, 2017
Merged

Fix cleanup of jsdom environment #129

merged 1 commit into from
Dec 13, 2017

Conversation

fdietze
Copy link
Member

@fdietze fdietze commented Dec 13, 2017

The problem was that dom nodes of previous tests leaked into later tests. This was problematic if the previous test used the same id, in this case id="btn". The nondeterminism came from the nondeterministic test execution order. Some test classes didn't clean up the dom which was problematic, if executed in a certain order.

fixes #59

Copy link
Member

@cornerman cornerman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very nice!

Copy link
Member

@LukaJCB LukaJCB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome!

@cornerman cornerman merged commit fce4eb8 into master Dec 13, 2017
@cornerman cornerman deleted the nondeterminism branch December 13, 2017 16:58
@mariusmuja
Copy link
Collaborator

Thanks for fixing this!

mariusmuja pushed a commit to mariusmuja/outwatch that referenced this pull request Dec 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nondeterministic test fail in DomEventSpec
4 participants