Project

General

Profile

Actions

action #71863

open

[os-autoinst] Include tests in code coverage analysis

Added by okurz about 4 years ago. Updated almost 4 years ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Organisational
Target version:
Start date:
2020-09-16
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See #71449 . It can happen that we do not run some tests or even test code. Including tests in the code coverage analysis allows to track the coverage and be able to realize when test code coverage drops

Acceptance criteria

  • AC1: test modules from "t/" will be covered as part of normal test runs

Related issues 1 (0 open1 closed)

Copied from openQA Project - action #71449: 25-cache-service.t fails repeatedly but circleCI receives the status as "success"Resolvedokurz2020-09-16

Actions
Actions #1

Updated by okurz about 4 years ago

  • Copied from action #71449: 25-cache-service.t fails repeatedly but circleCI receives the status as "success" added
Actions #2

Updated by okurz about 4 years ago

I am currently trying with https://github.com/os-autoinst/os-autoinst/pull/1536 but there are errors and/or warnings regarding Devel::Cover and the coverage report seems incomplete. So the suggestion was to first try to call prove from the parent directory in https://github.com/os-autoinst/os-autoinst/pull/1537 which looks better but still has problems.

Actions #3

Updated by livdywan almost 4 years ago

okurz wrote:

I am currently trying with https://github.com/os-autoinst/os-autoinst/pull/1536 but there are errors and/or warnings regarding Devel::Cover and the coverage report seems incomplete. So the suggestion was to first try to call prove from the parent directory in https://github.com/os-autoinst/os-autoinst/pull/1537 which looks better but still has problems.

You use the progressive tense yet the ticket is New

Actions #4

Updated by okurz almost 4 years ago

  • Status changed from New to Feedback
  • Priority changed from Normal to Low
Actions #5

Updated by okurz almost 4 years ago

  • Status changed from Feedback to Workable
  • Assignee deleted (okurz)
  • Target version changed from Ready to future

ok, I am not continuing right now as a I don't know how to ensure proper code coverage reports with the shifted runtime directory. I hope one of our perl experts can arrive at an anwser faster and more efficiently.. PRs are still there as "inspiration"

Actions

Also available in: Atom PDF