Re: Death to Foo and Bar

The concept is to use test classes with common relationships and attributes.
Foo/Bar or A/B don't have known properties, relationships etc. Perhaps there
is good reason to use Foo/Bar or A/B but it seems just as easy to the
original developer and much easier to future developers to use classes with
known relationships.

Maybe this is silly and I should just keep quiet. ;)




On Tue, Aug 5, 2008 at 8:35 PM, Fabio Maulo <[email protected]> wrote:

> I don't understand the concept.
>
> Many times I like write tests using classes like A and B and use my mind to
> solve the bug instead think about a business application.
> If a user send a real case I use it.
> --
> Fabio Maulo
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Nhibernate-development mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nhibernate-development
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Nhibernate-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nhibernate-development