Skip to content
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

prevent multiple databases in test classes #5457

Merged
merged 2 commits into from
Jan 11, 2024

Conversation

StevenMassaro
Copy link
Contributor

@StevenMassaro StevenMassaro commented Jan 11, 2024

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Due to a combination of the logic in liquibase-extension-testing used to determine whether a particular test class matches the specified databases, and the fact that the integration tests run in a matrix in GHA, test classes with more than one DatabaseTestSystem specified will not run on any platform in GHA. This PR prevents someone from accidentally creating a test class that has more than one DatabaseTestSystem.

Things to be aware of

Things to worry about

Additional Context

Copy link
Collaborator

@filipelautert filipelautert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As it is building and tests are working seems we don't have this condition yet, so it's a good thing to prevent it.

@StevenMassaro StevenMassaro merged commit c83f582 into master Jan 11, 2024
30 of 31 checks passed
@StevenMassaro StevenMassaro deleted the prevent-multiple-databases-in-tests branch January 11, 2024 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants