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

Test case classification and use of test containers for integration tests #157

Closed
StefanSchubert opened this issue Mar 1, 2024 · 1 comment
Assignees

Comments

@StefanSchubert
Copy link
Owner

StefanSchubert commented Mar 1, 2024

Test needs to be grouped or classified in IntegrationTests, UnitTests and DeveloperTests.
See https://www.baeldung.com/junit-filtering-tests

Acceptance criteria:

  • Tests are grouped with the @tag annotation, distinguishing "Integration, Unit- and DeveloperTests".
  • Tests are also grouped for specific components and there are TestSuites (again)
    Example:
    @SelectPackages("com.baeldung.tags") @IncludeTags("UnitTest") public class EmployeeDAOUnitTestSuite { }
  • Projects Wiki contains a section on the test concept. Explaining the purpose of each category.
  • Integration Tests are executed during the CI pipeline build using test-containers
  • H2 Dependencies are no longer required within the project, as all Integration tests are based upon testcontainer now.
@StefanSchubert
Copy link
Owner Author

Done, merged into main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant