Erwan, Scott,
Small comments Inline...
From: "Erwan de FERRIERES" <erwan.de-ferrie...@nereide.biz>
Hi Jacques,
inline
Le 11/12/2009 08:47, Jacques Le Roux a écrit :
What about groovy scripts, are they handled by Cobertura?
From what I know Cobertura needs .class files, and for the groovy files, it
would mean to compile them first
http://docs.codehaus.org/display/GROOVY/Code+Coverage+with+Cobertura
Class are created when they are used and placed in cache. As suggested Scott we could use the wonderful artifact info mechanism to
deal with this aspect and also the others (not UI)
And actions in Screens, is it worth do something? I guess checking
"static structural" files like web.xml, ofbiz-component.xml files (and
all xml like them, controllers, menus, commonsScreens and such) is not
necessary?
I think this would mean a lot of work to adapt a tool to this. But if we just stay on the services, this vould give a great
overview of their coverage.
As we are in a SOA system, and service is the most important part of the
system, we have to be sure they are tested.
For all user interface testing, validation could be done via storylines and scenarios, with expected results after an action, as
David described in UBPL, for the user point of view.
I guess this is more related to Selenim. Not sure how to link Cobertura and
Selenium though
Jacques
Jacques
From: "Erwan de FERRIERES" <erwan.de-ferrie...@nereide.biz>
Now the point would be to show the coverage of the simple methods and
also, maybe in sometime, the selenium coverage.
What would be great is finding a way to indicate which services are
tested, and then display it in the webtools. This won't give an
information as precise as cobertura but would add some quick display
on what is or can be tested.
If we agree on a syntax to use, I would be ready to add the screen in
OFBiz.
Cheers,
Le 11/12/2009 00:21, Scott Gray a écrit :
../..
--
Erwan de FERRIERES
www.nereide.biz
--
Erwan de FERRIERES
www.nereide.biz
