Fixtures to generate mock data for clean up use_swap
handling
#1183
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.
@lsetiawan : in this PR you'll find functions that generate mock data for testing the
use_swap
functionality for #1179.I made it such that the output is in identical format with
parser.ping_data_dict
, fortimestamp
,power
, andangle
.See my comment here for more info: #1179 (comment)
Because of the possible variations, I think using both the actual data for integration tests and mock data for unittest will be a good idea.
In terms of actual .raw data that we need to handle, see my previous investigation #489 (comment) and #489 (comment).