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 (103 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (429 stars)
PR merge metrics
 (Avg merge 24d 11h) (2 merged PRs in 30d)

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

Research direction
Investigate how to capture container logs per test by using JUnit's extension model or custom listeners to associate container output with specific test methods.
Tech stack
javadocker
Domain
testingdevops
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DockerGradleJUnit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40