Skip to content
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

Check tests for initial value propagation #156

Closed
4 tasks
killenb opened this issue Apr 15, 2020 · 2 comments
Closed
4 tasks

Check tests for initial value propagation #156

killenb opened this issue Apr 15, 2020 · 2 comments

Comments

@killenb
Copy link
Member

killenb commented Apr 15, 2020

Child of #123

The initial value propagation is connected with the exception handling scheme because the ExceptionHandlingDecorator takes care that no read transfer succeeds until the initial value could be received.

  • Extend the tests to check that no value with invalid time stamp is propagated.

  • ReadNonBlocking() and ReadLatest() must block until the initial value could be received

  • Special scenario works: Only reading fails (simulate with exception dummy)

    • The device can be opened
    • The initialisation sequence runs through (may be empty)
    • Recovery accessors can be written -> The device is opened successfully and reports no error.
    • The first read operation is executed and fails during its transfer. The device goes to error state, but recovers immediately....
    • All reads block until the read exception has been turned off. The first value is valid and has the right content.
  • All the tests should also work for transfer groups. They are only used in the TriggerFanOut. In the current implementation this is not working cleanly yet. Come up with a test scenario and comment it out. Note in the implementation ticket (FIXME does not exist yet) that the test should be activated.

@killenb
Copy link
Member Author

killenb commented Aug 5, 2020

This ticket seem a bit outdated since we have the systematic tests in #179. I see it as an addition to review #179 and check that all special cases mentioned here are covered.

@mhier
Copy link
Member

mhier commented Jun 16, 2021

Closed in favour of #179

@mhier mhier closed this as completed Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants