I have had similar issues with testing PHANtom. Apparently the test runner does meta-level stuff that interferes with other packages that modify method lookup (through method wrappers or other means). I have no fundamental fix, sadly. A workaround is to run the tests outside the test runner.
On Nov 14, 2013, at 11:30 AM, Ben Coman btc@openInWorld.com wrote:
I have seen use of Sets in tests introduce randomness in the ordering of results.
MartinW wrote:
Hello, i am experimenting with the Spy framework (i hope this is the appropriate newsgroup).
I encountered the following problem: Running unit tests through Spy gives sometimes other test results than running them with the Test Runner.
I first encountered this problem when i tried in Pharo 2:
Profiler runTestsForPackages: #('XML-Parser-Nodes' 'XML-Tests-Parser-Nodes')
When the same tests are run from the Test Runner all 126 tests pass, test results in the Spy Profiler show 12 failures.
Is anybody working with tests in Spy? Does anybody have an idea what may cause this phenomenon and how to fix it?
Best regards, Martin.
http://forum.world.st/file/n4722052/Tests_with_Spy.png
-- View this message in context: http://forum.world.st/Spy-alters-some-test-results-tp4722052.html Sent from the Moose mailing list archive at Nabble.com. _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile