Project

General

Profile

Actions
Copy link

coordination #109740

closed

coordination #109668: [saga][epic] Stable and updated non-qemu backends for SLE validation

[epic] Stable os-autoinst unit tests with good coverage

Added by okurz over 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
Ready
Start date:
2021-06-30
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

To be able to safely improve and extend os-autoinst, e.g. for #109668, we need to have reliable and stable unit tests, good code coverage and sufficient static checks.

Subtasks 6 (0 open — 6 closed)

action #94952: [easy][beginner] Increase code coverage of os-autoinst basetest.pm size:MResolvedrobert.richardson2021-06-30

Actions
action #107998: [sporadic][os-autoinst] t/29-backend-driver.t fails in "log output for backend driver creation"Resolvedtinita2022-03-08

Actions
action #111251: Cover code of os-autoinst path OpenQA/ fully (statement coverage) size:MResolvedtinita2022-05-18

Actions
action #111254: Cover code of os-autoinst path backend/ fully (statement coverage) size:MResolvedmkittler2022-05-18

Actions
action #121357: [easy][beginner] Ensure 100% test coverage of t/ in os-autoinst size:MResolvedosukup

Actions
action #122047: [tools] tesseract ocr test failsResolvedosukup2022-12-15

Actions

Related issues 4 (0 open — 4 closed)

Related to openQA Project (public) - action #109620: os-autoinst: Improve unit-test code coverage for backend::svirt size:MResolvedosukup

Actions
Related to openQA Project (public) - action #99663: Use more perl signatures - os-autoinst size:MResolvedokurz2021-10-01

Actions
Related to openQA Project (public) - action #108530: os-autoinst wheels: x11_start_program from os-autoinst-distri-openQA dynamically loaded from another git repo size:MResolvedlivdywan2022-03-17

Actions
Related to openQA Tests (public) - action #109737: [opensuse][sporadic] test fails in chromium due to lost characters when typing in the address bar size:MResolvedlivdywan2022-04-09

Actions
Actions
Copy link
 #1

Updated by okurz over 2 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
Actions
Copy link
 #2

Updated by okurz over 2 years ago

  • Status changed from Blocked to New
Actions
Copy link
 #3

Updated by okurz over 2 years ago

  • Subject changed from [epic] Stable os-autoinst unit tests to [epic] Stable os-autoinst unit tests with good coverage
Actions
Copy link
 #4

Updated by livdywan over 2 years ago

  • Related to action #109620: os-autoinst: Improve unit-test code coverage for backend::svirt size:M added
Actions
Copy link
 #5

Updated by okurz over 2 years ago

  • Status changed from New to Blocked
Actions
Copy link
 #6

Updated by okurz over 2 years ago

  • Related to action #99663: Use more perl signatures - os-autoinst size:M added
Actions
Copy link
 #7

Updated by okurz over 2 years ago

  • Related to action #108530: os-autoinst wheels: x11_start_program from os-autoinst-distri-openQA dynamically loaded from another git repo size:M added
Actions
Copy link
 #8

Updated by okurz over 2 years ago

  • Related to action #109737: [opensuse][sporadic] test fails in chromium due to lost characters when typing in the address bar size:M added
Actions
Copy link
 #9

Updated by okurz almost 2 years ago

Blocked by #99663

Actions
Copy link
 #10

Updated by okurz almost 2 years ago

After #99663 we can then merge https://github.com/os-autoinst/os-autoinst/pull/2260 to remove deprecated backends and also check https://app.codecov.io/gh/os-autoinst/os-autoinst and define specific code coverage extension tasks for folders and files.

Actions
Copy link
 #11

Updated by okurz almost 2 years ago

  • Status changed from Blocked to Feedback

#99663 resolved, waiting time for https://github.com/os-autoinst/os-autoinst/pull/2260 is over. I asked mergify to rebase and test once more. Let's see if that brings sufficient coverage.

Actions
Copy link
 #12

Updated by okurz almost 2 years ago

  • Status changed from Feedback to Resolved

We have good and reliable coverage up to the point where we can ask anybody changing code like in backends to provide corresponding changes to the test code.

Actions
Copy link

Also available in: Atom PDF