-
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
Additional grouping of big tables #168
Comments
While this might be possible, I am not sure whether this is the best thing to do. What about splitting the scenario in multiple ones? Then you could give each scenario a meaningful name to group the cases. |
The only solution then is to group the scenario by users as the classes are scanned automatically. I'd hoped that I'd be able to not split the dataprovider one more time, but probably you are right and this is the easiest solution. |
Hm, in this particular case, I'd have to split one test into 4 tests and since this a crud test, there would be 16 tests instead of 4 - pretty verbose IMHO. |
What would be your suggestion? |
Maybe to define an annotation where a field name can be supplied that will be then used for the additional grouping? |
Ok, but how should the grouping actually look like in the report? |
Good question By stripping the redundant content, the large table is much easier to read.
In the html5 report, the grouping could be collapsible. |
Is it really important for you to have the grouping in the text report? Otherwise this could be just implemented in the HTML report and there would be no need for additional annotations. |
It would be perfectly fine if this is possible in the HTML report. |
ok, great. That simplifies the solution :-) |
I implemented this now in the HTML Report, you can have a look how it looks like here: |
Looks really fine to me, thank you! |
And again :)
Test Class: com.sobis.pirsjava.tests.security.IKeywordSecurityTest
Scenario: create keyword
Given logged in user
When user creates entity
Then jafaccessdeniedexception thrown
Cases:
It would be great if it is possible to define a parameter to perform a grouping, wouldn't it? :)
The text was updated successfully, but these errors were encountered: