Geofence test script #314
Merged
Geofence test script #314
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LukasWikander
requested review from
konglobemeralt,
viktorjo,
frickerik and
alfaro01
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In short, the test specifies a square 100x100m geofence centered at the origin, sends 4 MONR inside it followed by one outside, followed by two inside. The test passes if, after 0.1s of the MONR outside the geofence, the CCStatus field of HEAB is still "abort" (even though the two MONR after were inside). Depends on #313.
It seems that Supervision is not up to date with all the latest modifications, so the test currently fails when Supervision disarms the scenario on failing to parse trajectory files - the fact that it did so however is very good!