kubeshop / testkube

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

Testkube v/s extended version of k6 (xk6) and Cypress ( like Cypress-audit) #2529

Closed chandana194 closed 1 year ago

chandana194 commented 1 year ago

Hi Team,

Would like to know if testkube is able to handle the k6/Cypress scripts which are written using extended version of k6 (i.e xK6) or external plugin's of Cypress like (Cypress-audit )

Could you please let me know on this?

Thanks

vsukhin commented 1 year ago

You can fork existing Testkube executor repo and update executor docker image for desired test engine. Then you can create a copy of default (for example, postman) executor (you need to change its name to mypostman and type to myspostman/collection and use your own image instead of default one. And create test type of mypostman/collection to run these tests

chandana194 commented 1 year ago

You can fork existing Testkube executor repo and update executor docker image for desired test engine. Then you can create a copy of default (for example, postman) executor (you need to change its name to mypostman and type to myspostman/collection and use your own image instead of default one. And create test type of mypostman/collection to run these tests

Could you please share if any documentation is available for the same

vsukhin commented 1 year ago

Check this page https://kubeshop.github.io/testkube/test-types/executor-custom

vsukhin commented 1 year ago

Hi,

Do you want to create a completely new executor or just update the docker image in an existing one? In last case, you need to fork existing k6 executor and chage Docker file it uses You don't to even touch golang code in this case

Regards, Vlad

On Wed, Oct 19, 2022 at 9:38 AM chandana194 @.***> wrote:

Hi @vsukhin https://github.com/vsukhin I am trying to build custom testkube executor as suggested by you. have cloned the template repo and trying to modify the go.mod file with my local project path.

like as suggested in the documentation : https://github.com/kubeshop/testkube-executor-template Step2 : Change go.mod file with your path (just replace github.com/kubeshop/testkube-executor-template project-wise with your package path)

but I am facing the below error when try to change path. Could you please let me know what could be the issue?

Command issued : go mod tidy Error message : go: malformed module path "/Users/cnagara/Documents/Testkube/testkube-executor-k6-browser-testing": empty path element [image: Screenshot 2022-10-19 at 12 07 34 PM] https://user-images.githubusercontent.com/113690498/196615054-9539898b-3398-45c0-90c9-76758b607bb6.png

— Reply to this email directly, view it on GitHub https://github.com/kubeshop/testkube/issues/2529#issuecomment-1283505812, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNVFQWJL6OVEL6CWLDMB6TWD6JOXANCNFSM6AAAAAARE5RP6Q . You are receiving this because you were mentioned.Message ID: @.***>

chandana194 commented 1 year ago

Hi, Do you want to create a completely new executor or just update the docker image in an existing one? In last case, you need to fork existing k6 executor and chage Docker file it uses You don't to even touch golang code in this case Regards, Vlad On Wed, Oct 19, 2022 at 9:38 AM chandana194 @.> wrote: Hi @vsukhin https://github.com/vsukhin I am trying to build custom testkube executor as suggested by you. have cloned the template repo and trying to modify the go.mod file with my local project path. like as suggested in the documentation : https://github.com/kubeshop/testkube-executor-template Step2 : Change go.mod file with your path (just replace github.com/kubeshop/testkube-executor-template project-wise with your package path) but I am facing the below error when try to change path. Could you please let me know what could be the issue? Command issued : go mod tidy Error message : go: malformed module path "/Users/cnagara/Documents/Testkube/testkube-executor-k6-browser-testing": empty path element [image: Screenshot 2022-10-19 at 12 07 34 PM] https://user-images.githubusercontent.com/113690498/196615054-9539898b-3398-45c0-90c9-76758b607bb6.png — Reply to this email directly, view it on GitHub <#2529 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNVFQWJL6OVEL6CWLDMB6TWD6JOXANCNFSM6AAAAAARE5RP6Q . You are receiving this because you were mentioned.Message ID: @.>

Hi @vsukhin

Thank you for the update . My requirement is to update the existing k6 executor with xk6-browser extension.

now I tried forking the existing k6 executor and modified the docker file as required. and tried building the image with the below command as mentioned in the documentation. Now I am facing the below error

docker build -t chandana194/testkube-executor-k6:1.0.0 .
[+] Building 0.0s (1/2)
=> [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount3905568880/Dockerfile: no such file or directory

vsukhin commented 1 year ago

This is what Google search returns https://stackoverflow.com/questions/64221861/an-error-failed-to-solve-with-frontend-dockerfile-v0