apache / apache/maven-surefire

[SUREFIRE-1978] logging testcases to separate logs

Open
#2,870 0 comments 0 reactions 0 assignees View on GitHub
enhancement priority:major
Dominant language
Java
Stars
461
Forks
588
Avg merge
1d 8h
Merged PRs (30d)
19

Description

**[Wojciech](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER283423)** opened **[SUREFIRE-1978](https://issues.apache.org/jira/browse/SUREFIRE-1978?redirect=false)** and commented

At this moment logs from testcases are in the file named after testsuite f.e:

```java
target/surefire-reports/org.apache.hadoop.hdfs.server..diskbalancer.command.TestDiskBalancerCommand-output.txt
```

It is no way to determine which log there is from which testcase. It would be useful to have separate log for separate testcase f.e:

```java
target/surefire-reports/org.apache.hadoop.hdfs.server..diskbalancer.command.TestDiskBalancerCommand_testCancelCommand-output.txt
```

---
No further details from [SUREFIRE-1978](https://issues.apache.org/jira/browse/SUREFIRE-1978?redirect=false)

Contributor guide

Open the contributing guide

Research direction

Start by tracing how Surefire produces the logs under target/surefire-reports, using the TestDiskBalancerCommand-output.txt example as the current behavior. Determine where testcase names are available when logs are written, then verify that each testcase gets a distinct log such as TestDiskBalancerCommand_testCancelCommand-output.txt and that the existing suite-level naming remains understood.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.