CN112445994A - Method for carrying out automatic operation in opened Chrome browser - Google Patents
Method for carrying out automatic operation in opened Chrome browser Download PDFInfo
- Publication number
- CN112445994A CN112445994A CN202011259992.1A CN202011259992A CN112445994A CN 112445994 A CN112445994 A CN 112445994A CN 202011259992 A CN202011259992 A CN 202011259992A CN 112445994 A CN112445994 A CN 112445994A
- Authority
- CN
- China
- Prior art keywords
- extension
- chrome
- browser
- msghost
- chrome browser
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses a method for carrying out automatic operation in an opened Chrome browser. The invention comprises the following steps: compiling a Chrome extension and an MsgHost process; configuring a Chrome browser, and loading the extension written in the step 1: opening a Chrome browser and navigating to an automatic operation page; when the Chrome browser is opened, the Chrome browser can automatically search for extension information in a registry, the MsgHost of extension application is opened in a sub-process mode through the address recorded in the registry, and interface elements needing to be operated are selected in the Chrome browser and the information is stored; compiling an automatic operation case; according to the invention, for the construction of an integral automatic platform, the automatic connection among the systems can be realized, the traditional manual operation is replaced, and the working efficiency is improved; tools for collecting and identifying Chrome web page interface elements and methods for automating the same are provided. The operation of the manual Chrome is realized by using a program in the automation of the business process, and the operation is more convenient and efficient than the traditional manual operation.
Description
Technical Field
The invention belongs to the technical field of RPA automation, and particularly relates to a method for carrying out automation operation in an opened Chrome browser.
Background
Chrome is a web browser developed by Google corporation that is based on other open source software writing, including WebKit, with the goal of improving stability, speed, and security, and creating a simple and efficient user interface. The name of the software comes from a web browser GUI (graphical user interface) called Chrome. The beta test version of the software is released in 2008, 9, 2, and 50 language versions are provided, and Windows, macOS, Linux, Android and iOS versions are provided for downloading. Google will launch an "applet" enhanced web application on google browser Chrome. Chrome browser is characterized by simplicity and rapidness. The Chrome browser supports multi-tag browsing, each tag page runs in an independent sandbox, and the crash of one tag page can not cause other tag pages to be closed while the safety is improved. Furthermore, Google Chrome is based on a more powerful JavaScript V8 engine, which is not currently available with Web browsers.
When a business process is automatically developed, no corresponding solution exists in the industry at present for a system which runs in a Chrome browser, particularly a Chrome browser which is opened. Therefore, after the work of other systems or platforms capable of being automatically operated is completed, the Chrome system which is already opened cannot be directly automatically operated, so that the automatic process of the RPA is broken and the automatic operation cannot be continued.
Disclosure of Invention
The invention aims to: in order to solve the above-mentioned problems, a method for performing automation operation in an open Chrome browser is provided.
The technical scheme adopted by the invention is as follows: a method for performing automation operation in an open Chrome browser comprises the following steps:
s1, writing a Chrome extension and an MsgHost process;
s2, configuring a Chrome browser and loading the extension compiled in the step 1;
s3, compiling a WebSocketServer and communicating with the WebSocket of the MsgHost;
s4, opening the Chrome browser, navigating to the automatic operation page, selecting the interface element needing to be operated in the Chrome browser and saving the information
And S5, writing an automation operation case.
In a preferred embodiment, the Chrome extension is mainly used for acquiring the runtime of the opened webpage, is written in Javascript language, and provides some APIs by a Chrome browser, including input and output communication; the browser defines Background and Content for the opened web pages respectively, the Background and the Content are represented as global Background pages respectively, all the web pages are opened, the Content is loaded as the context of the current web page, and the browser can communicate with an application program through a standard input and output stream.
In a preferred embodiment, the MsgHost is an application program that communicates with an extension; c # writing is adopted, and communication with the extension is realized through input and output streams; the webpage event can be loaded through extension, when a mouse moves to a corresponding webpage, the mouse can be highlighted, an element area and an element position can be obtained, a script program can also be sent to the extension, clicking, rolling, inputting and other operations in webpage interface elements are executed, and meanwhile, in order to transmit the information, the MsgHost also realizes a WebSocket client.
In a preferred embodiment, the MsgHost is implemented by multiple threads; the intermediate adopts message communication, is connected to the WebSocketServer through the configuration of a reading program, forwards the message of the browser standard input stream to the WebSocketServer, and the WebSocketServer processes and saves the actions of information, clicking, keyboard input and the like of interface elements.
In a preferred embodiment, the interface element information includes the webpage, the element type and the position in the interface; the position in the interface has a plurality of description forms, if the ID of the element is found to be unique, the element can be determined by the ID; if the element ID is not unique, the hierarchical relationship of the interface element can be determined through an xpath or css cascading style sheet to be positioned, and the interface element feature descriptor is sent and stored with the WebSocket through the communication input and output stream.
In a preferred embodiment, MsgHost also needs to implement the operation mode of the interface element; triggering operations such as mouse clicking, keyboard inputting and the like on the interface through the interface element descriptors and the corresponding operation actions; the real specific operation execution application is a Chrome extension plug-in, and when the MsgHost receives a corresponding action request, an extension execution Javascript is called.
In a preferred embodiment, the step S2 specifically includes:
step 2.1: opening a Chrome browser, and entering an extension program configuration page through 'more tools- > an extension program';
step 2.2: opening a developer mode in an extension configuration page;
step 2.3: and selecting 'loading the decompressed extension program', and loading the extension program written in the step 1.
In a preferred embodiment, the WebSocketServer is written by C #, serves as a server of the MsgHost, defines various RPC remote calls with the MsgHost, and mainly comprises an interface element storage module and an automation operation module; the interface element storage module is mainly used for defining JSON formatting of interface element information; and the automatic operation module receives JSON formatted interface element information as an operation target parameter and is used for calling an exposed element operation method in the MsgHost.
In a preferred embodiment, in order to determine that the extension is loaded successfully in step 2.3, Chrome queries the relevant information of the extension in the Windows registry at the time of starting. Marking through the extended UUID in the registry, under the affiliated registry entry, having the application program path corresponding to the extension, and opening the extension application in the way of subprocess by reading the corresponding information when the Chrome is started.
In summary, due to the adoption of the technical scheme, the invention has the beneficial effects that:
1. according to the invention, the automation operation with the Chrome browser is realized, and the Chrome browser is opened and is used by an extension enterprise. To build an integral automatic platform, all systems can be automatically connected, the traditional manual operation is replaced, and the working efficiency is improved.
2. The invention provides a tool for collecting and identifying Chrome webpage interface elements and a method for automatically operating the Chrome webpage interface elements. The operation of the manual Chrome is realized by using a program in the automation of the business process, and the operation is more convenient and efficient than the traditional manual operation.
Drawings
FIG. 1 is a flow chart of the present invention;
FIG. 2 is a schematic diagram of Chrome automation in the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Before describing the specific embodiments, the terms referred to herein are first explained as follows:
chrome browser: also known as Google browser, is an open source web browser developed by Google, inc. The code of the present software is written based on other open source software, including WebKit and Mozilla, with the goal of improving stability, speed, and security, and creating a simple and efficient user interface. The name of the software comes from a web browser Graphical User Interface (GUI), also known as "Chrome.
Interface elements: the visual content in the webpage opened by the Chrome browser is usually described by using HTML, and common interface elements include an Input box, a Div layer, an Image element, an a hyperlink element, a Table interface element, and the like.
MsgHost: chrome Native Messaging is a set of extensions and application communication mechanisms defined by google. The extension and application may exchange messages with the native application using an API similar to other messaging APIs. Native applications that support this functionality must register a native messaging host that knows how to communicate with the extension. Chrome will start the host in a separate process and communicate with it using standard input and standard output streams. The MsgHost in this example is an extension program developed by using the mechanism, and besides communicating with the Chrome, the MsgHost also realizes a WebSocket client for forwarding the standard input and output streams of the standard Chrome to an application program.
WebSocketServer: WebSocket is a protocol originally provided by HTML5 for full-duplex communication over a single TCP connection. WebSocket enables data exchange between the client and the server to be simpler, and allows the server to actively push data to the client. In the WebSocket API, the browser and the server only need to complete one handshake, and persistent connection can be directly established between the browser and the server, and bidirectional data transmission is carried out. The WebSocket server is a server implemented by using a WebSocket protocol and is used for receiving two-way communication with the MsgHost.
With reference to figures 1-2 of the drawings,
example 1:
with reference to fig. 1, a method for implementing automation operation in an open Chrome browser includes:
step 1: writing a Chrome extension and MsgHost process, wherein the MsgHost in the step S1 is an application program communicated with the extension; c # writing is adopted, and communication with the extension is realized through input and output streams; the webpage event can be loaded through extension, when a mouse moves to a corresponding webpage, the mouse is highlighted, an element area and an element position are obtained, a script program can also be sent to the extension, clicking, rolling, inputting and other operations in webpage interface elements are executed, meanwhile, in order to transmit the information, the MsgHost also realizes a WebSocket client, and the MsgHost is realized by multiple threads; the middle part adopts message communication, is connected to a WebSocketServer through reading program configuration, forwards a message of a browser standard input stream to the WebSocketServer, and the WebSocketServer processes and stores actions such as information, clicking, keyboard input and the like of an interface element, and the MsgHost also needs to realize an operation mode of the interface element; triggering operations such as mouse clicking, keyboard inputting and the like on the interface through the interface element descriptors and the corresponding operation actions; the real specific operation execution application is a Chrome extension plug-in, and when the MsgHost receives a corresponding action request, an extension execution Javascript is called;
step 2: configuring a Chrome browser, and loading the extension written in step 1, wherein step S2 specifically includes:
step 2.1: opening a Chrome browser, and entering an extension program configuration page through 'more tools- > an extension program';
step 2.2: opening a developer mode in an extension configuration page;
step 2.3: selecting 'loading decompressed extension program', loading the extension program written in the step 1, and in order to judge that the extension is loaded smoothly in the step 2.3, Chrome inquires the relevant information of the extension in the Windows registry when starting. Marking through the extended UUID in the registry, under the affiliated registry entry, having an application program path corresponding to the extension, and opening the extension application in a sub-process mode by reading corresponding information when the Chrome is started;
and step 3: opening a Chrome browser and navigating to an automatic operation page;
as shown in fig. 2, when being opened, the Chrome browser automatically searches for extension information in the registry, opens the MsgHost of the extension application in a sub-process manner through the address recorded in the registry, and all the information is configured in the maincast
And 4, step 4: selecting interface elements needing to be operated in a Chrome browser and storing information, wherein the interface element information in the step S4 comprises a webpage to which the interface elements belong, element types and positions in the interface; the position in the interface has a plurality of description forms, if the ID of the element is found to be unique, the element can be determined by the ID; if the element ID is not unique, determining the hierarchical relationship of the interface element through an xpath or css cascading style sheet to be positioned, and sending and storing the interface element feature descriptor and the WebSocket through a communication input/output stream;
and 5: compiling an automatic operation case;
the automation operation case is written by using C # and refers to the WebScoketServer as shown in FIG. 2. The WebScoketServer is used as a server of the MsgHost, defines various RPC remote calls with the MsgHost and mainly comprises an interface element storage module and an automatic operation module, the WebSocketServer is compiled by C #, is used as the server of the MsgHost, defines various RPC remote calls with the MsgHost and mainly comprises an interface element storage module and an automatic operation module; the interface element storage module is mainly used for defining JSON formatting of interface element information; and the automatic operation module receives JSON formatted interface element information as an operation target parameter and is used for calling an exposed element operation method in the MsgHost.
The interface element storage module is mainly used for defining JSON formatting of interface element information;
the automatic operation module receives JSON formatted interface element information as an operation target parameter and is used for calling an exposed element operation method in the MsgHost;
example 2:
on the basis of the embodiment 1, the step 5 automatic operation case comprises a WebScoket communication module, an interface element storage module, a mouse operation module and a keyboard operation module;
further, the MsgHost is an application program communicating with the extension. And C # writing is adopted, and communication with the extension is realized through input and output streams. The webpage event can be loaded through extension, when a mouse moves to a corresponding webpage, the mouse can be highlighted, an element area and an element position can be obtained, a script program can also be sent to the extension, clicking, rolling, inputting and other operations in webpage interface elements are executed, and meanwhile, in order to transmit the information, the MsgHost also realizes a WebSocket client.
Further, the MsgHost is implemented by multiple threads. The intermediate adopts message communication, is connected to the WebSocketServer through the configuration of a reading program, forwards the message of the browser standard input stream to the WebSocketServer, and the WebSocketServer processes and saves the actions of information, clicking, keyboard input and the like of interface elements.
Further, the interface element information contains the web page to which it belongs, the element type, and the location in the interface. The position in the interface has a plurality of description forms, if the ID of the element is found to be unique, the element can be determined by the ID; if the element ID is not unique, the hierarchical relationship of the interface element can be determined through an xpath or css cascading style sheet to be positioned, and the interface element feature descriptor is sent and stored with the WebSocket through the communication input and output stream.
Further, MsgHost also needs to implement the operation mode of the interface element. And triggering operations such as mouse clicking, keyboard inputting and the like on the interface through the interface element descriptor and the corresponding operation action. The real specific operation execution application is a Chrome extension plug-in, and when the MsgHost receives a corresponding action request, an extension execution Javascript is called.
For example, login needs to input an account password:
(1) calling an input method in the WebSocketServer in an automatic use case to input an account password;
(2) the WebSocketServer sends a target interface element and Javascript to be executed to Chrome extension through the MsgHost;
(3) expanding to find a corresponding element through the webpage where the interface element is located and characteristic positioning, and inputting an account password by calling a value of a set element;
(4) in the same way, finding the login button element and triggering a click event of the element to simulate login;
(5) the login is completed.
Although the present invention has been described herein with reference to the illustrated embodiments thereof, which are intended to be preferred embodiments of the present invention, it is to be understood that the invention is not limited thereto, and that numerous other modifications and embodiments can be devised by those skilled in the art that will fall within the spirit and scope of the principles of this disclosure.
Claims (9)
1. A method for performing automation operation in an open Chrome browser is characterized in that: the method for carrying out automatic operation in the opened Chrome browser comprises the following steps:
s1, writing a Chrome extension and an MsgHost process;
s2, configuring a Chrome browser and loading the extension compiled in the step 1;
s3, compiling a WebSocketServer and communicating with the WebSocket of the MsgHost;
s4, opening the Chrome browser, navigating to the automatic operation page, selecting the interface element needing to be operated in the Chrome browser and saving the information
And S5, writing an automation operation case.
2. The method of claim 1 for automation in an open Chrome browser, wherein: the Chrome extension is mainly used for acquiring the running time of the opened webpage, is written by adopting Javascript language, and provides some APIs (application programming interfaces) including input and output communication by a Chrome browser; the browser defines Background and Content for the opened web pages respectively, the Background and the Content are represented as global Background pages respectively, all the web pages are opened, the Content is loaded as the context of the current web page, and the browser can communicate with an application program through a standard input and output stream.
3. The method of claim 1 for automation in an open Chrome browser, wherein: MsgHost in the step S1 is an application program for communicating with the extension; c # writing is adopted, and communication with the extension is realized through input and output streams; the webpage event can be loaded through extension, when a mouse moves to a corresponding webpage, the mouse can be highlighted, an element area and an element position can be obtained, a script program can also be sent to the extension, clicking, rolling, inputting and other operations in webpage interface elements are executed, and meanwhile, in order to transmit the information, the MsgHost also realizes a WebSocket client.
4. The method of claim 1 for automation in an open Chrome browser, wherein: the MsgHost in the step S1 is realized by multiple threads; the intermediate adopts message communication, is connected to the WebSocketServer through the configuration of a reading program, forwards the message of the browser standard input stream to the WebSocketServer, and the WebSocketServer processes and saves the actions of information, clicking, keyboard input and the like of interface elements.
5. The method of claim 1 for automation in an open Chrome browser, wherein: the interface element information in the step S4 includes the web page, the element type, and the position in the interface; the position in the interface has a plurality of description forms, if the ID of the element is found to be unique, the element can be determined by the ID; if the element ID is not unique, the hierarchical relationship of the interface element can be determined through an xpath or css cascading style sheet to be positioned, and the interface element feature descriptor is sent and stored with the WebSocket through the communication input and output stream.
6. The method of claim 1 for automation in an open Chrome browser, wherein: the MsgHost also needs to realize the operation mode of the interface element; triggering operations such as mouse clicking, keyboard inputting and the like on the interface through the interface element descriptors and the corresponding operation actions; the real specific operation execution application is a Chrome extension plug-in, and when the MsgHost receives a corresponding action request, an extension execution Javascript is called.
7. The method of claim 1 for automation in an open Chrome browser, wherein: the step S2 specifically includes:
step 2.1: opening a Chrome browser, and entering an extension program configuration page through 'more tools- > an extension program';
step 2.2: opening a developer mode in an extension configuration page;
step 2.3: and selecting 'loading the decompressed extension program', and loading the extension program written in the step 1.
8. The method of claim 1 for automation in an open Chrome browser, wherein: the WebSocketServer is compiled by adopting C #, serves as a server of the MsgHost, defines various RPC remote calls with the MsgHost, and mainly comprises an interface element storage module and an automatic operation module; the interface element storage module is mainly used for defining JSON formatting of interface element information; and the automatic operation module receives JSON formatted interface element information as an operation target parameter and is used for calling an exposed element operation method in the MsgHost.
9. The method of claim 7 for automation in an open Chrome browser, wherein: in the step 2.3, in order to judge that the extension is loaded smoothly, the Chrome queries the relevant information of the extension in the Windows registry when starting. Marking through the extended UUID in the registry, under the affiliated registry entry, having the application program path corresponding to the extension, and opening the extension application in the way of subprocess by reading the corresponding information when the Chrome is started.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011259992.1A CN112445994A (en) | 2020-11-12 | 2020-11-12 | Method for carrying out automatic operation in opened Chrome browser |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011259992.1A CN112445994A (en) | 2020-11-12 | 2020-11-12 | Method for carrying out automatic operation in opened Chrome browser |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112445994A true CN112445994A (en) | 2021-03-05 |
Family
ID=74736043
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011259992.1A Pending CN112445994A (en) | 2020-11-12 | 2020-11-12 | Method for carrying out automatic operation in opened Chrome browser |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112445994A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254018A (en) * | 2021-07-14 | 2021-08-13 | 广州易方信息科技股份有限公司 | Automatic operation method and device for webpage view |
| CN113360824A (en) * | 2021-06-30 | 2021-09-07 | 四川效率源信息安全技术股份有限公司 | Webpage evidence obtaining and data extracting method based on Chrome browser debugging protocol |
| CN114816614A (en) * | 2022-03-14 | 2022-07-29 | 达而观信息科技（上海）有限公司 | Method for realizing process automation robot control browser |
| CN116302621A (en) * | 2023-05-19 | 2023-06-23 | 杭州实在智能科技有限公司 | Method and system for picking up information-created environment elements based on QT interface library |
-
2020
- 2020-11-12 CN CN202011259992.1A patent/CN112445994A/en active Pending
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113360824A (en) * | 2021-06-30 | 2021-09-07 | 四川效率源信息安全技术股份有限公司 | Webpage evidence obtaining and data extracting method based on Chrome browser debugging protocol |
| CN113254018A (en) * | 2021-07-14 | 2021-08-13 | 广州易方信息科技股份有限公司 | Automatic operation method and device for webpage view |
| CN114816614A (en) * | 2022-03-14 | 2022-07-29 | 达而观信息科技（上海）有限公司 | Method for realizing process automation robot control browser |
| WO2023173734A1 (en) * | 2022-03-14 | 2023-09-21 | 达而观信息科技（上海）有限公司 | System and method for implementing process automation robot control browser |
| CN114816614B (en) * | 2022-03-14 | 2024-03-22 | 达观数据有限公司 | Implementation method for controlling browser by flow automation robot |
| CN116302621A (en) * | 2023-05-19 | 2023-06-23 | 杭州实在智能科技有限公司 | Method and system for picking up information-created environment elements based on QT interface library |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112445994A (en) | Method for carrying out automatic operation in opened Chrome browser | |
| KR101645052B1 (en) | Debugging pipeline | |
| US8028268B2 (en) | System and method for building software package for embedded system | |
| US7072951B2 (en) | HTTP transaction monitor with capacity to replay in debuggings session | |
| KR100290200B1 (en) | Host information access via distributed program objects | |
| CA2304608C (en) | A method for extending the hypertext markup language (html) to support enterprise application data binding | |
| US20190034199A1 (en) | Auto-generation of application programming interface (api) documentation via implementation-neutral analysis of api traffic | |
| JP4942916B2 (en) | System and method for direct access to functionality provided by an application | |
| US20030115572A1 (en) | System, method and computer program product for application development using a visual paradigm to combine existing data and applications | |
| US20070033281A1 (en) | Error management system and method of using the same | |
| US9442822B2 (en) | Providing a visual representation of a sub-set of a visual program | |
| CN102346780B (en) | The acquisition methods of web page address and acquisition device | |
| JP2010504591A (en) | Common component framework | |
| WO2003007166A2 (en) | System and method for providing help services | |
| US20210209526A1 (en) | Landing page processing method, device and medium | |
| WO2002029641A2 (en) | Http transaction monitor with replay capacity | |
| CN112506778A (en) | WEB user interface automatic test method, device, equipment and storage medium | |
| US7171650B2 (en) | System and method for integrating resources in a network | |
| US20090132908A1 (en) | Apparatus, program and method for accepting a request from a client computer via a network and executing a web application | |
| CN111694744B (en) | Test development method based on monkey source code | |
| KR101418390B1 (en) | system for remotely debugging an application programming and controlling method therefor | |
| US20230311322A1 (en) | Systems and Methods for Using a Browser to Design Robotic Process Automation (RPA) Robots | |
| US8311801B2 (en) | Technology for supporting modification of messages displayed by program | |
| EP1977338B1 (en) | External configuration of processing content for script | |
| JP2002182811A (en) | Software support system and computer readable recording medium with support program recorded thereon |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |