Show more information for bad mock() invocations

Open
  • Is something wrong?
#271 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
testing

Research direction

Start by locating the mock() handling that produces the message “getDefaultOptions() does not have an associated action - consider a niceMock()?”. Read nearby tests and error-reporting code to determine what invocation context is available. Done means the failure output includes useful context such as the class name and defined rules, with tests covering the expanded message.

Written by the indexing model from the issue text.

Description

Component: Mocking Size: 1 (Small) Type: Improvement

Currently it shows:

getDefaultOptions() does not have an associated action - consider a niceMock()?

But it could include more information like the class name, rules that are defined, etc.

Dominant language
PHP
Stars
45
Forks
3
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elliotchance/concise

All issues in elliotchance/concise

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.