Project

General

Profile

Actions

action #10704

open

Make warnings in tests fatal

Added by okurz over 8 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2016-02-10
Due date:
% Done:

0%

Estimated time:

Description

user story

As an openQA developer I want openQA unit and integration tests to fail when warnings are encountered to ensure not introduce regressions

acceptance criteria

  • "make test" fails if new warnings are encountered
  • the existing warnings are fixed or properly marked and skipped

tasks

  • It should help if we first fix all existing warnings to make new ones more visible
  • research how to make "prove" catch warnings and make them fatal
  • why does "prove -W" ("") not work as I expect it?
  • decide on an approach
  • make warnings fatal in all tests
  • fix existing warnings

further notes


Related issues 2 (1 open1 closed)

Related to openQA Project - action #78240: prevent circular dependencies in bmwqemu.pm and autotest.pm to be able to use "strictures"Resolved2020-11-19

Actions
Copied to openQA Project - action #108503: Collect and prominently display warnings from autoinst.logNew2016-02-10

Actions
Actions

Also available in: Atom PDF