❓ what does everyones meltano testing suite look like? not necessarily tap/target testing, but testing meltano configuration holistically

If you were to "test meltano configuration holistically", what would be an example failure case? that your environment is missing a tap/target configuration?

Yeah, that could be an example failure case. I guess I’m thinking of individual tap/target testing as unit testing and testing meltano commands as integration testing. Just was curious to see if anyone is doing dry meltano elt runs or something of the sort as part of their testing suite.

For integration test, I guess we can use docker-compose and this: https://github.com/jpetazzo/dind (in case of you need to run it on your CI/CD pipeline). • Pros: You can set up your environments just for testing, and ditch it once the test has finished. • Cons: Probably going to take a long time. I want to see if there is any better/alternative way to do this.

Would be curious if the meltano team has any thoughts on this. Cc @taylor @aaronsteers @douwe_maan

There are not establish patterns, but I think we should start establishing some 🙂 Testing

meltano elt

dry run is a good start, but that really just verifies that

meltano.yml

is valid, not anything about the pipeline/tap/target itself. It could be useful to test tap/target configuration as well, if those credentials are available in the CI environment, but we don't have https://gitlab.com/meltano/meltano/-/issues/2609 yet.

@douwe_maan yep seems like

test

is what Im looking for. Going to watch that issue 👍

@david_wallace Let me know if you'd be interested in contributing it 🙂

@douwe_maan I’d love to! little crunched for time recently (I’m a team of one) so probably wont be able to prioritize for a while, but I’ll be sure to let you know