Execute Test as Step displays error

2 posts, 0 answers
  1. Tyson McCall
    Tyson McCall avatar
    6 posts
    Member since:
    Apr 2010

    Posted 07 Jan 2011 Link to this post

    I recently upgraded to WebUI Dev 2010_3_1213 release.  When I try to execute a test which has a 'Test as Step' within the steps the test doesn't execute.  

    Test Log:
    '1/7/2011 12:23:11 PM' - Starting execution....
    '1/7/2011 12:23:12 PM' - Failure detected during execution. Details:
    '1/7/2011 12:23:12 PM' - System.InvalidOperationException: Type 'ArtOfTest.WebAii.Core.FrameInfo' cannot be added to list of known types since another type 'ArtOfTest.WebAii.Core.FrameInfo' with the same data contract name 'http://schemas.datacontract.org/2004/07/ArtOfTest.WebAii.Core:FrameInfo' is already present. If there are different collections of a particular type - for example, List<Test> and Test[], they cannot both be added as known types.  Consider specifying only one of these types for addition to the known types list.
       at ArtOfTest.WebAii.Design.ProjectModel.Project.LoadTest(String filePath)
       at ArtOfTest.WebAii.Design.Execution.ExecutionUtils.TestRequiresSilverlight(Test test, String deploymentFolder, ExecutionType exeType)
       at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(Test test, Settings settings, String deploymentFolder, ExecutionType exeType, Int32 lastStepIndex, DebuggerOptions debuggerOptions)
    '1/7/2011 12:23:12 PM' - Test completed!

    NOTE: If I toggle the 'test as step' off, the test executes fine.  

    I would like to include other test as steps. Is there a solution for this?  

  2. Keaegan
    Keaegan avatar
    126 posts

    Posted 12 Jan 2011 Link to this post

    Hi Tyson McCall,

    The most common reason we see for this type of issue is that you have two instances of ArtOfTest.WebAii installed in your GAC (C:\Windows\Assembly), and you are also using a 3rd party/custom assembly that is targeting the Older version of ArtOfTest.WebAii, whereas the project is trying to use the newest version of the assembly. This would most likely be in-between the two tests that are referenced in the ticket (the test, and the one targeted as a test as step). Look in both of these for an item that would cause this type of conflict.

    If you cannot locate the cause, would you be able to provide a copy of this solution within a private dropbox folder (so others can't see the solution, just you and us here at Telerik) for us to take a look at? This would be so we could assist with isolating the issue to a specific test step (within the test that cannot execute as a step).

    Kind regards,
    the Telerik team
    Interested in Agile Testing? Check out Telerik TV for a recording of Automated Testing in the Agile Environment
Back to Top