From: Richard Conroy <richard.conroy@...>
Date: 2011-11-07T17:37:18+09:00
Subject: Re: Good debugging mechanism

--0016364d23cd4406fe04b120f66d
Content-Type: text/plain; charset=ISO-8859-1

Generally it is sufficient to test only the public methods of your
implementation, but to ensure good coverage it is often easier to test the
non-public helper methods.

When you are ensuring that your application is tested it is necessary to
test every code path, which is why you will end up with more tests methods
than public methods.

On Mon, Nov 7, 2011 at 8:30 AM, Uma Mahesh <umamahesh_nyros@yahoo.com>wrote:

> shall we need to have test cases for every methods that were implemented
> in the application ?
>
>
> Thank You,
> Uma Mahesh Varma,
> Skype :       umamahesh.nyros
>
>
> ________________________________
> From: Rimantas Liubertas <rimantas@gmail.com>
> To: ruby-talk ML <ruby-talk@ruby-lang.org>
> Sent: Monday, November 7, 2011 12:59 PM
> Subject: Re: Good debugging mechanism
>
> > writing good tests.
>
>
> How do you debug your tests then? By writing other tests?
> Tests may show you the need to debug that's it.
>
>
> Regards,
> Rimantas
> --
> http://rimantas.com/
>



-- 
http://richardconroy.blogspot.com | http://twitter.com/RichardConroy

--0016364d23cd4406fe04b120f66d--