Mark tests as passed/failed in Browserstack with reason #14
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The incentive behind this fork is to demonstrate how to mark tests as passed/ failed in browserstack.
Browserstack's current documentation does not allow you to do so. So even if your test fails it will be marked as passed (green) on browserstack.
In addition, there is an example of how to update the reason for the test's failure using browserstack rest api. see 'single_failed.js'
Mark tests as passed/failed in Browserstack
Report reason for failed test to Browserstack
Report failed expectations to Browserstack
Upgrade to support Protractor 5