-
Notifications
You must be signed in to change notification settings - Fork 595
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
Test that trigger is not ready before dependency exists with dependency annotation #7896
Comments
/area test-and-release |
@Cali0707: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/assign |
@Cali0707 we have to change all the trigger.IsReady(...) setup phase to requirement phase? |
hey @Rahul-Kumar-prog , you only need to move the You will also need to add the step function I was mentioning above that verifies that the trigger is not ready with reason |
@Cali0707 And when I write trigger.---- there no any dependencydoesnotexist. |
I'd recommend reading the documentation in https://github.com/knative-extensions/reconciler-test/ which I linked above, this explains how the e2e tests and phases work
|
@Rahul-Kumar-prog Hello Rahul, are you still working on this issue? |
Thankyou @Leo6Leo for pin me i forget about this issue or PR. |
Problem
Currently in the rekt test
TestTriggerDependencyAnnotation
, we do not verify that the trigger is not ready until the PingSource exists. A simple way to fix this would be to move thetrigger.IsReady(...)
call from theSetup
phase to theRequirement
phase, and then add a new step function to theSetup
phase which checks that the trigger is not ready with reasonDependencyDoesNotExist
.Persona:
Which persona is this feature for?
Exit Criteria
The rekt test verifies that the trigger is not ready with reason
DependencyDoesNotExist
before the PingSource is installed.Time Estimate (optional):
How many developer-days do you think this may take to resolve? 1
Additional context (optional)
eventing/test/rekt/features/trigger/feature.go
Line 44 in c104df5
The text was updated successfully, but these errors were encountered: