-
-
Notifications
You must be signed in to change notification settings - Fork 356
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
simplify k8s integration test (cypress or others) #1114
Comments
I would like to work on this enhancement!! |
It is all yours! Basically we need to make sure that the spoils of the k8s and the vault challenges are correct and not |
Hey @commjoen can you please provide me with the answers of 5,6,7,33 as of now as it will save my time |
You can find them in the spoil endpoints of the challenges. Can you please:
Can you fail the test if it the spoil is a default value or the challenge does not resolve with the spoiled value of the first step please? |
These only work when you use a k8s setup with vault. See the readme and the existing workflow (https://github.com/OWASP/wrongsecrets/actions/workflows/minikube-vault-test.yml ) to be extended /changed for this issue. |
heyy @commjoen !! i have written the cypress scripts for challenge 5,6,7,33 but for eg:- test of challenge 5 in line no 5, the answer of the challenge is visible clearly and that's not good programming practice so what should i do to hide that, or will that be fine ??? |
Can you programmatically obtain the answer from a spoiler and put it in the answer box :-)? |
we now have a script that does integration testing with the k8s setup for the github action. We need to convert this to cypress or to an easier extensible shell script with just a simple yaml definition or something alike
The text was updated successfully, but these errors were encountered: