action #37429

action #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 over 1 year ago. Updated 11 months ago.

Status:ResolvedStart date:15/06/2018
Priority:LowDue date:09/04/2019
Assignee:ybonatakis% Done:

0%

Category:Enhancement to existing testsEstimated time:5.00 hours
Target version:QA - future
Difficulty:
Duration: 213

Description

Motivation

I as a QA Project Manager would like to know which tests were not executed for particular build in the report to understand risks we have to miss bugs in given areas.

https://github.com/os-autoinst/openqa_review/issues/98

Acceptance criteria

  1. Generated report from openqa-review includes section which lists skipped tests

Further details

Script can executed manually.

Generated reports can found here: Latest report based on openQA test results http://s.qa.suse.de/test-status , SLE12: http://s.qa.suse.de/test-status-sle12 , SLE15: http://s.qa.suse.de/test-status-sle15


Related issues

Copied to openQA Tests - action #50186: [functional][y] Include url to the skipped tests in openq... Resolved 15/06/2018 21/05/2019

History

#1 Updated by okurz over 1 year ago

  • Copied to action #37432: [functional][u] work on https://github.com/os-autoinst/openqa_review/projects/1 according to ordering added

#2 Updated by okurz over 1 year ago

  • Copied to deleted (action #37432: [functional][u] work on https://github.com/os-autoinst/openqa_review/projects/1 according to ordering)

#3 Updated by okurz over 1 year ago

  • Target version changed from Milestone 17 to Milestone 17

#4 Updated by riafarov over 1 year ago

  • Due date deleted (03/07/2018)
  • 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.

#5 Updated by okurz over 1 year ago

  • 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.

#6 Updated by okurz over 1 year ago

  • Description updated (diff)

#7 Updated by okurz over 1 year ago

  • 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 :)

#8 Updated by okurz over 1 year ago

  • Due date set to 28/02/2019

#9 Updated by okurz about 1 year ago

  • 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

#10 Updated by okurz about 1 year ago

  • Description updated (diff)

#11 Updated by riafarov about 1 year ago

  • Due date changed from 28/02/2019 to 12/03/2019

#12 Updated by riafarov 12 months ago

  • Due date changed from 12/03/2019 to 26/03/2019

No capacity

#13 Updated by riafarov 12 months ago

  • 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

#14 Updated by riafarov 12 months ago

  • Description updated (diff)

#15 Updated by ybonatakis 11 months ago

  • Assignee set to ybonatakis

#16 Updated by ybonatakis 11 months ago

  • Status changed from Workable to In Progress

#17 Updated by ybonatakis 11 months ago

  • Status changed from In Progress to Feedback

@riafarov @okurz i wonder where is the best place to add this section?

#18 Updated by JERiveraMoya 11 months ago

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.

#19 Updated by ybonatakis 11 months ago

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

#20 Updated by JERiveraMoya 11 months ago

  • Due date changed from 26/03/2019 to 09/04/2019

Moving to next sprint.

#22 Updated by riafarov 11 months ago

  • Status changed from Feedback to Resolved

#23 Updated by riafarov 11 months ago

  • Copied to action #50186: [functional][y] Include url to the skipped tests in openqa_review added

Also available in: Atom PDF