We should be able to set a global Ajax timeout as we can for wait on elements timeout.
Tests that have Not Completed tests, shouldn't list the overall test as Pass or Fail....rather it should set the overall run as "not complete"
In addition - when loading not completed tests within test runs, they are just shown as fail with no background and white text. The run is listed as pass if there are no fails but existing "not completes".
Recommendation to add Not Complete as overall result in addition to individual tests that are no in a passed or failed state
Currently Test Studio updates only the necessary tests and resources to the storage server. When the test execution starts on the execution server, Test Studio will download everything available in the storage server.
Please check how this can be optimized to ensure that there are all the necessary resources for the test execution.
Conditional statements (if, while, and such) should be able to use an extracted values as a condition.
Also multiple conditions will be very useful in some cases.
I think it would be neat to be able to view / edit markdown files within a project within the Test Studio application. Being able to see a markdown file in the project list, and have them open in a editor tab so you can review / make edits.
For example I create markdown files that have high level summary's of what each test completes, or potential helpful debugging information on a particular test.
Hi,
I was going though the IOS and Android api-reference document (https://docs.telerik.com/teststudio/test-studio-mobile/api-reference/ios), I was wondering if there is a method to get row count of a UITableView or of any other collection
This can make it much easier to loop and traverse through the TableView dynamically and interacting with the elements inside the TableView easily.
I noticed the Hybrid api-reference document has a method called "getRowCount" but it works with Web.(uint rowCount = this.ActiveDevice.Web.GetRowCount(Elements.MyScreen.WebView.TableView);)
Is there anything similar for iOS and Android?
Thanks,
Ajinkya
There are user scenarios in which load testing http requests can be data driven with predefined and known data. In such case there will be no need of a dynamic target taking data from a previous http call to pass the necessary data.
It will be useful to add the ability to directly data drive the http request parameters.
Please add the possibility to edit multiple test lists' settings at the same time and create new test list with already predefined settings.
This will make it easier to maintain my project.
Currently the results view in Test Studio only shows results from the Results folder in the project. Please add an option to change this path to a different folder or navigate through the different results in subfolders.
Hello,
Is it possible to use SetExtractedValue or an equivalent/alternative method available in teststudio mobile?
We used that method in Teststudio web to verify entered data in later steps. We've checked the documentation but couldn't find anything like it.
In this case we want to create a test for a webshop. In this test we add an article to our shoppingcart, in every step in the order process we want to verify that the article has the same price and amount.
Kind regards,
Martien van Steenbergen
Hi,
In my test scenario, I am logging into various applications with different usernames and passwords. Test scripts are bound to external data source (xml file) which stores each application credentials.
I don't want to explore these details in the test/test list results, but currently everything in the data source file is logged. Please find a solution.
Explore the possibilities to integrate with third party email services like SendGrid - this uses a username which is not a valid email. Thus the current implementation of the SMTP settings in the Scheduling configuration cannot be used to send an email.
It would be useful to have a method where you could specify global/environmental variables/parameters that is separate and independent from the data driven feature. These global parameters would be avalaible to all tests using the Data Driven interface of binding values to test steps, but would not be mingled in the data source itself. This way you can create a data driven test that runs iterations but keep the environmental static data e.g. userid's to login as, separate from the data itself.