cannot run test with SpecExplorer + VS2010 + Windows 8

Locked cannot run test with SpecExplorer + VS2010 + Windows 8

  • martedì 24 luglio 2012 07:11
     
     

    Tried old and new version of SpecExplorer. Same behavior

    No problem on Win7.

    To repro it, very simple,

    Create a empty spec explorer project and generate testsuit.

    build successfully and run the test suit. Get the following errors.

    A first chance exception of type 'System.Runtime.Remoting.RemotingException' occurred in mscorlib.dll

    E, 3616, 9, 2012/07/24, 00:06:20.456, MyTEST_Machine\QTAgent32.exe, AgentObject.OnBackgroundSendTestMessage: Connection to controller was lost. System.Runtime.Remoting.RemotingException: The argument type 'Run {067a9cc0-e2a5-49fc-af5b-31ac21d2bc25}, Test {5d940a16-bf51-4e44-a1fa-461b28496795}: Started' cannot be converted into parameter type 'Microsoft.VisualStudio.TestTools.Common.TestMessage'. ---> System.InvalidCastException: Object must implement IConvertible.

       at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)

       at System.Runtime.Remoting.Messaging.Message.CoerceArg(Object value, Type pt)

       --- End of inner exception stack trace ---

    Server stack trace:

       at System.Runtime.Remoting.Messaging.Message.CoerceArg(Object value, Type pt)

       at System.Runtime.Remoting.Messaging.Message.CoerceArgs(MethodBase mb, Object[] args, ParameterInfo[] pi)

       at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]:

       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

       at Microsoft.VisualStudio.TestTools.Controller.IControllerCallback.AgentEvent(String agentName, TestMessage message)

       at Microsoft.VisualStudio.TestTools.Agent.AgentObject.<>c__DisplayClass14.<OnSendTestMessage>b__12()

       at Microsoft.VisualStudio.TestTools.Execution.ExecutionUtilities.InvokeController(Action invokeController, String caller, Boolean& connectionLost)

    'QTAgent32.exe' (Managed (v4.0.30319)): Loaded 'c:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.VisualStudio.Enterprise.AspNetHelper.dll'

    'QTAgent32.exe' (Managed (v4.0.30319)): Loaded 'c:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.VisualStudio.TeamSystem.Licensing.dll'

    V, 3616, 13, 2012/07/24, 00:06:20.930, MyTEST_Machine\QTAgent32.exe, Tracing starting up. Stopwatch frequency is 2597649

    'QTAgent32.exe' (Managed (v4.0.30319)): Loaded 'c:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.VisualStudio.QualityTools.NicServices.dll'

    'QTAgent32.exe' (Managed (v4.0.30319)): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll'

    The thread 'Agent: adapter run thread for test 'AccumulatorTestSuiteS0' with id '5d940a16-bf51-4e44-a1fa-461b28496795'' (0x17e4) has exited with code 0 (0x0).

    The thread 'ExecutionUtilities.InvokeWithTimeout helper thread 'Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestAdapter.AbortTestRun'' (0x1778) has exited with code 0 (0x0).

    The thread 'Agent: state execution thread for test 'AccumulatorTestSuiteS0' with id '5d940a16-bf51-4e44-a1fa-461b28496795'' (0x17b4) has exited with code 0 (0x0).

    The thread 'Agent: test queue thread' (0x1a8c) has exited with code 0 (0x0).

    W, 3616, 8, 2012/07/24, 00:06:21.076, MyTEST_Machine\QTAgent32.exe, AgentObject.AgentStateWaiting: Proceeding to clean up data collectors since connection to controller is lost

    The thread 'Agent: heartbeat thread' (0xe4c) has exited with code 0 (0x0).

    The thread '<No Name>' (0x18b4) has exited with code 0 (0x0).

    The thread '<No Name>' (0x1690) has exited with code 0 (0x0).

    The thread '<No Name>' (0xcc0) has exited with code 0 (0x0).

    The thread '<No Name>' (0x1e0c) has exited with code 0 (0x0).


    Great Wall