SLF4J Test

Changelog

slf4j-test-2.9.0 (2023-03-22)

Full Changelog

Implemented enhancements:

• #360 - Add ability to make assertions using the PredicateBuilder more fluent (by @topbadger)

  Static helper method and method overloads are added to make assertions using the PredicateBuilder more fluent.

  This allows assertions to be declared as follows:

  assertThat(logger).hasLogged(aLog().withLevel(Level.WARN).withMessage("Something"));
  

  as opposed to:

  assertThat(logger).hasLogged(new PredicateBuilder().withLevel(Level.WARN).withMessage("Something").build());
  

Updates:

• Bump org.slf4j:slf4j-api from 2.0.6 to 2.0.7
• Bump org.assertj:assertj-core from 3.23.1 to 3.24.2

slf4j-test-2.8.1 (2023-01-05)

Full Changelog

Fixes:

• #323 via #334 Allow logged message to be null (by @valfirst)

slf4j-test-2.8.0 (2022-12-28)

Full Changelog

Implemented enhancements:

• #188 via #328 - Restructure assertions to be based on predicates (by @topbadger)

  By re-structuring the assertion logic to be based upon predicates, the following enhancements have been made:

  Custom Predicates

  Consumers can now provide custom predicates so that they can assert on LoggingEvents in specific ways in addition to the ways previously supported by the library.

  Example:

  assertThat(logger)
      .hasLogged(event -> event.getFormattedMessage().startsWith("First section of long log message"));
  

  MDC Comparison Strategy

  The MDC comparison strategy can now be set by consumers.

  • The full MDC context isn't always relevant to the test, yet the assertions previously enforced this check. The result was that people were unable to use the fluent assertions we provide in a number of scenarios.
  • The previous behaviour of requiring the MDC contents to match exactly has been retained as the default.

  Example:

  assertThat(logger)
      .usingMdcComparator(MdcComparator.IGNORING)
      .hasLogged(warn("Some log message"));
  

  Enhanced Assertion Failure Messages

  Assertion failure messages have been enhanced to show the list of LoggingEvents that were actually captured to make debugging the cause of the failure easier.

  Example:

  Failed to find event:
    LoggingEvent{level=ERROR, mdc={}, marker=Optional.empty, throwable=Optional[throwable], message='There was a problem!', arguments=[]}
  
  The logger contained the following events:
    - LoggingEvent{level=WARN, mdc={}, marker=Optional.empty, throwable=Optional.empty, message='Some other problem', arguments=[]}
    - LoggingEvent{level=ERROR, mdc={}, marker=Optional.empty, throwable=Optional.empty, message='Yet another problem', arguments=[]}
  

slf4j-test-2.7.0 (2022-12-19)

Full Changelog

Implemented enhancements:

• #314 via #324 - Introduce a new capture.level property and API to control captured events globally (by [@youribonnaffe]https://github.com/youribonnaffe)

  Introduce a new global setting capture.level to disable storing (and printing) logs at a given level (following the level hierarchy).

  The implementation is very similar to the print.level global setting.

  This is useful when tests are generating a lot of logging events that are not of interest and don't need to be captured. ArchUnit tests are known to be such tests and can be quite slow when slf4j-test is used.

Updates:

• Bump org.slf4j:slf4j-api from 2.0.0-alpha7 to 2.0.6
• Bump joda-time:joda-time from 2.10.14 to 2.12.2
• Bump org.assertj:assertj-core from 3.22.0 to 3.23.1

slf4j-test-2.6.1 (2022-04-01)

Full Changelog

Fixes:

• #255 via #257 Fix memory leak when clearing logs in all threads (by @sofiamorseletto) Going back to the custom ThreadLocal implementation (uk.org.lidalia.lang.ThreadLocal) in order to prevent memory leaks.

slf4j-test-2.6.0 (2022-03-21)

Full Changelog

Implemented enhancements:

• #247 Log events found when AssertJ assertion fails (by @jamietanna)

  This helps quite a bit with diagnosing why an assertion fails, as the alternative is to either attach a debugger or System.out.println the logging events found.

• #250 via #251 Add TCCL attribute to LoggingEvent (by @sofiamorseletto)

  The changes add an attribute on LoggingEvent which contains the Thread Context Classloader used when the logging event was created. This allows the assertion of the TCCL of a certain log to check that the log was handled by the correct classloader.

Updates:

• Bump org.slf4j:slf4j-api from 2.0.0-alpha6 to 2.0.0-alpha7
• Bump com.google.guava:guava from 31.0.1-jre to 31.1-jre
• Bump joda-time:joda-time from 2.10.13 to 2.10.14

slf4j-test-2.5.0 (2022-02-08)

Full Changelog

Updates:

• #228 - Bump org.slf4j:slf4j-api from 2.0.0-alpha5 to 2.0.0-alpha6

  NOTE: slf4j-test:2.5.0 is compatible with slf4j-api:2.0.0-alpha6and higher and it is not compatible with previous versions (see compatibility matrix for more details). The root cause is breaking changes in SLF4J API:

  • breaking change 1
  • breaking change 2

• Bump org.assertj:assertj-core from 3.21.0 to 3.22.0

slf4j-test-2.4.1 (2021-12-23)

Full Changelog

Implemented enhancements:

• #207 - Enable assertions to be made on LoggingEvents from any thread (by @topbadger)

  The current implementation only verifies against the LoggingEvents captured by the thread that is running the test. TestLogger provides access to all events captured across any thread via TestLogger::getAllLoggingEvents() so a modifying method has been added to the assertion class to allow the assertion mode to be switched.

  Example usage:

  assertThat(logger).anyThread().hasLogged(...);
  

• #220 via #221 - Format null-s in LoggingEvent#getFormattedMessage() the same way as SLF4J (by @josephw)

  LoggingEvent#getFormattedMessage() is public (#23). However, it hasn't presented null values the same way as SLF4J, due to un-matched wrapping/unwrapping of Optional:

  LoggingEvent e = new LoggingEvent(Level.INFO, "Content: {}, {}", null, "value");
  System.out.println(e.getFormattedMessage());
  

  Produced previously:

  Content: Optional.empty, value
  

  Produces now:

  Content: null, value
  

Updates:

• Bump org.slf4j:slf4j-api from 2.0.0-alpha4 to 2.0.0-alpha5
• Bump joda-time:joda-time from 2.10.10 to 2.10.13
• Bump com.google.guava:guava from 30.1.1-jre to 31.0.1-jre
• Bump org.assertj:assertj-core from 3.20.2 to 3.21.0

slf4j-test-2.4.0 (2021-08-25)

Full Changelog

Updates:

• #190 - Bump org.slf4j:slf4j-api from 2.0.0-alpha2 to 2.0.0-alpha4

• #190 - Update according to the changes in SLF4J API 2.0.0-alpha3

  NOTE: slf4j-test:2.4.0 is compatible with slf4j-api:2.0.0-alpha3and higher and it is not compatible with previous versions (see compatibility matrix for more details). The root cause is breaking change in SLF4J API.

slf4j-test-2.3.0 (2021-08-05)

Full Changelog

Implemented enhancements:

• #184 - Add assertion for substrings of log messages (by @jamietanna)
• #187 - Add assertions based on LoggingEvent (by @jamietanna)

Internals:

• #185 via #186 Enforce consistent code style (by @jamietanna)

slf4j-test-2.2.0 (2021-07-29)

Full Changelog

Implemented enhancements:

• #181 via #182 - Add initial AssertJ assertions (by @jamietanna)

Updates:

• #124 via #126 - Add an explicit license to the project
• Bump org.slf4j:slf4j-api from 1.8.0-beta2 to 2.0.0-alpha2
• Bump joda-time:joda-time from 2.10 to 2.10.10
• Bump com.google.guava:guava from 26.0-jre to 30.1.1-jre

slf4j-test-2.1.1 (2018-09-17)

Full Changelog

Implemented enhancements:

• Make LoggingEvent self-descriptive: implement toString method (by @valfirst)

Updates:

• Bump com.google.guava:guava from 25.1-jre to 26.0-jre

slf4j-test-2.1.0 (2018-06-29)

Full Changelog

Implemented enhancements:

• #23 - Make LoggingEvent#getFormattedMessage public (by @valfirst)
• Drop uk.org.lidalia:lidalia-lang dependency (by @valfirst)

Updates:

• Bump org.slf4j:slf4j-api from 1.8.0-beta1 to 1.8.0-beta2
• Bumpjoda-time:joda-time from 2.9.9 to 2.10
• Bump com.google.guava:guava from 24.1-jre to 25.1-jre

slf4j-test-2.0.0 (2018-03-19)

Full Changelog

Breaking changes

• Increase minimum required JDK version from 7 to 8
• Change base package to com.github.valfirst to reflect ownership

Implemented enhancements:

• #6 - Implement JUnit 5 support (by @valfirst)
• Optimize performance: replace CopyOnWriteArrayList with Collections.synchronizedList in TestLoggerFactory (by @valfirst)

Updates:

• Bump org.slf4j:slf4j-api from 1.8.0-beta0 to 1.8.0-beta2
• Bump com.google.guava:guava from 20.0 to 24.1-jre

slf4j-test-1.3.0 (2018-01-05)

Full Changelog

groupId was changed to com.github.valfirst to reflect ownership

Implemented enhancements:

• Support new SLF4J binding mechanism introduced in SLF4J 1.8

Updates:

• Upgrade to Guava 20.0, Joda Time 2.9.9

Version 1.2.0

Allows construction of standalone instances to facilitate logging in different contexts.

Version 1.1.0

Fixes https://github.com/Mahoney/slf4j-test/issues/4 - Detect throwable as last varargs element if the format string has n-1 parameters.

With thanks to https://github.com/philipa

Version 1.0.1

Fixed an issue where null arguments to a logging event and null values in the MDC caused a NullPointerException due to Guava's strict attitude to nulls. Null arguments now appear as Optional.absent() and null values in the MDC as the String “null”.