Won't Fix
Last Updated: 30 Apr 2015 05:50 by ADMIN
Created on: 25 Nov 2014 20:08
Type: Bug Report
Value for UseQuery not saved in specific customer project
The value for UseQuery in a FrameInfo is always set. You clear it, save changes only to find it's turned back on. Test Studio is not persisting the change to disk.

Attached to the internal problem report will be a link to the project as well as a link to a 5 minute video demonstrating the problem.
1 comment
Daniel Djambov
Posted on: 30 Apr 2015 05:49
Telerik: This is how currently Test Studio merge logic works. Changing the frame property you get it merged to another one on next load. Whether it will come with the right property value depends on which test is loaded first. Our frame here is in use by WebTest(1) which is down in the list and so the other frame comes first, ours get merged and loses its name as well as UseQuery. 

Changing the merge logic will result in breaking change for coded tests of existing customers.

As a work-around (and to confirm the root of the issue) If you rename WebTest(1) to aaWebTest(1) - on reload the frame is persisted, however other frame elements are added too (expected).

We have a Feature Request to rework this logic and you can track it from here: http://feedback.telerik.com/Project/161/Feedback/Details/123628-elements-page-merging-mechanism-should-not-depend-on-the-order-of-tests