Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Mocking public properties gives undefined property error

Open
#77 0 comments 1 reaction 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
devtools, testing

Research direction

No file or test is named. Reproduce the shown Mockery User::class property assignment under PHPStan, then trace how phpstan-mockery handles MockInterface properties. Done means the assignment no longer reports the undefined-property diagnostic, with a regression test covering the example.

Written by the indexing model from the issue text.

Description

When creating a mock and setting a property on the mock, which is the recommended way for mocking public properties, it gives an undefined property error.

$user = Mockery::mock(User::class);
$user->name = "Oliver";
Access to an undefined property Mockery\MockInterface::$name. 

current workaround is to just add the following ignore error

        - '#Access to an undefined property Mockery\\MockInterface::\$.*\.#'
Dominant language
PHP
Stars
109
Forks
25
Avg merge
1h 41m
Merged PRs (30d)
1

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 phpstan/phpstan-mockery

All issues in phpstan/phpstan-mockery

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.