Poco UI Automation Framework

The Player class in lib/player.py is used to abstract and isolate game-related behaviors (character actions, etc.) from specific libraries like hunter, poco, or airtest. This isolation allows for easier framework upgrades.

Key components:

• PROCESS: A variable representing the Hunter project code (e.g., 'g62').
• NeteasePoco: Used via the poco property to interact with the game UI.
• Singleton: The Player class is implemented as a Singleton to ensure a single instance manages the connection.

Example implementation structure:

# coding=utf-8
import sys
import re
from airtest_hunter import AirtestHunter, open_platform, wait_for_hunter_connected
from poco.drivers.netease.internal import NeteasePoco as Poco

PROCESS = 'g62'  # hunter project code

class Player(object):
    __metaclass__ = Singleton

    def __init__(self, hunter=None):
        self._hunter = hunter or get_hunter_instance()
        self._poco_instance = None

    @property
    def poco(self):
        if not self._poco_instance:
            self._poco_instance = Poco(PROCESS, self._hunter)
        return self._poco_instance

    @property
    def hunter(self):
        return self._hunter

    def refresh(self):
        wait_for_hunter_connected(PROCESS, timeout=16)
        self._hunter = get_hunter_instance()
        self._poco_instance = Poco(PROCESS, self._hunter)

    def server_call(self, cmd):
        self.hunter.script(cmd, lang='text')

When UI elements lack static names (common in programmatically generated lists), Poco allows you to select elements using multiple criteria. You can chain or combine the following selection methods:

1. Attribute Selection: Select elements based on existing attributes.
2. Hierarchy Relationship: Use methods like .child() or .offspring() to navigate the UI tree.
3. Positional Relationship: Access elements by their index in a collection (e.g., items[0]).

These methods can be chained together to create complex selectors for specific UI nodes.

# coding=utf-8

from poco.drivers.unity3d import UnityPoco

poco = UnityPoco()

# Chaining hierarchy methods: find 'main_node', then its 'list_item' children, 
# then the 'name' offspring of those children
items = poco('main_node').child('list_item').offspring('name')

# Accessing by position
first_one = items[0]
print(first_one.get_text())
first_one.click()

Supports Cocos Creator 2.2.1 or higher.

1. Clone the poco-sdk repository.
2. Copy the cocos-creator/Poco folder to your project's JavaScript folder.
3. Enable WebSocketServer:
   • Locate your engine's ccConfig.h (e.g., .../CocosCreator_2.2.1/resources/cocos2d-x/cocos/base/ccConfig.h).
   • Change #define USE_WEBSOCKET_SERVER 0 to #define USE_WEBSOCKET_SERVER 1.
4. Initialize: In your game's first initialized script (e.g., inside onLoad), require the Poco module and assign it to the window object to prevent it from being destroyed.

Note: Currently only supports Android and Windows platforms. Poco is only available after packaging and is not available in preview mode.

Example Usage:

cc.Class({
    extends: cc.Component,

    onLoad: function () {
        var poco = require("./Poco") // use your own relative path
        window.poco = new poco(); // do not destroy
        cc.log(window.poco);
    },
});

cc.Class({
    extends: cc.Component,

    .....

    //remember to put code in onLoad function
    onLoad: function () {
       .....

            var poco = require("./Poco") // use your own relative path
            window.poco = new poco(); // not destroy
            cc.log(window.poco);

        },

       .....
    });

Automated testing should be treated as an engineering project rather than discrete scripts. Use the following directory structure to ensure long-term maintainability and IDE support (like PyCharm autocomplete):

─ my_testflow/
    ├─ testflow/            <------- Rename this to a valid identifier (e.g., g18)
    |   ├─ __init__.py
    |   ├─ lib/
    |   |   ├─ __init__.py
    |   |   ├─ case.py
    |   |   └─ player.py
    |   └─ scripts/
    |       ├─ __init__.py
    |       ├─ test1.py
    |       └─ folder/
    |           ├─ __init__.py
    |           └─ test2.py
    ├─ res/
    ├─ pocounit-results/
    ├─ setup.py
    ├─ requirements.txt
    └─ .gitignore

Directory Roles:

• testflow/lib: Contains common code modules and libraries.
• testflow/scripts: Contains all test case scripts.
• res: Stores resource files.
• pocounit-results: Stores execution results.