mirror of
https://github.com/docker/docs.git
synced 2026-03-29 07:18:51 +07:00
b951e92f57
## Description Migrate 17 Testcontainers guides from testcontainers.com into the Docker docs site, covering Java (14 guides), .NET (2 guides), and Node.js (1 guide). This follows up on PR #24450 which added the initial Go and Python guides. Each guide is converted from AsciiDoc to Hugo Markdown, split into multi-chapter stepper navigation, updated to the latest Testcontainers API, and verified with passing tests running in containers. Java guides use testcontainers-java 2.0.4 with the new 2.x Maven coordinates and package names (e.g., `testcontainers-postgresql`, `org.testcontainers.postgresql.PostgreSQLContainer`). The Quarkus guide uses Quarkus 3.22.3 with TC 1.x managed by the Quarkus BOM, since no released Quarkus version ships TC 2.x yet. ## How to test All code snippets have been verified by running each guide's source repository tests inside Docker containers with the Docker socket mounted. To re-run the verification, use the `/testcontainers-guides-migrator` skill included in this PR (`.claude/skills/testcontainers-guides-migrator/SKILL.md`). The skill's Step 6 documents the exact container commands and macOS Docker Desktop workarounds (host override, docker-java API version, etc.) needed to run each language's tests: ``` /testcontainers-guides-migrator I want you to verify all the guides in this branch. Do a full review, verifying that all code snippets compile, the code is executable, and ALL the tests pass. Run them as docker containers, never locally. ``` ## Related issues or tickets Supersedes #24450 (expanded from 2 guides to all 19) ## Reviews - [ ] Technical review - [ ] Editorial review - [ ] Product review --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
44 lines
1.3 KiB
Markdown
44 lines
1.3 KiB
Markdown
---
|
|
title: Run tests and next steps
|
|
linkTitle: Run tests
|
|
description: Run your Testcontainers WireMock integration tests and explore next steps.
|
|
weight: 30
|
|
---
|
|
|
|
## Run the tests
|
|
|
|
```console
|
|
$ ./mvnw test
|
|
```
|
|
|
|
Or with Gradle:
|
|
|
|
```console
|
|
$ ./gradlew test
|
|
```
|
|
|
|
You should see the WireMock Docker container start in the console output. It
|
|
acts as the photo service, serving mock responses based on the configured
|
|
expectations. All tests should pass.
|
|
|
|
## Summary
|
|
|
|
You built a Spring Boot application that integrates with an external REST API,
|
|
then tested that integration using three different approaches:
|
|
|
|
- WireMock JUnit 5 extension with inline stubs
|
|
- WireMock JUnit 5 extension with JSON mapping files
|
|
- Testcontainers WireMock module running WireMock in a Docker container
|
|
|
|
Testing at the HTTP protocol level instead of mocking Java methods lets you
|
|
catch serialization issues and simulate realistic failure scenarios.
|
|
|
|
To learn more about Testcontainers, visit the
|
|
[Testcontainers overview](https://testcontainers.com/getting-started/).
|
|
|
|
## Further reading
|
|
|
|
- [Testcontainers WireMock module](https://testcontainers.com/modules/wiremock/)
|
|
- [WireMock documentation](https://wiremock.org/docs/)
|
|
- [Testcontainers JUnit 5 quickstart](https://java.testcontainers.org/quickstart/junit_5_quickstart/)
|