CN113946333B - Mobile terminal logic script execution method and device - Google Patents
Mobile terminal logic script execution method and device Download PDFInfo
- Publication number
- CN113946333B CN113946333B CN202111167825.9A CN202111167825A CN113946333B CN 113946333 B CN113946333 B CN 113946333B CN 202111167825 A CN202111167825 A CN 202111167825A CN 113946333 B CN113946333 B CN 113946333B
- Authority
- CN
- China
- Prior art keywords
- execution
- event
- source
- result
- event execution
- 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.)
- Active
Links
Images
Classifications
-
- 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
-
- 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/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
Abstract
The invention discloses a method and a device for executing a logic script of a mobile terminal, wherein the method comprises the following steps: receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of the event, and traversing the corresponding number file of the event in the UI trigger control event to acquire the corresponding execution request; triggering an event execution manager according to the execution request, and acquiring an event execution source; and determining an execution result according to the event execution source, wherein the execution result comprises a synchronous execution result and an asynchronous execution result. According to the invention, the corresponding execution request is obtained, the event execution manager is triggered to further obtain the event execution source, and finally the execution result is obtained, so that the development efficiency is improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for executing a logic script of a mobile terminal.
Background
When a conventional mobile phone App performs data acquisition by using a form, a series of operations such as logic processing and the like are performed on acquired data, for example, logic processing is performed after the data is acquired, before the data is submitted, whether the data is in an agreed range is judged, if the data is in the agreed range, the data is submitted, the form is closed, otherwise, an error is prompted, and another mode is to acquire or update some data when the form is opened. Typically, such logic is done during development using hard coding or executed after back-end development using a JS-like dynamic compilation statement. However, these methods cause developers and testers to repeatedly intervene in similar or analogous service development and service testing, which results in low efficiency, and the service logic of the existing methods can only be abstracted at the code level, without service attributes, and similar service scenes are difficult to multiplex.
Disclosure of Invention
The invention aims to provide a method and a device for executing a mobile terminal logic script, so as to solve the problems that the development efficiency is low and similar scenes are difficult to reuse in the prior art.
In order to achieve the above object, the present invention provides a method for executing a mobile terminal logical script, including:
receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of an event, and traversing the corresponding number file of the event in the UI trigger control event to obtain a corresponding execution request;
triggering an event execution manager according to the execution request, and acquiring an event execution source;
and determining an execution result according to the event execution source, wherein the execution result comprises a synchronous execution result and an asynchronous execution result.
Preferably, after triggering the event execution manager according to the execution request and obtaining the event execution source, the method further includes:
judging whether the event execution source is locked;
if the event execution source contains the locking mark, caching the event execution source, entering a buffer execution queue, and executing the event execution source;
if the event execution source does not contain the locking mark, the event execution source is locked to determine the execution event, the execution event is input into a cache queue, and the event execution source is released and executed.
Preferably, after triggering the event execution manager according to the execution request and obtaining the event execution source, the method further includes:
and after the event execution source is obtained, if the event execution source contains a forced interrupt mark, clearing the cache execution queue.
Preferably, after triggering the event execution manager according to the execution request and obtaining the event execution source, the method further includes:
after judging whether the event execution source contains the forced interrupt mark, if the event execution source does not contain the forced interrupt mark, acquiring a dynamic parameter of the event execution source, calculating whether the event execution source is executed according to the dynamic parameter, if the dynamic parameter is not matched with a preset threshold value in the event execution source, determining that the event execution source is not required to be executed, and if the dynamic parameter is matched with the preset threshold value in the event execution source, determining that the event execution source is required to be executed.
Preferably, the determining an execution result according to the event execution source includes:
if the execution result is the synchronous execution result, acquiring an execution mark, and continuously executing the next event behavior until the execution is finished;
and if the execution result is the asynchronous execution result, inputting the asynchronous execution result into the event execution manager to obtain a corresponding execution behavior until the execution is finished.
The invention also provides a device for executing the logic script of the mobile terminal, which comprises the following components:
the acquisition module is used for receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of an event, and traversing the corresponding number file of the event in the UI trigger control event to acquire the corresponding execution request;
the trigger module is used for triggering the event execution manager according to the execution request and acquiring an event execution source;
and the execution module is used for determining an execution result according to the event execution source, wherein the execution result comprises a synchronous execution result and an asynchronous execution result.
Preferably, the system further comprises a trigger submodule for:
judging whether the event execution source is locked;
if the event execution source contains the locking mark, caching the event execution source, entering a buffer execution queue, and executing the event execution source;
if the event execution source does not contain the locking mark, the event execution source is locked to determine the execution event, the execution event is input into a cache queue, and the event execution source is released and executed.
Preferably, the trigger submodule is further configured to:
and after the event execution source is obtained, if the event execution source contains a forced interrupt mark, clearing the cache execution queue.
Preferably, the trigger submodule is further configured to:
after judging whether the event execution source contains the forced interrupt mark, if the event execution source does not contain the forced interrupt mark, acquiring a dynamic parameter of the event execution source, calculating whether the event execution source is executed according to the dynamic parameter, if the dynamic parameter is not matched with a preset threshold value in the event execution source, determining that the event execution source is not required to be executed, and if the dynamic parameter is matched with the preset threshold value in the event execution source, determining that the event execution source is required to be executed.
Preferably, the execution module is further configured to:
if the execution result is the synchronous execution result, acquiring an execution mark, and continuing to execute the next event behavior until the execution is finished;
and if the execution result is the asynchronous execution result, inputting the asynchronous execution result into the event execution manager to obtain a corresponding execution behavior until the execution is finished.
Compared with the prior art, the invention has the beneficial effects that:
receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of the event, traversing the corresponding number file of the event in the UI trigger control event to obtain a corresponding execution request, triggering an event execution manager according to the execution request, obtaining an event execution source, determining an execution result according to the event execution source, and the execution result comprises a synchronous execution result and an asynchronous execution result. In the working process of the tester, the tester only needs to test the behaviors of acquiring the execution request and the event execution source, and does not need to test specific scenes, and the developer does not need to code and develop each scene, so that the development efficiency is improved.
Drawings
In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart illustrating a method for executing a mobile-side logical script according to an embodiment of the present invention;
FIG. 2 is a flow diagram of an initial execution provided by another embodiment of the present invention;
FIG. 3 is a flow diagram of generating a behavior registrar, according to yet another embodiment of the present invention;
FIG. 4 is a schematic flow chart diagram of an embodiment of a method for generating an event execution source;
FIG. 5 is a flow diagram illustrating a release event execution source according to another embodiment of the invention;
FIG. 6 is a flowchart illustrating a method for executing an interrupt-forcing flag according to another embodiment of the present invention;
FIG. 7 is a flowchart illustrating a method for determining whether the action needs to be executed according to an embodiment of the present invention;
FIG. 8 is a diagram of execution results provided by one embodiment of the present invention;
FIG. 9 is a flowchart illustrating a method for performing synchronization according to another embodiment of the present invention;
FIG. 10 is a flowchart illustrating an asynchronous execution method according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a mobile terminal logical script execution apparatus according to yet another embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without inventive step based on the embodiments of the present invention, are within the scope of protection of the present invention.
It should be understood that the step numbers used herein are only for convenience of description and are not used as limitations on the order in which the steps are performed.
It is to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
The terms "comprises" and "comprising" indicate the presence of the described features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term "and/or" refers to and includes any and all possible combinations of one or more of the associated listed items.
Referring to fig. 1, an embodiment of the present invention provides a method for executing a mobile terminal logical script, including the following steps:
s101: receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of the event, and traversing the corresponding number file of the event in the UI trigger control event to obtain a corresponding execution request.
Specifically, when the App performs UI operation, the App searches for a corresponding number file in a UI trigger control event to obtain an execution request, and regarding description of the event, the event code is used for time numbering, the success prompt information of the successTip execution event is obtained, the jump field judges whether execution of the time needs to be skipped, actionCodes is a description behavior, and a plurality of different types of behaviors can exist in one event. Regarding the description of the behavior, the actionCode is used for the behavior number, the failTip is used for the information presented when the execution fails, the jump field is used for judging whether to skip the behavior or not, and finally the type of the type behavior is output.
Referring to fig. 2, when an App initializes, it downloads a logical script structure definition file and registers metadata of a specific execution object with different behaviors, the logical script structure definition file is downloaded locally in batches and stored, after the App enters, it is determined whether the file is used for the first time, if so, it uses a server to download the file in full, if not, it uses a server to download in incremental, and finally, it stores update time and stores the file with an event number as a file name.
S102: and triggering an event execution manager according to the execution request, and acquiring an event execution source.
Specifically, referring to fig. 3, the executor metadata is registered, and the type is registered as a key in the form of submitting the behavior executor metadata through data and returning the behavior executor metadata.
Referring to fig. 4, when an App performs a UI operation, an event of a UI control searches for a file with a corresponding number from a directory of a specified folder according to an event code associated during coding, reads file contents into an event execution manager to form an event, and the event execution manager starts processing, where the reading process is as follows:
A. clicking the UI triggers a control event.
B. And taking out the event number in the hard coding process and transmitting the event number to the event execution source manager.
C. And if the event file is loaded, the content of the structure file is taken out from the memory, otherwise, the structure file is locally read, loaded and cached.
D. And entering the event into an event execution source manager to obtain an event execution source.
Referring to fig. 5, because there are multiple controls on the UI interface, different controls are associated with different event numbers, and a user may trigger different or the same control events for multiple times, before executing an event, it is determined first whether an event execution source in the event execution manager is locked, if so, an event triggered by the current event is cached first, and is executed after the event being executed is executed, the event triggered by the control is returned immediately, after the current event is executed in the event manager, it is checked whether there is an unexecuted event in the buffer queue, if so, the execution continues until the queue is emptied, otherwise, the execution returns to the buffer queue
Judging whether the event execution source is locked or not, if the event execution source contains a locking mark, caching the event execution source, entering a buffer execution queue, executing the event execution source, if the event execution source does not contain the locking mark, locking the event execution source to determine an execution event, inputting the execution event into the cache queue, releasing the event execution source, and executing.
Referring to FIG. 6, during the event execution process, it is determined whether the event manager receives the forced interrupt flag. In the execution process, the interface where the control is located may be destroyed by the user in a return manner, and if the interface is destroyed, the event corresponding to the corresponding control does not need to be executed, and meanwhile, the event in the buffer queue does not need to be executed, and the user directly empties and exits.
Referring to fig. 7, when the event of the widget is delivered, some dynamic parameters are attached, and used for calculating whether the event or the behavior is required to be actually executed in the jump field in the execution process, these parameters may be present in the current global parameter cache to wait for being used, and after the forced interrupt flag is determined, the jump field calculation is performed. And judging whether the event needs to be executed really or not according to the current context condition, and starting to execute each action circularly if the event needs to be executed really.
After judging whether the event execution source contains the forced interrupt mark or not, if the event execution source does not contain the forced interrupt mark, acquiring dynamic parameters of the event execution source, calculating whether the event execution source is executed or not according to the dynamic parameters, if the dynamic parameters are not matched with a threshold value preset in the event execution source, determining that the event execution source is not required to be executed, and if the dynamic parameters are matched with the threshold value preset in the event execution source, determining that the event execution source is required to be executed.
In the event and behavior, the jump field is used to describe the event or behavior, and is calculated to be sufficient to determine whether the event or behavior needs to be actually executed, and the key words described in the jump field are shown in table 1.
TABLE 1 keyword definitions
| Variables of | ￥[param] | Collection of | in() | Range | between() |
| Condition determination | when{}then{} | Value comparison | ＞，＞＝，＝＜，＜，＝＝，！＝ | Logic conditions | &&，|| |
| Lookup | find | Type conversion | toI()，toS() |
The source of the variable value in table 1 is the value of each control in the form stored in the memory by the temporary key value stored in the memory, and is exemplified by adopting a parameter mode in the jump field, as follows:
1) the event or action is skipped when parameter 1 is equal to or greater than 10 and the value of parameter 2 is equal to the string "OK".
$[param1]>＝10&&$[param2]＝＝‘OK’。
2) The event or action is skipped when the value of parameter 1 corresponds to one of 10,20,30 or the value of parameter 2 ranges between 50 and 100.
$[param1]in(10,20,30)||$[param2]between(50,100)。
3) When the parameter 1 contains the character string "100", the character string "100" is extracted and converted into an integer type, and it is determined whether the value is between the parameter 2 and the parameter 3.
when{$[param1].find(’100’)}then{$[param1].find(’100’).toI()between($[param2],$[param3])}。
Behaviors are divided into two categories in execution: synchronous behavior and asynchronous behavior. The method is used for distinguishing whether a new thread is started in the execution process, and distinguishing in the execution process through specific types, and each behavior has a description mode corresponding to a service, such as:
the logic structure is generated through a special event behavior editor and stored in a server, developers can directly associate the event of the UI control with the logic executed by the event in a hard coding mode in the development process by multiplexing an event code, and different editing options can be presented in the designated area by dragging predefined behaviors to the designated area and selecting different behaviors in corresponding attribute editing in a behavior editing interface.
S103: and determining an execution result according to the event execution source, wherein the execution result comprises a synchronous execution result and an asynchronous execution result.
Specifically, if the execution result is the synchronous execution result, the execution flag is obtained, and the next event behavior is continuously executed until the execution is finished.
Referring to fig. 8, when the event execution manager iterates the behavior in the event, the event execution manager also needs to calculate the forcible interrupt flag determination and the jump field, and in the iterative process, for different behavior types, the event execution manager extracts the corresponding behavior executor metadata from the behavior register according to the current behavior type, instantiates the behavior executor metadata, and sends the behavior structure data to the corresponding behavior executor for processing. Behaviors are abstract to the event execution manager, which is not aware of the internal logical processing of a behavior, but knows that the behavior should be executed in a synchronous or asynchronous manner with subsequent execution. And judging whether the operation is synchronous or asynchronous according to the execution return result of the behavior.
Referring to fig. 9, if the returned result is the synchronous execution result, the behavior is executed synchronously, at this time, the execution flag is taken out, if the execution flag is a success flag, the next behavior is executed continuously, otherwise, an error is prompted according to the failTip field configured by the behavior, the loop execution is exited, and the subsequent behavior is ignored.
Referring to fig. 10, if the return is an asynchronous execution result, the logic of the thread where the current behavior is located is exited, but the event execution source flag in the event execution manager is not cleared, the internal open thread of the asynchronous behavior continues executing, and an asynchronous behavior result is returned, the event manager separately stores the asynchronous behavior result and the remaining behaviors to the event manager, the asynchronous behavior result is stored in the newly opened thread in addition to the event manager, and is used for notifying the execution result of the behavior, after the execution of the behavior is completed, a notification is received through the asynchronous behavior result, and the event manager re-enters the event manager, at this time, the event manager does not perform judgment processing on the event, but directly continues processing on the remaining behaviors, and the processing logic is the same as that before performing asynchronous return.
The method comprises the steps of receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of the event, traversing the corresponding number file of the event in the UI trigger control event to obtain a corresponding execution request, triggering an event execution manager according to the execution request, obtaining an event execution source, determining an execution result according to the event execution source, and obtaining the execution result which comprises a synchronous execution result and an asynchronous execution result. In the working process of the tester, the tester only needs to test the behaviors of acquiring the execution request and the event execution source, and does not need to test specific scenes, and the developer does not need to code and develop each scene, so that the development efficiency is improved.
Developers do not need to pay attention to how different business scene logics are compiled and executed, the scripts can be edited on a visual interface as required, testers do not need to repeatedly test the business scene logic codes, the testers only need to pay attention to whether the scripts can generate expected business effects, the business scenes are abstracted and decomposed into different behaviors, the different business scenes can be solved by using the limited behaviors, and the delivery efficiency and the App stability are improved.
Referring to fig. 11, another embodiment of the present invention provides a mobile terminal logical script execution apparatus, including:
the obtaining module 11 is configured to receive an execution request of a UI trigger control event, where the UI trigger control event includes a corresponding number file of an event, and traverse the corresponding number file of the event in the UI trigger control event to obtain a corresponding execution request.
And the triggering module 12 is used for triggering the event execution manager according to the execution request and acquiring an event execution source.
And the execution module 13 is configured to determine an execution result according to the event execution source, where the execution result includes a synchronous execution result and an asynchronous execution result.
For specific limitations of the mobile terminal logic script execution apparatus, reference may be made to the above limitations on the mobile terminal logic script execution method, which is not described herein again. All or part of each module in the mobile terminal logic script execution device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
Claims (8)
1. A method for executing a mobile terminal logic script is characterized by comprising the following steps:
receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of the event, and traversing the corresponding number file of the event in the UI trigger control event to acquire the corresponding execution request;
triggering an event execution manager according to the execution request, and acquiring an event execution source; after the event execution source is obtained, if the event execution source contains a forced interrupt mark, a cache execution queue is cleared;
and determining an execution result according to the event execution source, wherein the execution result comprises a synchronous execution result and an asynchronous execution result.
2. The method according to claim 1, wherein after triggering the event execution manager according to the execution request and obtaining an event execution source, the method further comprises:
Judging whether the event execution source is locked;
if yes, caching the event execution source, entering a buffer execution queue and waiting for execution.
3. The method for executing a mobile-side logical script according to claim 1, wherein after triggering the event execution manager according to the execution request and obtaining an event execution source, the method further comprises:
after judging whether the event execution source contains the forced interrupt mark, if the event execution source does not contain the forced interrupt mark, acquiring a dynamic parameter of the event execution source, calculating whether the event execution source is executed according to the dynamic parameter, if the dynamic parameter is not matched with a preset threshold value in the event execution source, determining that the event execution source is not required to be executed, and if the dynamic parameter is matched with the preset threshold value in the event execution source, determining that the event execution source is required to be executed.
4. The method according to claim 3, wherein the determining an execution result according to the event execution source comprises:
if the execution result is the synchronous execution result, acquiring an execution mark, and continuing to execute the next event behavior until the execution is finished;
And if the execution result is the asynchronous execution result, inputting the asynchronous execution result into the event execution manager to obtain a corresponding execution behavior until the execution is finished.
5. A mobile terminal logic script execution device is characterized by comprising:
the acquisition module is used for receiving an execution request of a UI trigger control event, wherein the UI trigger control event comprises a corresponding number file of an event, and traversing the corresponding number file of the event in the UI trigger control event to acquire the corresponding execution request;
the triggering module is used for triggering the event execution manager according to the execution request and acquiring an event execution source; the trigger module further comprises a trigger submodule for clearing the cache execution queue if the event execution source contains a forced interrupt flag after the event execution source is acquired;
and the execution module is used for determining an execution result according to the event execution source, wherein the execution result comprises a synchronous execution result and an asynchronous execution result.
6. The mobile end logic script execution apparatus of claim 5, further comprising a trigger submodule for:
judging whether the event execution source is locked;
And if so, caching the event execution source, and entering a buffer execution queue to wait for execution.
7. The mobile end logic script execution apparatus of claim 5, wherein the trigger submodule is further configured to:
after judging whether the event execution source contains the forced interrupt mark, if the event execution source does not contain the forced interrupt mark, acquiring a dynamic parameter of the event execution source, calculating whether the event execution source is executed according to the dynamic parameter, if the dynamic parameter is not matched with a preset threshold value in the event execution source, determining that the event execution source is not required to be executed, and if the dynamic parameter is matched with the preset threshold value in the event execution source, determining that the event execution source is required to be executed.
8. The mobile end logic script execution apparatus of claim 7, wherein the execution module is further configured to:
if the execution result is the synchronous execution result, acquiring an execution mark, and continuing to execute the next event behavior until the execution is finished;
and if the execution result is the asynchronous execution result, inputting the asynchronous execution result into the event execution manager to obtain a corresponding execution behavior until the execution is finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111167825.9A CN113946333B (en) | 2021-09-30 | 2021-09-30 | Mobile terminal logic script execution method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111167825.9A CN113946333B (en) | 2021-09-30 | 2021-09-30 | Mobile terminal logic script execution method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113946333A CN113946333A (en) | 2022-01-18 |
| CN113946333B true CN113946333B (en) | 2022-06-14 |
Family
ID=79330033
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111167825.9A Active CN113946333B (en) | 2021-09-30 | 2021-09-30 | Mobile terminal logic script execution method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113946333B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109739487A (en) * | 2019-01-04 | 2019-05-10 | 广州市玄武无线科技股份有限公司 | A kind of business logic processing method, equipment and computer readable storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100369013C (en) * | 2006-02-24 | 2008-02-13 | 北京博联伟图科技有限公司 | Process monitoring method for embedded application software testing |
| JP6418004B2 (en) * | 2015-02-26 | 2018-11-07 | 富士通株式会社 | Event notification program, event notification method, and event notification device |
| CN105095092A (en) * | 2015-09-25 | 2015-11-25 | 南京大学 | Static analysis and dynamic operation based detection of atomic violation of JS (JavaScript) code in Web application |
| CN112463156B (en) * | 2020-11-25 | 2023-04-28 | 福建天泉教育科技有限公司 | Method and terminal for component attribute linkage verification |
-
2021
- 2021-09-30 CN CN202111167825.9A patent/CN113946333B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109739487A (en) * | 2019-01-04 | 2019-05-10 | 广州市玄武无线科技股份有限公司 | A kind of business logic processing method, equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113946333A (en) | 2022-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106339312B (en) | API test method and system | |
| CN111124906B (en) | Tracking method, compiling method and device based on dynamic embedded points and electronic equipment | |
| US8589884B2 (en) | Method and system for identifying regression test cases for a software | |
| CN108459964B (en) | Test case selection method, device, equipment and computer readable storage medium | |
| US20080120601A1 (en) | Information processing apparatus, method and program for deciding priority of test case to be carried out in regression test background of the invention | |
| US7996840B2 (en) | Method, system, and apparatus for scheduling pattern based web services | |
| CN114546738B (en) | Universal test method, system, terminal and storage medium for server | |
| CN115422063A (en) | Low-code interface automation system, electronic equipment and storage medium | |
| CN111538659B (en) | Interface testing method, system, electronic equipment and storage medium of business scene | |
| CN111708771A (en) | Data duplicate checking method, device, equipment and computer storage medium | |
| CN112579461A (en) | Assertion processing method, system and storage medium | |
| CN101506772B (en) | Environment state changes to alter functionality | |
| CN111309622A (en) | Application program testing method and device, terminal equipment and storage medium | |
| CN113946333B (en) | Mobile terminal logic script execution method and device | |
| CN111159028B (en) | Webpage testing method and device | |
| CN112559344A (en) | Remote mock testing method and system | |
| CN116578282A (en) | Code generation method, device, electronic equipment and medium | |
| CN111124791A (en) | System testing method and device | |
| CN111400135A (en) | Method and device for extracting service data | |
| CN113791809B (en) | Application exception handling method and device and computer readable storage medium | |
| JP2004094374A (en) | Logging system | |
| CN113031964B (en) | Big data application management method, device, equipment and storage medium | |
| CN115048104A (en) | Code generation method and device based on syntax tree and electronic equipment | |
| CN113704114A (en) | Automatic testing method, device, equipment and medium for functional interface | |
| CN113448985A (en) | API (application program interface) interface generation method, calling method and device and electronic equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |