The current FHIR Testing - Assert Execution definition states:

If the conditions of the assertion are not met, the test being executed fails and execution of the test is halted. Test execution will then continue with the next test.

This limits the user to the first failed assert results for a given test. Asserts are independent of each other and only rely on the associated operation.

https://chat.fhir.org/#narrow/stream/179166-implementers/topic/TestScript.20-.20assert.20processing

The Zulip chat discussion proposed two possible approaches:

Define a new TestScript.test.action.assert.stopTestOnFail boolean element.

'true' - current behavior, stop test execution if this assert fails
'false' - new default behavior, continue test execution regardless of this assert's result

Or,

Redefine the FHIR Testing - Assert Execution processing to allow all asserts to be evaluated.

Feedback on pros and cons of either approach is welcome.