and if one add a #inspect send in a testMethod, the results are the same with the TestRunner but differ if one run them from Nautilus. As an example, with: ----- testEnteringTextInPort | composite textMorph | composite := GLMCompositePresentation new with: [ :a | a rubricText display: '' ]. window := composite openOn: 4. textMorph := self find: RubScrolledTextMorph in: window. textMorph simulateClick. self assert: textMorph activeHand keyboardFocus = textMorph textArea. self simulateKeyStrokes: 'hello'. (composite pane port: #text) value asString inspect. <-------------------------------- ** inspect added here ** self assert: (composite pane port: #text) value asString = 'hello' ---- by running tests from Nautilus, the inspect runs ok and the result string is 'hello'. but now #testAcceptKeyCanBeOverriden turns yellow
by running test from the TestRunner, #testEnteringTextInPort and #testPastingUpdatesTextPort stay yellow (as without the inspect) and #testAcceptKeyCanBeOverriden is green
Alain
Le 2 juil. 2013 à 12:49, Tudor Girba tudor@tudorgirba.com a écrit :
Thanks. I got the same problem and I do not know where to start from. It's really strange.
For those interested, the tests are in the GLMRubricTextMorphicTest class. If you run all of them repeatedly, you get some errors. If you run them individually, you do not.
Alain: do you happen to have an insight?
Doru
On Tue, Jul 2, 2013 at 11:53 AM, Yuriy Tymchuk yuriy.tymchuk@me.com wrote: Hi guys.
I hope that we can release 4.8 and move to Pharo 3.0 soon. I wanted to fix failing tests and the only one is Rubric test. I was working with it for some time, and I have no idea what's up. When you run tests separately they work fine, but when being run in a suite some test fail and failures are inflicted by test order
Maybe someone have ideas where to look at? UI maybe?
Uko _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"