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 screenshots path from takeScreenshot\takeElementScreenshot actions into report #2216

Closed
arubtsov opened this issue Mar 15, 2018 · 2 comments
Assignees
Labels
API MODIFICATION LEVEL: non-breaking changes AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: reporting TYPE: enhancement The accepted proposal for future implementation.
Milestone

Comments

@arubtsov
Copy link
Contributor

Are you requesting a feature or reporting a bug?

Requesting a feature.

What is the current behavior?

If path option is specified for one of takeScreenshot actions in test, then testRunInfo parameter of reportTestDone reporter plugin's method receives only base screenshots path (specified in screenshots method of test runner).

What is the expected behavior?

Information about screenshots locations could be obtained from testRunInfo.

How would you reproduce the current behavior (if this is a bug)?

Provide the test code and the tested page URL (if applicable)

Tested page URL:

Test code

Specify your

  • operating system:
  • testcafe version:
  • node.js version:
@AndreyBelym AndreyBelym added this to the Sprint #12 milestone May 21, 2018
@AlexKamaev AlexKamaev self-assigned this May 24, 2018
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue May 30, 2018
AlexKamaev added a commit to AlexKamaev/testcafe that referenced this issue May 31, 2018
miherlosev pushed a commit to miherlosev/testcafe that referenced this issue Jun 25, 2018
@MargaritaLoseva
Copy link
Contributor

I'm working on this

@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
…s into report (closes DevExpress#2216) (DevExpress#2476)

* more properties

* fix tests

* fix minor review changes

* move quarantine attempts info to separate object in testRunInfo

* add test for unstable and naming changes
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
API MODIFICATION LEVEL: non-breaking changes AREA: server STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: reporting TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

6 participants