Project

General

Profile

Actions

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.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
2018-06-15
Due date:
2019-04-09
% Done:

0%

Estimated time:
5.00 h
Difficulty:

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 1 (0 open1 closed)

Copied to openQA Tests - action #50186: [functional][y] Include url to the skipped tests in openqa_reviewResolvedybonatakis2018-06-152019-05-21

Actions
Actions #1

Updated by okurz almost 6 years ago

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

Updated by okurz almost 6 years ago

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

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 17
Actions #4

Updated by riafarov almost 6 years ago

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

Actions #5

Updated by okurz almost 6 years 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.

Actions #6

Updated by okurz over 5 years ago

  • Description updated (diff)
Actions #7

Updated by okurz over 5 years 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 :)

Actions #8

Updated by okurz over 5 years ago

  • Due date set to 2019-02-28
Actions #9

Updated by okurz about 5 years 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
Actions #10

Updated by okurz about 5 years ago

  • Description updated (diff)
Actions #11

Updated by riafarov about 5 years ago

  • Due date changed from 2019-02-28 to 2019-03-12
Actions #12

Updated by riafarov about 5 years ago

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

No capacity

Actions #13

Updated by riafarov about 5 years 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 h
Actions #14

Updated by riafarov about 5 years ago

  • Description updated (diff)
Actions #15

Updated by ybonatakis about 5 years ago

  • Assignee set to ybonatakis
Actions #16

Updated by ybonatakis about 5 years ago

  • Status changed from Workable to In Progress
Actions #17

Updated by ybonatakis about 5 years ago

  • Status changed from In Progress to Feedback

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

Actions #18

Updated by JERiveraMoya about 5 years 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.

Actions #19

Updated by ybonatakis about 5 years 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

Actions #20

Updated by JERiveraMoya about 5 years ago

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

Moving to next sprint.

Actions #22

Updated by riafarov about 5 years ago

  • Status changed from Feedback to Resolved
Actions #23

Updated by riafarov about 5 years ago

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

Also available in: Atom PDF