It would be useful to be able to set the value of a variable directly instead of expecting the result of another step.
It would be useful if there is a module (a standalone step, or step property, or a new tab in the step UI) which is dedicated for text only. Its purpose should be to provide some notes about any additional settings required or something similar.
The latest Chrome v.69 dialogs cannot be handled in Windows 7 environment.
When you manually add an element via the Element menu, and the element already exists (according to the find logic) but under a different friendly name such that it gets merged with the existing element, there's no indicator to the user what happened. The user is not informed what element it got merged into. 1) Manually add an element to the test, the added element should be highlighted in Element Explorer via the yellow arrow 2) Click on a different test step to highlight a different element in Element Explorer 3) Add the same element again, but enter a different friendly name Expected: Because the duplicate element was merged with the element from step 1, some visual cue displayed to the user to indicated which element it was merged into Actual: Under the recording toolbar it says "Added xxxx" where xxxx is the name you manually entered. However element xxxx is nowhere to be found, the yellow arrow still points to the element for step 2 above. Nothing tells you that it got merged with the element from step 1.
When trying to schedule remote execution, in specific cases with huge files which are over MongoDB limit of 16BM (https://docs.mongodb.com/manual/reference/limits/), we fail to upload the tests in the DB and remote execution is stuck or behaves abnormally (does not update originally uploaded test if it was with smaller size and is already in the DB). One of the outputs is that scheduled run is immediately terminated and error is shown in Test Studio Results view, saying "Unable to load test". Need to implement a mechanism that handles such cases and uploads big files in chunks, not as one object.
Cannot set GET call after two POST calls one after another - it throws `Timeout Error` and GET cannot be send from Telerik (Wireshark is used to verify this).
Running a performance test with enabled performance counters executed on a localized (Italian) machine cannot save the results and fails abnormally (please see the screenshot).
Load Testing - when encoded response is received from the server in Load Test it cannot be decoded. Implement a feature for decoding the response so to be able to extract the value and add it as a dynamic target (for example) in a Load Test.
Steps to reproduce: 1. Configure the Scheduling service as per the instructions here. 2. Two factor authentication for the account was also enabled and a password for the application was created. Expected: Send email after a scheduled execution. Actual: Error in the log file: telerik.teststudio.executionmanagerservice.exe(1844:3),Error] ResultMailSender.ClientSendCompleted() : Smtp sending email failed: Failure sending mail.
Step up/ Step down is not working as it should. To be able to choose value we should set initial one first.
In a source controlled (TFS) project when a code file is added to an existing test from another user, getting the change checks out the test file.
Steps: 1. Create a test case with two steps: - HTTP request with GET verb - Any non-http step (Verification, Set Varisble, Wait, GoTo or Coded Step) 2. Run the http request step as a single step (if the whole test is executed instead, the test run passes successfuly) 3. Run the second step too - also as a single step Result: The second step passes, but an error appears in the test output: "13:57:37.017 [ERROR] Unable to cast object of type 'System.String' to type 'System.Byte'." If the second step is a Set Variable step or a Coded Step that creates a runtime variable, the resulting runtime varible will fail to be created and will not be available if further test steps get executed. Expected behavior: The second step should pass with no errors and any runtime variable that it creates should be properly created and available for further test steps.
Local Test List execution against JS Browsers should close all running browser instances (Firefox and Chrome)
Implement the ability to pre-define a set value for custom required fields except the Test Name in a QC setup.