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

Make distinction between Testcontainers for integration tests and development more clear in documentation #35856

Closed
scottfrederick opened this issue Jun 12, 2023 · 2 comments
Assignees
Labels
type: documentation A documentation update
Milestone

Comments

@scottfrederick
Copy link
Contributor

The documentation has a section on using Testcontainers for testing. Sub-sections have information specific to integration testing and development-time testing, but this distinction is not clear from the headings. It might be better to separate these two testing concerns into separate sections to make the differences more clear.

@hantsy
Copy link

hantsy commented Jun 14, 2023

Quarkus Dev and Micronaut test-resources, the background testcontainers are working seamless in those cases running the application and running integration tests.

I really do not understand the purpose of Spring Boot newly introduced test Application class, and some config(such as declaring test containers as beans) are only for the development time.

@wilkinsona wilkinsona changed the title Make distinction between Testscontainers for integration tests and development more clear in documentation Make distinction between Testcontainers for integration tests and development more clear in documentation Jun 14, 2023
@eddumelendez
Copy link
Contributor

some config(such as declaring test containers as beans) are only for the development time.

It was fixed in spring boot 3.1.3. See #36661

So, the experience is consistent between testing and development mode

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation A documentation update
Projects
None yet
Development

No branches or pull requests

4 participants