Use .NET Testcontainers for integration tests #23
Conversation
This file contains 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
Requires support for virtualisation on Github hosted runners to continue.
…eInformation.IsOSPlatform()
tvandinther
added
bug
tvandinther
deleted the
16-fix-integration-tests-for-macos-and-windows-runners
branch
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.
Resolves #16
Integration tests for remote database connections with libsql-server moved from using docker-compose to using the test containers library which allows programmatic creation of containers with C# codes as test fixtures.
This PR also introduces changes for the test runner to skip tests using containers if the test platform is not Linux. This is set for the Github Actions runners which do not support Linux virtualisation yet on either Windows or macOS.