Good naming scheme for test derived artifacts (screenshots) #2936
Unanswered
Bananeweizen
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I was working on an extension that takes screenshots of failed tests. Right now the naming scheme of the screenshot files is roughly this:
context.getRequiredTestClass().getName() + "_" + context.getRequiredTestMethod().getName() +someExtension
However, given there might be parameterized tests, dynamic tests etc. this is probably not sufficient in some cases. I guess that others had to solve the "create a name for an artifact that can traced back to the test that created it" problem before me, so I'm wondering if someone can recommend a better naming scheme?
Beta Was this translation helpful? Give feedback.
All reactions