Add support for module tests#39
Open
xsedla1o wants to merge 8 commits into
Open
Conversation
This file contains hidden or 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
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.
Adds lightweight testing utilities for DP3 secondary modules so app developers can unit-test module hook behavior without running a full DP3 instance.
Secondary modules were difficult to test because they normally depend on DP3 runtime wiring. This branch provides a
unittest-friendly harness that loads real app entity config, captures hook registrations, and lets tests invoke hooks directly with validated DP3 task/datapoint objects.Examples
To showcase potential usefulness of such helpers, usable test suites were drafted for select internal apps:
Changes
dp3.testinghelpers, centered aroundDP3ModuleTestCase.hooks.
DataPointTasks that would do no work, while preserving internal synthetic-task use cases.