> -Original Message-
> From: talk-boun...@lists.nyphp.org [mailto:talk-boun...@lists.nyphp.org] On
> Behalf Of Gary A. Mort
> Sent: Friday, November 15, 2013 6:23 PM
> To: talk@lists.nyphp.org
> Subject: Re: [nyphp-talk] Why do unit tests not inherit?
>
> On 11/15/2013 10:58 AM, Robert
On 11/15/2013 10:58 AM, Robert Stoll wrote:
I even think it is ok to have some degree of code duplication in test
classes just to make the test case very obvious. Each test case should
ideally just cover one aspect (method) and if you start having a lot
of test cases for just one method, then y
The primary reason that you don't see projects using inheritance like that
is that it's not actually good OO design to do so. And the fact that you
can't design the tests the same way as the classes just further reinforce
the fact that the abstractions are wrong.
Check out this video where I talk
> -Original Message-
> From: talk-boun...@lists.nyphp.org [mailto:talk-boun...@lists.nyphp.org]
> On Behalf Of Michael Hernandez
> Sent: Friday, November 15, 2013 4:43 PM
> To: NYPHP Talk
> Subject: Re: [nyphp-talk] Why do unit tests not inherit?
>
> On Nov 15, 2013, at 10:26 AM, "Gary A.
On Nov 15, 2013, at 10:26 AM, "Gary A. Mort" wrote:
>
> Is there a reason that most unit tests published for PHP Open Source projects
> do not use OOP programming?
>
> --
> Class Pets
> Class Dogs extends Pets
> Class Cats extends Pets
>
>
> Unit tests written for those classes generally are
Is there a reason that most unit tests published for PHP Open Source
projects do not use OOP programming?
--
Class Pets
Class Dogs extends Pets
Class Cats extends Pets
Unit tests written for those classes generally are defined like
Class TestPets extends TestCase
Class TestDogs extends TestCas
