Re: Testing Searcher Object

How many ways are there for it to go right?  I can see a null response, a
single return, multiple returns. Can it get duplicates? What other results
are "happy" paths?

How many ways are there for it to go wrong? An invalid search? A backend
that isn't working? An invalid input? what? What else?

Remember, you're testing the SEARCHER OBJECT not every possible search, or
the system behind it.




On Mon, May 26, 2014 at 10:16 AM, Eb [email protected][testdrivendevelopment]
<[email protected]> wrote:

>
>
> Hi -
>
> We were having a conversation about testing a "searcher" object.
> Basically, this object does a search based on the inputs passed into it.
> Do tests have to be written for every permutation of inputs for the class
> to have been tested properly?
>
> Thanks.
>
> --
> blog: http://eikonne.wordpress.com
> twitter: @eikonne
>
>
> 
>



-- 
Tim Ottinger, Sr. Consultant, Industrial Logic
-------------------------------------
http://www.industriallogic.com/
http://agileinaflash.com/
http://agileotter.blogspot.com/