Integration with third party tools is important for the success of Swift Testing and the ecosystem as a whole. To support this, Swift Testing should offer tools more control over how custom issues are recorded and what is shown.
Currently, when a third party assertion fails, they can only use the existing Issue.record
static method. Which misleading records that as an unconditional failure. Swift Testing should allow recording of assertions without misleadingly labeling them as unconditional failures.
Read the full proposal here.