-
Notifications
You must be signed in to change notification settings - Fork 21
Run examples in examples/ and docstrings in the CI #378
Copy link
Copy link
Open
Labels
part:testsAffects the unit, integration and performance (benchmarks) testsAffects the unit, integration and performance (benchmarks) testspart:toolingAffects the development tooling (CI, deployment, dependency management, etc.)Affects the development tooling (CI, deployment, dependency management, etc.)type:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Milestone
Metadata
Metadata
Assignees
Labels
part:testsAffects the unit, integration and performance (benchmarks) testsAffects the unit, integration and performance (benchmarks) testspart:toolingAffects the development tooling (CI, deployment, dependency management, etc.)Affects the development tooling (CI, deployment, dependency management, etc.)type:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Type
Projects
Status
To do
What's needed?
We need to make sure that examples in
examples/and docstrings do really work. For now onlyexamples/is being linted, which is a start, but there still could be issues with them when ran.Proposed solution
We probably need a script to extract the docstring exampmles and put them in a shape where they can be ran:
async) main function.We probably need some script to control how to run examples.
Alternatively we can adapt examples to run as
pytesttests, then we have at least the parallelization and timeout part solved (viapytest-xdistandpytest-timeout).We probably need to adapt the examples:
We need a workflow to run this:
pushworkflow events: since these examples depend on the microgrid sandbox, we shouldn't run them for every PR, as will probably be too flaky and too slow. If running for every push is still too flaky, we can run nightly. The most important thing is that we are sure they can run before a release.Use cases
No response
Alternatives and workarounds
No response
Additional context
No response