Make testing easier by adding a disable() method

[LaurentEsc]

This PR is related to issue #39 and is a suggestion to allow easy Validator mocking:

HoneypotValidator::shouldReceive('validateHoneytime')
    ->once()
    ->andReturn(true);

I have updated the documentation.

[LaurentEsc]

Moving the HoneypotFacade to another namespace is a breaking change, probably not the best idea ...

[garygreen]

To be honest I think at this point it would make sense to just get rid of the HoneypotValidator.php and move those 3 functions into Honeypot.php and update the tests. That way there isn't a need for two facades which seems overcomplicated imo.

[garygreen]

Also I think I would prefer to see something like Honeypot::enable() and Honeypot::disable() as oppose to the suggestion of mocking the validator functions.

[LaurentEsc]

Something like this ? I also like Honeypot::disable() for testing.

[garygreen]

Looks good to me. Tests pass?

[garygreen]

Once updated I would suggest to squash the commits.

[LaurentEsc]

The problem with using Class@Method instead of a closure is that is creates a new instance to validate, so disable() doesn't work.

[garygreen]

Gotcha. I'm pretty sure the validator resolves the class thru the IOC so in theory if you did honeypot@method it should work.

[LaurentEsc]

Indeed, seems to work.

[LaurentEsc]

Tests didn't pass after I cloned:

1) Msurguy\Tests\HoneypotTest::test_get_honeypot_form_html BadMethodCallException: Method Mockery_0_Msurguy_Honeypot_Honeypot::getFormHTML() does not exist on this mock object

[garygreen]

It should be generate, tests prob has been failing on that for a while.

[LaurentEsc]

Documentation updated and commits squashed.

[garygreen]

Looks good. :+1: