August 28, 2015
Experience Faster SOAP Apps in TestTrack 2015.1
Good news for TestTrack SDK developers...and your users! Starting with TestTrack 2015.1, you will experience faster performance from your SOAP applications. Depending on the call and amount of data returned, you may see SOAP operations yield a 10-50% performance improvement. Why? We upgraded the gSOAP toolkit used with the SDK. This also means the SDK now complies with the SOAP 1.2 standard. There is one tiny caveat. The new gSOAP version has stronger restrictions on data types than previous versions. If your code does not comply with the data type standards, you may see errors returned from your SOAP applications after upgrading to TestTrack 2015.1.Email sign up
What does this mean to you?The short story—You should test your applications in a test environment and make any required code changes before upgrading your production environment to TestTrack 2015.1. This is a good best practice to remember for any upgrade. The full story—If your code does not comply with data type standards, you will see invalid type and missing tag value errors after upgrading. If you use .NET, you are less likely to see these errors because data types are enforced. If you use another language, such as Perl or Python, or build the XML yourself, you may get errors. Following are a few examples of code that return errors. In this example, an error is returned because the specified data type is ‘long’ and the value is a string.
<defectNumber xsi:type="xsd:long">"274"</defectNumber>In this example, an error is returned because the m-pFileData tag value is missing.
<attachmentlist … <item xsi:type="urn:CFileAttachment"> <m-pFileData xsi:type="xsd:base64Binary"></mpFileData> <m-strFileName… </item> </attachmentlist>Again, make sure you test your applications and make any changes before upgrading TestTrack in your production environment. For more information, check out our knowledgebase or TestTrack SDK help.