[RFC] Create test utility for managing instance state #32630
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.
Summary & Motivation
Currently, it's very hard to create a test instance that has states like "run failed after x step" or "run is in progress and y steps have completed so far". This makes testing things like declarative automation pretty challenging as you need to go through a bunch of hoops in order to get your test instance in the desired states, but this is definitely not limited to DA testing -- it's a pretty consistent issue with testing in our codebase.
This creates a contextmanager that provides convenience methods for managing this state. Name is terrible, just getting the idea moving.
How I Tested These Changes
Changelog
NOCHANGELOG