QA » openQA Project

Related use cases¶

Especially UC1 and UC5

ideas¶

• Failing tests
  • with unassigned ticket -> currently implemented as unassigned report
  • with resolved / closed ticket (also see #12092)
  • related ticket: #10188
• 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