A critical product needed in the Test Studio suite is a Test Editor for only creating and debugging a single test. It would be a stripped down version of Test Studio Ultimate, with only the Record and Playback features of the primary Test tab. Take out the Performance, Test Lists, Results, and Reports tabs. We use Test Studio for APM - post production Application Monitoring in DevOps. We purchased only 2 copies of Ultimate - one for each environment QA and PROD - so that the scheduling, performance and reporting features were dedicated to an environment and a senior admin in our DevOps roles. However, we have multiple team members whose only job is to create the tests. I have to swap licenses on the Ultimate version or create a DEV Project in the QA configured machine to allow them to simply create the tests, but then I cannot schedule new tests in a test list. Please create a Test Editor and give it for free to Ultimate purchasers or price it inexpensively. Productivity of our DevOps team would be greatly increased. We could even hand it to Customer Power Users to create their own post production Monitoring Tests to submit to us for their Application Monitoring script. A great way to capture more APM Market share.
Since version 2018.3 Test Studio has a video recording feature that captures a video of the test execution when running a test list ( https://docs.telerik.com/teststudio/getting-started/test-execution/test-list-execution#recording-of-test-list-execution ). When Bug Tracking Integration is enabled ( https://docs.telerik.com/teststudio/features/integration/bug-tracking/configuration ) it would be useful to include the path to the video of the failed test in the failure details of the submitted bug in TFS or Jira.
Please add the ability to export the data from the Details tab in the Performance testing in excel. Refer to the screenshot attached internaly for more clarity.
Essentially an image verification step, but to validate the complete layout of the full screen. Although position-based logic is not the most stable approach, it would be helpful to be able to run a step that makes sure that everything on the screen renders correctly (with maybe options based off browser, device, etc.).
I'd like to see more desktop UI supported than just wpf. Visual studio and ranorex both support automation of desktop applications written in Windows forms and Delphi so I think you need to catch up with the competition.
Add ability to specify on which execution servers to run the test list when run through the CommandLineClient. Currently you are only able to specify the scheduling server. When the test list is executed it will run on all execution machines that are connected to the scheduling.
Hey guys, I'm looking for a feature in test studio that would allow users to have multiple ramp up/down times using the load/performance testing functionality. For example, start with X users then gradually ramp up to Y users over the next N minutes. After N minutes maintain a constant load of Y users for the rest of the duration of the load test. To me, this is the one feature test studio is lacking compared to the other players in the load/performance testing industry. Please like if you agree that this would be a great feature for the test studio team to implement. Thanks all! Steve Charlton T4G Limited
Option is currently limited to only the manual test opened in Test Explorer.
The send results dialog that allows you to send email notification upon test list completion is only generated when scheduling tests for remote execution. I would like this feature to be available when test lists are run immediately using the "Run List" button/command
In a load test - encrypted part of the URL is not recognized as a dynamic parameter. Steps to reproduce and further details are available in the internal description.
Currently you can build If Then Else and Do While loops, etc. via the Test Studio UI. Our team has many scenarios where these won't work for us and we need to use Try Catch instead to avoid failed steps (that really didn't fail). To simplify this - instead of requiring us to add coded steps to accomplish this Telerik may be able to add the ability to build these steps via the UI.
The chrome plugin is always active and outputting console logs, I would like to be able to do what UBlock does and be able to say "Yeah you can run here" so it's only being used on domains I want to record with.
It will be useful to have ordered tests execution option in Visual Studio plug-in - an analog of Test List in Test Studio.
At this point recording a test for React-Native applications does not automatically use elements ID
Test Studio already uses a ~ as a wildcard option within Frame properties. could this same wildcard option be extended to the Compare Mode properties. The current behavior is that you can merge the pages together by changing the page Title to match, even a partial title, however when recording another step it generate a new page in the Element Repository. The desired outcome is that with the wildcard it would recognize the page as already in the repository and add any new elements within that page. For example, if I am building a test against Amazon.com they have many pages that start with Amazon.com:..., but have much more info that is dynamic following. A wildcard could just recognize the Amazon.com portion as the same page ignoring the dynamic portion. Compare Mode: Title and Title: ~Amazon.com
Add the option to select multiple tests to open in the Used By Modal When using the Used by feature on a test or element it lists all the tests using the element or test. But one can select only one test at a time to view or make any changes. It would be really helpful to be able 1 ) to select multiple tests to open 2) to be able to add these into a test list /view This will help to quickly modify/run/debug these tests when a change is made to the UI.
From ticket 846095 Many times I forget to hit the pause button when I start navigating or clicking in a browser with the recorder on. This of course creates a test step in my test without me noticing it until I run my test and get a fail or some undesired result. Having the option to set the default record state could save me time fixing inadvertently recorded test steps.