-
Notifications
You must be signed in to change notification settings - Fork 98
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
Allow for commenting of steps #50
Labels
Comments
Just to clarify, this should be really a new piece of information on a step rather than just setting the extendedDescription of a particular step instance? |
Also, from my understanding of the codebase, this would roughly involve the following:
I hope I got the basic design of this feature right. |
Airblader
added a commit
to Airblader/JGiven
that referenced
this issue
Jun 25, 2016
This commit allows commenting on a step by calling comment() after invoking the corresponding step method. Furthermore, it displays said comment in the plain text report, if one was given. relates to TNG#50
Airblader
added a commit
to Airblader/JGiven
that referenced
this issue
Jun 25, 2016
This commit allows commenting on a step by calling comment() after invoking the corresponding step method. Furthermore, it displays said comment in the plain text report, if one was given. relates to TNG#50
Airblader
added a commit
to Airblader/JGiven
that referenced
this issue
Jun 26, 2016
We display step comments just like extended descriptions as a tooltip. In case both an extended description and a tooltip are specified for the step, both are displayed with a line break in between them. relates to TNG#50
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is already possible to provide an extended description to steps by using the
@ExtendedDescription
annotation. However, sometimes you want to comment a certain step-invocation and not all invocations of that step. This comment should also appear in the report.Example:
The text was updated successfully, but these errors were encountered: