Using method returnValaueMap with mock objects results in mock object returning null instead of specified mock object.

[christianhueser]

I wonder whether it is correct behaviour in the current phpunit-mock-objects version that a mock object setup with method returnValueMap() for a method returning different mock objects when called with different parameters returns always null instead of the specified mock objects. If I use matcher at() instead of method returnValueMap() and specify the ordering of method calls, everything works just fine and the correct mock objects will be returned.

[sebastianbergmann]

Dear contributor,

let me start by apologizing for not commenting and/or working on the issue you have reported or merging the pull request you have sent sooner.

PHPUnit 5.0 was released today. And today I am closing all open bug reports and pull requests for PHPUnit and its dependencies that I maintain. Please do not interpret the closing of this ticket as an insult or a lack of interest in your problem. I am sorry for any inconvenience this may cause.

If the topic of this ticket is still relevant then please open a new ticket or send a new pull request. If your ticket or pull request is about a defect then please check whether the issue still exists in PHPUnit 4.8 (which will received bug fixes until August 2016). If your ticket or pull request is about a new feature then please port your patch PHPUnit 5.0 before sending a new pull request.

I hope that today's extreme backlog grooming will allow me to respond to bug reports and pull requests in a more timely manner in the future.

Thank you for your understanding,
Sebastian