Add test for SBP-1534 STEC list empty #1287
Conversation
| tow: 180 | ||
| wn: 3 | ||
| num_msgs: 1 | ||
| seq_num: 1 |
There was a problem hiding this comment.
I think the sequence number might be zero-based, at least it's what I'm getting when encoding an SsrAtmo message with a single grid point into SBP in https://github.com/swift-nav/sip/:
There was a problem hiding this comment.
Mmmm are you sure? I set this field to 1, since the first (original) CorrectionBounds test has 1. I look the SBP documentation and it's not clear if the seq_num starts from 0 or 1.
There was a problem hiding this comment.
I ask to Ekumen team, so I will just leave here @fpezzinosn answer: "for testing it was better to use a number different from zero since it would be hard to tell if it was encoded properly or if it failed".
If you prefer I can change to 0. Let me know what you think.
Description
@swift-nav/devinfra
Add a MsgSsrGriddedCorrectionBounds msg (SBP-1534) test, that checks if an empty STEC list can be encoded / decoded.
Task PC-313
API compatibility
It doesn't add compatibility risk. It increases the coverage for a test case.