One approach could be to set up an event listener and trap assertions when they fire.
In the attached Test Case,
- the first step sets up a listener
- the second step fires some assertions (using Generate Warning so that each assertion executes)
- the third step removes the listener and prints out the trapped assertion's long and short descriptions.
Check and see if you can do something like this. The TC prints both the Long and Short description of the assertions that fire so you can see the difference in the output.
If no assertions fire, the properties holding the descriptions would be empty.