Visual Studio behaves differently when using the PresentationCore.dll and on scaling different than 100% - here is some additional information about the Microsoft DPIHelper class.
Using this one somehow interferes with how Test Studio and the Testing Framework handles the different display scaling settings and causes some actions to be performed on wrong element.
Currently iOS Xamarin application can be configured to be testable on a Mac machine.
A good extension of the feature will be to add the ability to build the iOS application from Visual Studio on Windows machine.
It will be useful to implement handling the scenario where a page supports multiple files download in a sequence
- a prompt to decide whether to allow or block the multiple files download,
- download dialog steps to handle each of the files download location.
In VS 2010 and VS 2008 there was the Test View. From there you can get at a number of Test Studio specific test level settings, such as BrowserType, SilverlightEnabled, etc. There appears to be no equivalent in VS 2012. Test View has been replaced with a Test Explorer, but clicking on a test in Test Explorer does not bring up any test properties. As a result it appears you have no method to get at the Test Studio specific settings in VS 2012.
In VS2010, "this.ExecutionContext.DeploymentDirectory" returns the path to the default deployment directory. In VS2012 however, there is no such default directory and same property returns the path to the project folder. This is really confusing for our customers and we need to either change the implementation or remove that property completely. The following article describes how to set a deployment directory in VS2012: http://msdn.microsoft.com/en-us/library/vstudio/ms182475(v=vs.110).aspx
Again another item I have discussed, I operate in a Closed network environment and access to the VU's via the current online validation method does not work. The guys have been great to offer me the option of a specific build but maybe how licenses are validated could be changed to allow for this type of working environment ? - its the only tool I have ever had a problem doing this with.
Based on the documentation, system path is a manual step http://docs.telerik.com/teststudio/features/test-runners/add-path-environment-variables It would be very beneficial when you are setting up multiple test machines to add system path automatically(or an option) as part of TestStudio MSI installation.
I would like to make the list of agents "select all" checkbox, as checking multiple machines is tedious and if you misclick you have to start over as they are all deselected. I would also like to see a static set and save the "email to" in the results settings. I would also like to know who the test case owner is in the email as a option. I would like to have the ability to have the tests that fail in the list create a new test list, consisting of the failed test lists to run at a later time.
One of my element has the following find logic:
XPath is exactly //td/input[@title[contains(., 'End Date (Month Day Year)')]]
When I ran my script I got the error below:
Exception thrown executing coded step: 'Enter Leave Request To Date in 'LeaveRequestToDateText''.
'//td/input[@title[contains(. 'End Date (Month Day Year)')]]' has an invalid token.
I notice that the find logic expression displayed in the error message has a missing comma. Do you know why?
When used in code Wait.For() certain element's attribute state, does not respect the timeout set to wait.
Additional details shared internally.
I'd like the ability to create my own Step Builder steps.
This way, the QA team could use my custom built steps to achieve common task without our web based product.
In our product, we need the ability to search a table for specific cells and retrieve image input buttons on that cell row. Of course we can easily achieve this by doing a coded step. However, this is a very common task for us and if my QA team could just select a custom built step builder step that has its own specific parameters (TableID, CellText, ImageInputAltText, etc), then I would remove one area of them having to get into code behind to achieve their task. The QA, while able to do some development, its not their core competency, so I would like to minimize their exposure.
Possible Reasons my company would need such:
* Often times we need to count the number of times a cell with a certain word in it exist in a table.
* We have a common set of steps that always needs to occur together (enter in text, click search, find in table, click that link [the start of every process in our product])
* Find a row within a table that has two matching text cells.
We have a lot of tests which we reuse as steps in many other tests. But to add them we have to go every time: Step Builder -> Test As Step -> Find Test -> Add See below action how it would be much much more efficient and would speed up development a lot (Test Studio is all about UI :)