-
Notifications
You must be signed in to change notification settings - Fork 535
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
TCK Improvement: Throw meaningful error in white box subscriber verification when Probe.registerOnSubscribe isn't called #416
Comments
Sounds like a good improvement, are you giving it a shot or should I try to next week (won't be able this week)? |
I'll take a look today. |
@jroper If the promise hasn't been completed at the time of trying to use it, it should yield a test failure:
Perhaps that failure is hidden by an NPE? In which case, we might want to both flop AND throw? |
@jroper are these tests running without |
@jroper I'm planning on issuing the 1.0.2-RC1 within 24h and would love to include this improvement as well. Will you have time to take a stab at it, or can provide a "failing test" someone could use to verify if it gets fixed? Thank you! |
@jroper 6h to go |
@viktorklang Do you want the fix for this included in RC1? If so, I can have a look and post a fix today. |
@akarnokd That'd be very nice. If the fix is small then it should be quick to inorporate (in time for RC1) |
The OP is not very detailed on how to trigger this failure so I have to figure that out too. Plus, "none of the the SubscriberWhiteboxVerification tests check" indicates all of them is affected and should be tested/modified. |
Ideally the fix can be applied in one place, but let's see what it turns out to need. |
Please assign milestone @viktorklang ? |
@ktoso Done! |
Currently, none of the the
SubscriberWhiteboxVerification
tests check whetherWhiteboxSubscriberProbe.registerOnSubscribe
is invoked before it starts trying to use the puppet supplied by that invocation. So, if it wasn't invoked, it just throws an NPE:It would be nice if this was checked, and a meaningful error message (saying that
registerOnSubscribe
hasn't been invoked) was thrown.The text was updated successfully, but these errors were encountered: