Introduction to Mobile Recorder in Katalon Studio

Device View and All Objects

You can click on any object in the tree of All Objects or in Device View to choose it. For verification, Katalon indicates their equivalent in line with that.

1. Device View simulates the screen of a device. In this view, you can interact with the AUT.
2. The All Objects view collects and arranges all the mobile objects in Device View into a tree.

Source: Mobile recorder

Available Actions

The Available Actions section presents multiple buttons that signify Mobile actions that can be carried out on the AUT. Mobile measures come in two varieties which are object actions and application actions.

1. Object action: To use an object action, you must first choose an object from Device View or All Objects. You can view the activities available for a selected object by selecting it.
2. Application action: An application action can be carried out without a specified item.
   
   
    
3. Tap: Tap a mobile component.
4. Tap and Hold: Tap and maintain pressure on a movable element.
5. Swipe: Act like you're swiping your fingers across a smartphone.
6. Get Text: Retrieve a mobile element's text.
7. Set Text: Position the text on an element that may move. Additionally, it removes the mobile element's previous value.
8. Clear Text: A mobile element's clear text.
9. Scroll To Text: Move the cursor to an element with the specified text.
10. Hide Keyboard: If your keyboard is visible, hide it.

Validate UI elements and recorded actions

You can conduct the Capture Object action by simply right-clicking on any element in Device view or All objects, or you can add the Verify and Wait for keywords as test steps from the context menu. Recorded Actions contain a record of the chosen verification action. Input may require a double-click for some keywords.

Some of the actions are the following:

1. Capture Object: Used to take a picture of something.
2. Check Element Existence: Check to see if a mobile element is available.
3. Verify Element Not Exist: Check to see if a mobile element is there or not.
4. Verify Element Visible: Check if a mobile element can be seen.
5.  Verify Element Not Visible: Check to see if a mobile element is available or not. 

Source: Mobile recorder

The Recorded Actions table provides each recorded action you've taken on the AUT, along with any relevant input or output. Later, these components develop into test stages for your test case. By selecting Add, you can manually add new actions using keywords, remove unneeded actions, and reorder previously recorded actions by selecting Move Up or Move Down.

Captured Objects

All of the things that you interacted with throughout the recording session are displayed under Captured Objects. By double-clicking on an object that Katalon has captured, you can view all of its detailed information in the Object Properties table. The locator method and value of an item are its most crucial attributes. You can select a different locator technique from the options offered if that is what you prefer, and a new locator will be created. To check if your freshly updated locator can successfully find the target object, click Highlight after that.

Frequently Asked Questions

What are the guidelines for designing API tests?

In designing API tests, the five guiding concepts are setup, execution, verification, reporting, and cleanup.

What tools are available for API testing?

Many different API testing tools are available. Katalon Studio, Postman, SoapUi Pro, Apigee, and others are examples of standard tools.

Can TestNG be used in Katalon?

You can convert your test cases from Selenium, TestNG, or JUnit projects to Katalon Studio starting with version 7.4. 0. You may use Katalon to run and maintain your current Selenium, TestNG, and Junit applications without starting from scratch thanks to the supported features and keywords.

Conclusion

To conclude this blog, firstly, we discussed Mobile Recorder in Katalon Studio. Then we saw the action bar, configurations, Device View, and All Objects. Then we debated available actions and validated UI elements, and recorded actions. In the end, we saw captured objects and their primary actions. 

For more content, Refer to our guided paths on Coding Ninjas Studio to upskill yourself. 

Do upvote our blogs if you find them helpful and engaging!

Happy Learning!