When qTest Explorer records your application, it tries to recognize every UI element that you took action on it to generate a descriptive capture action, or step. For example:
- You clicked on a button having a label Submit, qTest Explorer produces "Click on Submit button"
- You entered email@example.com to a text box having a label User name in front of it, qTest Explorer produces "Type firstname.lastname@example.org in User name text box"
- You clicked on a Save menu item, qTest Explorer produces "Click Save menu"
- You clicked on a hyperlink having a text Go to QASymphony, qTest Explorer produces "Click Go to QASymphony link"
- And so on
In order to produce those descriptive and meaningful capture actions, qTest Explorer must be able to recognize the UI elements in your application. In other words, qTest Explorer must be able to identify a button, a text field, a radio button, a menu item, etc. that you took action on it.
Every Desktop or Web application is built with a specific UI Framework containing a set of UI elements. Each UI Framework can be either free or commercial.
Below are UI frameworks that qTest Explorer is able to recognize, we call it the qTest Explorer Supported UI Frameworks
- MFC elements
- Win32 elements
- Winforms.NET elements
- WPF.NET elements
- Java desktop app built with
- Standard Widget Toolkit (SWT) elements
- Swing elements
Desktop and Web Explorer
- HTML 5 elements
- jQueryUI elements
- KendoUI elements
- Dojo elements
- Sencha elements
Frequently Asked Questions
1. Why does Explorer produce "Click 'here'" after I clicked on a button, a hyperlink, a menu item?
- The button or hyperlink or menu item that you took action on might not actually be marked up, or rendered, as a standard button, hyperlink or menu item. The application developer might use other UI elements, such as a panel, a rectangle, a HTML <span>, <p>, <div> tag, or even an image, and might also apply some styles to make it look like a button or a hyperlink or menu item.
2. Our application is built using a UI framework that Explorer claims to support it, but Explorer still produces "Click 'here'" or "Type 'here'" on some UI elements
- Although your application is built with a UI Framework that qTest Explorer is supposed to be able to recognize it, the application developer still have customized some UI elements that made it become 'unknown' elements to Explorer. For example, your web application uses standard HTML 5 elements to render the page, and you find an element looks like a hyperlink. However, underlying it might not be marked up with a standard <a /> tag, but a <span> or <p> or <div> tag with some styles applied to it, e.g. text decoration is set to underlined, and text color is set to blue, like this one I am not a hyperlink although I am underlined and blue
3. Our application is built using a UI Framework that qTest Explorer does not recognize it. What can I do?
- Let us know what UI Framework is used to build your application. If we can download the showcase (or the demo) of that UI Framework somewhere from the internet then we could train qTest Explorer to recognize it
- Sometimes it's tricky for us to add support for unknown or commercial UI Framework. If this is your case, can you share or allow us access to your application to inspect the UI elements and build a customized mechanism in qTest Explorer to recognize them?