Currently Test Studio keeps the entire TFS connection settings in the projects settings.aiis file. This creates a problem when trying to work on the same project at two locations in which the URL to connect to TFS is different e.g. one URL to use for Intranet and another URL to use for Internet. To handle this situation the source path should be kept in the settings.aiis file, and some sort of server reference, but the URL to TFS should be outside the settings.aiis file, use a link or reference somehow. Similar to how Visual Studio accomplishes this.
When you export to Excel from the steps detailed view (see attached screen shot) the steps timing information is not included, only the step result and failure details (if any) - see attached Excel file for an example. It would be nice to have timing information included.
It would be nice to be able to look for an exact URL match where the WebAii comparison methods behind the scenes can be told to ignore any query string on the URL it sees in the browser. This way, when on a page with an URL of "something/go" and you perform an action that changes the page to "something/goTo?Id=23" the WaitForPage could be told to look for an exact match on "something/goTo" and not prematurely say it sees the correct page, because you had to look for a partial match because of the query string.
It's nice that you can configure Scheduling Server to send emails, but there's no way to test the email settings. Please add a Send Test Email button to the email configuration dialog, similar to that shown in the attached screen shot.
It would be great if there was the ability to change the database connection strings when scheduling tests, similar to the way the base URL can be changed. We have multiple test environments and multiple databases so the ability to change our connection strings to match our test environments would be such a benefit :)
With Find Logic for an element, sometimes the Find Logic uses Text Content on initial element recording and other times the Find Logic uses ID. I request for functionality in Test Studio to prioritize what logic is actually used in the Find Logic. Generally speaking on the applications I have used Test Studio to automate testing, there are elements that has specific text content on a page. These elements start out with their Find Logic to have TextContent since I think that is the most unique identifier about them. But as TextContent is concerned, there is a possibility of change of text on that element. So I would target the element with the ID of the element or the ID of a parent element and then use tagindex to be specific. After initial recording, I put in the extra time to modify the Find Logic to fit my need. If an element does not have an Id, but the element has a direct parent (only 1 level above) element with an ID, use that parent element and then the additional find logic for specific element over using TextContent. Having this functionality of Find Logic prioritization will hopefully provide a general consistency to improve my user experience.
A customer would like the ability to define custom frame info logic to be respected during recording. This will avoid the need to manually modify the recorded frame info once recorded and do it repeatedly for each new recorded frame. On customer own words: "Each time I record a step, it records a full base URL, and I have to go and delete the portion of it that matches my already used base URL, and replace it with a caret. However, when I record a navigate step, if a portion of the URL matches my base URL, it automatically removes the portion that matches my base URL, and only records what needs to be added to it. Is there a way to do this while I record interactions with elements in frames? As well, our frame IDs are static, while the Names are dynamic. Again, every time I record a step, I have to delete the name from the frame find logic. Is there a way for me to set test studio to not record the name at all, since it is useless to me and just adds some extra work? I also have the same question about queries, since I always end up deleting the query that gets recorded as well."
Add an ability to select multiple tests in a test list under the Test Lists tab -> Tests. We should be able to Move Up or Down the selected group of tests in the test list all at once instead of one test at a time.
When I want to add a test as a step, it would be nice if when I click the "Test as Step" button, I could just start typing to filter the tests instead of needing to click on the text box. I always have too many tests to scroll through, and always need to filter, so it would be nice if I could just start typing instead of clicking on the text box. The same concept goes for changing the primary target of a step. When I click the ellipses to update the target, I often just start typing to find the object I'm looking for, and then remember that I need to go click on the text box. It's not a big deal, but it is a bit of a hassle that should be an easy fix.
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”.