Define and generate output that can be used as input to TKG
Open
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Next step in this change-based journey is to feed output from scripts within this repo to TKG so that it has info that it can use to advise whether certain test targets can be skipped and/or must be run.
Contributor guide
Research direction
Start by reviewing the scripts in this repository and how their current output is produced. Determine the information TKG needs to advise which test targets can be skipped or must run, then define and generate output that TKG can consume. Done means the generated output can provide that test-selection information to TKG.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100