avast/gradle-docker-compose-plugin

JUnit to capture container outputs with test output

Open

#389 opened on Nov 30, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Groovy (429 stars) (103 forks)batch import
enhancementhelp wanted

Description

test {
	useJUnitPlatform()
}
dockerCompose.isRequiredBy(test)

dockerCompose {
	captureContainersOutput = true

Currently container output capture flows into main Test Results window: Снимок экрана 2022-11-30 в 06 21 49

Regretfully test results of a particular test do not contain them: Снимок экрана 2022-11-30 в 06 22 30

With many tests it would be required to find log messages that happened during a particular case buried inside long logs.

Is it possible to somehow capture container output that was produced during a particular test run with test output, so when I click on a particular test one could see both:

  • logs from call containers during that particular test
  • logs from that particular test code

Any workarounds are welcome! (And thanks for great plugin!)

Contributor guide

Tech stack
None
Domain
testingbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Gradle plugin developmentJUnit testingDocker Compose
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the container output capture mechanism in the plugin, likely located in the source code for docker compose tasks. Understand how JUnit test lifecycle can be hooked to capture logs per test. The existing comment may provide additional context. Look at how test output is reported and consider using JUnit's TestWatcher or similar to associate container logs with specific tests.