The automated browser configuration should setup your browsers to always download files instead of opening them right in the browser as documented here: http://www.computerhope.com/issues/ch001114.htm
Kendo Drop down custom template could create the list item elements surrounded by div and thus cannot be reginized as a Kendo element by the translator. By design the translator is built to recognize spans only. It would be useful to extend the usability of the translator.
Mobile testing is not super steady in recognising elements, and as a result often taps the wrong element. A way to improve this could be the add a way to tap an element with a specific text (i.e a button).
I was thinking that in some cases we might want to record a video of a test fixture so that we can see them over here without lag by playing the video, or we could even automatically run a test again if it fails to record a video of the test that failed to see exactly where and why it failed visually as well as the text log output.
The custom website cannot be recorded and executed with Test Studio recorded against Chrome and FF. Even if the page is fully loaded it seems that ReadyState is not recognized. As a workaround a pollyfill for IE can be implemented in order to run the application under IE and use this browser for recording and execution.
In the new build pipeline in TFS 2015, there is no ability to run Test Studio tests because it uses a different build agent than the XAML builds, failing because of lack of interactivity. According to Telerik Support, this is a known issue. Going forward, I would hope that Telerik would support this new build automation from TFS.
When checking in, the full path and name of the test is not viewable, even though there is space in the window.
It would be helpful if there was a search field in the Test Studio Help documentation so that one can quickly drill down to the topic of interest instead of having to manually open the folders to find topic they are looking for.
Very often automated testing requires conditional statements that look for the property of a specific element to equal a certain value - and if it does perform an action, if not continue on with the test. The issue we are having using If Then Else is that a failure is reported when the condition isn't met thereby failing the entire test. Example - Some users of our system have a setting that toggles the Save Confirmation popup as on/off depending on the user. For some users this confirmation popup appears, for others it doesn't. I've added an If Then Else conditional statement that waits for the OK button in the confirmation popup window to Exist. If it does it clicks the 'OK' button. If not it continues on with the test. The issue is that if the 'OK' button does not exist the If Then Else logs it as a failed step when it really isn't - it's a branch in my test that decides on what actions to take based on a property value of a specific element. This is a VERY common scenario in software testing. My enhancement request is to add a 'Log Failure' check box to the Test Step Properties. The default value would be checked (log failure if step fails). But this would also allow the user to un-check so even if the step fails it will not log it as a failed step (similar to continue on failure). The would be a very powerful enhancement that would help to reduce the number of unique test cases we need to design and would make our automation approach for many of our test cases much simpler.
Sometimes customers want to be able to run their test with the browser launching in a special mode (e.g. incognito mode, custom/specific user profile, etc.). If the customer could add custom command line parameters to be used when launching the browser they could accomplish this.
Test Studio runs a WPF test using only the logged user's credentials. It will be a good feature to be able to use different users credentials to start the WPF app with.
Chrome cannot be started with the required by Test Studio arguments when the "Application Identity" service is enabled in Windows 10 and as a result cannot record or execute tests with Test Studio. It will be beneficial to investigate the case on our end and identify if there is anything we could improve or at least document the known issue. A workaround could be to either disable that service or to add an exception for Chrome in an AppLocker rule to exclude it from the respective GPO.
Steps to reproduce: 1. Configure the Scheduling service as per the instructions here. 2. Two factor authentication for the account was also enabled and a password for the application was created. Expected: Send email after a scheduled execution. Actual: Error in the log file: telerik.teststudio.executionmanagerservice.exe(1844:3),Error] ResultMailSender.ClientSendCompleted() : Smtp sending email failed: Failure sending mail.
With the upcoming rebuild of the element repository, can it be added in to compile coded steps while running remotely after element repository is being dynamically generated?