I am using the latest internal build do to the issue with edits to elements or test cases not propagating in Test Lists. A new issue has crept up for us when working with frames.
In order for our tests to run in our various environments and to get around framebox IDs we edit the properties of the framebox. We typically remove the frame name and add a "~" to the href as our base URL changes slightly depending on which environment (DEV,QA,Stage,Prod). This works great we can run it in all environments as well as across our different clients personalized URLs without having to keep a bunch of one off test cases.
The issue I am experiencing is when I make these edits to the properties they do not stick even if I save the project before I try to run it again. I have found that I can make my changes and then save it but I have to refresh the entire element library in order for my edits to take hold. We have a large element library so it takes time to refresh before we can confirm if the modification to the test worked. This adds to much overhead having to refresh and wait and hope it works so we dont have to try again. There are also times when doing these edits crashes the entire Studio and we have to restart which is very frustration for anyone.
Has anyone experianced this? Is there a workaround that is possible?
In order for our tests to run in our various environments and to get around framebox IDs we edit the properties of the framebox. We typically remove the frame name and add a "~" to the href as our base URL changes slightly depending on which environment (DEV,QA,Stage,Prod). This works great we can run it in all environments as well as across our different clients personalized URLs without having to keep a bunch of one off test cases.
The issue I am experiencing is when I make these edits to the properties they do not stick even if I save the project before I try to run it again. I have found that I can make my changes and then save it but I have to refresh the entire element library in order for my edits to take hold. We have a large element library so it takes time to refresh before we can confirm if the modification to the test worked. This adds to much overhead having to refresh and wait and hope it works so we dont have to try again. There are also times when doing these edits crashes the entire Studio and we have to restart which is very frustration for anyone.
Has anyone experianced this? Is there a workaround that is possible?
4 Answers, 1 is accepted
0
David
Top achievements
Rank 1
Rank 1
answered on 23 Mar 2014, 10:30 AM
Leonard - I have heard similar issues in previous builds, but latest internal 2013.2.1510 seems to be working for us (so far).
0
Accepted
Hi Leonard, David.
David is absolutely correct - this is a bug that has been addressed recently. You can actually download and try the latest internal build labeled 2013.2.1524 we published today.
Download link Version notes
Regards,
Konstantin Petkov
Telerik
David is absolutely correct - this is a bug that has been addressed recently. You can actually download and try the latest internal build labeled 2013.2.1524 we published today.
Download link Version notes
Regards,
Konstantin Petkov
Telerik
0
LEONARD
Top achievements
Rank 1
Rank 1
answered on 26 Mar 2014, 04:53 PM
Excellent I will update my Test Studio as soon as the scheduled runs for the day are completed. Thanks for the response.
0
LEONARD
Top achievements
Rank 1
Rank 1
answered on 27 Mar 2014, 02:39 PM
Worked thanks.