unsatisfied expectation terminates suite
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start at the place where Mockery::close() is called and inspect how Mockery\Exception failures propagate through the Codeception module. Check the behavior of Codeception\Module::fail() and identify how the current test can fail without terminating the suite; done means one failed test does not stop the remaining suite.
Written by the indexing model from the issue text.
Description
When mockery expectations fail, the currently running suite terminates because of exception thrown. I think the good solution would be to catch Mockery\Exception\* and fail the current test only.
Tell me how to fail the current test from the place where Mockery::close() is called and I'll prepare a pull request. \Codeception\Module::fail() terminates the suite completely?
- Dominant language
- PHP
- Stars
- 34
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Codeception/MockeryModule
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Codeception/MockeryModule#23 ·
All issues in Codeception/MockeryModule
Similar issues
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·
-
needs-triage Platform(Default)
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
HttpClient
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
symfony/symfony-docs#23092 ·
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 95/100