We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From Slack: Raised by @Julian
Hi guys, really nice framework. Would like to know how I can change the test category. The default is:
String DEFAULT_REGRESSION_CATEGORY = "Regression";
As an SDET or Dev I want to set the test category at test level So that I can get filter these tests in the HTML report after the test run
Things to do:
#category1 #category2
@Author1
ZeroCodeReportGeneratorImpl#optionalAuthor
#free-text
Regression
Allow
@Author
@@Author
#Category
Also relates to: #207 (not a AC of this ticket)
The text was updated successfully, but these errors were encountered:
@authorjapps, can I work on it? Need some guidance though, as I'm relatively new to the code base.
Sorry, something went wrong.
@harshasridhar , please go ahead. Thanks!
Please ping us in Slack in case you need any help ✌️
Available in v 1.3.23
1.3.23
authorjapps
No branches or pull requests
Background:
From Slack:
Raised by @Julian
Hi guys, really nice framework. Would like to know how I can change the test category. The default is:
AC1
As an SDET or Dev
I want to set the test category at test level
So that I can get filter these tests in the HTML report after the test run
Things to do:
#category1 #category2
in the test scenario free text@Author1
which sets the filter for authorsZeroCodeReportGeneratorImpl#optionalAuthor
method implementation and usage#free-text
and set to Extent category(which is currently set toRegression
)AC3
Allow
@Author
for capturing author name e.g. David, Alex, Anton etc@@Author
#Category
fro capturing category information e.g. DIT, DEV, SIT, Small-Regression, Smoke etcAlso relates to:
#207 (not a AC of this ticket)
The text was updated successfully, but these errors were encountered: