On the Executive Dashboard, the columns are all fixed sized, the problem with this is that it gives very little space for test and test list names and makes it difficult to view the naming.
Please provide a way to resize or view the names easily.
When one schedules a test list and the tests execute with the rerun failed tests option, there is only a limited number of things that can happen.
1) a test may pass.
2) a test may fail once but pass the second time.
3) a test may fail twice.
4) a test may not run.
My suggestion is that, if these are the four types of result, report only this.
When you say this:
Run Summary: 25 of 25 test(s) run; 22 passed, 3 failed, 0 not run.
there is ambiguity. It is not clear what happened. It could instead say:
Run Summary: (#) test(s) run, (#) passed, (#) failed but then passed, (#) failed twice, (#) not run.
If the summary is in the second form, there is no ambiguity.
It would be helpful extract the current selected value of a RadDropDownList, so it can be compared to the expected value. This is commonly used to verify if the selection was successful.
Please consider adding such extract steps for other similar controls.
Once you connect to a pop-up window, you can not switch back to the previous one, until the pop-up is closed. Some test scenarios will benefit from the possibility to switch back and forth.
Please consider this feature for next releases.
Currently, when a step in the API test fails, the whole test is stopped.
Please add the continue on failure option for steps in API project.
The ScrollToVisible option is not available for some of the actions that use translators. One of them is the RadSearchBox, where this property is not available.
Currently the workaround is to add an Enter text step against the <input> element. To do that, you need to use the highlighter and record any verification step. Then add the Enter text step from the step builder, enable SimulateRealTyping and change the ScrollToVisible option.
The Keyboard (KeyPress) test step is missing the option to change the ScrollToVisibleType in the properties pane. Although the step actually performs the scroll to visible action and I see the code, when I select Edit in Code.
Please add the ScrollToVisibleType option.
It will be useful to improve the output data in API test results. Currently the generated results files from an API test run do not contain data for the actual sent and received requests.
The available workaround is to use Fiddler and capture the generated traffic during the API test run.
It would be nice if there was a way to avoid simulating real typing for a search box. There is no option to enable/disable it, but it is clearly using this behavior. I've tried a workaround of entering text directly in the input element, but it doesn't seem to register it when this technique is used. I don't see how a textbox can be made to work without this behavior but a search box cannot.
Simulating real typing tends to be the most fragile part of our tests, and all we really need is to enter text and then search. It also slows down the tests quite a bit vs. just setting the text directly.
Currently when a test step is set to SimulateRealClick or SimulateRealTyping, the target element is unconditionally scrolled to the top of the browser window, even in cases where the element is already visible. It would be more efficient to test if the target element is already fully visible and only scroll when needed.
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