action #38957

[functional][u] Refactor the openqa-review code to not use "Issue" object for the messages that does not have a valid bugref.

Added by oorlov over 1 year ago. Updated over 1 year ago.

Status:NewStart date:31/07/2018
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Enhancement to existing tests
Target version:QA - future
Difficulty:
Duration:

Description

There is a case in openQA, when soft fail is raised, but it does not contain a valid bug reference ('bugref' is a ticket number on Bugzilla or Progress tracking systems, written in a format of #, e.g. bcs#12345, poo#12345).

In the past, those soft-fail messages did not appear in the report and even might broke the report generation, as invalid bugref might be found.

We've fixed this behavior in poo#35760 with some workarounds. According to @dheidler, the message, that does not contain a valid bugref, should not be an Issue object, as the object was designed to represent an issue from bug tracker.

The task is to refactor the existing code in order to avoid using Issue object for the soft-fail messages, that does not contain a valid bugref.


Related issues

Related to openQA Tests - action #35760: [functional][u][medium] work on any issue from http://git... Resolved 02/05/2018 31/07/2018

History

#1 Updated by oorlov over 1 year ago

  • Related to action #35760: [functional][u][medium] work on any issue from http://github.com/okurz/openqa_review/issues/ added

#2 Updated by okurz over 1 year ago

  • Subject changed from [functional] Refactor the openqa-review code to not use "Issue" object for the messages that does not have a valid bugref. to [functional][u] Refactor the openqa-review code to not use "Issue" object for the messages that does not have a valid bugref.
  • Category set to Enhancement to existing tests
  • Target version set to Milestone 19

#3 Updated by okurz over 1 year ago

  • Target version changed from Milestone 19 to future

Also available in: Atom PDF