Avoid redundantly doubled test setup #19421
Merged
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.
Disable
AbstractTestQueryFramework.ensureTestNamingConvention
TestNG test to avoid redundant test setups.For many test classes, this it the last method that is not converted. For example, running
TestInformationSchemaConnector
with TestNG will run only this method. Disabling this will make tests likeTestInformationSchemaConnector
JUnit-only and improve test overall time (fewercreateQueryRunner
invocations).The test remains enabled for
BaseConnectorTest
andBaseConnectorSmokeTest
, which already use JUnit and thus are either all-JUnit or do setup twice anyway.This change also makes it easier to run all-JUnit test classes from an IDE, since now IDE will offer only the "Run with JUnit" option.
Alternative to #19400.