As you may know, we are currently in the process of building our first real-world, non-trivial application based on mbeddr. In this process we are of course finding and fixing all kinds of bugs. However, we also find more general productivity issues. For example, it is tedious and error prone to find the source of an assertion failed message in our test output. Sure, the output specifies the module/function/assert that failed, but it is still annoying.
To solve this problem we have created a new view, the mbeddr Error Output Analyzer. You paste the console output of a set of tests into a textarea. The view then parses the output and searches for the nodes that created the messages in the output. It lists the nodes in the view so you can then click on the node to select it in the editor:
We have created a similar view that finds TODOs in comments.