-
Notifications
You must be signed in to change notification settings - Fork 19
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
Address #78 #82
Address #78 #82
Conversation
For a path parameter which is marked as required , empty value should not be allowed. Ideally , in this case , we do not need to proceed towards enum check as the absence of a value should violate the mandatory path parameter requirement criteria irrespective of the schema of path parameter
@daveshanley - i ran all the tests locally and it had passed , not sure what did I miss |
|
Hi @daveshanley I ran go test ./... multiple times and I still see no failures. From the errors , it looks like the order of errors has been reversed in the output of the test.
However , on running this particular test multiple number of times locally , i get the expected outcome. Would it be possible for you to retrigger this workflow ? Do we need to have such assertions on the order of errors considering the fact that the list will contain all the errors ? |
Hi @daveshanley, I have been analyzing the failed test case. It can not be deterministic because the error messages are added to the error array from an async method. Here, I have modified that test to run multiple times and check how many times its failing. libopenapi-validator/validator_test.go Line 1024 in 6a51b95
noOfFailedTest has different values while running the test multiple times. Sometimes 5 number of times its failing out of 500, sometimes 4 out of 500. So, I guess the test case is not valid. Thanks, |
already merged. |
@daveshanley - For a path parameter which is marked as required , empty value should not be allowed. Ideally , in this case , we do not need to proceed towards enum check as the absence of a value should violate the mandatory path parameter requirement criteria irrespective of the schema of path parameter