x: +49 441 - 4082-111
> > arne.limb...@openknowledge.de
> > www.openknowledge.de<http://www.openknowledge.de<http://www.openknowledge.de<http://www.openknowledge.de>>
> > <
> https://www.openknowledge.de/>
> >
> > Registergericht: Amtsgericht Oldenbur
de/event/>
>
>
>
>
>
> ____________
> Von: Arne Limburg
> Gesendet: Mittwoch, 15. Juli 2020 09:09
> An: dev@openwebbeans.apache.org
> Betreff: AW: Mock bean feature for meecrowave
>
> OK,
>
> I see your point and discussed this with Mark at monday
urg
Gesendet: Mittwoch, 15. Juli 2020 09:09
An: dev@openwebbeans.apache.org
Betreff: AW: Mock bean feature for meecrowave
OK,
I see your point and discussed this with Mark at monday evening. I'll code an
example to discuss the different cases. Then we can see what to include into
Meecrow
OK,
I see your point and discussed this with Mark at monday evening. I'll code an
example to discuss the different cases. Then we can see what to include into
Meecrowave or OWB Test. So I don't think, we'll put anything of that in the
next release.
I have found one minor issue I'll report and
Hi,
I just had a call with Mark and we discussed solutions for the mono flavor. We
came up with the following idea:
In an extension we collect all types to mock (we get all the testclasses via
ProcessAnnotatedType) and later in ProcessInjectionPoint we add an @Mock
qualifier to any injection
Hi Romain,
I don't understand your case 2.a. Even for mono flavor I would like to define
per test, which bean to mock and for which bean to take the real instance. I
have no idea how to do this with a simple extension.
For 2.b. an extension that is registered per class sounds reasonable. I'll
