Custom WPF app cannot be automated as the recorder crashes the application. Currently I am unable to login and cannot provide details if the recorder can be attached to the running instance. Details shared internally!
Step up/ Step down is not working as it should. To be able to choose value we should set initial one first.
Using FF - The popup is recognized and recorder is being attached to it but no actions inside get recorded, highlighting cannot be activated at all and the DOM tree is not displaying all elements. When executing a test recorded properly the popup gets closed immediately after it is opened and no actions can be executed against it. Using Chrome and IE - Recording and execution works as expected. Further details shared internally!
We have tens of fields on 100s of our scripts, it will be too laborious and not efficient to enter verification step for each field (text box, drop downs, radio buttons, etc.). We would like Telerik software to improve and detect automatically if it was able to enter the data in a particular field. If not, the script should error out like it does when a field (element) is not found.
steps to reproduce: 1. Open the test in the sample project. 2. Check the target elements' find logic for step 2 and 3 - these are modified to use TextContent for the html anchor. 3. The target elements in step 4 and 5 are the same - recorded in a second recording session. Expected: To record steps against the same elements already existing. Actual: Two new elements are recorded with TagIndex used.
Steps to reproduce: 1. Open the sample project and run the test to the step before while. 2. Once the recorder is attached please select to run the while step only Actual: The cycle is being executed once although the condition is not met Expected: To run the cycle until the condition is met Details shared internally!
Steps to reproduce: 1. Create a Verify element Exists and Wait for element exists steps 2. Converting both to code generates Pages.Element.Wait.ForExists(30000); Expected would be that the Verify element Exists step rely on the global project elements timeout or alternatively verifies immediately. Actual: The current implementation is that the Verify step takes the default wait timeout for a wait step.
Steps to reproduce: 1. Create a sample project and add the following steps: - Verify element Exists - Verify element ExistsNot - Wait element Exists - Wait element ExistsNot 2. Convert these to code and double check that the ExistsNot steps refer to an element with the current find expression. In contrary the Exists steps refer the element from the Pages file directly. That way editing the find expression of the element will be updated and referred in the Exists steps. But the ExistsNot steps in code should be manually updated. Expected: The elements in all converted steps to be referred from the elements' repository.
The options optionally provided to the command line runner related to publish results to TFS are not working correctly with the new builds in TFS 2017 vNext.
Multiple customers reported that after applying a Windows update KB4041676 on a windows 10 system all excel files bound as data source in a Test Studio project stopped working as expected - the file stayed bound but no tables appear to select any of these. It would be good to investigate what that update causes.
1. Create a new WebForm project, build it, no AWSSDK.Core.dll in the bin folder. 2. Converted the project to a "Telerik UI for ASP.NET AJAX" project, build it, and now the AWSSDK.Core.dll and AWSSDK.S3.dll are added to the bin folder. Expected: These are not required outside of Test Studio.
1. Start recording a test against it and click over the cells in grid. Note that the first step is recorded against an element relying on TextContent. Each next element relies on AutomationID. 2. Run the test. Expected: To run successfully. Actual: Only the first step is being successful since the automationIDs are not present in the DOM tree. Note: The application does generate the automationIDs when started. They are only not present in the recorder DOM tree before a click is performed. Sample app shared internally.
I am unable to capture Load scenario traffic, from an existing web test, on Server 2012 R2 machine, running Test Studio version 2017.2.615.0 I am attaching the screenshot of what I am getting in each browser. It appears to be a certificate issue possibly.
Using Windows Server 2016 cannot run tests remotely. The configuration is correct and clean, no firewall, no AV, unblocked ports. Although remote execution does not start at all. The issue was observed by two customer's environments.
Mobile testing is not super steady in recognising elements, and as a result often taps the wrong element. A way to improve this could be the add a way to tap an element with a specific text (i.e a button).
In two attached test projects TestProjectForTelerik_BigReport and TestProjectForTelerik_SmallReport the same test actions are executed (tests set is the same too but there are some differences in test configurations). 1. Load www.telerik.com page 2. Come back to the main page 3. Click on a link to the products. The link is found by content (product's name) from data source (TelerikProducts.xls file, Products sheet) But different ways are used to run tests in the projects. In TestProjectForTelerik_SmallReport we start from SmallReportTest (use SmallReport test list from the project) and bind ClickProduct test to the data (the data source) directly. In TestProjectForTelerik_BigReport we start from BigReportTest (use BigReport test list from the project) and bind IntermediateStep test to the data directly. Data binding is removed from ClickProduct test but this one must inherit the parent data source. In IntermediateStep test we choose which test will be run next according to data from data source. In IntermediateStep we always run ClickProduct test. Please see comments in the IntermediateStep test for more information. This way is very needed for my real project. So, these two projects have very different report size for the small report it is 249674 bytes, for another 989670 bytes. The difference is about 4 times. If steps count in ClickProduct test or row count in data source increases, size difference will be more. As I can see in the report from TestProjectForTelerik_BigReport project, there are a lot of duplicated information in the report. The information from StepResults section of ClickProduct test is duplicated in DataIterationResults section of IntermediateStep test. Please check this. Maybe there is a way to decrease the report size. Resources shared internally
Steps to reproduce: 1. Select edit in live within element repository, and choose "select step" to locate element in live UI. 2. Once i choose that step from the list of tests it provides, TS executes everything up to that step AND that step itself. This can be an issue since that step is often clicking a link/button and opening a new page, where TS is unable to validate against since the element was only visible on previous page. Is it possible to make sure TS only executes the steps up until that selected step? so that when I try to validate against the live UI, the element should still be visible? Thanks!
Specific application modal popup is not handled properly Project and details shared internally.