charmbracelet / charmbracelet/x
Improve testing for model
Open
- Dominant language
- Go
- Stars
- 314
- Forks
- 94
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 2
Description
For example, I'd like to test my https://fx.wtf app. But right now testea only tests final output (which is 0 for fx).
I'd like to be able to send keystrokes and check intermediate results (same with -update model).
Contributor guide
Research direction
Start by locating the testea implementation and the model update path referenced by “-update model,” then inspect how input and final output are currently handled. Reproduce the fx.wtf case and trace where intermediate results could be observed; the work is done when keystrokes can be supplied and intermediate results can be checked for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100