AFAIK Cursive does nothing with the testing macro; it would be very useful if the details of the executing test, and any testing contexts, was presented as part of the assertion differences panel; this would partially offset #1945.

It would be nice if there was a banner of some kind that would identify the FQN of the executing test and any nested testing contexts.
AFAIK Cursive does nothing with the
testingmacro; it would be very useful if the details of the executing test, and any testing contexts, was presented as part of the assertion differences panel; this would partially offset #1945.It would be nice if there was a banner of some kind that would identify the FQN of the executing test and any nested
testingcontexts.