CN117609102A - Building industry Internet counting platform system testing method - Google Patents
Building industry Internet counting platform system testing method Download PDFInfo
- Publication number
- CN117609102A CN117609102A CN202410093403.9A CN202410093403A CN117609102A CN 117609102 A CN117609102 A CN 117609102A CN 202410093403 A CN202410093403 A CN 202410093403A CN 117609102 A CN117609102 A CN 117609102A
- Authority
- CN
- China
- Prior art keywords
- subtask
- subtasks
- task
- main
- tasks
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 26
- 238000000034 method Methods 0.000 claims abstract description 21
- 238000010276 construction Methods 0.000 claims abstract description 18
- 238000012163 sequencing technique Methods 0.000 claims abstract description 4
- 238000004519 manufacturing process Methods 0.000 claims description 12
- 238000000605 extraction Methods 0.000 claims description 5
- 230000000007 visual effect Effects 0.000 claims description 4
- 238000010998 test method Methods 0.000 claims 1
- 230000006870 function Effects 0.000 description 11
- 238000011161 development Methods 0.000 description 5
- 238000006467 substitution reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
Abstract
The invention discloses a method for testing an Internet counting platform system of the building industry, which comprises the steps of creating corresponding main tasks based on a preset front-end template, wherein each main task comprises a plurality of subtasks, the subtasks are newly built or created subtasks, and the created subtasks are referenced by different main tasks; carrying out parameter construction and variable replacement on the subtasks; displaying the created main tasks, generating a main task list, sequencing the main tasks of the main task list, selecting the main tasks to be executed, sequentially executing the sub tasks of the main tasks, and collecting the execution results of the sub tasks. The invention takes the subtask as the minimum execution unit to create the main task required by the construction number, different subtasks execute different construction number logics, the created subtask is referenced by different main tasks, the aim of multiplexing the construction number capacity is achieved, the repeated construction of the same subtask required by the construction number is avoided, and the construction number flow is simplified.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for testing an Internet counting platform system in the building industry.
Background
With the high-speed development of the building industry systems, all the systems almost have the characteristics of huge scale, various materials, complex business, strong system relevance, large transaction amount, quick demand change and the like. In addition, various new and old systems are staggered, the systems are strongly associated and the services are strongly coupled, so that the complexity of a test scene is continuously improved, and the test workload is also continuously increased. For example, in a centralized purchasing system, the whole process includes more than 20 steps including bidding, contract, performing, etc., more than 5 service modules are associated, more than 30 times of interface requests are required, the coupling of each system is serious, the cost of manufacturing test data is extremely high, and only the manufacturing cost needs about 2 days.
On the other hand, the current pain point and the current situation are analyzed: in the data layer, the manufacturing cost of the test data is high, and the test data richness is insufficient under the condition of high cost; on the tool level, a large number of small tools exist in a company large environment, and procedural and systematic tools are lacked; in the script level, the complex number-making scene needs to have a good code foundation, so the requirement on testers is higher; at the collaboration level, different teams may develop repeatedly for the same build scene.
Based on the problems, the invention provides a building industry Internet count platform system testing method, which improves the expandability and usability of the count platform, simplifies the count flow and reduces the count cost.
Disclosure of Invention
Aiming at the technical problems, the invention provides a method for testing an Internet counting platform system in the building industry, which takes subtasks as minimum execution units to achieve the aim of multiplexing counting capacity.
In order to achieve the above purpose, the technical scheme adopted by the invention is as follows:
a method for testing an Internet number-making platform system in the building industry comprises the following steps:
step 1, creating corresponding main tasks based on a preset front-end template, wherein each main task comprises a plurality of subtasks, each subtask is a newly built or created subtask, and the created subtask is referenced by different main tasks;
step 2, carrying out parameter construction and variable replacement on subtasks;
and step 3, displaying the created main tasks, generating a main task list, sequencing the main tasks of the main task list, selecting the main tasks to be executed, sequentially executing the sub tasks of the main tasks, and collecting the execution results of the sub tasks.
Further, in step 2, for some subtasks, the common parameters of the subtasks are set as variables to be replaced, and the execution result of the subtasks is set as extraction variables to be extracted.
Further, in step 2, the variable substitution includes: step a, checking whether a subtask has a variable which needs to be replaced; and b, extracting a corresponding value from the global variable by taking the name of the variable as a unique identifier, and replacing the corresponding variable by adopting the extracted value.
Further, in step 3, the execution of the subtasks includes: step A, a corresponding task executor is called according to the type of the subtask, and the current subtask is executed; step B, calling a corresponding result collector according to the type of the subtask, and collecting an execution result; step C, checking whether the subtasks have extracted variables; and D, extracting variables exist in the subtasks, and storing the extracted variables into the global variables for replacing associated subtask variables.
Further, the primary task is a counting task or a counting tool, which can be referenced by the counting task.
Further, creation of the accounting task includes: and inputting task information, newly creating a subtask or referring to the created subtask, and newly creating the subtask in a number-making mode.
Further, the number making mode includes database number making, automatic number making, custom interface number making and custom function number making.
Further, the creation of the count tool includes: accessing a component of the low-code platform, inputting task information, and adding a new subtask or referencing the created subtask; the low-code platform comprises a designer and a renderer, wherein the designer provides different components, the front-end layout of the counting tool is completed by selecting and dragging the components, the renderer acquires JSON data of the corresponding counting tool from an interface, sequentially draws the corresponding components according to the types of the components, restores the JSON data to a visual interface, and completes the creation of the counting tool.
Further, the task information includes task names, task descriptions, business lines, and environments.
Further, the method also comprises the step of saving the execution result of the subtasks and generating a history report.
Compared with the prior art, the invention has the following beneficial effects:
the invention takes the subtask as the minimum execution unit, the main task can quote the subtask, the method is flexible and convenient, the aim of multiplexing the count making capability is achieved, and the workload of count making is reduced. The invention displays the created main tasks and sub tasks, is convenient for unified maintenance and management, and is convenient for extraction and use required by other numbers. The invention provides two counting methods, namely a counting task and a counting tool, so as to adapt to different counting scenes.
Drawings
FIG. 1 is a flow chart of the method of the present invention.
Detailed Description
Term interpretation:
JSON path is a language used to find or extract data in JSON objects.
JS, fully called JavaScript, is a lightweight, interpreted or just-in-time compiled programming language with functional preference.
SQL statements are structured query statements.
The present invention will be described in further detail with reference to the accompanying drawings, in order to make the objects, technical solutions and advantages of the present invention more apparent. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
As shown in fig. 1, the method for testing the internet manufacturing number platform system of the building industry provided by the invention comprises the following steps:
step 1, creating corresponding main tasks based on a preset front-end template, wherein each main task comprises a plurality of subtasks, each subtask is a newly built or created subtask, and the created subtask is referenced by different main tasks;
step 2, carrying out parameter construction and variable replacement on subtasks;
and step 3, displaying the created main tasks, generating a main task list, sequencing the main tasks of the main task list, selecting the main tasks to be executed, sequentially executing the sub tasks of the main tasks, and collecting the execution results of the sub tasks.
The invention is realized in the count making platform, the subtasks are used as the minimum execution units to create the main tasks required by the count making, different subtasks execute different count making logics, the created subtasks are referenced by different main tasks, the purpose of multiplexing count making capability is achieved, the repeated construction of the same subtasks required by the count making is avoided, and the count making flow is simplified.
For example, the commodity purchase task includes subtask 1, acquire idempotent keys; subtask 2, generating a service ID; a subtask 3, acquiring commodity information; subtask 4, creating an order; subtask 5, obtain the payment bill number; subtask 6, paying orders; the commodity refund task comprises a subtask 1 and an idempotent key; subtask 2, generating a service ID; a subtask 3, acquiring commodity information; subtask 4, creating an order; subtask 5, obtain the payment bill number; subtask 6, paying orders; a subtask 7, acquiring user bank account information; subtask 8, perfecting refund information; subtask 9, initiate refund. The commodity purchase task and the commodity refund task have longer data construction flow, and the commodity purchase task and the commodity refund task have the same partial flow, namely subtasks, so that the creation workload can be reduced by referring to the subtasks 1, the subtasks 2, the subtasks 3, the subtasks 4, the subtasks 5 and the subtasks 6 in a mode of referring to the existing subtasks.
The creation of the main task specifically comprises the following steps: creating a main task, wherein the main task comprises information such as a task type, a task name, a creator, a task state, task parameters and the like; secondly, starting to create a subtask, firstly judging whether the created subtask is quoted, if so, directly inserting the subtask into a main task, if not, creating a new subtask which contains information such as a task type, a task name, a creator, a task state, a step index (step_index), a task parameter and the like, inserting the subtask into the main task after the subtask is successfully created, recording the relation between the main task and the subtask through a main key, and sequentially repeating the creation steps of the subtask until the main task is created.
Different subtasks are different number making methods, and the subtasks need to be executed by corresponding executors according to the types of the subtasks. Different parameter constructs are required before the subtasks are executed. After each subtask is created, the subtask can be debugged, and the debugging can be successfully executed only after the subtask is created.
In this embodiment, for some subtasks, its common parameters are set as variables, so that serial call of multiple interfaces is facilitated, then the variables are exposed to the number-of-manufacture platform, different values are given to the variables to achieve different number of manufacture, and the variables are identified by special symbols, such as "$ { variable name }. Because the subtasks can be cited by different main tasks, in order to improve the flexibility and reusability of the number of creation and meet various number of creation scenes, when the subtasks are subjected to parameter construction and variable replacement, common parameters such as an interface request address, a request head or a request body of the subtasks can be set as variables, the variables are subjected to replacement processing before the subtasks are executed, and the variables are replaced with real values required by the corresponding main tasks. For some subtasks, the execution result is set as an extraction variable, and the extraction variable is stored in a global variable and can be used for variable replacement of other subtasks. For example, the interface path in one current subtask is/api/fw/v 1/item/service/front/detail/$ { incamentserviceid }, which contains an exchangeable variable, the name of the variable is incamentserviceid, the value of the variable $ { incamentserviceid } is replaced by taking the value of the global variable, the value of the variable is the execution result of another subtask, the execution result is 899, and the interface path of the current subtask after replacement is: ipi/fw/v 1/item/service/front/detail/899. Therefore, when different main tasks refer to the same created subtask, the purpose that the subtasks are multiplexed without mutual influence is achieved only by replacing the subtask variables.
In this embodiment, variable substitution includes: step a, checking whether a subtask has a variable which needs to be replaced; and b, extracting the expression of the variable according to the regular expression or the json path, wherein the subtask has the variable to be replaced, taking the name of the variable as a unique identifier, extracting a corresponding value from the global variable, and replacing the corresponding variable by adopting the extracted value.
In this embodiment, the execution of the subtasks includes: step A, a corresponding task executor is called according to the type of the subtask, and the current subtask is executed; step B, calling a corresponding result collector according to the type of the subtask, and collecting an execution result; step C, checking whether the subtasks have extracted variables; and D, extracting variables exist in the subtasks, and storing the extracted variables into the global variables for replacing associated subtask variables.
In this embodiment, the primary task is a counting task or a counting tool, which can be referred to by the counting task. The count task is a count scene generated based on a count mode; the counting tool is a special counting task, integrates a low-code platform, and allows the counting task to be generated through a component custom user interaction interface of the low-code platform.
Creation of the count task includes: the task information (basic information such as task name, task description, service line, environment (qa\stg\ prd) is input, the subtasks are newly built or the subtasks which are created are quoted, and the subtasks are newly built in a number-of-creation mode. The number-making mode includes database number-making, automatic number-making, custom interface number-making and custom function number-making. The database creation number is a custom SQL sentence, and after the subtask names, the subtask steps and the database selection are filled in, the custom SQL sentence is filled in to form a new subtask in the page. The automatic creation number is communicated with the existing automatic platform, and the subtasks are newly built by adopting the interfaces maintained by the existing automatic platform. The custom interface creation number is a custom interface, and information such as a subtask name, a subtask step, an interface path, a request mode, a message header and the like is filled in to newly build the subtask, so that an http/https/dubbo protocol is supported. The custom function creation number is that under the condition that the interface is too complicated to enter, the custom function is written, the custom function is packaged into an interface, and after the function is successfully registered by the existing automation platform, a newly-built subtask of the function is called.
Creation of the count tool includes: accessing a component of the low-code platform, inputting task information (basic information such as task names, task descriptions, service lines, environments (qa\stg\ prd) and the like), adding a subtask newly or referring to the created subtask, and creating the subtask through the component provided by the low-code platform. Where the components support 100+ components such as time, date, single line input, multiple line input, time range, drop down list, etc.
The existing counting tools are realized by a front-end hard coding mode, certain requirements are set for the front-end knowledge level of a developer, and the tools are modified and then the services are released to be effective. The counting tool can complete tool creation without front-end development capability by integrating the self-defined front-end page of the low-code platform, can complete tool creation with complex page interaction by knowing simple JS knowledge, reduces tool development threshold, and saves development time. All information of the counting tool, including page layout and page display components, is stored in a JSON format by the rear end; the modification takes effect immediately without the need for a release service. The invention is connected with a low-code platform, provides rich components, can directly draw pages, and saves the development cost of test tools.
The low code platform comprises a designer for design of the build tool front end layout and a renderer for rendering of the build tool visual interface. The designer FormDesigner provides rich front-end component libraries, different front-end components realize the encapsulation of Element-UI components, add binding field attributes, event attributes and styles for components and forms, realize component dragging through the dragable component of the Element UI, and finish the front-end layout of the counting tool. When the component is selected, the field attribute, the event attribute and the style of the currently selected component are displayed, and the data input box is defaulted. The user inputs data such as component field attribute, event attribute, style and the like on the page, and the system can convert information of a counting tool (including all information such as page layout, data binding, components, style, event and the like) into data in a JSON format for storage; the renderer FormRender obtains data in a JSON format of the counting tool from the interface, and then sequentially draws corresponding components according to the types of the components, so that the JSON data is restored to a visual interface; the user inputs the preset necessary parameters of the tool, clicks the button of the execution tool, and the system extracts the data of each component and calls the corresponding task executor to execute the counting tool.
After the creation of the main task is completed, the created main task is displayed, a main task list is generated, and the main tasks of the main task list are ordered. And displaying the main tasks created by each user under the account corresponding to the user account number platform, wherein the display comprises the main tasks created by the user history, and the created main tasks can be also displayed on line for other users to see. The main task list comprises a plurality of main tasks, each main task comprises a subtask list and a plurality of subtasks under the subtask list, and the main task list/subtask list supports operations such as task checking, executing, online, offline, deleting and the like.
After the creation of the main task is completed, the main task to be executed is selected and its sub-tasks are sequentially executed. And selecting a corresponding task executor according to the type of the main task to execute, specifically calling different task executors according to different task types, and uniformly converting jsonstr transmitted by the front end of the task executor into standard request parameters. The database executor is used for the database counting task, and encapsulates database operation logic; the automatic counting task adopts an automatic executor, the automatic executor is connected with an automatic test platform in a butt joint mode, the subtasks are converted into automatic test steps, and the automatic test steps are forwarded to the automatic test platform for execution; the counting task of the custom interface counting adopts a custom interface executor, and the custom interface executor encapsulates the execution logic of the Http request; the number making task of the custom function number making adopts a custom function executor, and the custom function executor comprises a preset custom function, such as generating a random character string, generating a time stamp and the like; the counting tool executes according to the Http protocol and the interfaces of the Dubbo protocol supported by the self-defined front end page component, and the bottom layer of the counting tool calls the Http executor and the Dubbo executor respectively according to the subtask interface types.
Aiming at the counting task and the counting tool, the counting platform defines two task transmitters which are TaskExecutor, toolExecutor respectively, inquires and records main task information, starts an asynchronous thread pool TaskExecutorThreadPool after recording, finds out corresponding subtasks according to the main task information, converts parameters of each step of the subtasks into unified standard parameters and sends a request through the task executors until the subtasks under the main task are executed.
Finally, storing the execution result of the subtasks to generate a history report. After executing the counting task/counting tool, the execution result and the execution details can be checked through a history report, and the history report can clearly mark the execution details of each step, specific request parameters, request results and the like.
Finally, it should be noted that: the above embodiments are merely preferred embodiments of the present invention for illustrating the technical solution of the present invention, but not limiting the scope of the present invention; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions; that is, even though the main design concept and spirit of the present invention is modified or finished in an insubstantial manner, the technical problem solved by the present invention is still consistent with the present invention, and all the technical problems are included in the protection scope of the present invention; in addition, the technical scheme of the invention is directly or indirectly applied to other related technical fields, and the technical scheme is included in the scope of the invention.
Claims (10)
1. The method for testing the Internet number-making platform system of the building industry is characterized by comprising the following steps of:
step 1, creating corresponding main tasks based on a preset front-end template, wherein each main task comprises a plurality of subtasks, each subtask is a newly built or created subtask, and the created subtask is referenced by different main tasks;
step 2, carrying out parameter construction and variable replacement on subtasks;
and step 3, displaying the created main tasks, generating a main task list, sequencing the main tasks of the main task list, selecting the main tasks to be executed, sequentially executing the sub tasks of the main tasks, and collecting the execution results of the sub tasks.
2. The method for testing the building industry internet manufacturing number platform system according to claim 1, wherein in the step 2, for some subtasks, common parameters of the subtasks are set as variables to be replaced, and execution results of the subtasks are set as extraction variables to be extracted.
3. The method for testing an internet construction number platform system according to claim 1, wherein in the step 2, the variable replacement comprises: step a, checking whether a subtask has a variable which needs to be replaced; and b, extracting a corresponding value from the global variable by taking the name of the variable as a unique identifier, and replacing the corresponding variable by adopting the extracted value.
4. The method for testing an internet manufacturing number platform system for construction industry according to claim 2, wherein in step 3, the execution of the subtasks comprises: step A, a corresponding task executor is called according to the type of the subtask, and the current subtask is executed; step B, calling a corresponding result collector according to the type of the subtask, and collecting an execution result; step C, checking whether the subtasks have extracted variables; and D, extracting variables exist in the subtasks, and storing the extracted variables into the global variables for replacing associated subtask variables.
5. The method of claim 1, wherein the primary task is a manufacturing task or a manufacturing tool.
6. The method for testing an internet accounting platform system of an architectural industry of claim 5, wherein the creating of the accounting tasks comprises: and inputting task information, newly creating a subtask or referring to the created subtask, and newly creating the subtask in a number-making mode.
7. The method of claim 6, wherein the building industry internet building number platform system test method comprises database building number, automation building number, custom interface building number, custom function building number.
8. The method for testing an internet construction counting platform system according to claim 5, wherein the creating of the counting tool comprises: accessing a component of the low-code platform, inputting task information, and adding a new subtask or referencing the created subtask; the low-code platform comprises a designer and a renderer, wherein the designer provides different components, the front-end layout of the counting tool is completed by selecting and dragging the components, the renderer acquires JSON data of the corresponding counting tool from an interface, sequentially draws the corresponding components according to the types of the components, restores the JSON data to a visual interface, and completes the creation of the counting tool.
9. The method for testing an internet manufacturing platform system for construction industry according to claim 6 or 8, wherein the task information includes task names, task descriptions, service lines and environments.
10. The method for testing an internet manufacturing number platform system for construction industry according to claim 1, further comprising storing the execution result of the subtasks and generating a history report.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410093403.9A CN117609102A (en) | 2024-01-23 | 2024-01-23 | Building industry Internet counting platform system testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410093403.9A CN117609102A (en) | 2024-01-23 | 2024-01-23 | Building industry Internet counting platform system testing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117609102A true CN117609102A (en) | 2024-02-27 |
Family
ID=89958363
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410093403.9A Pending CN117609102A (en) | 2024-01-23 | 2024-01-23 | Building industry Internet counting platform system testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117609102A (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5668994A (en) * | 1993-04-30 | 1997-09-16 | International Business Machines Corporation | Conversation management routine for co-operative processing applications |
| US7331038B1 (en) * | 2003-07-02 | 2008-02-12 | Amazon.Com, Inc. | Predictive prefetching to improve parallelization of document generation subtasks |
| US20100205606A1 (en) * | 2009-02-12 | 2010-08-12 | Panzer Adi | System and method for executing a complex task by sub-tasks |
| US20130080995A1 (en) * | 2011-09-23 | 2013-03-28 | Ahmad RAZA | Method and an apparatus for developing software |
| CN106445681A (en) * | 2016-08-31 | 2017-02-22 | 东方网力科技股份有限公司 | Distributed task scheduling system and method |
| WO2018126964A1 (en) * | 2017-01-04 | 2018-07-12 | 中兴通讯股份有限公司 | Task execution method and apparatus and server |
| CN111221726A (en) * | 2019-12-25 | 2020-06-02 | 平安普惠企业管理有限公司 | Test data generation method and device, storage medium and intelligent equipment |
| US20200327498A1 (en) * | 2016-03-21 | 2020-10-15 | National Ict Australia Limited | Business Process Execution on a Blockchain Platform |
| CN114281707A (en) * | 2022-01-12 | 2022-04-05 | 平安普惠企业管理有限公司 | Number making method, service application testing method and related equipment thereof |
| CN114925105A (en) * | 2022-03-25 | 2022-08-19 | 中国人寿保险股份有限公司 | Method for making number of insurance business and related equipment |
| CN115794641A (en) * | 2022-12-06 | 2023-03-14 | 平安健康保险股份有限公司 | Method, device and equipment for making number based on business process and storage medium |
| CN116383064A (en) * | 2023-04-05 | 2023-07-04 | 北京值得买科技股份有限公司 | Automatic script counting platform and method |
| US20230236880A1 (en) * | 2020-10-02 | 2023-07-27 | Tonkean, Inc. | Systems and methods for maintaining data objects to manage asynchronous workflows |
| CN116841758A (en) * | 2023-06-30 | 2023-10-03 | 腾讯科技（深圳）有限公司 | Workflow task processing method, device, computer equipment and storage medium |
| CN117056235A (en) * | 2023-09-27 | 2023-11-14 | 建信金融科技有限责任公司 | Test data generation method, device, equipment and medium |
-
2024
- 2024-01-23 CN CN202410093403.9A patent/CN117609102A/en active Pending
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5668994A (en) * | 1993-04-30 | 1997-09-16 | International Business Machines Corporation | Conversation management routine for co-operative processing applications |
| US7331038B1 (en) * | 2003-07-02 | 2008-02-12 | Amazon.Com, Inc. | Predictive prefetching to improve parallelization of document generation subtasks |
| US20100205606A1 (en) * | 2009-02-12 | 2010-08-12 | Panzer Adi | System and method for executing a complex task by sub-tasks |
| US20130080995A1 (en) * | 2011-09-23 | 2013-03-28 | Ahmad RAZA | Method and an apparatus for developing software |
| US20200327498A1 (en) * | 2016-03-21 | 2020-10-15 | National Ict Australia Limited | Business Process Execution on a Blockchain Platform |
| CN106445681A (en) * | 2016-08-31 | 2017-02-22 | 东方网力科技股份有限公司 | Distributed task scheduling system and method |
| WO2018126964A1 (en) * | 2017-01-04 | 2018-07-12 | 中兴通讯股份有限公司 | Task execution method and apparatus and server |
| CN111221726A (en) * | 2019-12-25 | 2020-06-02 | 平安普惠企业管理有限公司 | Test data generation method and device, storage medium and intelligent equipment |
| US20230236880A1 (en) * | 2020-10-02 | 2023-07-27 | Tonkean, Inc. | Systems and methods for maintaining data objects to manage asynchronous workflows |
| CN114281707A (en) * | 2022-01-12 | 2022-04-05 | 平安普惠企业管理有限公司 | Number making method, service application testing method and related equipment thereof |
| CN114925105A (en) * | 2022-03-25 | 2022-08-19 | 中国人寿保险股份有限公司 | Method for making number of insurance business and related equipment |
| CN115794641A (en) * | 2022-12-06 | 2023-03-14 | 平安健康保险股份有限公司 | Method, device and equipment for making number based on business process and storage medium |
| CN116383064A (en) * | 2023-04-05 | 2023-07-04 | 北京值得买科技股份有限公司 | Automatic script counting platform and method |
| CN116841758A (en) * | 2023-06-30 | 2023-10-03 | 腾讯科技（深圳）有限公司 | Workflow task processing method, device, computer equipment and storage medium |
| CN117056235A (en) * | 2023-09-27 | 2023-11-14 | 建信金融科技有限责任公司 | Test data generation method, device, equipment and medium |
Non-Patent Citations (4)
| Title |
|---|
| JUN-HUA REN: "Predicting Software Defects Using Self-Organizing Data Mining", 《IEEE ACCESS》, 9 June 2019 (2019-06-09), pages 122810 - 122810 * |
| KILMER: "通用技术 造数 - 我的理解与落地实践", pages 1 - 6, Retrieved from the Internet <URL:《https://testerhome.com/topics/35061》> * |
| 王立歆: "基于分层强化学习的自动化软件测试技术研究", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》, 15 January 2023 (2023-01-15), pages 138 - 511 * |
| 胡旭东: "自动驾驶汽车测试场景生成方法研究及其应用", 《万方》, 18 January 2022 (2022-01-18), pages 1 - 56 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105700888B (en) | A kind of visualization quick development platform based on jbpm workflow engine | |
| US9911092B2 (en) | Systems and methods for a real-time workflow platform | |
| CN110244942B (en) | Page generation method, device and system | |
| US20040107414A1 (en) | Method, a language and a system for the definition and implementation of software solutions | |
| CN111427561A (en) | Service code generation method and device, computer equipment and storage medium | |
| CN105956087A (en) | Data and code version management system and method | |
| CN111538731A (en) | Industrial data automatic generation report system | |
| CN111143577B (en) | Data labeling method, device and system | |
| US20230102947A1 (en) | Providing operations in accordance with worksheet relationships and data object relationships | |
| CN111190814B (en) | Method and device for generating software test case, storage medium and terminal | |
| CN111694561A (en) | Interface management method, device, equipment and storage medium | |
| CN114594927A (en) | Low code development method, device, system, server and storage medium | |
| CN108268615B (en) | Data processing method, device and system | |
| CN114707474A (en) | Report generation method and device, electronic equipment and computer readable storage medium | |
| US20200167209A1 (en) | Configurable Analytics For Microservices Performance Analysis | |
| CN115469849B (en) | Service processing system, method, electronic equipment and storage medium | |
| CN111949915A (en) | Visual customization method and system for production process of remote sensing product | |
| CN115329753B (en) | Intelligent data analysis method and system based on natural language processing | |
| CN111309378A (en) | Machine learning model life cycle management system and method | |
| CN117609102A (en) | Building industry Internet counting platform system testing method | |
| JP6063235B2 (en) | Work automation support system and work automation support method | |
| CN114281539A (en) | Resource allocation method, system and storage medium | |
| CN114035783A (en) | Software code knowledge graph construction method and tool | |
| CN114860218A (en) | Low code development method and device | |
| CN112527609A (en) | Early warning information pushing method and device, electronic equipment and storage medium |
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 |