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.

Sign up for GitHub

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

Jump to bottom

Screenshot folder hierarchy #1595

Closed
ClaytonAstrom opened this issue Jul 7, 2017 · 2 comments
Closed

Screenshot folder hierarchy #1595

ClaytonAstrom opened this issue Jul 7, 2017 · 2 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.

Comments

@ClaytonAstrom
Copy link

Are you requesting a feature or reporting a bug?

Feature

What is the current behavior?

Screenshot folder hierarchy is by testIndex (test-1/browser, test-2/browser, etc.)

What is the expected behavior?

Screenshot folder hierarchy should be by fixture/testName/browser

Specify your

  • operating system: Windows 7
  • testcafe version: 0.16
  • node.js version: 6.10.1
@ClaytonAstrom
Copy link
Author

Duplicate of #1515 I think

@ClaytonAstrom ClaytonAstrom mentioned this issue Jul 10, 2017
Closed
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ClaytonAstrom