Hi
I have some databound parrent tests.
For these I have created seperate sheets in my excel, to ensure my part test are working i switch their databinding between the sheets to ensure them working in all environments.
Everytime i rebind a test the excel file gets corrupted! I have to restart the computer and then it works again… What is the fix for this?
I have attached an example of being unable to open the excel document!
Steps to reproduce: Using the project attached execute the test which should handle a dialog. Expected behavior: The save dialog is handled successfully Actual behavior: The dialog is not handled and the following is output in the log: System.TimeoutException: Timed out waiting '60000' msec. for any dialog to be handled '1' Result StackTrace: at ArtOfTest.WebAii.Win32.Dialogs.BaseDialog.WaitUntilAnyHandled(IEnumerable`1 dialogs, Int32 handleCount, Int64 timeoutMilliseconds, Boolean resetHandleCount) at ArtOfTest.WebAii.Win32.Dialogs.BaseDialog.WaitUntilHandled(Int32 handleCount, Int32 timeout, Boolean resetHandleCount) at ArtOfTest.WebAii.Win32.Dialogs.BaseDialog.WaitUntilHandled() at UnitTestProject2.UnitTest1.TestMethod1() in c:\Users\ittodorov\Documents\Visual Studio 2012\Projects\UnitTestProject2\UnitTestProject2\UnitTest1.cs:line 42
Changing the DPI settings to 125%, for example, on Windows 7 causes troubles with the Desktop clicks when running tests against Chrome. The click is below or above the target element. Highlighting in record mode may also be affected.
Workaround: As a workaround the Desktop clicks (MouseClick() method) can be replaced with the Click() method, which works as expected. The alternative in a non-coded solution is to disable the 'SimulateRealClick' option for the click steps.
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
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.
Multiselect control cannot be recorded against IE as expected. When selecting more than one value from it, using the Ctrl key, not all selected options are listed in the 'SelectedItems' step property.
The 'SelectedItems' step property does not display names of the selected items and it is not visible how many elements there are to be selected.
If the desired items are manually added in the mentioned property, they will be selected correctly in run-time.
The latestMongoDB 4.0.6. cannot be restarted from Scheduling Configuration setup, the mongo service config gets broken if started through the Scheduling wizard and service cannot be started anymore.
Workaround to resolve the not working MongoDB service:
Using the latest version of MongoDB 4.0.6.1. Since the current state of the Mongo service is not a working one, it will be required to completely uninstall the MongoDB and then perform a clean installation again.
2. The important note is to install the MongoDB as a Windows service - this is the default configuration.
3. This installation will install and start the MongoDB service.
4. Next important thing to keep in mind is to avoid restarting the MongoDB service from the Scheduling configuration - this is the first tab of the wizard and it shouldn't be used until a permanent fix is available.
5. The Scheduling and Storage services can be freely configured from the respective two tabs and the remote execution should be working now.
Using a previous version of MongoDB
1. If the version of MongoDB is not of great importance, you can install any previous version.
2. The easiest way is to completely uninstall both MongoDB and Test Studio from Windows Control Panel.
3. Then perform a clean installation of the latest version of Test Studio. This will install MongoDB 3.0. and you can freely start the Scheduling configuration.
The recorder is not recognizing elements in the iframe and I am not able to record any actions.
Test Studio Run-time edition does not deploy the TestAdapter.dll with its installation.
Thus Test Studio tests cannot be executed with the VSTestConsole.exe in a Azure DevOps (VSTS) pipeline.
Workaround:
The TestAdapter.dll for VS 2017 and VS 2019 is being deployed to the Test Studio installation folder (for Ultimate or Dev Edition installations) along with the respective *.vsix package. Until the misbehavior is fixed, the vsix package can be copied to the agent machine and installed with double click. Then refer the dll from the respective location.
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?