Testing: add unit (module) test facilities#396
Draft
AshFungor wants to merge 1 commit intoriebl:masterfrom
Draft
Testing: add unit (module) test facilities#396AshFungor wants to merge 1 commit intoriebl:masterfrom
AshFungor wants to merge 1 commit intoriebl:masterfrom
Conversation
Owner
|
I think building "small networks" for checking modules is the way to go. Instead of putting effort into any orchestration tooling in the first place, I would rather like to see how such networks could look like, which test input data is required and how it is provided, and how checks (test assertions) are applied. An alternative to pytest might be CTest, i.e. adding test configurations to our CMake configuration. |
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.
Hey, @riebl!
I had a look into OMNeT++ test utility and I feel that it's a bit limited and feels "packed": adding source code alongside configuration files all in different format and style seems a bit brutal to me. I thought that we may build up a small number of facilities for unit (OMNeT++ modules) tests, which would be orchestrated and validated by pytest. The idea is launch small networks of (ideally) a couple of modules and then check if it works ok.
What do you think?