Executing the following code in Chrome does not work: ActiveBrowser.Actions.InvokeScript("document.getElementById('elemenID').click()"); the behavior is the same with the following workarounds: Element.InvokeEvent(ScriptEventType.OnClick); Element.Click(); More details are provided in the internal description.
Test Studio is not recording in <input type="tel"> inputs using JS Browsers. Locate an html using <input type="tel"> and try recording using Chrome or Firefox Problem: values are not recorded. Workaround: Use Internet Explorer for recording such inputs, the execution works as expected
Make a change to Test A, but don't save. Make a change to Test B, but don't save. Revert Test A to the server version. Navigate back to Test B & note that the red checkmark displays next to the test name. Open Test B & note that the pending change was wiped out. A warning message should be displayed to advise users that any unsaved changes will be wiped out if they revert a test to the server version.
Currently if you use a verify step on a <table> element, if the verify fails, you get "Expected count does not match" as an error message for failure information. I think this message should also include a line saying what the expected verified count was, and (or at the very least) an indicator of what the count was that the step failed to. Various things could cause a count to be wrong, and I believe that knowing what the count was at the moment that step failed, would help greatly in debugging these failures.
When using specific find logic for an anchor element there is a problem to locate the proper element during test execution. Steps to reproduce and access to the application are in the internal description.
There is out of memory exception generated when Run - To Here is applied to a step close to the end of the scenario. Steps to reproduce and access to the application are in the internal description.
It would be very beneficial to be able to see all of the failures from my project on a single screen, with from/to date parameters too, and be able to report on failure by type as well.
It will be useful to support ReactNative applications not only partially - in a hybrid test to record the native elements and manually add steps against the web elements.
Steps to reproduce: 1. Open a project and open the Project Settings. 2. Navigate to the Find Logic tab and change the order of the attributes. 3. Click the Cancel button (note the project is not marked as dirty). 4. Open the Settings/Find Logic again. Expected: The order of attributes is the default (ass before any changes were applied and cancelled). Actual: The attributes are in the order changed but cancelled. If the project is reloaded the attributes are back in their initial order.
It would be an useful feature if the desktop web tests could be somehow used for mobile web applications. For example, If these could be converted to a mobile web test or used for automatic recording process.
When open a test project in VS 2015 - Update 3 and try to open test file with no data - the following exception occur: "Object reference not set to an instance of an object." All other test files with data are opened normally. The problem is hard to reproduce. The workaround is to use different VS version or to attach empty data to a test.
All details shared internally!!!
It would be useful if there is a module (a standalone step, or step property, or a new tab in the step UI) which is dedicated for text only. Its purpose should be to provide some notes about any additional settings required or something similar.
To reproduce the problem - first maximize Chrome and then resize the browser in a coded step using the sample line bellow: ActiveBrowser.Window.Move(new System.Drawing.Rectangle(150, 150, 1000, 700), false);
Steps to reproduce and access to the application are in the internal description.