tektoncd/pipeline

refactor fatal and error in unit tests

Open

#6,641 opened on May 9, 2023

View on GitHub
 (10 comments) (0 reactions) (1 assignee)Go (1,943 forks)auto 404
good first issuehelp wanted

Repository metrics

Stars
 (9,013 stars)
PR merge metrics
 (PR metrics pending)

Description

We have a mix of t.Fatalf and t.Errorf in our existing unit tests. It's most of the times user's choice to decide which one to implement. There are no specific guidelines as part a tekton pipeline development process.

As part of this issue:

  • Task 1: Define a specific guideline around t.Fatalf and t.Errorf and document them as part of our unit test best practices.

  • Task 2: Revisit our code base to make sure we are aligned and following with the guidelines documented in Task 1.

See relevant comment - https://github.com/tektoncd/pipeline/pull/6596#discussion_r1188598706

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.