[SUREFIRE-1042] Provide way of running tests so that stack trace isn't dumped onto console

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

We never used to get stack traces from any failed tests (asserts) being dumped onto the console. "Upgrading" to 2.16 means that they now get dumped onto the console (UGLY IMHO). Can we at least have the option of the previous output behaviour (2.10 for example)? If there already is a way of achieving this, please advise, I couldn't find anything that had an effect.

---

**Affects:** 2.13, 2.14, 2.15, 2.16

**Attachments:**
- [test.zip](https://issues.apache.org/jira/secure/attachment/12776117/test.zip) (_2.83 kB_)

2 votes, 5 watchers

Use the attached test.zip to reproduce the console output difference between Surefire 2.10 and versions 2.13–2.16. Trace how failed-test output is emitted, then define and verify an option that restores the earlier behavior without dumping stack traces to the console.

Written by the indexing model from the issue text.