[DAFFODIL-2643] unit test needed that shows how to capture and examine log for proper logging

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.2.1
• Component/s: Infrastructure, QA
• Assignee: Unassigned
• Reporter: Mike Beckerle
• Created: 01/Feb/22 16:29
• Updated: 06/Feb/24 19:14

Description

Proper logging should be testable.

We need a unit test that sets up a logger and verifies that a particular logging message is present. The purpose of this test is (a) show logging is working at all (b) show how to do this so as to insure certain log messages are present.

Ideally the TDML language should have a way of specifying expected log output:

<logs>
  <log>string here that must be in log message case insensitive</log>
  <log>another such string</log>
</logs>

And consistent with DAFFODIL-864, which calls for TDML negative errors, warnings, validation errors, etc. there should be negative log checking as well.