openQA job group review script had already been developed in previous hackweeks:
Posted review results in job group page looks like:
Failed by Product Issues (17.6% 3 in total):
Bug referenced: bsc#1111111 THIS IS BUG ONE
- Test Suite 1
- Test Suite 2
Softfailed (29.4% 5 in total):
Bug referenced: bsc#2222222 THIS IS BUG TWO
- Test Suite 3
- Test Suite 4
It honestly summarizes test suites run results by percentage and failure pattern/reason, associated product bug or automation fix, and whether a failure is being followed up or in pending status on the job group level which gives an overview quickly and clearly.
I was wondering whether it would be more helpful or interesting if:
Compare software packages between the current and last builds to let people know whether a software package is modified or not
Investigate and implement the above by using Golang
Learn new things from above work items
Goal for this Hackweek
Finish the project
No Hackers yet
Looking for hackers with the skills:
Nothing? Add some keywords!
This project is part of:
Hack Week 20
This project is one of its kind!