[ 
https://issues.apache.org/jira/browse/QPID-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-6265:
-----------------------------
    Attachment: 0001-WIP-Refactor-QBTC-logging.patch

Patch originally implemented by Keith Wall contains the improvements for 
logging in QBTC

> [Java Broker] Improve generation of system test outputs
> -------------------------------------------------------
>
>                 Key: QPID-6265
>                 URL: https://issues.apache.org/jira/browse/QPID-6265
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Tests
>    Affects Versions: 0.30
>            Reporter: Alex Rudyy
>            Assignee: Alex Rudyy
>         Attachments: 0001-WIP-Refactor-QBTC-logging.patch
>
>
> Refactor system test framework to allow for the test logs from failed tests 
> to be collected easily by CI. This task must include the outstanding issue 
> whereby some tests fail to generate test output for the client or the test 
> itself (such as the MultiNodeTest).
> We said that our system test output should be:
>     single log file per test method
>     output from test/client/broker(s) combined into the single log with 
> output from each easily recognisable
>     method for Jenkins to archive output files from those tests that fail
> It would also be desirable if we can start to reduce the responsibilities of 
> the QBTC.
> We have some tests (the logging tests) that parse the output of the test log 
> looking for operation log messages etc. In the long term these tests will be 
> remove, however, this is not in scope for this task. Instead, we might want 
> to do something simple to allow the test to continue to operate (such as 
> defining a custom appender)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to