JanusGraph / JanusGraph/janusgraph

Redirect test case output to their individual output files.

Open
#143 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/testing
Dominant language
Java
Stars
5.8k
Forks
1.2k
Avg merge
13h 53m
Merged PRs (30d)
6

Description

Currently, all the test cases in a module output their logging to a single file `test.log`.
Also there are some console output from the test cases interleaving with formal status and result on the console.
We can re-direct the logging output and console output to individual output file for each test case. On the console, the test result will be displayed cleanly without output in between.
```
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.janusgraph.diskstorage.solr.BerkeleySolrTest
Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 141.503 sec - in org.janusgraph.diskstorage.solr.BerkeleySolrTest
Running org.janusgraph.diskstorage.solr.SolrIndexTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.565 sec - in org.janusgraph.diskstorage.solr.SolrIndexTest

```
Surefire and failsafe plugs' `redirectTestOutputToFile `property will be used.
Each test case TestA will have a TestA-output.txt in the surefire or failsafe report directory for easy diagnostic.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Surefire and Failsafe plugin configuration and the redirectTestOutputToFile property. Verify that each test case writes its console and logging output to an individual report-directory file, while the console retains clean test status and results.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.