-
Notifications
You must be signed in to change notification settings - Fork 205
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
Highlight available test result comments on overview #514
Conversation
9740792
to
8c9ac90
Compare
@@ -533,6 +533,8 @@ table.overview .failedmodule { | |||
.fa.result_incomplete { color: #AF1E11;} | |||
.fa.module_none { color:#bebebe;} | |||
|
|||
.comment { color: Grey; } |
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 you want the selector more specific - or the class name itself. comments can be anywhere anything - but you're only meaning the one icon on the overview page.
updated:
@coolo I did not do "prefetch" as I don't know what this would actually do in this context or how I should do it and also I did not test with a production database dump as I forgot the link you gave me with a dump. |
@@ -139,6 +139,14 @@ | |||
</span> | |||
% } | |||
% } | |||
% if ($res->{comments} && $res->{comments} > 0) { |
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.
do you expect it to be < 0?
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.
no, but if it would be, I better not try to dereference the comments.
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.
then the > 0 is nonsense
updated:
|
+waitfor should the comments bubble always be shown or only when selected with a query parameter? |
as job comments are very rare, I'm fine with them being always there in case |
The availability of comments on the test result page is shown on the test result overview page next to the status icon and failed modules if available. The icon only appears if comments are available. This way it should be much easier for reviewers of test runs to exchange and see if an issue has already been noticed by someone else. Be aware that so far the comments are per test result not per test case or scenario. Related issue: https://progress.opensuse.org/issues/10212
Prefetch the job comments instead of relying on custom query.
aww, I messed up, wait for update. Please don't look |
Also remembers tab on reload of URLs with hash.
updated:
|
Highlight available test result comments on overview
The availability of comments on the test result page is shown on the test
result overview page next to the status icon and failed modules if available and if selected with the corresponding query parameter "show_comment=1".
The icon only appears if comments are available. This way it should be much
easier for reviewers of test runs to exchange and see if an issue has already
been noticed by someone else.
Be aware that so far the comments are per test result not per test case or
scenario.
Related issue: https://progress.opensuse.org/issues/10212
see screenshot for example with hover info:
![openqa_comment_bubble](https://cloud.githubusercontent.com/assets/1693432/12575830/e16a1e3a-c40f-11e5-98b0-70cc8fef62d0.png)