microsoft / microsoft/go-sqlcmd
The TestCmd pattern does not provide functionality to validate output
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
Currently the Testcmd function just executes a command, but doesn't allow for further verification that the output generated was expected
cmdparser.TestSetup(t)
cmdparser.TestCmd[*AddEndpoint]()
cmdparser.TestCmd[*AddContext]("--endpoint endpoint")
cmdparser.TestCmd[*UseContext]("--name context")
Provide a pattern that enables TestCmd to validated the output was as expected, maybe an array/slice of RegExs that must validate?
Contributor guide
No contributing guide indexed for this repository
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 reading the existing cmdparser.TestSetup and cmdparser.TestCmd usage shown in the issue, then locate their implementation and current tests. Define how expected command output should be supplied and validated, and add coverage showing that matching output passes while unexpected output fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100