Pretty test report formatting
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 280
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
Please answer these questions before submitting a bug report.
### What version of godog are you using?
```
> godog -version
v0.10.0
```
### What version of Go are you using?
```
> go version
1.14
```
### What did you do?
Create a test case where a test step description is very long
### What did you expect to see?
No blank lines in the formatted output
### What did you see instead?
lots of blank lines in the formatted output

### Additional context
-
Contributor guide
Research direction
Start by reproducing the report with a test step description long enough to trigger the extra blank lines, using godog v0.10.0 and Go 1.14 as the reported environment. Trace the formatter or report-output entry point and verify that the corrected output contains no unintended blank lines for long steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100