3 Dec
2012
3 Dec
'12
6:19 p.m.
Status: Started
Owner: damien.c...(a)gmail.com
CC: tudor.gi...(a)gmail.com, chisvasi...(a)gmail.com
Labels: Type-Defect Priority-Medium Platform-Pharo Component-Glamour
New issue 886 by damien.c...(a)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.
3 Dec
3 Dec
6:21 p.m.
Comment #1 on issue 886 by damien.c...(a)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
10:36 p.m.
Comment #2 on issue 886 by tu...(a)tudorgirba.com:
GLMMorphicSpotterTest>>testCreation is not automatic
http://code.google.com/p/moose-technology/issues/detail?id=886
Is this not fixed now?
4 Dec
4 Dec
8:30 a.m.
Comment #3 on issue 886 by damien.c...(a)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.
8:52 a.m.
Comment #4 on issue 886 by tu...(a)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 :)
4401
days inactive
4402
days old
4 comments
1 participants
participants (1)
-
moose-technology＠googlecode.com