tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TOMEE-1958) Mockito doesn't @MockInjector to be set as container properties
Date Thu, 13 Oct 2016 11:32:20 GMT

     [ https://issues.apache.org/jira/browse/TOMEE-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Romain Manni-Bucau updated TOMEE-1958:
--------------------------------------
    Summary: Mockito doesn't @MockInjector to be set as container properties  (was: Allow
@MockInjector to be placed on test class when using application composer)

> Mockito doesn't @MockInjector to be set as container properties
> ---------------------------------------------------------------
>
>                 Key: TOMEE-1958
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1958
>             Project: TomEE
>          Issue Type: Improvement
>            Reporter: Xavier Dury
>            Priority: Trivial
>
> Currently, when using {{ApplicationComposer}}, {{@MockInjector}} can be declared in two
ways:
> {code}
> public @MockInjector FallbackPropertyInjector injector() {
> 	return new MockitoInjector();
> }
> public @MockInjector Class<? extends FallbackPropertyInjector> injectorClass()
{
> 	return MockitoInjector.class;
> }
> {code}
> As almost everything can now be declared with annotations on the test class ({{@ContainerProperties}}
= {{@Configuration}}, {{@Classes}} ~ {{@Module}}), it would be nice if {{@MockInjector}} could
be too:
> {code}
> @RunWith(ApplicationComposer.class)
> @MockInjector(MockitoInjector.class)
> @Classes(...)
> public class MyTest {...}
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message