Unplanned
Last Updated: 14 Feb 2020 13:26 by ADMIN
There are two issues with the way load tests are created.
1. Editing the newly created user profile. At the moment we rely explicitly on recording. There is no way to edit what you have recorded and make changes to the request.
   - There should be way to copy paste requests.
   - There should be way to create empty requests which you can then customize.
   - There should be a way to use external data in the requests from a data store.
   - There should be a way to reorder requests.
2. There should be an easy way to test your requests. At the moment there is no way to test how the recorded requests in the user profile perform.
The only way is to run a load test with a single user and record with fiddler. Then, in fiddler, I evaluate what was executed and then go back to the user profile editor and make changes. It should be done directly from the user profile editor.
Pending Review
Last Updated: 12 Feb 2020 11:30 by David

On the Executive Dashboard, the columns are all fixed sized, the problem with this is that it gives very little space for test and test list names and makes it difficult to view the naming.

Please provide a way to resize or view the names easily.

Pending Review
Last Updated: 12 Feb 2020 07:53 by Ray

When one schedules a test list and the tests execute with the rerun failed tests option, there is only a limited number of things that can happen.

1) a test may pass.

2) a test may fail once but pass the second time.

3) a test may fail twice.

4) a test may not run.

My suggestion is that, if these are the four types of result, report only this.

When you say this:

    Run Summary:  25 of 25 test(s) run; 22 passed, 3 failed, 0 not run.

there is ambiguity. It is not clear what happened. It could instead say:

    Run Summary: (#) test(s) run, (#) passed, (#) failed but then passed, (#) failed twice, (#) not run.

If the summary is in the second form, there is no ambiguity.

Pending Review
Last Updated: 10 Feb 2020 09:34 by Efficio

It would be helpful extract the current selected value of a RadDropDownList, so it can be compared to the expected value. This is commonly used to verify if the selection was successful.

Please consider adding such extract steps for other similar controls.

Pending Review
Last Updated: 06 Feb 2020 12:43 by Jessica

Once you connect to a pop-up window, you can not switch back to the previous one, until the pop-up is closed. Some test scenarios will benefit from the possibility to switch back and forth.

Please consider this feature for next releases.

Unplanned
Last Updated: 28 Jan 2020 08:58 by ADMIN
Our team utilizes Test Studio for our product's test automation.  The company as a whole has standardized on Zephyr (on Jira Cloud) for test case tracking / metrics / etc. but I'd like to avoid double entry of data, so it'd be nice if Test Studio would sync to Zephyr via the ZAPI interface to avoid doing double work with having to log test runs manually in Zephyr and create / update test cases in both locations.  Basically, I'm lazy and I'd like an automated way to keep this information in sync.
Pending Review
Last Updated: 13 Jan 2020 13:13 by Aditya

Currently, when a step in the API test fails, the whole test is stopped.

Please add the continue on failure option for steps in API project.

Unplanned
Last Updated: 10 Jan 2020 08:29 by ADMIN
Created by: Jim
Comments: 2
Type: Feature Request
0
The video recordings are generated with the test list name and timestamp and the log is generated like so - TelerikTesting_Log_timestamp. I would like to have the option to change and customize those filenames.
Unplanned
Last Updated: 27 Dec 2019 07:46 by ADMIN

The ScrollToVisible option is not available for some of the actions that use translators. One of them is the RadSearchBox, where this property is not available.

Currently the workaround is to add an Enter text step against the <input> element. To do that, you need to use the highlighter and record any verification step. Then add the Enter text step from the step builder, enable SimulateRealTyping and change the ScrollToVisible option.

Unplanned
Last Updated: 27 Dec 2019 07:46 by ADMIN

The Keyboard (KeyPress) test step is missing the option to change the ScrollToVisibleType in the properties pane. Although the step actually performs the scroll to visible action and I see the code, when I select Edit in Code.

Please add the ScrollToVisibleType option.

Unplanned
Last Updated: 27 Dec 2019 07:46 by ADMIN

It will be useful to improve the output data in API test results. Currently the generated results files from an API test run do not contain data for the actual sent and received requests. 

The available workaround is to use Fiddler and capture the generated traffic during the API test run.

Unplanned
Last Updated: 23 Dec 2019 06:57 by ADMIN
Created by: Michael
Comments: 0
Type: Feature Request
2
While IE is still supported by Microsoft, it just doesn't work well in some instances and has problems with some modern web design elements. Any chance of adding the capability or a possible workaround for using an alternative browser to recapture images for the storyboard? 
Pending Review
Last Updated: 17 Dec 2019 12:07 by ADMIN

It would be nice if there was a way to avoid simulating real typing for a search box.  There is no option to enable/disable it, but it is clearly using this behavior.  I've tried a workaround of entering text directly in the input element, but it doesn't seem to register it when this technique is used.  I don't see how a textbox can be made to work without this behavior but a search box cannot.

Simulating real typing tends to be the most fragile part of our tests, and all we really need is to enter text and then search.  It also slows down the tests quite a bit vs. just setting the text directly.

Completed
Last Updated: 13 Dec 2019 12:57 by ADMIN
Currently when a test step is set to SimulateRealClick or SimulateRealTyping, the target element is unconditionally scrolled to the top of the browser window, even in cases where the element is already visible.
It would be more efficient to test if the target element is already fully visible and only scroll when needed.
Unplanned
Last Updated: 06 Dec 2019 07:35 by ADMIN
Created by: Robert
Comments: 0
Type: Feature Request
0
Add the possibility to configure custom fields for bug tracking in Azure DevOps. This feature exists for TFS and Jira, but not for Azure DevOps.
Pending Review
Last Updated: 05 Dec 2019 14:45 by ADMIN
Created by: akhil
Comments: 1
Type: Feature Request
0
Can we perform API Code unit testing using telerik where code is written in Visual studio
Pending Review
Last Updated: 02 Dec 2019 18:09 by Ewin
ADMIN
Created by: Boyan Boev
Comments: 6
Type: Feature Request
10
We should be able to set a global Ajax timeout as we can for wait on elements timeout.
Unplanned
Last Updated: 29 Nov 2019 17:40 by Dan
Created by: Dan
Comments: 1
Type: Feature Request
1
It will be useful to implement the option to get the text of a dialog without using a custom dialog handler. 
Unplanned
Last Updated: 26 Nov 2019 11:24 by ADMIN
Created by: Anshum
Comments: 0
Type: Feature Request
2
Please add the option to export the results from a performance test.
Pending Review
Last Updated: 22 Nov 2019 15:37 by ADMIN

Tests that have Not Completed tests, shouldn't list the overall test as Pass or Fail....rather it should set the overall run as "not complete"

In addition - when loading not completed tests within test runs, they are just shown as fail with no background and white text.  The run is listed as pass if there are no fails but existing "not completes".

Recommendation to add Not Complete as overall result in addition to individual tests that are no in a passed or failed state

1 2 3 4 5 6