Re: links between Junit tests and source code!!

Steven Gordon <[email protected]>
Newsgroups gmane.comp.programming.refactoring
Message-ID <[email protected]>
150 tests means 150 runs and reports.  It does not sound that big to me.

If you need it once in order to document the relationships and then only
need to do it for each new test created going forward, then this is less
work than fully automating it (including testing and fully debugging that
automation).  If you can script running one test in isolation and one
report, then you just need to either parameterize that script or make 150
copies of it (yuck).  It is yucky, but not too much work for a one-time
requirement.

If your system is so highly volatile that you believe the same test will be
testing other classes in the future than it is testing today, then
automation would really be necessary.

All these options are better than brain explosion.

However, the best option is to challenge the need for this kind of
information in the first place.  Knowing which methods are not tested by any
of the tests is all a project should really care about.  If a method is
tested by at least one test, why does it matter which test it is?

On Fri, Nov 27, 2009 at 7:49 AM, ABDULLAH KASSEF <[email protected]>wrote:

>
>
> I think create a separate report after running each test does not possible,
> since I have a
>  big project repository i.e. about 150 test cases with about 450-500 class,
> so my problem
> now is how I can know which test case tests this class ignoring a naming
> convention ?, because most of these test cases names do not relate to class
> names, also you can find
> one test case tests multi classes , and other test case calls multi classes
> and tests
> one of them, so my question is there is a tool I can use to create a links
> between them or/and how I can develop a tool create such these links??
>
> please help me, because now I am feeling that my brain may explode in any
> time!!!!
>
>
> --- On Thu, 11/26/09, Steven Gordon <[email protected]<sgordonphd%40gmail.com>>
> wrote:
>
> From: Steven Gordon <[email protected] <sgordonphd%40gmail.com>>
>
> Subject: Re: [refactoring] links between Junit tests and source code!!
> To: [email protected] <refactoring%40yahoogroups.com>
> Date: Thursday, November 26, 2009, 9:38 AM
>
>
>
>
> On Thu, Nov 26, 2009 at 9:37 AM, Adam Sroka <adam.sroka@gmail. com> wrote:
>
> > You can also get a
> > coverage report if you run Cobertura (
> > http://cobertura. sourceforge. net/sample/) which annotates the class to
> say
> > what parts are covered by tests (But it doesn't tell you which test tests
> > what.)
>
> I believe if you ran the tests one at a time and created a separate
> report after running each test, each report would tell you what was
> exercised by that particular test.
>
> I would not consider this level of detail to be worth that additional
> amount of effort, but I believe it could be automated.
>
> [Non-text portions of this message have been removed]
>
>  
>


[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.