action #37429
closed
coordination #34138: [functional][u][epic][eternal] work on any issue from http://github.com/os-autoinst/openqa_review/issues/
[functional][y] Improve openqa_review to include skipped tests into the report
Added by okurz almost 6 years ago.
Updated about 5 years ago.
Category:
Enhancement to existing tests
- Copied to action #37432: [functional][u] work on https://github.com/os-autoinst/openqa_review/projects/1 according to ordering added
- Copied to deleted (action #37432: [functional][u] work on https://github.com/os-autoinst/openqa_review/projects/1 according to ordering)
- Target version changed from Milestone 17 to Milestone 17
- Due date deleted (
2018-07-03)
- Assignee set to okurz
As per our discussion I move it out from the sprint. Let me know if you want to discuss it again, we can rework and schedule. Sprint is full anyway.
- Assignee deleted (
okurz)
- Target version changed from Milestone 17 to Milestone 18
@riafarov I tried to provide a bigger context with the ticket hierarchy. #37351 is the saga which should give a long-term vision and motivation why we work in this direction. Now there is also a relation to #27735 about using ttm which might be an alternative but also bring together ideas. The parent ticket #34138 has a motivation with explanation what openqa-review is used for and how people rely on it. Please help me to make it even more clear if it is not enough.
- Description updated (diff)
- Priority changed from Normal to Low
- Target version changed from Milestone 18 to future
y-team does not like this somehow but leaving with lower prio in case anyone from y-team looks for "and now for something completely different" eventually :)
- Due date set to 2019-02-28
- Subject changed from [functional][y] work on https://github.com/okurz/openqa_review/projects/1 according to ordering to [functional][y] work on https://github.com/os-autoinst/openqa_review/projects/1 according to ordering
- Description updated (diff)
- Due date changed from 2019-02-28 to 2019-03-12
- Due date changed from 2019-03-12 to 2019-03-26
- Subject changed from [functional][y] work on https://github.com/os-autoinst/openqa_review/projects/1 according to ordering to [functional][y] Improve openqa_review to include skipped tests into the report
- Description updated (diff)
- Estimated time set to 5.00 h
- Description updated (diff)
- Assignee set to ybonatakis
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
I'm not sure if I understand your question, but if you're referring to sections of the report to be generated, I guess it could be at the end, in a similar way to sections "new issues" or "existing issues" for each architecture.
JERiveraMoya wrote:
I'm not sure if I understand your question, but if you're referring to sections of the report to be generated, I guess it could be at the end, in a similar way to sections "new issues" or "existing issues" for each architecture.
ok. i think you answered my question. Thanks @JERiveraMoya
- Due date changed from 2019-03-26 to 2019-04-09
- Status changed from Feedback to Resolved
- Copied to action #50186: [functional][y] Include url to the skipped tests in openqa_review added
Also available in: Atom
PDF