This is not really a bug. We are integrating Azure Dev Ops into our development environment and I've come across several links explaining how to integrate Test Studio to work in the Azure Dev Ops environment. It's still somewhat abstract to me, but it seems that one of the prerequisites highlighted in red below does not exist in our Azure Dev Ops Environment. Could I be missing something? Or have significant changes been made in the terminology that make it hard to keep up with?

Any help would be welcome or a point the right direction.

SSq

Hi there,

I'm looking for some clarification on what settings can be changed when passing a settings file to the ArtOfTestRunner.exe.

When I try to run a test list the settings for "Web" appear to follow the values I set as well as being able to change the Execution Delay, however when I try to change the 'RerunFailedTests' value it will still use the value set in the original list. 

Example settings.json I used

{	"Settings": {
  "__type": "ArtOfTest.WebAii.Core.Settings", "__value": {
    "Web": {  "__type": "ArtOfTest.WebAii.Core.Settings+WebSettings", "__value": {
        "RecycleBrowser": false,
        "DefaultBrowser": 12,
        "BaseUrl": "https://BaseUrl.com/qa",
        "KillBrowserProcessOnClose": false,
        "KillBrowsersBeforeStart": false
    }},
    "ExecutionDelay": 0,
    "RerunFailedTests": true
}}}

How can I pass in the  RerunFailedTests value from the settings json file?

Thanks for your help,

Liam 

Please expose the data binding system. this would allow test to be truly dynamic. e.g. allow users to load property files containing hostname and port and do a find and replace of the hostname and port in test files. This way users don't have to maintain one test per machine per port, they just have to maintain one test and one property file.

Have a simple GUI that allows configuring Execution Server (Telerik.TestStudio.Scheduling.Client.exe.config) directly, being able to change ports and other settings, including Storage Service ports and DB configuration.

Test Runner UI rework:
1. combine the Scheduling and Execution screens with their read-only static information in 1 tab and make sure it is not the default one
2. Rename Process History tab to something like "Runtime Information" and make it the default view tab
3. Improve runtime information by preserving history for all performed runs and add options for export of results and logs

The generated code does include a comment suggesting that the next line of code will be extracting a value in to a variable, but the related code is not generated.

I would like to be able to re-order tests in my project tree view...not for order of execution like in a test list, but to make them easier to manage....or at least give me more options for management.

Like if I'm working on a new test in a big list, maybe I want it at the top\bottom instead of just sorted into the list.

Now that it is possible to have mixed load/web tests, it will be good in Test Lists view for the selected test list to see the type of tests that are used in the list.

User might not know by name what kind of tests are in the list, so it will be good to have this visibility granted by the default Tests view when a test list is selected

Steps to reproduce:
1. Record a simple test.
2. Open storyboard and verify that in each picture the test element is highlighted.
3. Click on recapture storyboard.
Actual: After recapture storyboard is over the element highlight rectangle found inside the storyboard screenshots will disappear.
Expected: Highlight remains after recapture storyboard.

We have all the recorded objects inside a silverlight iframe.

Now our applications have changed and we don't have Iframe anymore.  

But existing scripts are not working as it throws error that silverlight/contentframe is missing. 

Hi Team,

Renaming an element will change the corresponding existing test steps descriptions. However the new ones do not get affected as per this: http://screencast.com/t/SIHUbqDEjes

Thanks in advance,
Faten

 As a result it seems that the translators for Kendo Angular Input and TextBox components are, currently, not backwards compatible with the previous versions of these controls. 

It will be great to fix these so that the latest Test Studio can be used for testing web pages built with previous versions of Kendo Angular controls.

When you add a "Wait for Exists" step from the Step Builder, against existing element in the Elements Explore, it will keep the image that was captured during the recording of that element.

That image is used as a backup logic to try and find the target element for the "Wait for Exists" step, but it should not be used. 

The workaround is to delete the image in the target element only for the "Wait for Exists" step.

Long test list execution with video recording generates large video file. As a result, after the run is finished, results are not stored successfully.

The data for large result size is reported to DB but it is not parsed correctly and you can see the following error in the application log.

The Image verification and OCR steps do not work for WPF tests.

Those steps are simply not added to the test with the latest release 2020.R2.

The HTML output from ArtOfTest.Runner.exe from failed test is missing the expected and actual image on failure. The same details are available, if the output is generated from Test Studio Standalone version.

The actual image on failure exists in the specified output location, but is not included in the HTML. When you open the results with the Result Viewer, you can see the actual image on failure, but the expected image is still missing. Maybe those are 2 separate things to look at.