"Active browser is now null", caused from disposed Manager instance, fails randomly some of the tests. The behavior is not consistent and can't be reliably reproduced, where the same tests fail.
If you have opened the web test and execute a performance test list, which includes this test, the performance details will not be updated automatically in the Performance tab.
You need to reopen the web test and go to the Performance tab to view the updated details.
I have an application, where 1 click triggers 2 consecutive confirm dialogs. I handled them both and Test Studio recorded 2 handle confirm dialog steps.
When I run the test against Internet Explorer it works as expected, but in Chrome it is stuck at the second confirm dialog.
Auto-submitting a bug from local test run works as expected, but not from a remote execution server.
The issue comes from the different certificates that Test Studio and the remote execution server use and the fact that there were changes in Jira's API.
A specific WPF application with custom controls cannot be highlighted correctly.
Details shared internally.
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".
I have a project with load test. The test has many user profiles and I need to add more in some cases. When they become too much, I can not save my changes in Test Studio.
The .tstest file is about 40-50 MB when I have this issue.
I have a screen with multiple KendoNumericTextBox. After trying to use recorded and coded step to handle the second KendoNumericTextBox in the page using KendoInputValue, these same problem occurs to me:
1. The function "ClearBeforeTyping" clears the first KendoNumericTextBox instead of the second one but correctly input the data in the second one.
2. The function "UseClientAPI" clears and input data in the first KendoNumericTextBox instead of the second one.
When i validate and locate each of the element, the tool is able to locate them correctly. In coded step, I only use the second textbox , not the first one but in execution, it still edit the first textbox and the problems mentioned above happened.
What should i do to be able to handle this type of textbox correctly?
For certain control Test Studio can record elements using chained queries - include parent and child element. If one wants to create such manually or modify an existing element to use chained query, needs to use the coded approach to define elements' queries. There is no way how to adjust an element's query to be chained if using the Edit element pane in the UI.
It will be really useful to add the ability to modify the elements queries and transform these to chained queries.
Android mobile app cannot be configured with Android Gradle plugin 3.4.2 and no test can be recorded against that.
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: