-
Notifications
You must be signed in to change notification settings - Fork 338
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
Make it possible to include custom columns from TestActions in case, class and package tables #503
Conversation
Desired reviewer: @timja |
can you check the build is green before requesting my review please |
Looks also the master branch is broken : https://ci.jenkins.io/job/Plugins/job/junit-plugin/job/master/321/ |
@timja @jonesbusy thanks for comments! Yes, the reason the build fails is RequireUpperBoundDeps, and this issue comes from the master branch. It's not introduced by my pull request. For example, I saw the same failure in @timja 's pull request #501 that was merged yesterday: https://ci.jenkins.io/job/Plugins/job/junit-plugin/view/change-requests/job/PR-501/1/ It looks like the issue has been introduced by dependabot after c789200. At the same time, it looks like @timja is replacing dependabot with renovate? I'm happy to try and tackle the RequireUpperBoundDeps failure if no-one gets to it before me. Am I expected to fix that in this pull request, or shall it be done separately in a different pull request? |
Weird given CI passed on that build. I've switched it to renovate but they are basically the same tools with a slightly different feature set. If you're happy to do it then a separate PR would be great. Otherwise I'll get to it when I have a chance |
@timja @jonesbusy I've created pull request #505 to work around the RequireUpperBoundDeps failure. |
@jonaslind I'm not maintainer of this plugin, but same things happen to me on the skip-notifications-trait-plugin |
Now with the fix from #505, the build is green. |
@timja , do you think you'll be able to review this pull request? |
At some point yes but I don't have time right now, I've requested review from all the maintainers though |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine, is there a reason you're just doing this for class results and not other ones?
* <li>classresult-tableheader.jelly: allows additional table headers to be shown in the test class' table of test methods</li> | ||
* <li>classresult-tablerow.jelly: allows additional table cells to be shown in the test class' table of test methods</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think class's is the correct possessive singular:
* <li>classresult-tableheader.jelly: allows additional table headers to be shown in the test class' table of test methods</li> | |
* <li>classresult-tablerow.jelly: allows additional table cells to be shown in the test class' table of test methods</li> | |
* <li>classresult-tableheader.jelly: allows additional table headers to be shown in the test class's table of test methods</li> | |
* <li>classresult-tablerow.jelly: allows additional table cells to be shown in the test class's table of test methods</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the grammar fix, will include in next commit!
@timja Thank you for the review! I only did this for
That'll make custom columns more generic and consistent across pages. It's more future-proof. I'll prepare a new commit with jelly hooks in these places too as well as unit tests verifying that it works. Please let me know if you can think of another table where it makes sense to add custom columns. There are |
I think they are as you click through test rests from the class level to the individual test level. Its often hard to tell where they are used, I generally put some gibberish in each file and click around till I trace them back |
@timja, here's a new commit with custom columns added to Please have a look when you have the time. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, just one docs change missing
@@ -121,4 +121,8 @@ public TabulatedResult blockToTestResult(@NonNull PipelineBlockWithTests block, | |||
public String getChildTitle() { | |||
return ""; | |||
} | |||
|
|||
public String getChildType() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add javadoc
Add optional jelly hooks that allow TestActions to contribute custom columns to tables that list CaseResults, ClassResults and PackageResults.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Thank you very much @timja for all your help and input! |
Add optional jelly hooks that allow TestActions to contribute custom columns to tables that list CaseResults, ClassResults and PackageResults.
More details in the corresponding enhancement issue:
Fixes #494