Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposal and best practices for --test capability #28

Open
aaronsteers opened this issue Nov 14, 2021 · 0 comments
Open

Proposal and best practices for --test capability #28

aaronsteers opened this issue Nov 14, 2021 · 0 comments

Comments

@aaronsteers
Copy link
Contributor

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aaronsteers