-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistent way to create and teardown test repositories #655
Labels
Status: Up for grabs
Issues that are ready to be worked on by anyone
Comments
Merged
I like the |
What's the current status of this one? Are any bits of this closed PR relevant? May I start working on it? |
Nobody's working on this currently. Feel free. |
2 tasks
Should be closed? |
nickfloyd
added
Status: Up for grabs
Issues that are ready to be worked on by anyone
and removed
up-for-grabs
labels
Oct 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a consistent way to create a test repository for the purpose of integration tests:
And a couple of different ways to cleanup this repository:
OR
OR
We also have a couple of places where we use
IDisposable
to signal to xUnit to run some disposal code outside the scope of the test.So basically, everything is terrible.
There's a couple of constraints to be wary of here:
IDisposable.Dispose
isn'tawait
-able 😢Ideally, I'd like some sort of wrapper which we can use:
Where
CreateTestRepository
is an extension method that takes care of generating the unique name for the repository and calling the necessary APIs. There might be some ickyness insideDispose
to workaround the blocking/non-blocking problem, but hopefully this makes it easier to scaffold new integration tests...The text was updated successfully, but these errors were encountered: