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

Core: Ensure late-add high-priority tests are inserted in proper order #1269

Merged
merged 1 commit into from
Mar 25, 2018

Conversation

trentmwillis
Copy link
Member

@trentmwillis trentmwillis commented Mar 1, 2018

As mentioned in this comment: https://github.com/qunitjs/qunit/pull/1260/files#r169779552

(Note: Test has some weird behavior in PhantomJS, but verified it works as expected in Chrome, Safari, and FireFox)

@Arkni
Copy link
Contributor

Arkni commented Mar 1, 2018

The weird behavior in PhantomJS is due to QUnit.config.reorder being reset to false inside of grunt-contrib-qunit's bridge file , see grunt-contrib-qunit/phantomjs/bridge.js#L20-L21. Those 2 lines were there since the first commit.

@trentmwillis
Copy link
Member Author

Thanks for that insight, I would have never figured that out! Will update the comment in the test then.

@trentmwillis
Copy link
Member Author

Comment in the test has been updated. Should be good to go now I think.

@trentmwillis
Copy link
Member Author

@qunitjs/qunit-team would one of you mind reviewing this for me?

Copy link
Contributor

@platinumazure platinumazure left a comment

Choose a reason for hiding this comment

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

LGTM, sorry for the late review.

@trentmwillis trentmwillis merged commit fc1c3ce into qunitjs:master Mar 25, 2018
@trentmwillis trentmwillis deleted the running-priority branch March 25, 2018 05:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants