cucumber / cucumber/godog

Remove step number from Progress Formatter

Open
#671 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.7k
Forks
280
Avg merge
2d 20h
Merged PRs (30d)
2

Description

### 👓 What did you see?

When running numerous scenarios and using the `progress` formatter,
When the step is a mod of 70, the step numbers are printed on the progress line and a line break is introduced.
This seems to be only useful for debugging the formatter itself and should likely be removed.
Additionally, there should be a line break after each scenario is completed.

Current output:
```
.......=== RUN TestFeatures/MyFeature1
........... 420
.=== RUN TestFeatures/MyFeature2
........................=== RUN TestFeatures/MyFeature3
```

Offending Line/Area:
https://github.com/cucumber/godog/blob/e55eab64f70a325565ef93558c0d646fce1760e7/internal/formatters/fmt_progress.go#L109

### ✅ What did you expect to see?

Expected output:
```
=== RUN TestFeatures/MyFeature1
...........
=== RUN TestFeatures/MyFeature2
........................
=== RUN TestFeatures/MyFeature3
```

In the case of more than 70 steps per Scenario the output should expect to look like:
```
=== RUN TestFeatures/MyFeature1
............................................................
............................................................
...........................................
=== RUN TestFeatures/MyFeature2
............................................................
.........

```

### 📦 Which tool/library version are you using?

Golang Godog Main Branch

### 🔬 How could we reproduce it?

_No response_

### 📚 Any additional context?

I'll tackle this myself if this makes sense to others.

Contributor guide

Open the contributing guide

Research direction

Start in internal/formatters/fmt_progress.go around line 109, the offending area identified in the issue. Compare the current output with the expected examples, then verify the formatter for normal scenarios and scenarios exceeding 70 steps, including a line break after each scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing-qa
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.