Easy testing for traits

[davedevelopment]

Thought I'd have a crack at this to see what it looked like, a few people have whined about it in #200. It's not really what I'd consider a responsibility of a test double framework, but we have the tools to do it...

<?php

require "vendor/autoload.php";

Mockery::globalHelpers();

trait Foo {
    function foo() {
        return $this->doFoo();
    }

    abstract function doFoo();
}

$mock = mock(Foo::class);
$mock->allows()->doFoo()->andReturns('wooop');

var_dump($mock->foo());

• Tests
• Docs
• Changelog

[robertbasic]

It's been a while since I last looked at mockery's internals, but shouldn't you call isTrait here? If not, why do we need the isTrait method? I don't see it called anywhere.

[davedevelopment]

It doesn't need calling there and therefore you are right, we don't need it for this implementation. I put it in there thinking I would, will back it out.

[davedevelopment]

I don't think this has any bearing on this functionality, but maybe someone else might think of something, there is an RFC currently under discussion to bring interfaces to traits - https://wiki.php.net/rfc/traits-with-interfaces.

[coveralls]

Coverage increased (+0.9%) to 78.075% when pulling 8524260 on davedevelopment:testing-traits into 3c90be8 on padraic:master.