MeltanoLabs / MeltanoLabs/Singer-Working-Group
Proposal and best practices for `--test` capability
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In the tap SDK, we introduced a --test operation which ensures connectivity and which could be expanded to include other tests as well.
It could be helpful to develop a common convention for similar testing across taps and targets.
These tests could include validations such as:
- setting validation
- catalog validation
- connectivity tests
- stream record generation for n records
- confirm records match json schema
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
Review the tap SDK's existing --test operation and the proposed validation areas: settings, catalogs, connectivity, record generation, and JSON Schema matching. Compare how taps and targets currently handle these checks, then define and document a common convention and its scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100