-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Cypress tests #6
Comments
Heym @iluwatar Unfortunately, current ArgoCD plugin supports file based tests, when Cypress is directory based tests. So, this is not a bug, it's just not supported at the moment. Still feel freee to open a feature request, we will need to think how to process directory based tests |
Okay, can I just edit this issue or do I need to create another one? |
Just change it
…On Fri, 28 Oct 2022, 17:56 Ilkka Seppälä, ***@***.***> wrote:
Okay, can I just edit this issue or do I need to create another one?
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNVFQUPGWQRQU2SYUMUZSDWFPLSXANCNFSM6AAAAAARQ35FCE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Changed the title, but unable to edit the labels |
Hey @iluwatar |
testkube #2634 |
Hello @iluwatar , is this issue still happening for you ? |
Contact Details
ilkka.seppala@gofore.com
What happened?
I followed the instructions in README.md to setup Argo CD to work with Testkube. In the final step, I point the testkube-tests application to a Github repository folder that contains Cypress tests, but the tests are not being created. It can be reproduced with these parameters:
On the other hand, if I point the application to a repository and folder containing postman tests, it seems to work. For example, the examples/postman-collections folder of this repository.
Version
1.0.0 (Edge)
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: