[
https://issues.jboss.org/browse/ARQ-1831?page=com.atlassian.jira.plugin.s...
]
Juraj Húska commented on ARQ-1831:
----------------------------------
IMHO the first four-8 rows of stacktrace are usually important, it would be nice if only
those lines are visible by default.
Another addition I would welcome is having the exception message be bold, as for me these
things are most important when looking at failed test:
# name of the test method and test class
# exception message
# from now on screenshots as well
Make reported exception stack-traces more concise
-------------------------------------------------
Key: ARQ-1831
URL:
https://issues.jboss.org/browse/ARQ-1831
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Recorder
Affects Versions: recorder_1.0.0.Alpha4
Reporter: Juraj Húska
Priority: Minor
Reported exceptions stack-traces are too long, they sometimes take more then two screens.
It makes report less readable.
It would be nice if they are shorter.
For example if they are generated to {{html}}:
* then they can be written inside {{textarea}} or another block, frame with predefined
height, so one will be able to scroll in such a block to reveal full stack-trace
* or something like Twitter Bootstrap
[
collapse|http://getbootstrap.com/2.3.2/javascript.html#collapse] can be employed.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)