Use test containers to facilitate running various integration tests#1931
Conversation
… configuration to be able to run integration tests more easily
…ion tests, for : Postgresql, MySql, Oracle, SQLServer and Firebird (not tested)
Can you be more specific? I may be able to help. |
|
@jzabroski In fact, I realized after that the Firebird client seems not to require anything to be installed, and I made a syntax mistake in its connection string (that I just fixed).
I never workd with Firebird, I may be missing something. About the Oracle native client, I didn't try, but the managed client works well. |
# Conflicts: # test/FluentMigrator.Tests/FluentMigrator.Tests.csproj
The maintainer of Firebird is super polite. We may just be able to ask him what we're doing wrong. I believe they have a mailing list to ask questions on. It's been a while since I asked them for something. |
|
@PhenX I think we reviewed everything. I think it's relatively OK to not prioritize the Firebird stuff right now. Making it a separate ticket. |
|
After reading test containers releases I saw DB2 ! So I added it, and while adding it I realized I'm an idiot about the Firebird "issue" I talked about : current tests work on a "temporary table" file, that was my issue, so I added a check to use a test containers DB when available.
I also fixed tests from a previous PR I did (CanUseRawSqlInUpdateAndDelete). |
Added DB2 docker support Fixed CanUseRawSqlInUpdateAndDelete tests Fixed Firebird integration tests with page size too small errors Ignore Oracle native tests when no native client available
I fixed a few tests too. I couldn't make Firebird not Oracle Native tests to work, as they require installation of a specific client, which I didn't do.
When running all the tests, when activating Postgresql, Mysql, SQL Server and Oracle containers, take 70 seconds to run when the containers are not already running (but images already downloaded), and nearly 30s when the container is already running.
What do you think ?