Steps to reproduce:
1. Open an Enter password step and expand in the step pane
2. Set the encrypt property
Expected: All fields with the actual text entered should be masked with *
Actual: If the step is expanded the actual text entered field does not change its value.
Note: Reopening the test fixes the visual glitch.
When using a builtin step for checking rowscount of a table that uses "greater than" or "less than" it fails even though it should not.
"Equals" works fine.. but if I use any other TableVerificationType than "equals", then it fails.. unless if I convert it to a coded step.
So to reiterate: If I convert the step to a coded step then it works.
We have several test projects that now have failing tests because of this.
Attached test project that showcases the problem.
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!
Pre-requisite: Upgrade to 2019.1.212.0 from 2018.3.1004.0
1. Select the Test List tab
2. Click the List button and add a new Test List with appropriate tests.
3. Click Save
4. Notice the "Storage service unreachable." message pop-up.
5. Click "OK" on the pop-up.
6. Notice that the Test List and Tests are saved as expected.
**This issue did not happen on the previous version of Test Studio
The step gets successfully executed but fails with the following exception:
InError set by the client. Client Error:
Cannot read property 'toggle' of undefined
BrowserCommand (Type:'Action',Info:'NotSet',Action:'InvokeJsFunction',Target:'ElementId (tagName: '',occurrenceIndex: '-1')',Data:'$("th:eq(1)").data("kendoFilterMenu").popup.toggle()',ClientId:'663fc963-6051-4044-9dfb-ce01ca15339d',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Cannot read property 'toggle' of undefined')
Workaround: Record the click step to open the filter without using the Test Studio translator, or in other words against the span element directly.
Data bound request does not support "application/json" content type.
The exception listed in the log:
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.
When the element's find expression fails to find the element it should log in the execution log, that alternative method of verification is used.
The Wait for Exists step does not log the usage of image verification, even though the find expression fails.
The behavior with click step is as expected and the log is correctly generated.'17-Jul-19 14:10:30' - 'Pass' : 2. Click 'BtnKSubmit'
During the trial period of Test Studio, by each start of Test Studio or Visual Studio there is a prompt window to continue the trial or activate a purchased license.
The license prompt window of the Test Studio plugin (part of the DevCraft Ultimate package as well) in Visual Studio 2019 start window prevents typing in the following native VS windows - Create project and Clone/Checkout code.
I. Change how Visual Studio 2019 starts:
1. Open any existing project in VS 2019
2. Open Tools-> Options-> Environment -> Startup
3. Select any of the other listed options in the dropdown on the right - Most recent solution or Empty Environment.
II. For the cases when DevCraft Ultimate is installed and the Test Studio plugin is not the current focus of evaluation.
1. Disable the Test Studio extensions.
2. Open any existing project in VS 2019
3. Open Extensions -> Manage Extensions -> disable the following extensions:
The imported test was created with data binding. After I imported the test successfully, I did not get/have the xls that was used in the other project. The test execution fails due to the missing data source file.
GetComputedStyle() for hyphenated computed style against Microsoft Edge does fails with the following error:InnerException: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
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.