Ving.md

Features of ATMOSPHERE you may find useful

• You can take a full advantage of the ATMOSPHERE framework by using its distributed architecture.

  • You may execute the test remotely by changing the IP on the @Server annotation or create/modify the config.properties file. To connect remote Agent to a Server use runAgent command with CLI arguments.
  • You may use the Server and the Agent on separate machines.
  • You can connect multiple agents to the Server. Each Agent can handle up to 14 devices.

• Use the atmosphere-ui-viewer to dump the UI elements. Also you may find its remote control options useful.

  See: atmosphere-ui-viewer

  git clone https://github.com/MusalaSoft/atmosphere-ui-viewer.git

  cd atmosphere-ui-viewer

  ./gradlew build (build the project)

  ./gradlew run (starts the atmosphere-ui-viewer application)

• The VING Android App is actually a web view. You can use the WebView class from ATMOSPHERE project and debug the HTML with chrome://inspect/#devices on Chrome browser.

  See: WebView usage

  See: WebView integration tests examples

  See: Remote web view debugging

• You can easy get a list of all available devices: testBuilder.getAllAvailableDevices();. No need to execute adb device command. ATMOSPHERE will get all available remote devices for you.

• In some cases it is useful to have video records for the test execution on a device. Use .startScreenRecording() and .stopScreenRecording() to record the device screen during the test execution. The records will be created on the ScreenRecords folder on the Agent root directory. Additionally you can create an FTP server and setup ATMOSPHERE to use it. All the screen records will be automatically uploaded to the FTP Server (tested on vsftpd(recommended), ProFTPD, Windows IIS FTP, FileZilla).

  • agent.properties file: set ftp.server = true (Agent directory)
  • set the ftpserver.properties (Agent directory)
  • set the FTP connection properties - config.properties(test project working directory)

• Sometimes it is useful to see the remote device logCat. Use .startLogcat(), .stopLogcat() for remote debugging and live logCat logging on the client's console.