Document toolboxDocument toolbox

Header

OV_Add Web Application or SFDC Objects

Owned by Shruti Agrawal
Last updated: May 23, 2024
6 min read

Add web Application Objects

Choosing between Image Objects and Mouse Hover can largely depend on the specific context and requirements of the application under test. Here are a few use cases that might help clarify when to choose one over the other:

  1. Image Objects: If you're dealing with an application that relies heavily on images for functionality or user interaction, using image objects might be the preferred method for testing. For example, consider an online retail website with a catalog of products displayed as images. Users are expected to interact with these images to view product details or add items to their shopping cart. In this case, it would be beneficial to add these images as image objects to ensure they load correctly, are interactive as intended, and lead to the correct product information when clicked. However, be aware that image-based testing can be less reliable than testing based on properties or attributes of objects, as images might change more frequently or be affected by screen resolution or color settings. It's also more resource-intensive, as comparing images or searching for image patterns is computationally expensive.

  2. Mouse Hover: If your application includes elements that only become visible or interactive when the mouse pointer is placed over them (hovered), then using the Mouse Hover function during testing is necessary. For example, consider a website with dropdown menus that only appear when you hover over a menu item. To thoroughly test the functionality of these dropdown menus, you would need to use the Mouse Hover function in the testing process. Similarly, many websites display additional information or options when you hover over certain elements, like a product image that shows more details when hovered over. Again, to test these hover-based interactions, you'd need to use the Mouse Hover function. It's worth noting that hover interactions might not be accessible on touch devices, as there's no cursor to hover with. If your application is primarily intended for touch devices, testing hover functionality might not be as important.

In conclusion, your choice between Image Objects and Mouse Hover depends on the specifics of the application you're testing. For comprehensive testing, you would ideally want to use a mix of both, depending on the context, to ensure all aspects of the application are thoroughly tested.

A vital note about Qualitia Smart Locator:

Smart Locator has the capacity to automatically identify dynamic objects during the execution of a test case. If this option is enabled, you won't be able to edit object details such as the locator value and locator type.

If you choose to disable this option, the object will no longer be identified by Smart Locator. If you wish to re-enable this option for this object at a later stage, you'll need to either learn this object anew using Qualitia Object Spy or specify a valid XPath for the object. The object will be re-enabled for Smart Locator identification only after its first execution.

If you see a Light Bulb icon next to an Object, it indicates that the Smart Locator is used to identify the Object.

You have the capability to include an object from a web application currently under test with just a single click. You can then choose the type of locator that best suits your needs. Qualitia additionally offers you the flexibility to include objects in the form of an image object.

Below is the standard sequence for incorporating objects for a typical Web application:

  1. Link

  2. Name

  3. ID

  4. XPath

  5. CSS

For SFDC (Salesforce) applications, the standard sequence differs slightly and is as follows:

SFDC: Label

  1. Link

  2. Name

  3. ID

  4. XPath

  5. CSS

When dealing with image objects, the locator type defaults to Image. You have the autonomy to modify this locator type sequence in alignment with your specific needs.

The last locator precedence will be stored and when you login for the next time, the same locator precedence will be defaulted.

📚Prerequisites

Before moving forward, please confirm that

  1. Your computer has connectivity to the Qualitia Server.

  2. In the scenario of adding objects from a Salesforce application, it's crucial to ensure you've selected a Salesforce project. Salesforce applications are best viewed/added via the Chrome ObjectSpy as Salesforce applications are not fully supported on Edge.

Adding Objects

Add Web Application Objects (excluding image objects)

The inclusion of web application objects (excluding image objects) involves the following steps:

  1. Login to QAS - Client <insert Screenshot>

  2. Access Develop from left navigation of your QAS - Client to view Test Explorer screen.

  3. Initiate either the Edge or Chrome ObjectSpy. For an in-depth guide on launching a web ObjectSpy, please refer to Launching ObjectSpy.

  4. Ensure you are in Learn Objects Tab. <insert Screenshot>

  5. Enable Hover mode, as shown in the screenshot. <Screenshot>

  6. Position your mouse pointer over the object and once the object details are highlighted, click on it.

  7. This action will result in the object being added to the list in the ObjectSpy window.

  8. If you prefer to edit or delete any of the existing objects in the session, hover on the added Object in ObjectSpy window.

  9. You will see three options:

    1. Edit

    2. Highlight

    3. Delete

  10. Click the Edit (Pencil) icon adjacent to the object you intend to modify.

  11. You can edit

    1. Name: Name of the Object

    2. Class: Class of the Object

    3. Locator Type

    4. Locator Value

  12. If you prefer to change the object with another object, click Update Object icon.

  13. The section will change to light orange color to give the feedback that the Update Object mode is on.

  14. Click the new Object you wanted to replace; the object will be updated.

  15. After making the necessary changes to the object details, click Save.

  16. Once all the changes are made, click Save To Repository to update the changes.

  17. At the bottom of the screen, you can see the number of objects from this page added to the repository.

Add Image Objects

When it comes to integrating image objects, the process is as follows:

  1. Login to QAS - Client. <insert Screenshot>

  2. Access Develop from left navigation of your QAS - Client to view Test Explorer screen.

  3. Click Objects icon from extreme right of the toolkit.

  4. You will see Object Repository.

  5. All the objects will be listed.

  6. Initiate ObjectSpy. For comprehensive guidelines on how to launch a web object spy, please refer to Launching Object.

  7. Ensure you are in Learn Objects Tab. <insert Screenshot>

  8. Input the URL of the application you're testing into the address bar.

  9. Activate Image mode, as illustrated in the screenshot. <include screenshot>

  10. Choose the image you wish to include using the drag and drop method and set the position of the pointer by clicking on the image.

  11. The image object will then be added to the list in the ObjectSpy window.

  12. Hover on the object that you want to edit.

  13. You will see three options

    1. Edit

    2. Highlight

    3. Delete

  14. Click the Edit (Pencil) icon adjacent to the object you intend to modify.

  15. You can edit

    1. Name: Name of the Object

    2. Class: Class of the Object

    3. Locator Type

    4. Locator Value

  16. if you prefer to change the object with another object, click Update Object icon.

  17. The section will change to light orange color to give the feedback that the Update Object mode is on.

  18. Click the new Object you wanted to replace; the object will be updated.

  19. After making the necessary changes to the object details, click Save.

  20. After incorporating all the necessary objects, click Save to Repository.

  21. Your objects will be stored in the repository, as shown in the relevant screenshot.

  22. It is suggested that you use the Web Object Spy in either left dock mode or right dock mode. However, if you prefer using it in a different dock mode, you can simply click the Hover/Image button to commence usage.

Duplicate objects are not allowed.

The object will be locked for any edits if any user or you for that matter is trying to edit the Object in Object Repository and trying to edit it using the Object Spy.

 

Highlight Objects

  1. Login to QAS - Client <insert Screenshot>

  2. Access Develop from left navigation of your QAS - Client to view Test Explorer screen.

  3. Initiate either the Edge or Chrome ObjectSpy. For an in-depth guide on launching a web object spy, please refer to Launching ObjectSpy.

  4. Ensure you are in Learn Objects Tab. <insert Screenshot>

  5. Hover on the object that you want to edit.

  6. You will see three options

    1. Edit

    2. Highlight

    3. Delete

  7. Click Highlight icon.

  8. The object that was used will be highlighted in the browser window.

💡Golden Nuggets: Best Practices for Object Management

  • Please note that the screen resolution where optimum UX for Object Spy will work would be 884px x 675px.

📞📚 Here to Help: Support and Resources

Need a helping hand? Don't hesitate to reach out to your Qualitia Relationship Manager. For more resources, our official Qualitia documentation and community website are just a click away!

Footer