Add functional test for wait_for_valid_timestamp

[DeborahOoi96]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

Add unit test coverage for wait_for_valid_timestamp

What testing has been done?

Existing and newly added tests all pass

[DeborahOoi96]

I'm not quite sure how to test this, so I just went with no_error / expected error tests.
I have tried reading back xxx_trigger.timestamp_val in Labview but I can't seem to get back a value that is not AbsoluteTime 0. Maybe I'm testing it wrongly because I'm new to daqmx. Maybe some reference on how to properly use wait_for_valid_timestamp will be helpful.

[zhindes]

What do you mean the timestamp_val doesn't return anything? This is a simulated device, so I would at least expect a 0 timestamp...

[DeborahOoi96]

What do you mean the timestamp_val doesn't return anything? This is a simulated device, so I would at least expect a 0 timestamp...

@zhindes sorry I wasn't clear in the description. I meant it only returns AbsoluteTime 0. I have updated the comment

[zhindes]

What do you mean the timestamp_val doesn't return anything? This is a simulated device, so I would at least expect a 0 timestamp...

@zhindes sorry I wasn't clear in the description. I meant it only returns AbsoluteTime 0. I have updated the comment

Ah ok. Well that's the best we can do with simulated device. That being said, I suspect simulated devices always return that regardless of whether or not we waited for a timestamp. So, yeah, not very useful. I'm fine with what you have.

[zhindes]

and fix the field_daq task name