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.
Visual Studio behaves differently when using the PresentationCore.dll and on scaling different than 100% - here is some additional information about the Microsoft DPIHelper class.
Using this one somehow interferes with how Test Studio and the Testing Framework handles the different display scaling settings and causes some actions to be performed on wrong element.
I ran a test list through 'Schedule TestList' using "Run locally" scheduling setup and i received an email with html attachment. When i open the html I can see the actual and expected screenshot are missing.
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.
While connecting to Jira Cloud (https://name.atlassian.net) with valid userid and password, its giving error message "The remote server returned an error :(401) Unauthorized".
Scenario:Use a simple Login-Logout test that is separated into two different tests, executed as steps (Login test & Logout test = login-logout test) for performance run.
Issue: The current overview functionality will show the execution of the test steps 'login' and all the individual steps from the nested test, then moves onto the 'logout' test and the steps for the second nested test. The times displayed for the 'Test as Step' steps is the client side time, required for the initialization of the nested test.
There are two options for more understandable results - the 'Test as Step' step should either not representing any time, or displaying the summed up time of the nested step execution.