Since quite new the Shadow DOM in HTML5 is not supported by Test Studio. In order to reproduce, load the website from the internal description in Chrome and try recording against the login form.
Please add a submenu to the 'Run to Here' which allows you to select the browser to be used instead of the default specified. The only way to select a different browser for 'Run to Here' is to go into 'Project settings -> Browsers' and remove the default browser.
A few applications, both web and WPF sense which Windows user is currently logged on and behave differently (different permissions) based on that user. It would help if, at the time of test execution, especially remotely, if you can specify which user to impersonate when running the test.
For a TFS source controlled project, there's no checked status indicator for test lists similar to tests. The user is left wondering if the test list needs to be checked in, or if they have the latest version from source control.
Occasionally a user sets up a data driven test and accidentally doesn't give it any rows of data, or the data source got changed and the data removed from it. Under this scenario the test starts, the browser launches then the browser closes and the test shuts down. The user is left confused why the test didn't do anything. Adding a "Warning 0 rows or data to iterate" would help clear up the cause of the symptom.
Binding should be allowed with a macro enabled workbook. Since more people are familiar with the workings of excel, it might be easier for others to understand sorting with excel rather than filtering with Telerik. This would also allow for more complex data binding than what the filters in Telerik can do.
We should be able to add a verification which verifies that a string is “not exactly”.
Now when you run the test through "Run From Here", "Run to Here" or "Run Selected" it doesn't stop at the break points.
I want to verify that no error notifications have been shown. To do this I use the following find expression: TagName=div,class=~mistro-notification-container,|,TagName=div,class=~mistro-notification,style=!display: none and I set invertCondition to true when I do the wait to see if shown. ActiveBrowser.WaitForElement(htmlFindExpression, 33000, true); The problem is that I have markup with divs that have the following classes and structure: <div .. class="mistro-notification-container... <div .. class="mistro-notification... <div .. class="mistro-notification-subtitile... <div .. class="mistro-notification-message.... And what happens is the find expression class=~mistro-notification actually finds the subtitle as it has no display: none on it. I want to be able to express HasClass like jquery: http://api.jquery.com/hasclass/ as this does exactly what I need, and will not detect partial class names? I have a workaround for this now... I just added some additional clauses to filter out those other classes. TagName=div,class=~mistro-notification-container,class=!mistro-notification-message,class=!mistro-notification-subtitle,|, TagName=div,class=~mistro-notification,style=!display: none However this is not very future proof... as if nested elements get added with additional classes that partially match the one expressed in my htmlfindexpression the test could break. Regards, Scott
When clicking on an existing Test List the popup if by default expanded. It would be nice if its collapsed by default. Or even one checkbox to expand/collapse everything. In addition to this an search field could also be handy.
If a users used Windows Explorer to move test around to different folders, they end up with broken parent tests, tests that cannot find the child test. The only way to discover which ones are broken is to execute the test. It would be convenient if there was a way for Test Studio to scan the project and report back on missing/broken links to subtests.
I have a databound test that tests a website for setting the correct language. This means I have alot of strings as data in my local dataset as I have to test a lot of elements on the website for exact language matches. Apparently I have stumbled upon a limit of max 50. Could this be increased? Alternatively I have to export data to xls or xml. regards
Currently the Search/Expression input box on the DOM Explorer is tiny, and does not re-size with the form. This is painful, as to see what is going on I need to copy the expression out into notepad, and then cut a piece out and then paste it back in etc... It would be ideal if this was changed to a re-sizable TextArea. It would save a lot of time. Regards, Scott
Currently in the error log it has the FindExpression used, which is great. However the format it is in is as follows: [id 'Exact' AddEditFormat-AddEditDisplayColumnsInFormat-Form] AND [TagName 'Exact' div] THEN UNDER NODE FIND [data-for 'Exact' Column Title] AND [style 'Contains' display: bock] AND [TagName 'Exact' h4][class 'Contains' mistro-form-invalid] AND [TagName 'Exact' div] AND [TextContent 'Exact' Column Title is required] To do any sort of debugging using the DOM Explorer I then have to convert this to: TagName=div,id=AddEditFormat-AddEditDisplayColumnsInFormat-Form,|,data-for=Column Title,style=~display: bock,TagName=h4,class=~mistro-form-invalid,TagName=div,TextContent=Column Title is required I would save a lot of time, if the error long just gave me the FindExpression in this format as well. Then I can just copy and past it into the DOM Explorer and start cutting sections out of it to see where I have gone wrong. Regards, Scott
From ticket 866800 Visual Studio has a feature to track/highlight the active document in Solution Explorer - see attached screen shot. It would be helpful if Test Studio had an equivalent feature where the currently active test becomes highlighted in the Project pane.
It would be nice to be able to find elements based on whether or not the element is visible, using the inline visibility property, or the inline Display property, or the CSS property. This matches what jQuery can do today: $('#testSpan2:visible') The above tests all possible combinations and returns a value based on whether or not the target element is visible. From ticket 865800
There isn't an easy way to see what the image verification is going to check. The Storyboard is a way to see, but does not consistently show across my projects. The Export is another way to do it but that takes me out of the test studio. this item is similar to the feedback item. http://feedback.telerik.com/Project/161/Feedback/Details/126406-need-easier-method-to-update-image-verifications
Need to be able to export test cases and test steps so we can document and produce a written test plan for the client that would like to test manually. would be great to have it can be exported to an Excel, CSV, Word or else, so on each row we can add extra columns such as the sign-off or the test result.
Many CI systems build the application to be tested in a workspace i.e. a unique folder. Test Studio is incompatible with this environment since you are forced to configure the full hardcoded path to the application before running the test. There is no mechanism provided to specify an alternate path from the command line at test execution time, similar to the BaseUrl setting that Web tests support.