# NoSmoke 2.0 Cookbook

NoSmoke is a cross platform UI crawler which scans view trees/conduct ocr operations and then generate and execute UI test cases. Used for smoke testing under continuous integration. Following Webdriver protocol. This document is written as a manual for NoSmoke 2.0.

# 1. Advantages of NoSmoke:

With it you can:

• ✅ Conduct automated UI test with simple configuration and minimum testing scripts manually created.

• ✅ More accurate than monkey test, instead of generate randomised UI test action, crawler analyse current screens potential UI elements and triggers action targeting those elements.

• ✅ One tool, multiple platforms - iOS and Android !! :]

• ✅ Visualise (automation) testing result and validate the testing history via Macaca-Reporter

# 2. How it works?

# From version 1.0

From NoSmoke version 1.0, it relies on retrieving source information from local drivers in xml format.

# From version 2.0

From NoSmoke version 2.0, OCR is introduced to NoSmoke, by retrieving textual information directly from image, previously tons of calculation of xml view hierarchy on driver process has been removed.

# Difference between versions:

# 3. List of Features

# a. Muliplatform

NoSmoke supports UI crawling and testing for iOS, Android, macaca-reporter is used to gather and present the crawling process.

# b. Configurable

Refer to the crawler.config.yml file in the NoSmoke/public folder as a example. You can choose which platform to conduct the crawling task:

desiredCapabilities:
    platformName: 'iOS/Android'
    deviceName: 'iPhone 6 Plus'
    app: '${downloadable address of .ipa/.apk file}'

And the corresponding configuration for crawling the app:

crawlingConfig:
  strategy: 'ocr'
  platform: '${platform: android/ios}'
  triggers:
    - '${prioritised trigger point}'
  exclude:
    - '${exclude text patten}'

# c. Hookable

NoSmoke 2.0 Reduced the number of Hooks provided for app crawling process, which also reduces the cost of integration.

After an certain UI action has been performed, you can intercept the crawling task and manually execute any UI operation. After you are done, you can resume the crawling automation process.

/**
 * Method to perform action for the current platform, invoked when the action is going to perform
 * @Params: action the action which belongs to current active node, user can determine the priority of action execution
 * @Params: crawler the crawler instance which contains the context information as well as crawler config
 * */
Hooks.prototype.onActionPerformed = async function(action, crawler) {
  // password input
  if (action.name == "Enter your MPIN") {

    // here hook provides API for click/type/drag.
    await this.click({'method':'xpath', 'xpath':'${xpath of element}'});
    await this.type({'method':'xpath', 'xpath':'${xpath of element}', 'value': '2580'});

  }
};

Read the following chapters to know how to setup then you can start on different platforms and further customization to fullfil your own desired crawling behaviour.

# Demos

Execution Examples of NoSmoke OCR.

# License

The MIT License (MIT)