Here are some examples.
Katas based on a JavaEE application:
- find all classes that are on a part of the application (select)
- from those find those that are annotated with #Remote (select)
- check to see if these are using inheritance (present)
- find all annotation types used within these classes (navigation: collect)
Katas based on the Moose code:
- How many metrics are there in Moose? (detect it in three different ways)
- Where are the metrics located over the class hierarchy?
- Which metrics do not have associated comments?
- How many Roassal/Mondrian visualization methods do not follow the convention of xyzOn:
view, but instead hardcode the view instantiation?
Cheers,
Doru
On Apr 4, 2013, at 1:42 PM, roberto.minelli(a)usi.ch wrote:
I totally agree. Having that would be great!
Cheers,
R
On Apr 4, 2013, at 12:44 PM, Stéphane Ducasse <stephane.ducasse(a)inria.fr>
wrote:
Hi guys
I would really like to get a list of simple questions/actions that we can use to run
katas around Moose.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Next time you see your life passing by, say 'hi' and get to know her."