locked
VS Integration Tests [VS2013] fails on new created VSPackage Project RRS feed

  • Question

  • Hi All,

    I noticed that the normal VS instance is launched for integration tests in VS2013, in VS2010 it launchs Exp Hive.

    Since the package is deployed to exp hive, some test fails even on the new created projects.

    You can repro this by creating a new VS package project and includes Integration Tests. Build and run the test, the normal hive starts and 4 cases failed, for example:

    Test Name: PackageLoadTest
    Test FullName: VSPackage6_IntegrationTests.PackageTest.PackageLoadTest
    Test Source: c:\Users\admin\Documents\Visual Studio 2013\Projects\VSPackage6\VSPackage6\VSPackage6_IntegrationTests\PackageTest.cs : line 42
    Test Outcome: Failed
    Test Duration: 0:00:00.0056127

    Result Message: Assert.IsTrue failed.
    Result StackTrace: 
    at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
       at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
       at System.Windows.Forms.Control.Invoke(Delegate method)
       at Microsoft.VSSDK.Tools.VsIdeTesting.UIThreadInvoker.Invoke(Delegate method) in f:\dd\VSSDK\VSIntegration\Tools\src\IDEHostAdapter\Framework\UIThreadInvoker.cs:line 44
       at VSPackage6_IntegrationTests.PackageTest.PackageLoadTest() in c:\Users\admin\Documents\Visual Studio 2013\Projects\VSPackage6\VSPackage6\VSPackage6_IntegrationTests\PackageTest.cs:line 43

     Also, when I want to set break point to debug the test case, I find it will never be hit.

    Could you let me know how to adjust target VS to Exp Hive on VS2013 and what's wrong for the debugger? (I'm using update 1 preview)

    Regards,

    YI


    MSC on Computer Science (Parallel algorithm)

    Thursday, January 16, 2014 9:18 AM

Answers

All replies