Thursday, November 23, 2023
2 changes · master
Enhancements to existing features
Test logs now identify the specific test case that produced each message, making failures easier to investigate. This improves internal debugging for browser-based and JavaScript tests, with a small increase in log size.
Original PR description
Currently the HttpCase logging uses a class-bound logger. This means the messages (including browser messages during tours) are associated with the test *class*, making debugging more difficult than necessary as the logs don't actually say which test the log comes from, you have to hunt that information somewhere else. Add a per-instance sub-logger, such that a test case's inner logs are associated with that test specifically, clarifying the logs (especially tours and js tests), at the cost of increasing the size of the logs a bit.
Knowledge article moves now create fewer chatter messages by combining parent and root article changes into one entry when possible. This makes article history easier to read and reduces noise for users tracking hierarchy changes.
Original PR description
When the user moves an article in the hierarchy, the chatter will display one log entry when either the parent article or the root article changes. To minimize the number of log entries, we will consolidate these two changes into a single log entry whenever possible, using the same format as the command palette (i.e., \<parent article\> - \<root article\>). This will make the chatter less noisy. task-3491588