Project

General

Profile

coordination #13812

[epic][dashboard] openQA Dashboard ideas

Added by dheidler about 5 years ago. Updated about 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2017-01-10
Due date:
% Done:

67%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Related use cases

Especially UC1 and UC5

ideas

  • Failing tests
  • Consider some testsuites as more important than other testsuites #13780
  • Filter on index page for specific groups -> gh#923
  • Group test results by build number, related ticked: #13742
  • finish at least one build per day -> Current workflow: QA reviewer decides this and can mark one build as important, feature request #15844
  • priority of bugs in review reports -> openqa_review#25
  • on index page add link to filter box (down) because "no one scrolls down" -> https://gitlab.suse.de/openqa/salt-states-openqa/merge_requests/19
  • "milestones" as special tags (asked by ast) -> http://open.qa/docs/#_tag_builds_with_special_comments_on_group_overview
  • special mode of Dashboard mode which allow to see summary of all job groups in optimized to full screen view #17886
  • Statistics over
    • failed/passed ratio per build for each product
    • number of executed testsuites per build for each product
  • List overall "todo: review" entries
  • Overall status indicator (eg. status light / 'Ampel')
  • "the oldest still open bug"
  • "the most flaky scenario / module / architecture"
  • back-references to bugs
    • "reverse" carry over: when old job failed and new job passed -> post comment into bug that would have been carried over to new job if it would have failed (related to okurz wiki )
  • scenario result and state change in each tests result
  • track all changes (eg. infrastructure, test changed, product changed, ...)
  • measure completion time of builds, also per architecture
  • tests that have not run for long time
  • live update of bug status (e.g. subscribe a special user to email and trigger events based on email reception)
  • personal customized view vs. static hierarchical dashboard view
  • "weather of scenario", e.g. is it failing all the time or just sporadically
  • better integration of status from external jobs and testing systems (see below)
  • customized, personal filter pre-saved
  • dheidler: learn about bugzilla integration in "smash" (e.g. ask tgoettlicher)

implementation ideas

better integration of status from external jobs and testing systems

To use openQA also as the main reporting platform relying on other tools we have in our infrastructure (at SUSE) there are already test runners feeding back the information e.g. in junit format. Also, using the client script jobs can be started and their result set along with comments, e.g. for tags. Example:

job_id=$(client --host http://localhost jobs post TEST=foo_external _GROUP="openSUSE Tumbleweed AArch64" BUILD=1 | sed -n 's/^{ id => \([0-9]\+\) }$/\1/p')
client --host http://localhost jobs/${job_id}/set_done post result=passed
client --host http://localhost jobs/${job_id}/comments post text=bsc#1234

references

could be inspired by sonar, e.g. see https://sonarqube.com/ and https://sonarqube.com/dashboard?id=c-family%3ASamba&did=148, but also jenkins Radiator View Plugin or jenkins eXtreme Feedback Panel Plugin or https://jenkins.io/blog/2016/01/10/beautiful-jenkins-dashboard/
… or https://github.com/influxdata/chronograf

And don't forget about http://testsuites.qa.suse.cz -> dead by now


Subtasks

action #15844: [tools]finish at least one build per dayResolvedokurz

action #17886: [dashboard] Create full screen view for openQA dashboardResolvedilausuch

action #18000: [dashboard] Better integration of status from external jobs and testing systemsWorkable


Related issues

Related to openQA Project - action #10148: better notification and user feedbackResolved2015-11-13

Related to openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on productResolved2016-01-12

Related to openQA Project - action #13712: [tools][dashboard]overview page for multiple products at onceResolved2016-06-21

Related to openQA Project - action #13714: backlink references in openqa comments to tickets inside the corresponding tickets, like githubNew2016-09-13

Related to openQA Project - coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issuesBlocked2017-01-232021-09-24

History

#3 Updated by mkittler about 5 years ago

  • Description updated (diff)

#4 Updated by okurz about 5 years ago

  • Description updated (diff)

#5 Updated by okurz about 5 years ago

  • Description updated (diff)

#6 Updated by okurz about 5 years ago

  • Related to action #10148: better notification and user feedback added

#7 Updated by okurz about 5 years ago

  • Related to action #10188: [tools][dashboard]Tracking open bugs based on product added

#8 Updated by okurz about 5 years ago

  • Description updated (diff)

#9 Updated by okurz about 5 years ago

  • Related to action #13712: [tools][dashboard]overview page for multiple products at once added

#10 Updated by okurz about 5 years ago

  • Description updated (diff)
  • Status changed from Feedback to In Progress

Add notes from today's meeting.

#11 Updated by okurz about 5 years ago

  • Description updated (diff)

#12 Updated by okurz about 5 years ago

  • Description updated (diff)

updated resolved ideas

#13 Updated by mkittler about 5 years ago

  • Description updated (diff)

#14 Updated by okurz about 5 years ago

  • Related to action #13714: backlink references in openqa comments to tickets inside the corresponding tickets, like github added

#16 Updated by okurz almost 5 years ago

  • Description updated (diff)

#17 Updated by okurz almost 5 years ago

  • Description updated (diff)

#18 Updated by mkittler almost 5 years ago

  • Description updated (diff)

#19 Updated by okurz almost 5 years ago

pull out "finish at least one build per day" as it's own ticket: #15844

#20 Updated by okurz almost 5 years ago

  • Description updated (diff)

#21 Updated by okurz almost 5 years ago

  • Category set to Feature requests

#22 Updated by okurz over 4 years ago

  • Description updated (diff)

#23 Updated by okurz over 4 years ago

  • Description updated (diff)

incorporate content from #17886

#24 Updated by okurz over 4 years ago

  • Has duplicate action #17886: [dashboard] Create full screen view for openQA dashboard added

#25 Updated by okurz over 4 years ago

  • Has duplicate deleted (action #17886: [dashboard] Create full screen view for openQA dashboard)

#26 Updated by okurz over 4 years ago

  • Description updated (diff)

#27 Updated by RBrownSUSE over 4 years ago

  • Subject changed from openQA Dashboard ideas to [tools]openQA Dashboard ideas

#28 Updated by RBrownSUSE over 4 years ago

  • Subject changed from [tools]openQA Dashboard ideas to [tools][dashboard]openQA Dashboard ideas

#29 Updated by okurz over 3 years ago

  • Description updated (diff)
  • Status changed from In Progress to Workable

crossed of the completed parts and reordered to show the still open ideas below the completed ones.

#30 Updated by okurz over 3 years ago

  • Description updated (diff)

http://testsuites.qa.suse.cz seems to be dead by now

#31 Updated by okurz about 3 years ago

  • Related to coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues added

#32 Updated by okurz over 1 year ago

  • Subject changed from [tools][dashboard]openQA Dashboard ideas to [epic][dashboard] openQA Dashboard ideas
  • Status changed from Workable to Blocked
  • Assignee set to okurz

#33 Updated by okurz about 1 year ago

  • Target version set to Ready

#34 Updated by okurz about 1 year ago

  • Status changed from Blocked to New
  • Assignee deleted (okurz)
  • Target version changed from Ready to future

#17886 is a subtask that got resolved. With this I would leave the further ideas for "future".

#35 Updated by szarate about 1 year ago

  • Tracker changed from action to coordination

Also available in: Atom PDF