[GitHub] [beam] damccorm opened a new issue, #17927: Add TriggerTester methods to check that timers are set

[GitBox <gi...@apache.org>]

damccorm opened a new issue, #17927:
URL: https://github.com/apache/beam/issues/17927

   TriggerTester exposes a `fireIfShouldFire(BoundedWIndow)` method. This is used to prompt a call to the trigger with the current state of the trigger tester (Input Watermarks, elements present, etc), and see if the trigger should fire. This is sufficient to test `shouldFire` of the `TriggerStateMachine` under test, but does not test that the `onElement` method sets an appropriate timer to cause such an interrogation to occur.
   
   Imported from Jira [BEAM-694](https://issues.apache.org/jira/browse/BEAM-694). Original Jira may contain additional context.
   Reported by: jkff.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [beam] damccorm closed issue #17927: Add TriggerTester methods to check that timers are set

[GitBox <gi...@apache.org>]

damccorm closed issue #17927: Add TriggerTester methods to check that timers are set
URL: https://github.com/apache/beam/issues/17927


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org