Shield for user interface testing
Real user input targeting an application under test is blocked to prevent interference with a test. A shield window can be placed in front of an application-under-test window to intercept input destined for the application. Users can be notified of interception or a failed attempt to access the application. Furthermore, the shield window can be employed to provide feedback about the test including pointer movement and area focus.
1. A test shield system, comprising:
a processor coupled to a memory, the processor configured to execute the following computer-executable components stored in the memory:
a generation component configured to generate a shield window; and
a position component configured to position the shield window in front of an active application-under-test window to intercept user input destined for the application under test.
2. The system of claim 1 , further comprising a location component configured to identify a screen location of the application to facilitate positioning of the shield window.
3. The system of claim 1 , further comprising a notification component configured to notify a user that input was intercepted.
4. The system of claim 1 , the shield window is transparent.
5. The system of claim 4 , further comprising a feedback component configured to provide test feedback on the shield window.
6. The system of claim 5 , the feedback includes position and/or movement of a pointer or cursor as a function of test activity.
7. The system of claim 5 , the feedback includes identification of test focus area that includes an active element under test.
8. The system of claim 5 , further comprising an interface component configured to enable tests to provide information about test progress in the shield window.
9. A method of reliable application testing, comprising:
employing at least one processor configured to execute computer-executable instructions stored in memory to perform the following acts:
deploying a transparent window in front of an active application-under-test window; and
blocking an input device message bound for the application under test with the transparent window.
10. The method of claim 9 , further comprising determining size and location of the application-under-test window.
11. The method of claim 9 , further comprising repositioning and/or resizing the transparent window in response to changes in the application-under-test window.
12. The method of claim 9 , further comprising notifying a user that the input device message was blocked.
13. The method of claim 9 , further comprising providing test feedback in the transparent window.
14. The method of claim 13 , further comprising:
monitoring the application under test; and
presenting graphic representations of test actions in the transparent window.
15. The method of claim 14 , comprising animating pointer movement, and/or highlighting an area of test focus.
16. The method of claim 13 , further comprising receiving the feedback from a test.
17. The method of claim 9 , further comprising indicating to the application-under-test window that it is in the foreground despite the transparent window residing in the foreground.
18. A method that facilitates user interface (UI) testing, comprising:
employing at least one processor configured to execute computer-executable instructions stored in memory to perform the following acts:
intercepting a pointer or keyboard message destined for an active application-under-test window with a transparent window positioned over top of the application-under-test window; and
providing test feedback through the transparent window.
19. The method of claim 18 , further comprising notifying a user that the message was intercepted and failed to reach the application.