Fix for running test cases in a regular browser like Firefox or Chrome #1795
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
thanks. |
lukeapage
added a commit
that referenced
this pull request
Jan 10, 2014
Fix for running test cases in a regular browser like Firefox or Chrome
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I tried running:
grunt connect:server:keepalive
and then running the tests like:
http://localhost:8081/tmp/browser/test-runner-rootpath-relative.html
but most of the tests failed in Firefox and Chrome because lessOutputObj.innerText was empty, however, innerHTML was populated. So if you add an "or" check it won't break the phantomjs tests but will also work in a regular browser.