Bruce Weirdan

Simplified: https://psalm.dev/r/8d4e5c66da

> Maybe you can also test which operations exactly triggered the switch to read-only. Do you have any specific test case in mind? The above is what I figured out...

The action does run `composer install`, however it does it with `--no-scripts` flag.

Definitely not intended: https://github.com/psalm/psalm-github-actions/blob/73f49b6857023123dfc809577888c31f6275afc9/Dockerfile#LL16C1-L16C47

The fix would be somewhere near these lines: https://github.com/psalm/psalm-plugin-phpunit/blob/e344eaaa27871e79c6cb97b9efe52a735f9d1966/src/Hooks/TestCaseHandler.php#L155-L160

Also please add the variant with `#[Test]` into this test case: https://github.com/psalm/psalm-plugin-phpunit/blob/e344eaaa27871e79c6cb97b9efe52a735f9d1966/tests/acceptance/TestCase.feature#L527-L548

@SignpostMarv can you provide a failing scenario, ideally as a Gherkin test ([see here](https://github.com/psalm/phpunit-psalm-plugin/blob/645be844dcdf323efdd42a90c7cd16dbf96cc0cb/tests/acceptance/TestCase.feature#L968))? Your code can be a little overwhelming at times.

Currently the plugin has no idea what `@depends` mean. > Anyone please tell me how to suppress this bug until it gets fixed. Adding `@psalm-suppress TooFewArguments` both in provider or...

Dev notes: > When a test receives input from both a `@dataProvider` method and from one or more tests it `@depends` on, *the arguments from the data provider will come...

> You may try to suppress it via config file. Didn't test it myself, but I think it might work Yep, the following does work: ```cucumber Feature: Suppression In order...