Status: Started Owner: damien.c...@gmail.com CC: tudor.gi...@gmail.com, chisvasi...@gmail.com Labels: Type-Defect Priority-Medium Platform-Pharo Component-Glamour
New issue 886 by damien.c...@gmail.com: GLMMorphicSpotterTest>>testCreation is not automatic http://code.google.com/p/moose-technology/issues/detail?id=886
This method opens a tool and requires user intervention. This blocks test runners and continuous integration.
Comment #1 on issue 886 by damien.c...@gmail.com: GLMMorphicSpotterTest>>testCreation is not automatic http://code.google.com/p/moose-technology/issues/detail?id=886
Name: Glamour-Morphic-Renderer-DamienCassou.176 Author: DamienCassou Time: 3 December 2012, 6:21:29.292 pm UUID: 24ea738e-586f-482a-8c93-107eb1411bc3 Ancestors: Glamour-Morphic-Renderer-TudorGirba.175
- Renames GLMMorphicSpotterTest>>testCreation to #creation as it is not a unit test: it requires manual intervention.
See issue #886
Comment #2 on issue 886 by tu...@tudorgirba.com: GLMMorphicSpotterTest>>testCreation is not automatic http://code.google.com/p/moose-technology/issues/detail?id=886
Is this not fixed now?
Comment #3 on issue 886 by damien.c...@gmail.com: GLMMorphicSpotterTest>>testCreation is not automatic http://code.google.com/p/moose-technology/issues/detail?id=886
Depends on what you mean by fixed. What did you want when you wrote this method? #creation is still not automatic. If you want an automated unit test, then you may consider this report as still be open. Otherwise you may want to delete the method and class.
Comment #4 on issue 886 by tu...@tudorgirba.com: GLMMorphicSpotterTest>>testCreation is not automatic http://code.google.com/p/moose-technology/issues/detail?id=886
It was more of a prototype. We need to write a test for the widget. So we keep it open :)
-
moose-technology＠googlecode.com