Hi Andy, It's a custom processor I'm writing. I was scratching my head wondering if that is it, or adding a test dependency for logback has something to do with it.
I just copy/pasted this one: https://github.com/apache/nifi/blob/d838f61291d2582592754a37314911b701c6891b/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/test/resources/logback-test.xml and droped it into my src/test/resources No such luck at seeing logs yet in my output yet. Ryan On Tue, Sep 26, 2017 at 5:59 PM, Andy LoPresto <[email protected]> wrote: > Ryan, > > Which module is this running in? Some modules have a logback.xml file > defined in /src/test/resources/logback.xml which configures the test > loggers, while others do not. If this is not configured in your module, you > won’t see the error messages on the console. You can copy an existing > logback.xml file from one of the other modules (be sure to use one from the > *test* directory, not the *main* directory). > > > Andy LoPresto > [email protected] > *[email protected] <[email protected]>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Sep 26, 2017, at 2:51 PM, Ryan H <[email protected]> wrote: > > Hi, > I'm curious if there's a way to get the ComponentLog to output to > StandardOut during a Unit Test. > > I see I can access them when I call > testRunner.getLogger().getErrorMessages(), > however, I'd really like to see a stacktrace if it happens without having > to iterate through an array to find it. > > I feel like I'm just missing something obvious here, I'd appreciate any > advice. > > Thanks, > Ryan > > >
