[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19889?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-19889:
----------------------------------------
Assignee: Jeff Cantrill (was: Andre Dietisheim)
> Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19889
> URL: https://issues.jboss.org/browse/JBIDE-19889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
>
> I was not cautious enough when merging, the maven build currently fails with the following:
> {code}
> Tests in error:
> LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
> {code}
> {code}
> testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-19889:
----------------------------------------
Summary: Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
Key: JBIDE-19889
URL: https://issues.jboss.org/browse/JBIDE-19889
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Andre Dietisheim
I was not cautious enough when merging, the maven build currently fails with the following:
{code}
Tests in error:
LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
{code}
{code}
testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
Invalid use of argument matchers!
2 matchers expected, 1 recorded:
-> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
This exception may occur if matchers are combined with raw values:
//incorrect:
someMethod(anyObject(), "raw String");
When using matchers, all arguments have to be provided by matchers.
For example:
//correct:
someMethod(anyObject(), eq("String by matcher"));
For more info see javadoc for Matchers class.
at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
Invalid use of argument matchers!
2 matchers expected, 1 recorded:
-> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
This exception may occur if matchers are combined with raw values:
//incorrect:
someMethod(anyObject(), "raw String");
When using matchers, all arguments have to be provided by matchers.
For example:
//correct:
someMethod(anyObject(), eq("String by matcher"));
For more info see javadoc for Matchers class.
at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
Invalid use of argument matchers!
2 matchers expected, 1 recorded:
-> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
This exception may occur if matchers are combined with raw values:
//incorrect:
someMethod(anyObject(), "raw String");
When using matchers, all arguments have to be provided by matchers.
For example:
//correct:
someMethod(anyObject(), eq("String by matcher"));
For more info see javadoc for Matchers class.
at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (JBIDE-19889) Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19889?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-19889:
----------------------------------------
Assignee: Andre Dietisheim
> Build became unstable: LazyCredentialsPrompterTest complains about wrong Matcher usage
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19889
> URL: https://issues.jboss.org/browse/JBIDE-19889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
>
> I was not cautious enough when merging, the maven build currently fails with the following:
> {code}
> Tests in error:
> LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter:65 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter:84 » InvalidUseOfMatchers
> LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull:75 » InvalidUseOfMatchers
> {code}
> {code}
> testPromptAndAuthenticateWhenInitializedWithAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.004 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateWhenInitializedWithAPrompter(LazyCredentialsPrompterTest.java:65)
> testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateReturnsFalseWhenItCantGetAPrompter(LazyCredentialsPrompterTest.java:84)
> testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest) Time elapsed: 0.001 sec <<< ERROR!
> org.mockito.exceptions.misusing.InvalidUseOfMatchersException:
> Invalid use of argument matchers!
> 2 matchers expected, 1 recorded:
> -> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> This exception may occur if matchers are combined with raw values:
> //incorrect:
> someMethod(anyObject(), "raw String");
> When using matchers, all arguments have to be provided by matchers.
> For example:
> //correct:
> someMethod(anyObject(), eq("String by matcher"));
> For more info see javadoc for Matchers class.
> at org.mockito.exceptions.Reporter.invalidUseOfMatchers(Reporter.java:241)
> at org.mockito.internal.invocation.MatchersBinder.validateMatchers(MatchersBinder.java:35)
> at org.mockito.internal.invocation.MatchersBinder.bindMatchers(MatchersBinder.java:24)
> at org.mockito.internal.handler.MockHandlerImpl.handle(MockHandlerImpl.java:58)
> at org.mockito.internal.handler.NullResultGuardian.handle(NullResultGuardian.java:29)
> at org.mockito.internal.handler.InvocationNotifierHandler.handle(InvocationNotifierHandler.java:38)
> at org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:51)
> at org.jboss.tools.openshift.common.core.ICredentialsPrompter$$EnhancerByMockitoWithCGLIB$$dadcfe44.promptAndAuthenticate(<generated>)
> at org.jboss.tools.openshift.express.test.core.LazyCredentialsPrompterTest.testPromptAndAuthenticateDeferredLoadsAndPromptsWhenInitializedWithNull(LazyCredentialsPrompterTest.java:75)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-610:
------------------------------------
In fact, [~supriya.bharadwaj], I'm surprised the error you encountered is not in the Troubleshooting part of this, as this would possibly be useful for me and other users.
> FeedHenry: Document how to change icon for mobile application
> -------------------------------------------------------------
>
> Key: TOOLSDOC-610
> URL: https://issues.jboss.org/browse/TOOLSDOC-610
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 4.3.0.Final
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Priority: Optional
> Labels: cordova, feedhenry
> Fix For: 4.3.0.Final
>
>
> As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen.
> Also part of a Did You Know? probably.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months
[JBoss JIRA] (TOOLSDOC-610) FeedHenry: Document how to change icon for mobile application
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-610?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-610:
------------------------------------
Added comments to the document and attempted to test, but getting some odd errors. Possibly the same ones Supriya had. In theory, these instructions should work fine. Will test with beta, probably.
> FeedHenry: Document how to change icon for mobile application
> -------------------------------------------------------------
>
> Key: TOOLSDOC-610
> URL: https://issues.jboss.org/browse/TOOLSDOC-610
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 4.3.0.Final
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Priority: Optional
> Labels: cordova, feedhenry
> Fix For: 4.3.0.Final
>
>
> As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen.
> Also part of a Did You Know? probably.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 4 months