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.
Hi!
I've just opened Moose and got quite surprised by the beauty of it. Nice fonts, nice white space.
One missing thing: the autocompletion which is not on tab :-)
Good job Doru!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Doru wrote:
>I need a bit of help with the issue of the SpecDebugger relying on the default inspector being implemented in Spec.
Hmm, one gets used to having a decent inspector. Going back to the Pharo 3 default is not funny…
The GTInspector might be a bit of an ugly duckling, but there really is a big bad-ass powerful swan
in there.
I strongly support the help request. And phd organization of course.
Stephan
The only sender of
MooseEntityState>cache: selector initializer: aBlock
^self
propertyAt: selector
ifAbsentPut: [aBlock cullValue: self entity]
is
MooseEntity>lookUpPropertyNamed: selector computedAs: aBlock
^self privateState cache: selector initializer: aBlock
all senders of which in the Moose 5 image are parameterless blocks.
Is anyone depending on the existence of the entity instVar
in MooseDefaultState (and accessors in MooseEntityState)?
When looking at the class comment on MooseEntity, I wonder
why the state has a back link.
Stephan
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-GlamorousToolkit Milestone-5.0
New issue 996 by tu...(a)tudorgirba.com: GTInspector should update the
presentations when a new one is added from inside
http://code.google.com/p/moose-technology/issues/detail?id=996
When browsing the methods in the inspector, we can add a new method with a
presentation. When this happens, we want to inspector to refresh so that
the presentation appears on top.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Hi!
I like the way Moose is shaking.
What about the Moose association? Who is willing to accept some money?
Is there a subscription? What are the fees? How the money will be spent?
Is there a logo Object Profile can put on the website to say it is part of the Moose Association?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Does anyone know about this tool?
http://www.xtran-llc.com/index.html
It also promises a meta-tool for software engineering and some software
analysis and transformation services already built in the tool.
regards,
Usman
Hi everyone.
For me it’s still not clear how does HISMO version versions :).
To help myself explain my question I’ve attached the image.
What happens if a new nodes are added to each version. Do all 3 snapshots share same nodes, or they are duplicated? Because when I look at MooseSampleData>>initialization it seams to me that 5 different models are created and references to them are stored to them from history.
Cheers.
Uko
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.9
New issue 986 by tu...(a)tudorgirba.com: Roassal Athens uses the default
Morph logic for PNG export
http://code.google.com/p/moose-technology/issues/detail?id=986
Even though Athens can render with nice anti aliasing, when exporting to
PNG, the default logic is being used:
ROMorphicPlatform>>imageExporterClass
^ ROPharoImageExporter
We should use the nice rendering of Athens for the export.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings