test: Rework Pipeline.run()
tests to ease declaration with dataclasses
#7790
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.
Related Issues
Pipeline.run()
#7611Proposed Changes:
Add a new
PipelineRunData
dataclass that holds all the information necessary to run aPipeline
and verify its correct execution. This dataclass will be returned by the functions marked with@given
together with thePipeline
instance to run.I also added a
_PipelineResult
dataclass used in the boilerplate code that runs and verifies thePipeline.run()
execution.How did you test it?
I ran tests locally.
Notes for the reviewer
I also changes slightly the tests for the "bad"
Pipeline
runs as they were unnecesssarily returning the expectedException
class too. This made it simpler to structure thePipelineRunData
dataclass.Checklist
fix:
,feat:
,build:
,chore:
,ci:
,docs:
,style:
,refactor:
,perf:
,test:
.