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

Name a screenshots folder by the test name, or add a text file under the folder having the test name #1975

Closed
adrianaisemberg opened this issue Nov 30, 2017 · 4 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: enhancement The accepted proposal for future implementation.

Comments

@adrianaisemberg
Copy link

Are you requesting a feature or reporting a bug?

Feature

What is the current behavior?

Running several tests and saving screenshots in each results in a list of folders and having no way to correlate between a test and its screenshots folder.

What is the expected behavior?

Somehow be able to find the relevant screenshots of a test, especially a failed test.

suggestion:
Place a test.txt file in each folder with the test details, such as name, file-name etc.

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

Write some tests. Take screenshots from each. Run all of them.
Observer the folder structure. Although it is well-structured (date/index/browser), it seems completely random when I want to find my test's screenshots.

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:
@adrianaisemberg
Copy link
Author

Just realized that the report shows the screenshots path:
image

@AndreyBelym
Copy link
Contributor

Hi @adrianaisemberg, we are in process of designing extensions of screenshoting API, and they will make screenshot paths more flexible. Stay tuned for the next couple of weeks!

Right now, it's possible to use JSON reporter: https://github.com/DevExpress/testcafe-reporter-json to get more structured screenshot information.

@AlexanderMoskovkin
Copy link
Contributor

closed in favor of #2152

miherlosev added a commit that referenced this issue Jul 6, 2018
* Screenshot file pattern

* refactor test constrants

* small refactoring

* renames

* don't correct file path for custom file path

* try to fix tests2

* revert back correct file path for custom path

* revert dedent module

* fix review issues
@AndreyBelym AndreyBelym added TYPE: enhancement The accepted proposal for future implementation. and removed TYPE: proposal labels Feb 6, 2019
@lock
Copy link

lock bot commented Mar 27, 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 27, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

3 participants