28 Dec
2011
28 Dec
'11
3:22 p.m.
Hi,
Thanks Steffen, I already found some java projects using JUnit annotations,
such as: @RunWith, @Test, @Before and @After, and verveinej imports all
this annotations.
Regards,
Hani
2011/12/28 Steffen Märcker <merkste(a)web.de>
Hi,
a quick look on JUnit shows that it eats its own dogfood - the tests for
JUnit use the annotations. Have a look at the sources on
https://github.com/KentBeck/**junit/downloads<https://github.com/KentBec…
Unfortunately I am not aware of other projects using this annotations. I
suggest to just have a look a newer projects on GitHub & Co.
Regards,
Steffen
Am 21.12.2011, 19:03 Uhr, schrieb Hani Abdeen <hani.abdeen(a)gmail.com>om>:
Hi,
Thanks Doru, using -autocp I've now the JUnit classes and a lot of other
stub classes :) it's good to consider the jars that come with the
project under-analysis.
@Steffen
Also thank you Steffen, you are right, we should consider, in addition to
the JUnit classes, the JUnit annotations when they are used in the java
project under-analysis.
Do you have/know a Java opensource project using JUnit annotations?
just to test the availability of those annotations using verveinej.
Cheers,
Hani
2011/12/21 Steffen Märcker <merkste(a)web.de>
It might be neccessary to consider the common JUnit annotations as well,
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/**mailman/listinfo/moose-dev<https://www.iam.un…
e.g. @Test, @RunWith, etc. Inheriting from
TestCase is not recommended
anymore in JUnit. Test methods and classes are now identified by their
annotations.
Regards, Steffen
Am 21.12.2011, 00:28 Uhr, schrieb Hani Abdeen <hani.abdeen(a)gmail.com>om>:
Hi,
______________________________**_________________
Using VerveineJ, the stub classes realted to unit tests (TestCase,
TestSuit
and Test classes) are not imported
also their namesapce junit.framework
These classes are imported using inFamix.
junit.framework.TestCase class is particularly important in order to
automatically detect unit test classes: TestCase subclassHierarchy.
If this class is not available in the moose model then the only way to
automatically detect unit test classes is by detecting the classes that
their names are postfixed by 'Tests':
mooseModel allClasses select: [:c| '*Tests' match: c name]
such a way can provide us with wrong results!
Cheers,
Hani
P.S.: use-case JFreechart project:
http://sourceforge.net/****projects/jfreechart/files/****
latest/download<http://sourceforge.net/**projects/jfreechart/files/**lat…
<http://**sourceforge.net/projects/**jfreechart/files/latest/**download<http://sourceforge.net/projects/jfreechart/files/latest/download>
which includes about 380 test classes (classes inherit from TestCase)
--
______________________________****_________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/****mailman/listinfo/moose-dev<https://www.iam.…
<htt**ps://www.iam.unibe.ch/mailman/**listinfo/moose-dev<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>