Clicknium provides the automation technology in a variety of scenarios with different forms, such as SAP automation, Java automation, Windows desktop automation and image automation. I would like to share the automation technology in Clicknium.
Regarding software automation technology, it was mainly used for software testing in the very beginning, especially for UI automation testing. Many system software designs take the accessibility of disabled users into account. See windows accessibility. In recent years, RPA (Robotic Process Automation) has been accepted by more and more enterprises. RPA plays a great role in multiple business field scenarios to optimize the process, reduce costs and increase efficiency, and quickly improve the level of informatization. RPA products generally include automated operation components for various software, data processing components, process logic control components, etc., among which UI automation components are the mostly used.
Windows applications include a functional design: Accessibility, which allows more users to operate the software. For example, allow the blind users to read the screen through their voice, etc. The UI automation technology provided by Microsoft can access the control elements of the windows application. The main technologies are as follows:
- UIA (UI Automation) UI Automation provides programmatic access to information about the user interface (UI) for Microsoft Windows, enabling assistive technology products (such as screen readers) to provide information about the UI to end users using means other than standard input and Manipulate UI. UI Automation also enables automated test scripts to interact with the UI.
- MSAA（Microsoft Active Accessibility） Microsoft Active Accessibility was the application accessibility solution from Microsoft earlier.
|Programing Languages||Written in managed code, client applications are most easily programmed using C#||based on the Component Object Model (COM) with support for dual interfaces.|
|Windows Presentation Foundation||full support||WPF do not contain native support for MSAA|
|Servers and Clients||a core service between the server (called a provider) and the client, providing more information to the client||servers and clients communicate directly, largely through the server's implementation of IAccessible|
|Security||UIA removes the need of providers to call through to other provider code. The UI Automation core service does all the necessary aggregation.||Some IAccessible customization scenarios require wrapping a base IAccessible and calling through to it. There is a potential security risk, since a partially trusted component should not be an intermediary on a code path.|
If you are interested in Windows automation technology, you can directly go to Microsoft's official technical documentation.
Java Access Bridge is a technology that exposes the Java Accessibility API in a Microsoft Windows DLL, enabling Java applications and applets that implement the Java Accessibility API to be visible to assistive technologies on Microsoft Windows systems. Java Accessibility API is part of Java Accessibility Utilities, a set of utility classes that help assistive technologies provide access to GUI toolkits that implement the Java Accessibility API.
To learn more about JAB, please visit oracle
Web automation mainly depends on the type of browsers, and currently, there are two main categories:
Due to different versions of IE, it is still a technical issue to make multiple versions of IE compatible.
There are generally three ways:
- Selenium webdriver To learn more about webdriver, please visit WebDriver, Chrome webdriver.
- Chrome devtool protocol(CDP) Since CDP is used in many tools, you can refer to awesome-chrome-devtools. Related to web automation testing, they are Puppeteer and Playwright. The playwright's python code to start the Chrome browser is as below:
browser = p.chromium.launch(channel="chrome", headless=False) context = browser.new_context() # Open new page page = context.new_page() # Go to https://www.google.com/ page.goto("https://www.google.com/")
With ProcessExplorer, you can see that Chrome starts the parameters as follows.
"C:\Program Files\Google\Chrome\Application\chrome.exe" --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=ImprovedCookieControls,LazyFrameLoading,GlobalMediaControls,DestroyProfileOnBrowserClose,MediaRouter,AcceptCHFrame,AutoExpandDetailsElement --allow-pre-commit-input --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --no-service-autorun --export-tagged-pdf --no-sandbox --user-data-dir=C:\Users\test\AppData\Local\Temp\playwright_chromiumdev_profile-V3LZUg **--remote-debugging-pipe** --no-startup-window
According to the chrome startup parameter description:
--remote-debugging-pipe: Enables remote debug over stdio pipes [in=3, out=4]. Optionally, specifies the format for the protocol messages, can be either "JSON" (the default) or "CBOR"
- Native messaging Extensions and apps can exchange messages with native applications by an API similar to the other message passing APIs. Native applications that support this feature must register a native messaging host knowing how to communicate with the extension. Chrome starts the host in a separate process and communicates with it using standard input and standard output streams. More about Native Messaging, please visit this link.
As SAP provides script automation officially, most RPA products automate SAP applications based on their own automation technology.
In addition to the above native automation technologies, the following automation technologies are generally used to achieve hybrid automation.
- Image recognition, shortcut keys
- Screen word picking
- Computer vision
- Windows Native API
With the automation technologies above, Clicknium offers development tools that allow users to:
- Capture UI elements and store them as locators or selectors.
- Automate all kinds of applications with a single Python API.
- Higher efficiency in writing code with locator IntelliSense. In addition to the automation technologies above, we also add other enhancements:
- Combine various automation technologies to increase robustness.
- Find the UI component with a fast searching algorithm.
- Algorithm for generating locators.
You can visit Clicknium Visual Studio Code Extension change log to see more functions.