Capture the file/line where test executors/recorders are called.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
This will allow improvements to the assertion report content, such as:
| a command of a similar type was executed via a dogma.CommandExecutor at file.go:342`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the test executor and recorder call paths in the Go code, then inspect how assertion reports are assembled. Done means reports include the caller's file and line for executor or recorder calls, as illustrated by the proposed file.go:342 output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100