ziniao-webdriver-doc

To automate multi-store browser sessions with the Ziniao WebDriver API, you use POST-based API calls like applyAuth, getBrowserList, startBrowser, and getRunningInfo to provision devices, list stores, and launch automated browser windows across environments.

Integrating Ziniao WebDriver into an automation pipeline requires a locally running Ziniao WebDriver service, POST-based API calls, requestId tracking for session management, and ChromeDriver compatibility determined from the startBrowser core_version parameter.

The startBrowser API handles ChromeDriver compatibility by returning a core_version parameter, which determines the specific ChromeDriver version required to successfully execute automated browser control for that session.

Yes, you can use Ziniao WebDriver to list available stores across different environments by invoking the getBrowserList API, which retrieves the provisioned store list for your local automation and QA workflows.

You track the running status of an automated browser session in Ziniao WebDriver by calling the getRunningInfo API, which reads current execution information and session states using the assigned requestId.