Project

General

Profile

Actions

coordination #44075

closed

[functional][y][epic] Use more static code style checks to make life for test developers such a pain that nobody dares to add new tests which we would not be able to maintain anyway ;)

Added by okurz over 5 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 25
Start date:
2018-11-21
Due date:
2019-06-04
% Done:

100%

Estimated time:
(Total: 12.00 h)
Difficulty:

Description

Motivation

https://etherpad.nue.suse.com/qa_sles_functional_retrospective sprint 29 about "supporting of all the possible scenarios, architectures and product versions in the same test module makes tests less readable, very hard to maintain".

Acceptance criteria

  • AC1: Additional policies or tools have been evaluated and feasible ones implemented in the local tests

Suggestions


Subtasks 7 (0 open7 closed)

action #44159: [functional][y][timeboxed:4h] Use more static code style checks - evaluate what perl critic policies make senseResolvedJERiveraMoya2018-11-212018-12-04

Actions
action #44165: [functional][y] Use more static code style checks - try to use https://metacpan.org/pod/Perl::Critic::Policy::ControlStructures::ProhibitDeepNestsResolvedJERiveraMoya2018-11-212018-12-04

Actions
action #44528: [functional][y] Understand why "perlcritic" was not run for a long timeResolvedriafarov2018-11-292019-02-12

Actions
action #47012: [functional][u] Summary or Maintainer info missing from test modulesResolvedokurz2019-02-012019-03-26

Actions
action #48599: [functional][y] Use Perl::Critic::Freenode perlcritic rules as in os-autoinst and openQAResolvedJERiveraMoya2019-03-022019-05-21

Actions
action #48602: [functional][y] Limit maximum file length with static code checksRejectedriafarov2019-03-02

Actions
action #48605: [functional][y] Reduce code nesting level to a limit of 4Resolvedybonatakis2019-03-022019-06-04

Actions
Actions

Also available in: Atom PDF