kudobuilder / kudobuilder/kuttl

[Enhancement] Output test case full path in final report

Open
#403 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
824
Forks
103
Avg merge
1d 11h
Merged PRs (30d)
6

Description

**What would you like to be added**:

Along with the result of the test (`PASS` | `FAIL`), print the full path to the test case if known through a TestSuite file.

**Why is this needed**:

With hundreds of possible tests being executed across a complex hierarchy of directories, knowing which test failed only by the name of the test case (i.e., the parent folder holding the kuttl test files) isn't often enough. For example, something like this is printed today:

```
--- PASS: kuttl/harness/external-metrics (25.87s)
--- PASS: kuttl/harness/nomutateDigest-verifyDigest-norequired (5.38s)
--- PASS: kuttl/harness/mutateDigest-noverifyDigest-norequired (3.30s)
--- PASS: kuttl/harness/keyless-nomutatedigest-noverifydigest-required (3.92s)
```

In reality, each of those test cases are six directories deep, and they may not all even be in the same parent directory.

This enhancement is to print, in the final report output, the full path to the test cases as known based upon the TestSuite file.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the final report output is assembled and how test-case paths are read from the TestSuite file. Follow the existing PASS/FAIL result flow and identify where the known full path can be carried into the report. Done means final output includes the full test-case path when available, while preserving current output when it is not.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.