You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this tap normally expects JSONL inputs, this probably would require that we have some sort of "replay" or "passthrough mode" where we just echo the .singer.json messages from a source file and not add any other Singer messages ourselves.
In terms of delivery, we could accept a pre-written config.json file that would contain a mapping to all the tests (with http refs declared as remote references to the SDK repo), and this would be helpful when the user then wanted to limit the tests. (For instance, if they know one is failing but they want to check with all but that one.)
Another way to deliver would be to have a top-level include_standard_tests = true config option that would have the same effect as the above while being easier to set. Perhaps better though, it to allow the --config option for this tap to come from an http reference. That would allow users simplicity of a one-liner execution tap-smoke-test --config=https://raw.githubusercontent.com/meltano/tap-smoke-test/main/demo-data/looping-stream-config.json. And to customize, they could download the file and change whatever they wanted.
The text was updated successfully, but these errors were encountered:
Would be awesome if we could send all "expect-to-succeed" tests from here:
singer_sdk.testing
sdk#1171Since this tap normally expects JSONL inputs, this probably would require that we have some sort of "replay" or "passthrough mode" where we just echo the
.singer.json
messages from a source file and not add any other Singer messages ourselves.In terms of delivery, we could accept a pre-written
config.json
file that would contain a mapping to all the tests (with http refs declared as remote references to the SDK repo), and this would be helpful when the user then wanted to limit the tests. (For instance, if they know one is failing but they want to check with all but that one.)Another way to deliver would be to have a top-level
include_standard_tests = true
config option that would have the same effect as the above while being easier to set. Perhaps better though, it to allow the--config
option for this tap to come from an http reference. That would allow users simplicity of a one-liner executiontap-smoke-test --config=https://raw.githubusercontent.com/meltano/tap-smoke-test/main/demo-data/looping-stream-config.json
. And to customize, they could download the file and change whatever they wanted.The text was updated successfully, but these errors were encountered: