Screenshot flexibility request

[ClaytonAstrom]

Are you requesting a feature or reporting a bug?

Feature

What is the current behavior?

Screenshot naming conventions are very restricted, command line parameter -S has no control at all.

What is the expected behavior?

1. Screenshots should have flexible naming conventions. For example, Junit Attachment Plugin uses the classname xml attribute to associate the artifacts with the package, or uses absolute references

2. Fixtures and/or tests should have the ability to individually take screenshots on fail. Maybe a hook that can be defined per test? If I have a fixture with:

   test("Test A", async => {});
   test("Test B", async => {});
   test("Test C", async => {});

   Then I should be able to specify which tests I want to take a screenshot on failure. Example:

   test("Test A", async => {});
   test
     .screenShotOnFail(
   	//Some kind of path structure here maybe?      
     )
     ("Test B", async => {});
   test("Test C", async => {});

Specify your

• operating system: Windows 7
• testcafe version: 0.16.0
• node.js version: 6.10.1

Similar issues: #1515 and #1595

[AlexanderMoskovkin]

closed in favor of #2152

[lock]

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.