Minerva White

A corollary to this is the other line from the same function that does `return reply.continue()`, also resulting in an erroneous call to the next handler in the promise chain.

Yes, this is indeed now resolved, though the test suite is still throwing out a warning as a result of jupiter/simple-mock#22. I'll update the above PR to fix this only.

@Relequestual As a workaround, you can use Wayback Machine to look at the API docs as they were: http://web.archive.org/web/20140701093815/http://mink.behat.org/api/

A use case where this has caused problems for me: [Letsencrypt](https://letsencrypt.org/) SSL certificate issue/renewal via [certbot](https://github.com/certbot/certbot) stores the current valid certificates/keys in the `/etc/letsencrypt/archive` directory and creates symlinks to the...

Added pull request with unit tested change