Actions
action #18000
opencoordination #13812: [epic][dashboard] openQA Dashboard ideas
[dashboard] Better integration of status from external jobs and testing systems
Start date:
2017-03-24
Due date:
% Done:
0%
Estimated time:
Description
User story¶
As a tester I want to use an easy way to publish my test results on an openQA server to use openQA as a dashboard for test results
acceptance criteria¶
- AC1: There is a way to fill the whole jobs details page without the need to use os-autoinst, e.g. console client to fill "Details" and "Logs & Assets"
- AC2: The whole workflow is documented
tasks¶
- Come up with a way how the console tool should upload the missing information, e.g. how the command line parameters are called, e.g. "openqa-client upload_screenshot ..."
- document the current API used internally by the openQA backend to uploads results, e.g. mandatory variables.
- optional: some refactoring and improvements can be done to ease using that API by other tools, too.
further details¶
goal: To use the openQA dashboard as the main reporting platform also for 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
Actions