Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 29 Apr 2014 06:52 by ADMIN
Nick
Created on: 09 Mar 2014 21:01
Type: Bug Report
1
Additions or changes to elements not saved if not used in current test
Using VS2012 and TS 2013.2.1327.0, changes to the element explorer (whether it's adding additional elements or changing properties of an existing element) are not retained if the new/changed element is not used in a test.  This is a critical issue with the plugin and has wasted many hours of our time building an Element repository that just gets erased after the project is closed/re-opened.

Steps to reproduce:
1. Create a new project
2. Open a new test
3. Click Record
4. Navigate to subject site
5. Without recording any steps, turn on highlighting and add a few page objects to the Element Explorer
6. Save the project, close and reopen VS
7. Note that none of the objects were retained.
8. Repeat steps 3 & 4
9. Record a step
10. Add additional elements after recording a step
11. Save and close then re-open the project
12. Note that the additional elements were retained
13. Now add additional elements without recording anything, then save/re-open
14. Note that the additional elements were not retained because none of the elements were used in the test
8 comments
ADMIN
Iliyan Panchev
Posted on: 29 Apr 2014 06:52 
Hey Nick. We released an internal build yesterday. This is the latest official release 2014.1.410 plus all bug fixes and development that we applied after it. The fix that you are interested in is also there. Have in mind that this build is not fully tested. 
You can download the build from your account in telerik.com, as well as from the Test Studio update notification. You need to choose in Project -> Settings -> Installation and Updates -> Notify me on any updates option and then run Update from the Help tab.
Nick
Posted on: 25 Apr 2014 13:44 
That is great news.  How will I know which update the fix will be in?  I'd be willing to install an early release/beta and let you know if it fixes my issue.
ADMIN
Iliyan Panchev
Posted on: 25 Apr 2014 13:31 
Thanks Nick, I am able to reproduce your problem with Test Studio 2013.2.1327. This is a bug that is actually fixed. The fix will be part of the upcoming Test Studio minor and major releases.
Nick
Posted on: 25 Apr 2014 12:57 
Not typically.  I call a common test to login all my other tests, so usually I would launch the browser/recorder, pause the recording, navigate to the point in my site where I need to add additional elements, then add those using the methods mentioned earlier.
ADMIN
Iliyan Panchev
Posted on: 25 Apr 2014 12:49 
In the steps to reproduce you say that you don't record any step. So, do you pause the recorder before you navigate to your test site? Because if you don't pause it, you should have at least a navigate step recorded.
Nick
Posted on: 25 Apr 2014 12:29 
Yes, IE10.  I experience the issue when enabling Highlight then clicking the blue button on each object and selecting "Add to Element Repository" and when dragging highlighted object to the pop out "Add to Element Repository" menu node on the left side of the screen.
ADMIN
Iliyan Panchev
Posted on: 25 Apr 2014 12:21 
Hi Nick, do you still experience this problem? If yes, with which browser do you reproduce the issue? And if it is in Chrome or Firefox, do you use the Recorder navigation field on bottom of the window, or you are using the standard browser navigation field?
Nick
Posted on: 10 Mar 2014 00:11 
I've discovered a workaround.  The workaround is that if I record a step after making any changes to the element repository, then saving that recorded step will in turn save the changes to the element repository.  This is not an acceptable workaround as it's unnecessary and very easy to lose/corrupt tests and test/element data, but it will do for the time being.  I hope that a better solution/fix is in the near future as adding elements prior to scripting is a use case that should have been considered when implementing this tool.  I've never worked for a company that didn't add elements manually prior to scripting(so that a proper naming convention can be applied to each element), so the fact that this cannot do this out of the box is disappointing.
Create an account Log In
View
Type
Status