A set of WaitForCondition() methods may be extremely useful. Like:
- WaitForElementVisible() etc.
It also might be pure WaitForCondition() which accepts a condition to wait for.19 votes
TestAPI is a perfect candidate to make available via a NuGet package. I think this will be very helpful for folks to get TestAPI quickly up and running in their test projects.17 votes
Makes sense. Under consideration.
Create a generalized API for fuzzing (as in security testing) of arbitrary payload.12 votes
I'd list to request a Touch inject API for touch applictions in win 7 and window 8 in furture6 votes
I'd like to request a OCR (optical character recognition) api that will allow me to gather text and the respective coordinates on a given control. I believe the MODI api already does this to some extent but does not return coordinates. Here are some proposed members:
Expose API for mocking.5 votes
TreeScope.Children does not work for complex UI's. As a tester I don't (want to) know the structure of the UI but I want to search all elements in the tree not only direct Childrens. Currently I must implement all the stuff again...5 votes
Makes sense. We will cover this in next releases.
Currently TestApi exposes only managed (.NET) interfaces. The proposal is to expose native interfaces (C++) to allow native clients to easily consume the library.5 votes
Convert TestApi to a cross-platform library that can be used on Windows, Mac, Wndows CE, etc.3 votes
Great point. We will make the change
I need support for infragestic controls for UI Automation1 vote
I was trying to get FaultScope working, but when it didn't work as expected I added a call to assert that faults were working, only to be hit with a number of fairly obtuse COR_PROFILER errors.
If I'm gong to convince my current team that the testapi a quality library, then it'd be great if these types of issues were handled a bit better, at least with a mechanism to set the correct settings, and perhaps with an exception getting thrown if a FaultScope were created without the relevant settings being enabled.1 vote
Since we have a start screen (which shows an animation an module loading status) the MainWindow is set to this start screen but not to the real one which will be shown AFTER the start screen. Wait for a specific MainWindow using an automation id something else and not for the first one.1 vote
Use WaitForWindow(automationId, timeout) instead.1 vote
The current TestApi deployment (of v.0.4) is a 19 Mb ZIP file. This is due to the fact that in addition to the bare essentials, the ZIP file contains PDBs, HTML-based documentation, sources, external tools (xUnit), and samples. The proposal is to create a mini-version of the deployment that only contains the DLLs, CHM, and a simple standalone sample.0 votes
- Don't see your idea?