A popup with "End of Central Directory record could not be found." error shows up when I try to add a custom step from the step builder.
When I restart Test Studio, the test works fine.
Android mobile app cannot be configured with Android Gradle plugin 3.4.2 and no test can be recorded against that.
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.
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
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.
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.
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.
Steps to reproduce: 1. Use Run->To Here against Chrome or Firefox. 2. Once the recorder is attached immediately hit the Pause button. Expected: The recorder is paused. Actual: The recorder is displayed as paused but it actually still records steps.