Skip to content

Test logging change

Logs are written in tests. This doesn't impact if they pass, but makes it look like a problem when an error is logged because of a certain test state - particularly when it logs an error but the error is allowed to happen via mocked functions.

  1. Suppress logs when they are confusing or not relevant for the test
  2. Assert logs are made when they should be - e.g. a QPlan server admin expects a log in a certain condition, we should test that the log is actually made related in unit tests.