OV_Leveraging Advanced Options in Application Launch with Qualitia

With Qualitia, you have the capacity to set certain capabilities while initiating the testing application. These are known as Appium capabilities, allowing you to modify the application session according to your requirements.

Here are examples of some advanced capabilities you can employ while launching the application:

1. NoReset: This capability enables you to reset the application before starting the session. For instance, if you want to start with a fresh instance of the app for every test run, you can set the noReset capability as true (Boolean). This capability is particularly useful when you are testing user data persistence across application restarts. For example, imagine you are testing a shopping app and you've added some items to your cart. If you want to verify that the items remain in the cart after the app restarts, you would set the noReset capability to false. On the contrary, if you want to ensure that each of your test sessions starts with a clean state without any leftover data from the previous sessions, you would set the noReset capability to true.

2. IntentAction: This corresponds to the intent action employed to initiate an activity. Each application might have its unique intentAction, which should be supplied by the app developer. For example, if your app needs to view a specific file at launch, you could use the android.intent.action.VIEW intentAction. Let's consider you are testing an email client app. If you want to test the functionality of drafting a new email directly from another app or a notification, you might use the android.intent.action.SEND or android.intent.action.SENDTO intentAction, which is designed to support sending emails. Another example could be testing the dialing functionality of a phone app using android.intent.action.DIAL or android.intent.action.CALL.

3. intentCategory This is the intent category used to start an activity. This information is usually provided by the app developer. For example, if your app's main activity should be listed as a launcher, the developer might use the android.intent.category.LAUNCHER intentCategory. If your application can handle different types of data, your app developer may provide different intent categories. For instance, an image editing app might have different categories like android.intent.category.OPENABLE for opening existing files or android.intent.category.APP_GALLERY for opening images directly from the gallery.

4. chromeOptions This capability allows you to personalize and configure a ChromeDriver session. For a full list of ChromeDriver capabilities and how to use them, you should refer to the chromeOptions documentation. For instance, if you want to run tests in a headless Chrome browser, you can use the 'args=–-headless' chromeOption. Suppose you're testing a web application on a server without a graphical interface or you want to save resources during testing, you could use args=--headless to run tests in a headless Chrome browser. Another scenario could be if you're testing how your web application handles pop-ups, you could use the args=--disable-popup-blocking chromeOption to disable Chrome's popup blocking feature during your tests. If you're running tests in parallel and want to avoid cache or cookies shared across sessions, you could use the args=--incognito chromeOption to start each test in a new incognito window.

To implement these advanced options when launching an application:

1. Initiate the Mobile Object Spy and select the application you're testing.

2. Click on Advanced options.

3. From the drop-down options, select the capability and input the corresponding value.

4. Click on Add Capability to finalize.

Examining Page Source and Object Properties with Qualitia

Qualitia gives you the ability to review the page source of your application under test. This feature helps you understand the object hierarchy, which can be beneficial in structuring your test automation workflow.

Moreover, Qualitia allows you to add objects directly from the page source view of your testing application. You can also view the properties of a selected object within the page source.

Here's how to access the page source and object properties:

1. Start the Mobile Object Spy and either install or launch the application you're testing.

2. From the right panel, click on Page Source. This action will open a new section displaying the page source.

3. Hover over the object in the page source that you'd like to add and click on the Add Object icon. For example, you might select a "Submit" button on a form within the app.

4. The chosen object will then appear in the Object Repository section of the right panel.