Open Eliott-Guevel opened 3 months ago
Thanks Eliot Thank for your report. If your tests works in isolation and not in a group it means that you get a dependency between your tests. The tester runner has been changed to make sure that the tests are not always run in the same order just to spot such hidden and bad dependencies. So can you check your code because to us this is not a Pharo problem. S
Bug description Some tests that pass in Pharo 11 don't pass in Pharo 12.
To Reproduce Steps to reproduce the behavior:
dev-incubator
branch)MolComponentManager
's tests in theMolecule-Examples
packagetestDeepCleanupGarbageCollect
,testFlushComponents
andtestGarbageCollect
can fail. Executing them individually doesn't raise errors, and since the tests pass in Pharo 11 it seems more of a Pharo 12 problem than ansetUp
andtearDown
problem.Expected behavior Tests that pass in Pharo 11 should also pass in Pharo 12.
Screenshots Examples of different outputs
Version information: