-
Notifications
You must be signed in to change notification settings - Fork 674
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
add run context to reportItem #2703 #2720
Conversation
❌ Tests for the commit cc8c95b have failed. See details: |
❌ Tests for the commit f50846c have failed. See details: |
@testcafe-build-bot /retest |
@@ -31,7 +31,8 @@ export default class Reporter { | |||
errs: [], | |||
unstable: false, | |||
startTime: null, | |||
testRunInfo: null | |||
testRunInfo: null, | |||
contexts: [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two different contexts: fixture and test.
See this help topic for more detail.
So instead of a single context
prop, please add two properties: ctx
and fixtureCtx
.
@@ -43,7 +44,8 @@ export default class Reporter { | |||
screenshotPath: reportItem.screenshotPath, | |||
screenshots: reportItem.screenshots, | |||
quarantine: reportItem.quarantine, | |||
skipped: reportItem.test.skip | |||
skipped: reportItem.test.skip, | |||
contexts: sortBy(reportItem.contexts, 'userAgent') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess sorting is not necessary.
In general case, a custom reporter plugin should decide itself will it sort contexts or not.
Thank you for your work. At present, we have some problems with running our tests in mobile browsers. |
No description provided.