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

add run context to reportItem #2703 #2720

Closed
wants to merge 2 commits into from

Conversation

marcusrc
Copy link

No description provided.

@testcafe-build-bot
Copy link
Collaborator

❌ Tests for the commit cc8c95b have failed. See details:

@testcafe-build-bot
Copy link
Collaborator

❌ Tests for the commit f50846c have failed. See details:

@marcusrc
Copy link
Author

@testcafe-build-bot /retest

@@ -31,7 +31,8 @@ export default class Reporter {
errs: [],
unstable: false,
startTime: null,
testRunInfo: null
testRunInfo: null,
contexts: []
Copy link
Collaborator

@miherlosev miherlosev Aug 14, 2018

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')
Copy link
Collaborator

@miherlosev miherlosev Aug 14, 2018

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.

@miherlosev
Copy link
Collaborator

miherlosev commented Aug 14, 2018

@marcusrc

Thank you for your work. At present, we have some problems with running our tests in mobile browsers.
You can continue your PR despite the red tests.

@miherlosev
Copy link
Collaborator

Hi @marcusrc

We've discussed your PR and decided not to include ctx and fixtureCtx in reportItem (see discussion in this issue for more detail).
We are thinking about an API that should cover your needs.

@miherlosev miherlosev closed this Aug 15, 2018
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.

3 participants