Closed aabedraba closed 1 year ago
The user story:
The problem:
testkube generate
is different from testkube create
testkube generate
only supports curl, K6 and Postman in detection mode (i.e. no way to specify the type with --type) testkube generate
is missing testkube create test
flags, like --name
, --label
, --prerun-script
, --image
... testkube generate
doesn't support testsuites
- testkube create test --crds-only
output contains stuff other than the CRD. The constraint:
testkube generate
, some users started using it, so we need to keep it Possible solution:
testkube create test
and clean the output of --crds-only
. We also deprecate testkube generate
testkube create test
to testkube generate
cc: @fivenp
We add all functionality of testkube create test to testkube generate
I do prefer this option quite a lot because it separates concerns and use cases clearly
If we'd go for Option 1 then we would always have mixed journeys. (e.g. I want to create a specific test vs. I want to create a test from a folder vs. I want to only have CRDs)
Current
testkube generate test-crds
works with Postman directories that have multiple tests.This functionality might not be available for
testkube create test --crds-only
Ideally we would want to only have
testkube create test --crds-only
and deprecatetestkube generate test-crds
once we have feature parity.