InjectMock does not work on observer method

[mickroll]

Describe the bug
Mocking a bean with @io.quarkus.test.junit.mockito.InjectMock does not work for methods that use @Observes.
Example:
public void onExampleEvent(@Observes ExampleEvent event) {...}
This method is called when ExampleEvent is fired, even if the bean containing this method is mocked by using @InjectMock.
Hint: any other method of the same bean is mocked successfully.

Expected behavior

• observer methods of a mocked bean should not be called when event is fired

Actual behavior

• observer methods of a mocked bean are called when event is fired

To Reproduce
Steps to reproduce the behavior:

1. git clone -b quarkus-observer-mock https://github.com/mickroll/demonstrator.git
2. run mvn clean install

Configuration
none

Screenshots
none

Environment (please complete the following information):

• Output of uname -a or ver: Microsoft Windows [Version 10.0.18363.959]
• Output of java -version: openjdk version "11.0.7" 2020-04-14
• GraalVM version (if different from Java): /
• Quarkus version or git rev: 1.6.1.Final
• Build tool (ie. output of mvnw --version or gradlew --version): Apache Maven 3.6.3

Additional context
the demonstrator was built similar to https://github.com/quarkusio/quarkus-quickstarts/tree/master/getting-started-testing

[geoand]

From @mkouba

I think that this is expected behavior - a bean that declares an observer is not removed and thus will be notified when a relevant event is fired, it's very similar to CDI @Alternatives - the beans are still there but cannot be injected

[famod]

I don't want to repeat the discussion from the zulip chat.
It's just that from a very user centric (not at all spec centric) view, you mock a bean (class). You expect the entire "class" to be mocked. 🤷‍♂️

I'll convert this to an enhancement instead of closing it (via the discussed documentation update PR) because that would look misleading in the next changelog.

[famod]

I'll convert this to an enhancement instead of closing it (via the discussed documentation update PR) because that would look misleading in the next changelog.

It seems I am not allowed to do that. @geoand WDYT?

[geoand]

You mean you can't change labels?

[geoand]

I don't really now what the exact permissions are (I'm not an admin of the repo)

[mkouba]

You expect the entire "class" to be mocked.

@famod I get your point. I think that we could try to temporarily disable all observers declared on mocked beans. I'll do some POC and we'll see how it goes...