This is a migrated thread and some comments may be shown as answers.

Upgrade Question:Test Studio 2012.2.1420 to TS 2014.1.410 (possible bug)

2 Answers 21 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
JT
Top achievements
Rank 1
JT asked on 12 May 2014, 02:19 PM
Hi,

I have upgraded from 2012.2.1420 to 2014.1.410 and encountered the following error message:

[05/07 13:56:31,Telerik.TestStudio.exe(12476:8),TestStudio] TestUpgrader.ConvertTestToJson() : Could not load test 'C:\...\...\TestName.aii' for upgrade.
[05/07 13:56:31,Telerik.TestStudio.exe(12476:8),TestStudio] SerializerService.<GetSettings>b__2() : Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
[05/07 13:56:32,Telerik.TestStudio.exe(12476:8),ProjectModel] TestFileHandler.LoadFromDisk() : EXCEPTION! (see below)
     Situation: Unable to load test 'C:\...\...\TestName.aii'
     Outer Exception Type: System.Runtime.Serialization.SerializationException
     Message: Error in line 2 position 69. Element 'http://artoftest.com/schemas/WebAiiDesignCanvas/1.0.0:Step' contains data from a type that maps to the name 'http://schemas.datacontract.org/2004/07/Telerik.WebAii.Design.Translators.Xaml.TreeListView:RadTreeListViewIntegerPropertyVerification'. The deserializer has no knowledge of any type that maps to this name. Consider using a DataContractResolver or add the type corresponding to 'RadTreeListViewIntegerPropertyVerification' to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding it to the list of known types passed to DataContractSerializer.
     HRESULT: 0x8013150C (Official ID (if app.) = COR_E_SERIALIZATION, Error Bit = FAILED, Facility = FACILITY_URT, Code = 5388)
     Call Stack:
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
          at ReadAutomationStepFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString[] , XmlDictionaryString[] )
          at System.Runtime.Serialization.ClassDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
          at ReadAutomationStepListFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString , XmlDictionaryString , CollectionDataContract )
          at System.Runtime.Serialization.CollectionDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Int32 id, RuntimeTypeHandle declaredTypeHandle, String name, String ns)
          at ReadWebAiiTestFromXml(XmlReaderDelegator , XmlObjectSerializerReadContext , XmlDictionaryString[] , XmlDictionaryString[] )
          at System.Runtime.Serialization.ClassDataContract.ReadXmlValue(XmlReaderDelegator xmlReader, XmlObjectSerializerReadContext context)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.ReadDataContractValue(DataContract dataContract, XmlReaderDelegator reader)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)
          at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)
          at System.Runtime.Serialization.DataContractSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
          at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
          at System.Runtime.Serialization.XmlObjectSerializer.ReadObject(XmlDictionaryReader reader)
          at ArtOfTest.WebAii.Design.ProjectModel.TestFileHandler.LoadFromXml(String normalizedPath)
          at ArtOfTest.WebAii.Design.ProjectModel.TestFileHandler.LoadFromDisk(String pathToFile, Boolean autoLoadTypes, FileOpenResult& result) 

Once I started looking at all of the tests that failed during the upgrade I found the common recorded step that was causing the issue:
radtreelistview(EncNavigationTreeRadtreelistview): root item count 'Equal' '0'.

***I am wondering if this is a bug or if this item is no longer valid and the upgrade is supposed to fail with the above message.












2 Answers, 1 is accepted

Sort by
0
Konstantin Petkov
Telerik team
answered on 13 May 2014, 06:39 AM
Hi JT,

It looks like that test ("TestName.aii") includes a verification step operating against the RadTreeListView component. There has been major rework of this component handling since the API was outdated (the component has been changed years ago). Despite that the test seems to use such a step getting it broken with the new version of Test Studio.

Can you send the test for us to look at please? You can submit private support ticket, just make sure to refer to this thread. We will fix the test manually and send it back to you to run with the latest releases.

I'm sorry for the caused inconvenience and thank you for the understanding!

Regards,
Konstantin Petkov
Telerik
 
The New Release of Telerik Test Studio Is Here! Download, install,
and send us your feedback!
0
JT
Top achievements
Rank 1
answered on 16 May 2014, 03:59 PM
Thank you for the reply Konstantin!
Fortunately we had a small number of tests that contained this verification step and I manually removed them from each test. 

This issue is now resolved. 
Tags
General Discussions
Asked by
JT
Top achievements
Rank 1
Answers by
Konstantin Petkov
Telerik team
JT
Top achievements
Rank 1
Share this question
or