It is rather difficult to debug tests that use nested sub-tests. You can't set a breakpoint in a sub-test (it's ignored) and you can't "Step over" and "Step into" similar to how source code debugging works in Visual Studio.
In record mode, select two steps to execute with Run->Selected Steps - one which triggers the dialog, and the other to handle it. Expected: To handle the dialog Actual: The Handle dialog step times out.
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.
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.
Really excited to have a dashboard to present to the team now
Is there anyway to configure the number of Tests that display from within a result? Right now it only looks like 5 is what is the default, that requires quite a big of pagination.
How can I change the size of the element suggestion pane? I can't seem to click and drag it, and I'd like to see more than two or three options.
Currently there is only a scroll that can be used to view all options.
Allow deserialization of dateTime values to strings instead of DateTime objects when extracting such with JSONPath.
When a dateTime value is returned in a JSON response ("2019-04-08T00:00:00") and a JSONPath expression is used to extract it from that response, Test Studio deserializes it to a DateTime object. This leads to losing its original format.
It will be useful to have the option to deserialize it in a plain string value.
When using the visual studio plug-in, if you update coded files (anything ending in .tstest.cs), when you open your project back up in TS standalone IDE, the changes you made to any given coded file will not automatically be detected so you must open up every .tstest file corresponding to the .tstest.cs files you changed in visual studio, and only then will the IDE see the changes
Test Studio Mobile is missing a Comment step in the Common section in Step Builder.
It helps to make the test steps more understandable to the person looking at them. At a future date, these comments will assist in a better understanding of what is going on in the test, for whoever is needing to change the tests.
Currently any custom added dynamic target should be created separately for each next request.
For example, if there is a user session token generated in the first responses and used in the following requests (as a cookie, header, etc.), the only way to pass it to all upcoming requests is to create a new one for each request.
It will be useful to have the ability to reuse the already created custom target and only change its destination step.
Ability to record a test step and then change the Element with an existing Element. Here is the workflow: I record a step and edit the Element. Then every time I record on the same UI object, Test Studio creates a new element. Since it creates a new element, I have to manually edit every duplicate element to exactly match the first element in order for them to merge. I would like the ability to change the element the step is using to an existing element.
When you schedule and run a test list you get the following entries in the Scheduling server log: [05/06 19:32:52,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobBroker.ScheduleJobAsync() : Job satisfied all preconditions, id = eae7a94a-c7b8-408f-9021-3a315eeb1042 [05/06 19:32:52,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobBroker.ScheduleJobAsync() : Job sent to scheduler, id = eae7a94a-c7b8-408f-9021-3a315eeb1042 [05/06 19:32:52,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobsController.CreateNewJob() : Accepted new job, Id = eae7a94a-c7b8-408f-9021-3a315eeb1042 [05/06 19:33:28,Telerik.TestStudio.ExecutionManagerService.exe(4344:40),Execution] JobRunner.RunJobAsync() : TestList loaded for job ID = eae7a94a-c7b8-408f-9021-3a315eeb1042 [05/06 19:33:28,Telerik.TestStudio.ExecutionManagerService.exe(4344:40),Execution] JobRunner.RunJobAsync() : Job started, ID = eae7a94a-c7b8-408f-9021-3a315eeb1042 [05/06 19:34:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobRunner.<CleanupTestRunsStatus>b__12() : TestList finished; updating dispatch group header job Id = eae7a94a-c7b8-408f-9021-3a315eeb1042 [05/06 19:34:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:12),Execution] JobRunner.<CleanupTestRunsStatus>b__12() : TestList finished; sending notifications [05/06 19:39:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:28)] First trace message from pool unnamed thread (managed ID = 28, native ID = 12868). [05/06 19:39:10,Telerik.TestStudio.ExecutionManagerService.exe(4344:28),Execution] JobRunner.<CleanupTestRunsStatus>b__12() : TestList execution status expired- removing from list job id=eae7a94a-c7b8-408f-9021-3a315eeb1042 What's missing is which execution server the test list was sent to. This can be important information in a setup that has multiple execution servers.
The size of failure information field in the verification builder is only two rows and cannot be resized. We should copy the text somewhere outside of Test Studio in order to see it. Steps to reproduce: 1. Create a test with a verification step. 2. With an attached recorded right click on the verification step and choose Edit. 3. The Sentence Verification Builder appears and if the validation fails the information field is really small and unreadable. See the attached screen shot.
I have this idea in mind but not sure how to start with. How to add a custom option(control like a button or check box) in the UI?
From ticket 869169 In the attached screen shot is an example of an ASP.NET partial page update. It includes a URL with a dynamically changing query string. The application needs that query string echoed back in the next GET. Currently Test Studio load tests do not parse "text/plain" responses for dynamic targets. As a result this scenario is not currently supported.
Currently when Test Studio wants to scroll an element to make it visible (such as when SimulateRealClick or SimulateRealTyping is enabled) Test Studio will always, and unconditionally, scroll the element to the top. This causes problems for a few applications that have a static UI element, the target element ends up being scrolled underneath this static UI element. It would be helpful to have a global setting which controls whether the target element is scrolled to the top or the bottom of the browser window. The parameter is available in the API, just need to expose it as a step setting, or a global setting so that customers aren't forced to convert the step to code and override the default behavior, which can be time consuming when there are lots of steps that this must be done on.