search

kubeshop / testkube

☸️ Kubernetes-native testing framework for test execution and orchestration
https://testkube.io
Other
1.32k stars 129 forks source link

Undefined behaviour after the custom executor is removed #3202

Open tkonieczny opened 1 year ago

tkonieczny commented 1 year ago

Undefined behaviour after the custom executor is removed

To Reproduce Steps to reproduce the behavior:

  1. Create a custom container executor
  2. Create a test using this container executor
  3. Remove container executor
  4. Try to run a test: Nothing happens after user clicks Run test in Dashboard - from the user perspective it's unclear why the execution hasn't started at all.

CLI:

tk run test container-curl-test                         

starting test execution testkube/container-curl-test (error: api/POST-testkube.Execution returned error: api server problem: can't create valid execution options: can't get executor spec: executor type 'container-curl/test' is not handled by any of executors ([testkube/artillery-executor testkube/curl-executor testkube/cypress-executor testkube/ginkgo-executor testkube/gradle-executor testkube/jmeter-executor testkube/k6-executor testkube/kubepug-executor testkube/maven-executor testkube/playwright-executor testkube/postman-executor testkube/soapui-executor]), context: null;
resp error:an error on the server ("unknown") has prevented the request from succeeding (post services testkube-api-server:8088))

Expected behavior I'm not sure what exactly should happen in this case. But, as a user I would expect at least an error message, that the executor isn't available.

tkonieczny commented 1 year ago

cc: @fivenp