Given a test that is marked as an expected failure, but passes nevertheless, the test will appear as failure in the test runner. There is a count of such unexpected passes in the "traffic light" pane.
When Run Failures is used, the count of unexpected passes is not reset to zero. Instead, the number of unexpected passes is added repeatedly. The total number of tests run also keeps adding up in the same way.
Clicked three times on Run Failures before taking this screenshot.
Test case, literally:
'From Squeak6.0 of 15 August 2022 [latest update: #22111] on 25 September 2022 at 5:37:39 pm'!
TestCase subclass: #Test
instanceVariableNames: ''
classVariableNames: ''
poolDictionaries: ''
category: 'Test'!
!Test methodsFor: 'tests' stamp: 'jr 9/25/2022 17:37'!
expectedFailures
^ #(testShouldFail)! !
!Test methodsFor: 'tests' stamp: 'jr 9/25/2022 17:37'!
testShouldFail
self assert: true.! !
Given a test that is marked as an expected failure, but passes nevertheless, the test will appear as failure in the test runner. There is a count of such unexpected passes in the "traffic light" pane.
When Run Failures is used, the count of unexpected passes is not reset to zero. Instead, the number of unexpected passes is added repeatedly. The total number of tests run also keeps adding up in the same way.
Test case, literally: