Allowed mocking __clone method

[Bilge]

There does not seem to be any compelling reason why void magic methods such __construct, __destruct or __clone should not be mockable. However, this PR only seeks to add __clone support.

As a bonus, added test namespace (MockeryTest) to Composer autoloader to save manually including test fixtures (and other test files) in tests.

Resolves #669.

[davedevelopment]

As mentioned on IRC in regards to BC, anyone currently cloning a Mockery mock would have to fix up their tests:

<?php

require "vendor/autoload.php";

class Foo {
    function __clone() {}
}

$double = Mockery::mock(Foo::class);

$second = clone ($double);
// PHP Fatal error:  Uncaught BadMethodCallException: Received Mockery_0_Foo::__clone(), but no expectations were specified in /Users/davem/src/mockery/library/Mockery/Loader/EvalLoader.php(34) : eval()'d code:774

You mentioned __destruct, doing the same for __destruct would have a similar behaviour. Any mock that mocks a type that defines __destruct would have to have a $mock->shouldReceive('__destruct') somewhere.

[patzerr]

hi,
@davedevelopment
the possibility to mock __construct on overloaded classes without breaking other unittests is possible, see the changes in library/Mockery/Mock.php::_mockery_constructorCalled in Pull Request #781
I guess doing the same for __cone could be done in the same way