[224] Exception in TestFixtureSetUp is never printed out to output window

It prints only the following instead of full stacktrace underneath TargetInvocationException

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at JetBrains.ReSharper.UnitTestSupport.PluginInterface.UnitUtil.InvokeUserCode(MethodInfo method, Object instance) in c:\TEMP\tmp4843.tmp\src\UnitTestSupport\src\PluginInterface\UnitUtil.cs:line 232
at JetBrains.ReSharper.UnitTestSupport.NUnit.NUnitFixture.Run(MethodInfo[] methodsToRun, Boolean[] explicitFlags) in c:\TEMP\tmp4843.tmp\src\UnitTestSupport.NUnit\src\NUnitFixture.cs:line 298

3 comments
Comment actions Permalink

Please could you send the small example showing this problem?

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Nat" <no_mail@jetbrains.com> wrote in message
news:28803959.1142382249575.JavaMail.itn@is.intellij.net...

It prints only the following instead of full stacktrace underneath
TargetInvocationException

>

System.Reflection.TargetInvocationException: Exception has been thrown by
the target of an invocation.
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at
JetBrains.ReSharper.UnitTestSupport.PluginInterface.UnitUtil.InvokeUserCode(MethodInfo
method, Object instance) in
c:\TEMP\tmp4843.tmp\src\UnitTestSupport\src\PluginInterface\UnitUtil.cs:line
232
at JetBrains.ReSharper.UnitTestSupport.NUnit.NUnitFixture.Run(MethodInfo[]
methodsToRun, Boolean[] explicitFlags) in
c:\TEMP\tmp4843.tmp\src\UnitTestSupport.NUnit\src\NUnitFixture.cs:line 298



0
Comment actions Permalink

Hello Eugene,

Try to write a unit test fixture that has textfixturesetup method throws
an exception.

Nat

Please could you send the small example showing this problem?



0
Comment actions Permalink

Good call. I've seen this, too, but forgot to bug it.

"Nat" <no_mail@jetbrains.com> wrote in message
news:28803959.1142382249575.JavaMail.itn@is.intellij.net...

It prints only the following instead of full stacktrace underneath
TargetInvocationException

>

System.Reflection.TargetInvocationException: Exception has been thrown by
the target of an invocation.
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at
JetBrains.ReSharper.UnitTestSupport.PluginInterface.UnitUtil.InvokeUserCode(MethodInfo
method, Object instance) in
c:\TEMP\tmp4843.tmp\src\UnitTestSupport\src\PluginInterface\UnitUtil.cs:line
232
at JetBrains.ReSharper.UnitTestSupport.NUnit.NUnitFixture.Run(MethodInfo[]
methodsToRun, Boolean[] explicitFlags) in
c:\TEMP\tmp4843.tmp\src\UnitTestSupport.NUnit\src\NUnitFixture.cs:line 298



0

Please sign in to leave a comment.