2013 R1 Beta: possible conversion problem with coded steps when upgrading to 2013?

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Request a Feature Report a Bug

Completed

Last Updated: 23 Aug 2013 14:32 by ADMIN

Craig

Created on: 18 Jul 2013 15:55

Type: Bug Report

2013 R1 Beta: possible conversion problem with coded steps when upgrading to 2013?

i tried loading in an existing project and there seems to be a conversion problem. The scripts run fine in the 2012 version, but in 2013 it is complaining about several coded steps missing directive or assembly reference. The '.tstest.cs' files are identical,  but the '.tstest' files are very different.

Attached Files:

BuildingElements.png

3 comments

ADMIN

Konstantin Petkov

Posted on: 19 Jul 2013 18:48

Hi,

Please submit a support ticket where you can get assistance and be able to send the project. We definitely need to investigate the issue then will follow up with our findings.

Please also cleanup the application log prior to opening the project and send the generated log as well.

Thanks a lot for your feedback!

Craig

Posted on: 19 Jul 2013 18:35

Hello,
The building elements notification does come up and display, but then goes away. I am still getting the compile problem, though. I restarted my system and just let it sit for two hours before I tried it again, but still received the compile error.

I think you are on to something with the elements not being complete, though. The elements listing in 2013 is noticeably shorter than the 2012 version. I hit refresh (and get the status bar while it is building), but the new list is still missing entries and I still get the compile errors. Is there a way to check if there was an error building the element list? I can identify some elements that are missing, but the project is far too large to attach.

ADMIN

Konstantin Petkov

Posted on: 19 Jul 2013 07:20

Hi Craig,

First I'm removing the attachment in case you don't want to share the tests publicly.

Your tests ran without compilation errors for me. I only created a new project, imported the tests and ran them - get no compiling issues.

This sounds like a known usability issue we have with the Beta in regards to running a coded test before the elements code generation is completed. With the performance improvements of loading tests initially in 2013.1 one gets the tests loaded faster, however the elements code may keep generating on the background. That usually happens with larger projects especially in case of hundreds and thousands of elements.

To work-around the problem you can:
- Open the project
- Open the test you'd like to run
- Look at the elements explorer - make sure it doesn't keep updating. You should notice the "Building elements" visual progress as in the attached image.

Please let me know if this helps.

Thanks!