You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment I can only comment my test cases using the comment command. This is a line by line documentation possibility that helps me structuring my test case - and that's it.
I'd like to have the possibility to document in the test case itself - what it is for, what it is testing - like I may do in javadoc for JUnit tests with HTML.
For achieving this I propose enhancing the existing comment command by accepting WIKI language for a flexible commenting and documentation solution. Then I could document my test cases in various comments and also include this in a well formatted way in the Wetator result report.
The text was updated successfully, but these errors were encountered:
But we have to think about how the WTE can support this.
Adjustable line height (per line)?
Preview for the generated Richtext/HTML?
Help page for the Wiki markup?
Only having one line to enter the raw Wiki markup does not help the user so much, does it?
% migrated from trac
At the moment I can only comment my test cases using the comment command. This is a line by line documentation possibility that helps me structuring my test case - and that's it.
I'd like to have the possibility to document in the test case itself - what it is for, what it is testing - like I may do in javadoc for JUnit tests with HTML.
For achieving this I propose enhancing the existing comment command by accepting WIKI language for a flexible commenting and documentation solution. Then I could document my test cases in various comments and also include this in a well formatted way in the Wetator result report.
The text was updated successfully, but these errors were encountered: