Unplanned
Last Updated: 29 Feb 2024 09:41 by Pribadi
Dear Telerik Support Team,

Currently, when running multiple test cases in Telerik Test Studio, we encounter the need to repeatedly launch and close the application under test for each individual test case. This process of launching and terminating the application adds unnecessary overhead and significantly extends the time required to execute our test suite.

To streamline our testing process and improve efficiency, we would like to suggest the implementation of an option that allows us to run multiple test cases without automatically killing the application at the end of each test case execution.

This feature would enable us to execute multiple test cases sequentially within the same application instance, eliminating the need to repeatedly launch and close the application for each test case. As a result, we would experience significant time savings and improved productivity in our testing efforts.

We believe that adding this option to Telerik Test Studio would greatly benefit your users and enhance the overall usability and efficiency of the tool.

We kindly request your consideration of this feature request, and we would greatly appreciate any updates or feedback on the feasibility of implementing this option in a future release of Telerik Test Studio.

Thank you for your attention to this matter. We look forward to your response.
Unplanned
Last Updated: 06 Feb 2024 14:52 by Stephan
A wpf application does not start correctly in Test Studio because the working directory cannot be specified.
Unplanned
Last Updated: 02 Feb 2024 12:26 by Software

Test Studio supports adding a single custom base test class in the project. If one more base test class is defined and listed in a test code-behind file, the coded steps will be listed as empty and will not show the option to choose any of the methods in the test class.The steps will be still executed, but no changes can be applied within Test Studio (only in VS).

because I want many test sharing the same OnAfterTestCompleted(), instead of adding it to each test, I created new class:

using....

namespace test_studio_tests
{
    public class CustomWebAiiTest : BaseWebAiiTest
    {
        public override void OnAfterTestCompleted(TestResult result)
        {
            // some code to be executed 
        }
    }
}

and then all the tests to inherit from this new class

public class TestClass : CustomWebAiiTest

instead of Base one as they did so far. in TS project keep compiling, but then all the tests have extra icon and coded steps are not recognized anymore. in the meantime in VS2022 with TS plugin, all is recognized and keep working without any issue.

Unplanned
Last Updated: 22 Jan 2024 08:18 by Software
I want to keep using only UPLOAD button in top menu of TS, so to have upload done intentionally. Want to hide this question every time I close TS.
Unplanned
Last Updated: 11 Jan 2024 16:52 by Lisa
Created by: Lisa
Comments: 2
Type: Feature Request
2

Hello Progress Support,

I wonder if we can have "Bind data" applied on the "String Length" in "Generate random string" step?

Thank you for your help.

Regards,

Lisa

Unplanned
Last Updated: 11 Jan 2024 12:50 by ADMIN
Created by: Max
Comments: 1
Type: Feature Request
0

Hello,

Currently when I create a Git repo and connect Test Studio it creates default branch called "master".

Would it be possible to make it consistent with good practice and Git standard and rename it to "main" in the next version of Test Studio?

Can this be added as feature request please.

Thank you,

Max

 

Under Review
Last Updated: 08 Jan 2024 15:11 by Rohan

When you execute a test list in CI environment with the ArtOfTest.Runner.exe, there is no option to publish the results to the storage server (if you have setup a storage server).

It will be great to have this option, so we can view the results in the Executive Dashboard.

Under Review
Last Updated: 08 Jan 2024 09:02 by ADMIN
Created by: Kristina
Comments: 0
Type: Feature Request
4

Allow users to add custom arguments when executing tests against any of the supported browsers.

This includes the Chrome Headless execution, which always defaults to en-EN language argument for example and you can't change it.

Unplanned
Last Updated: 08 Jan 2024 09:01 by ADMIN

When generating videos for the test runs from a test list, the output video files uses the name of the test only. There is no indication which is the test list from which this test was executed and when having multiple runs and videos it is difficult to relate these with the generated results. 

It will be useful to generate the names of the videos from a test list in a way to correspond to the test list name and particular run. 

Under Review
Last Updated: 08 Jan 2024 09:01 by ADMIN
Update the predefined device config settings with the latest available common iOS and Android devices. Check if the User-Agent request header needs to be updated as well, or more options to be provided. 
Unplanned
Last Updated: 08 Jan 2024 09:01 by ADMIN

Currently the exported result contains extended details only for the failed steps. If there is a warning for a step - like the warning that the element was found only by image, this can be only seen in the Test Studio result file. 

Extending the HTML exported result to show the step warning details will be very useful for anyone who review this type of result (attached in an email after a scheduled run, for example). 

Under Review
Last Updated: 08 Jan 2024 09:00 by ADMIN
Created by: David
Comments: 0
Type: Feature Request
7

Allow the ArtOfTest.Runner to publish the results to the Executive Dashboard. There they can be seen by members of the team, who do not have Test Studio installed.

Make it possible for the ArtOfTest.Runner to use multiple execution machines. Distribute the test list execution to other execution servers.

Declined
Last Updated: 08 Jan 2024 09:00 by ADMIN

A picture is worth a thousand words...

Declined
Last Updated: 08 Jan 2024 08:59 by ADMIN
Currently Test Studio load test can only use a dynamic target of type URL, if this takes its value from the response of a previous request. It will be useful to allow data driving this type of dynamic target with data from external source. 
Declined
Last Updated: 08 Jan 2024 08:59 by ADMIN

The Kendo Angular Multiselect control is not covered with the built-in translators.

It will be very useful and consistent if such translator is added in Test Studio.

Under Review
Last Updated: 08 Jan 2024 08:52 by ADMIN
On the Test Run List page (Where it lists each of the test runs) it would be nice to have a listing of how many tests ran, How many Passed and How many Failed. I could have a test run of 1000 scripts and 1 failed and another that ran 1000 scripts and 999 failed, from this view I would not see a difference in the 2 runs.
Under Review
Last Updated: 08 Jan 2024 08:52 by ADMIN
Created by: Shamsher
Comments: 0
Type: Feature Request
0
In some cases, the Test Studio application log can get large and it is not possible to open it. Please add the possibility to split it into different files or set a file size limit, so we can open and analyze it easier.
Under Review
Last Updated: 08 Jan 2024 08:51 by ADMIN
The Windows authentication feature in load testing saves the credential information unencrypted and completely visible. It will be convenient if this feature is enhanced and allows one to hide the used credentials. 
Declined
Last Updated: 08 Jan 2024 08:51 by ADMIN
It will be useful to implement global timeout settings in the context of API project. For example, if having multiple Http Requests steps, which timeout requires to be increased, you need to go through each separate step.  
Declined
Last Updated: 08 Jan 2024 08:32 by ADMIN

It would be useful to support the generated output file additionally in a human-readable format (markdown/html), when it comes to automated API testing.

 

We (dev/qa team) would like to attach the file to the story as documentation of the test case. So that the product manager or other colleagues (without license access) can easily take a look at the covered cases. 

The current xml output (sample attached) already provides a good overview and could be extended with background information in some places (for example <action>).

1 2 3 4 5 6