CN114281688A - Codeless or low-code automatic case management method and device - Google Patents
Codeless or low-code automatic case management method and device Download PDFInfo
- Publication number
- CN114281688A CN114281688A CN202111567248.2A CN202111567248A CN114281688A CN 114281688 A CN114281688 A CN 114281688A CN 202111567248 A CN202111567248 A CN 202111567248A CN 114281688 A CN114281688 A CN 114281688A
- Authority
- CN
- China
- Prior art keywords
- code
- acquiring
- use case
- keyword
- case
- 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
Abstract
The disclosure relates to a codeless or low-code automatic case management method and a device, wherein the method comprises the following steps: receiving a use case compiling request; the use case writing request comprises a plurality of keywords; inquiring in a preset database based on a plurality of keywords, and acquiring an operation step corresponding to each keyword; and acquiring an attribute value corresponding to each operation step, acquiring a calling method corresponding to the attribute value in a code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case, and adding a tag. Therefore, the automatic case can be compiled based on the Chinese keywords, and the regression testing efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of test technologies, and in particular, to a method and an apparatus for code-free or low-code automated case management.
Background
With the rapid development of software development, the related testing technology is more and more valued by the industry. The test case is used as an important asset in the software testing process, is not only a verification standard for whether the software meets the requirements, but also an important basis for test execution in quality activities.
The automation test is more important, so how to manage the manual use case and the automation use case is more important, and in the related technology, the maintenance and execution cost of the test case management is higher.
Disclosure of Invention
In order to solve the technical problem or at least partially solve the technical problem, the present disclosure provides a codeless or low-code automatic use case management method and apparatus.
The present disclosure provides a codeless or low-code automatic case management method, which includes:
receiving a use case compiling request; wherein the use case writing request comprises a plurality of keywords;
based on the plurality of keywords, inquiring in a preset database, and acquiring an operation step corresponding to each keyword;
acquiring an attribute value corresponding to each operation step;
and acquiring a calling method corresponding to the attribute value in a code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case, and adding a tag.
In an optional embodiment of the present disclosure, before the receiving the use case writing request, the method further includes:
obtaining a plurality of test cases;
acquiring a user behavior operation step corresponding to each test case compiled according to a behavior driving rule;
generating an execution code and annotation information corresponding to each user behavior operation step; wherein the annotation information comprises: the attribute value composed of the key words, the classes, the methods and the input parameters;
and constructing a mapping relation between the execution code and the annotation information, storing the execution code in the code warehouse, and storing the mapping relation in a database.
In an optional embodiment of the present disclosure, the operation step of obtaining, based on the query of the plurality of keywords in a preset database, a corresponding keyword includes:
and matching each keyword with the plurality of user behavior operation steps in the preset database, and acquiring an executable step matched with each keyword as the operation step corresponding to each keyword.
In an optional embodiment of the present disclosure, the method for code-free or low-code automated use case management further includes:
receiving a test request; wherein the test request comprises a test identification;
and acquiring an automation case comprising an automatic label based on the test identification, and executing the automation case.
In an optional embodiment of the present disclosure, the method for code-free or low-code automated use case management further includes:
and acquiring a manual use case comprising a manual label based on the test identification, and manually executing the manual use case.
The present disclosure provides a codeless or low-code automatic use case management device, which includes:
the receiving request module is used for receiving a use case compiling request; wherein the use case writing request comprises a plurality of keywords;
the query acquisition module is used for acquiring an operation step corresponding to each keyword based on the query of the keywords in a preset database;
the matching acquisition module is used for acquiring the attribute value corresponding to each operation step;
and the mapping adding module is used for acquiring the calling method corresponding to the attribute value in the code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case and adding a tag.
In an optional embodiment of the present disclosure, the automated use case management apparatus without code or with low code further includes:
the acquisition case module is used for acquiring a plurality of test cases;
the obtaining step module is used for obtaining executable steps corresponding to each test case compiled according to behavior driving rules;
a generation module for generating an execution code and annotation information corresponding to each executable step; wherein the annotation information comprises: the attribute value composed of the key words, the classes, the methods and the input parameters;
and the construction storage module is used for constructing a mapping relation between the execution code and the annotation information, storing the execution code in the code warehouse and storing the mapping relation in a database.
In an optional embodiment of the present disclosure, the query obtaining module is specifically configured to:
and matching each keyword with the executable steps in the preset database, and acquiring the executable steps matched with each keyword as the operation steps corresponding to each keyword.
In an optional embodiment of the present disclosure, the automated use case management apparatus without code or with low code further includes:
the receiving module is used for receiving the test request; wherein the test request comprises a test identification;
and the acquisition execution module is used for acquiring an automation case comprising an automatic label based on the test identifier and executing the automation case.
In an optional embodiment of the present disclosure, the obtaining execution module is further configured to:
and acquiring a manual use case comprising a manual label based on the test identification, and manually executing the manual use case.
There is provided according to an embodiment of the present disclosure an electronic device including: a processor; a memory for storing the processor-executable instructions; the processor is used for reading the executable instruction from the memory and executing the instruction to realize the automatic use case management method without code or with low code provided by the embodiment of the disclosure.
According to an embodiment of the present disclosure, a computer-readable storage medium is provided, which stores a computer program for executing the method for code-free or low-code automated use case management provided by the embodiment of the present disclosure.
Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages:
receiving a use case compiling request; the use case writing request comprises a plurality of keywords; inquiring in a preset database based on a plurality of keywords, and acquiring an operation step corresponding to each keyword; and acquiring an attribute value corresponding to each operation step, acquiring a calling method corresponding to the attribute value in a code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case, and adding a tag. Therefore, the automatic case can be compiled based on the Chinese keywords, and the regression testing efficiency is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present disclosure, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a flowchart illustrating an automated case management method without code or with low code according to an embodiment of the present disclosure;
fig. 2 is a flowchart illustrating another method for code-free or low-code automated case management according to an embodiment of the present disclosure;
fig. 3 is a diagram illustrating a scenario of an automated use case management method without code or with low code according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an automated use case management device without code or with low code according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure.
Detailed Description
In order that the above objects, features and advantages of the present disclosure may be more clearly understood, aspects of the present disclosure will be further described below. It should be noted that the embodiments and features of the embodiments of the present disclosure may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced in other ways than those described herein; it is to be understood that the embodiments disclosed in the specification are only a few embodiments of the present disclosure, and not all embodiments.
Fig. 1 is a flowchart illustrating an automated use case management method without code or with low code according to an embodiment of the present disclosure, as shown in fig. 1, including:
step 101, receiving a use case compiling request; wherein the use case authoring request comprises a plurality of keywords.
In the embodiment of the disclosure, a user can select a plurality of keywords and send a use case compiling request based on an actual use case compiling requirement, so that the use case compiling request can be received through an access interface, the use case compiling request is analyzed, and the plurality of keywords, such as "user", "click", "report", and the like, are obtained.
102, inquiring in a preset database based on a plurality of keywords, and acquiring an operation step corresponding to each keyword.
In the embodiment of the disclosure, a database is preset, in one embodiment mode, a plurality of test cases are obtained, a user behavior operation step corresponding to each test case written according to a behavior driving rule is obtained, and an execution code and annotation information corresponding to each user behavior operation step are generated; wherein the annotation information includes: and constructing a mapping relation between the execution code and the annotation information by using the attribute values formed by the key words, the classes, the methods and the input parameters, storing the execution code in a code warehouse, and storing the mapping relation in a database. Therefore, all manual cases can be converted into automatic cases, and the testing efficiency is improved.
The operation steps refer to login, creation, query and the like. In a specific embodiment, each keyword is matched with a plurality of executable steps in the preset database, and the executable steps matched with each keyword are obtained as the operation steps corresponding to each keyword.
And 103, acquiring an attribute value corresponding to each operation step.
And 104, acquiring a calling method corresponding to the attribute value in the code warehouse based on the method and the annotation mapping relation, combining the calling method into an automatic case, and adding a tag.
In the disclosed embodiment, 1. each operation step is a string stored in a database; 2. meanwhile, each character string can correspond to annotation information of one method in java codes through regular matching. Continuing with the above test case example as follows: 1) the operation steps are as follows: a user A reports event data B; 2) there is a piece of data in the database, the annotation information key is "user { string } reporting event data { string }", the attribute value: { class: "User", function: "UpdateEvent", parameters: "string" }; 3) each operation step can be inquired through regular matching, and corresponding attribute values are stored in a database, wherein the attribute values are { class: "User", function: "updateEvent", parameters: "string" }; 4) through the reflection mechanism of java, the method of this class can be called as follows:
the tag can be selected according to application requirements to identify a use case, such as a basic tag: project name, use case name, creation time, maintenance user, etc.; product labeling: the belonging component/module/service, the belonging version, the case test function completion degree and the like; grade label: use case levels (such as P0, P1, P2), composite levels (such as L1, L2, L3), and the like; code labeling: coverage functions, coverage paths, etc.; environment label: applicable environment, etc.; executing a label: execution duration, execution time, execution success rate, number of found problems, etc., and other tags: whether automated, etc. One or more tags may be selected for use in identifying the generated automation use case for subsequent use case management.
It should be noted that some operation steps may not find the corresponding calling method, and may prompt the user that the operation step cannot be executed, and the test case may also be marked as a non-automated test case.
To sum up, the code-free or low-code automatic case management method according to the embodiment of the present disclosure receives a case compiling request; the use case writing request comprises a plurality of keywords; inquiring in a preset database based on a plurality of keywords, and acquiring an operation step corresponding to each keyword; and acquiring an attribute value corresponding to each operation step, acquiring a calling method corresponding to the attribute value in a code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case, and adding an automatic tag. Therefore, the automatic case can be compiled based on the Chinese keywords, and the regression testing efficiency is improved.
Fig. 2 is a flowchart illustrating another method for code-free or low-code automated case management according to an embodiment of the present disclosure, and as shown in fig. 2, the method includes:
step 201, obtaining a plurality of test cases, obtaining a user behavior operation step corresponding to each test case compiled according to a behavior driving rule, and generating an execution code and annotation information corresponding to each user behavior operation step; wherein the annotation information includes: key, class, method, and input parameter.
Step 202, constructing a mapping relation between the execution code and the annotation information, storing the execution code in a code warehouse, and storing the mapping relation in a database.
Specifically, the behavior-driven rules can be set as needed, such as the user story description way of (Then) xxx if (Given) xxx, When (When) xxx.
For example, the test case writes each test case according to the behavior driving rule, obtains a plurality of executable steps, i.e., traverses all code directories conforming to the rule, and stores the executable steps and methods in the database, and the test cases are described as follows:
feature: testing whether the system metadata management function is correct;
scenario: creating a meta-event with the identity of a common user, and inquiring related data;
given: a common user 'Xiaoming' logs in the system;
when: creating a meta event '$ login', a Chinese name 'login event';
the method comprises the following steps: the query meta-event '$ login' fits expectations.
That is, all execution operations are packaged into steps in a behavior-driven manner and stored in a preset database, an external access interface is provided, all executable steps can be preloaded, and the retrieval capability is provided, so that when a use case is written, the use case can be retrieved through keywords.
For example, the name of the class to be scanned is known through the configuration path; 2) acquiring all included methods and specific annotations corresponding to the methods through the class names; 3) the annotation content is a key word, a class, a method and an input parameter form an attribute value, and the mapping relation is stored in a database; the analytic code is as follows:
step 203, receiving a use case compiling request; wherein the use case authoring request comprises a plurality of keywords.
In the embodiment of the disclosure, a user can select a plurality of keywords and send a use case compiling request based on an actual use case compiling requirement, so that the use case compiling request can be received through an access interface, the use case compiling request is analyzed, and the plurality of keywords, such as "user", "click", "report", and the like, are obtained.
And arranging 204, in a preset database, matching each keyword with a plurality of executable steps, and acquiring the executable steps matched with each keyword as operation steps corresponding to each keyword.
For example, 1. abstract the test case into user behavior operation steps, 2. each operation step contains several keywords. Taking a scenario that a user reports a buried point event as an example, the user behavior operation steps corresponding to the test case are as follows: 1) a user A reports event data B; 2) the data B is successfully processed by the data stream processing subsystem; 3) storing the data B into a kudu database; 4) the data B is correctly inquired through an analysis model interface; 3. each user behavior operation step comprises a plurality of keywords, such as inputting 'user', and can be matched with the user behavior operation steps: reporting event data xx by a user xx; a user xx inquires xx events; user xx logs out of the system; and (5) clicking a system upgrading button and the like by a user xx, returning all operation steps related to user operation to the current case boundary editing interface, selecting proper operation steps, inputting parameters related to the case compiling design, and finally forming a complete operation behavior, and forming a test scene by using more operation behaviors.
And step 205, acquiring an attribute value corresponding to each operation step, acquiring a calling method corresponding to the attribute value in the code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case, and adding a tag.
Specifically, the keywords can be matched with the operation steps, the associated annotation information can be obtained based on the operation steps, the corresponding attribute values can be queried based on the annotation information, the mapping relationship between the annotation information and the attribute values is stored in the database, and the operation steps matched with the keywords belong to the annotation information, so that the attribute values corresponding to each operation step can be obtained.
In the disclosed embodiment, 1. each operation step is a string stored in a database; 2. meanwhile, each character string can correspond to annotation information of one method in java codes through regular matching. Continuing with the above test case example as follows: 1) the operation steps are as follows: a user A reports event data B; 2) there is a piece of data in the database, the annotation information key is "user { string } reporting event data { string }", the attribute value: { class: "User", function: "UpdateEvent", parameters: "string" }; 3) the database can be inquired through the regular matching, and the corresponding attribute values are { class: "User", function: "updateEvent", parameters: "string" }; 4) the method of this class can be invoked in the following way by the reflection mechanism of java.
Step 206, receiving a test request; wherein the test request comprises a test identification.
Step 207, acquiring an automation case comprising an automatic label based on the test identifier, and executing the automation case; or, acquiring a manual use case comprising a manual label based on the test identification, and then manually executing the manual use case.
Specifically, when a test request is made, a test identifier is obtained, and the test identifier can uniquely identify one test case, so that the test case can be obtained based on the test identifier, and for an automatic case and a manual case, identification needs to be performed based on a label, so that automatic execution of the automatic case is screened, and manual intervention execution of the manual case also can be screened.
To sum up, in the code-free or low-code automated case management method according to the embodiment of the present disclosure, by acquiring a plurality of test cases, a user behavior operation step corresponding to each test case compiled according to a behavior driving rule is acquired, and an execution code and annotation information corresponding to each user behavior operation step are generated; wherein the annotation information includes: constructing a mapping relation between an execution code and annotation information by using an attribute value consisting of a keyword, a class, a method and an input parameter, storing the execution code in a code warehouse, storing the mapping relation in a database, and receiving a use case compiling request; the method comprises the steps that a case compiling request comprises a plurality of keywords, each keyword is matched with a plurality of executable steps in a preset database, the executable steps matched with each keyword are obtained and serve as operation steps corresponding to each keyword, attribute values corresponding to each operation step are obtained, calling methods corresponding to the attribute values are obtained in a code warehouse based on a method and annotation mapping relation, the calling methods are combined into an automatic case, a tag is added, and a test request is received; the test request comprises a test identifier, and based on the test identifier, an automation case comprising an automatic label is obtained, and then the automation case is executed; or, acquiring a manual use case comprising a manual label based on the test identification, and then manually executing the manual use case. Therefore, all automatic cases and manual cases can be maintained conveniently, the non-automatic cases can be automated in time, and the regression testing efficiency is improved.
As an example of a scenario, as shown in fig. 3, 1) abstracting a user behavior in a scenario test case into a suitable keyword and parameter combination, such as "user a reports time data B"; 2) writing related implementation methods and corresponding annotations; 3) ensuring that the basic method can cover the scene combination of the basic test case; 4) scanning the mapping relation of the execution code and the annotation to a database;
5) uploading code to a git (code platform) repository; 6) the system senses the update of the git warehouse by configuring a gitlab hook, pushes the latest execution code to the local, and re-scans the mapping relation of the whole user behavior data, and updates the new behavior corresponding relation data to the database; 7) when the test case is compiled, searching through keywords; 8) finally, through various automatically executable behavior steps, a scene test case capable of being automatically executed is formed.
Corresponding to the foregoing method for automatically managing use cases without code or with low code, an embodiment of the present disclosure provides an apparatus for automatically managing use cases without code or with low code, and fig. 4 is a schematic structural diagram of an apparatus for automatically managing use cases without code or with low code provided by an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device, as shown in fig. 4, the apparatus 400 for automatically managing use cases without code or with low code includes the following modules: a request receiving module 401, a query obtaining module 402, a matching obtaining module 403 and a mapping adding module 404.
A request receiving module 301, configured to receive a use case compiling request; wherein the use case authoring request comprises a plurality of keywords.
A query obtaining module 402, configured to obtain, based on the query of the multiple keywords in a preset database, an operation step corresponding to each keyword.
A matching obtaining module 403, configured to obtain an attribute value corresponding to each operation step.
And the mapping adding module 404 is configured to obtain calling methods corresponding to the attribute values in the code repository based on the method and the annotation mapping relationship, combine the calling methods into an automatic use case, and add a tag.
In some embodiments, the code-free or low-code automated use case management apparatus further includes:
and the case obtaining module is used for obtaining a plurality of test cases.
And the obtaining step module is used for obtaining the executable steps corresponding to each test case which is compiled according to the behavior driving rule.
A generation module for generating an execution code and annotation information corresponding to each executable step; wherein the annotation information comprises: key, class, method, and input parameter.
And the construction storage module is used for constructing a mapping relation between the execution code and the annotation information, storing the execution code in the code warehouse and storing the mapping relation in a database.
In some embodiments, the query obtaining module 302 is specifically configured to:
and matching each keyword with the executable steps in the preset database, and acquiring the executable steps matched with each keyword as operation steps corresponding to each keyword.
In some embodiments, the code-free or low-code automated use case management apparatus further includes:
the receiving module is used for receiving the test request; wherein the test request comprises a test identification;
and the acquisition execution module is used for acquiring an automation case comprising an automatic label based on the test identifier and executing the automation case.
In some embodiments, the obtaining execution module is further configured to:
and acquiring a manual use case comprising the manual label based on the test identification, and manually executing the manual use case.
To sum up, the code-free or low-code automatic use case management device according to the embodiment of the present disclosure receives a use case compiling request; the use case writing request comprises a plurality of keywords; inquiring in a preset database based on a plurality of keywords, and acquiring an operation step corresponding to each keyword; and acquiring an attribute value corresponding to each operation step, acquiring a calling method corresponding to the attribute value in a code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case, and adding an automatic tag. Therefore, the automatic case can be compiled based on the Chinese keywords, and the regression testing efficiency is improved.
The codeless or low-code automatic case management device provided by the embodiment of the invention can execute the codeless or low-code automatic case management method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Fig. 5 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure. As shown in fig. 5, the electronic device includes a processor 510, a memory 520, an input device 530, and an output device 540; the number of the processors 510 in the electronic device may be one or more, and one processor 510 is taken as an example in fig. 5; the processor 510, the memory 520, the input device 530 and the output device 540 in the electronic apparatus may be connected by a bus or other means, and the connection by the bus is exemplified in fig. 5.
The memory 520 may be implemented as a computer-readable storage medium for storing software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the code-less or low-code automated case management methods in embodiments of the present invention. The processor 510 executes various functional applications and data processing of the electronic device by running software programs, instructions and modules stored in the memory 520, that is, implements the code-free or low-code automated use case management method provided by the embodiment of the present invention.
The memory 520 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 520 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, memory 520 may further include memory located remotely from processor 510, which may be connected to an electronic device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 530 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic apparatus, and may include a keyboard, a mouse, and the like. The output device 540 may include a display device such as a display screen.
The disclosed embodiments also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are used to implement the method for code-free or low-code automated case management provided by the embodiments of the present invention.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the operations of the method described above, and may also perform related operations in the codeless or low-code automatic use case management method provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the above search apparatus, each included unit and module are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present disclosure, which enable those skilled in the art to understand or practice the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A codeless or low-code automatic case management method is characterized by comprising the following steps:
receiving a use case compiling request; wherein the use case writing request comprises a plurality of keywords;
based on the plurality of keywords, inquiring in a preset database, and acquiring an operation step corresponding to each keyword;
acquiring an attribute value corresponding to each operation step;
and acquiring a calling method corresponding to the attribute value in a code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case, and adding a tag.
2. The method for code-less or code-less automated use case management according to claim 1, further comprising, before the receiving a use case composition request:
obtaining a plurality of test cases;
acquiring a user behavior operation step corresponding to each test case compiled according to a behavior driving rule;
generating an execution code and annotation information corresponding to each user behavior operation step; wherein the annotation information comprises: the attribute value composed of the key words, the classes, the methods and the input parameters;
and constructing a mapping relation between the execution code and the annotation information, storing the execution code in the code warehouse, and storing the mapping relation in a database.
3. The codeless or low-code automatic use case management method according to claim 2, wherein the operation step of obtaining the keyword corresponding to each keyword based on the query of the keywords in a preset database comprises:
and matching each keyword with the plurality of user behavior operation steps in the preset database, and acquiring an executable step matched with each keyword as the operation step corresponding to each keyword.
4. The codeless or low-code automated use case management method according to claim 1, further comprising:
receiving a test request; wherein the test request comprises a test identification;
and acquiring an automation case comprising an automatic label based on the test identification, and executing the automation case.
5. The codeless or low-code automated use case management method according to claim 4, further comprising:
and acquiring a manual use case comprising a manual label based on the test identification, and manually executing the manual use case.
6. An automated use case management device without code or low code, comprising:
the receiving request module is used for receiving a use case compiling request; wherein the use case writing request comprises a plurality of keywords;
the query acquisition module is used for acquiring an operation step corresponding to each keyword based on the query of the keywords in a preset database;
the matching acquisition module is used for acquiring the attribute value corresponding to each operation step;
and the mapping adding module is used for acquiring the calling method corresponding to the attribute value in the code warehouse based on the method and the annotation mapping relation, combining the calling methods into an automatic case and adding a tag.
7. The codeless or low-code automated use case management device according to claim 6, further comprising:
the acquisition case module is used for acquiring a plurality of test cases;
the obtaining step module is used for obtaining executable steps corresponding to each test case compiled according to behavior driving rules;
a generation module for generating an execution code and annotation information corresponding to each executable step; wherein the annotation information comprises: the attribute value composed of the key words, the classes, the methods and the input parameters;
and the construction storage module is used for constructing a mapping relation between the execution code and the annotation information, storing the execution code in the code warehouse and storing the mapping relation in a database.
8. The codeless or low-code automated use-case management device according to claim 6, wherein the query obtaining module is specifically configured to:
and matching each keyword with the executable steps in the preset database, and acquiring the executable steps matched with each keyword as the operation steps corresponding to each keyword.
9. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing the processor-executable instructions;
the processor is used for reading the executable instruction from the memory and executing the instruction to realize the codeless or low-code automatic use case management device method of any one of the claims 1 to 5.
10. A computer-readable storage medium, wherein the storage medium stores a computer program for executing the codeless or low-code automated use case management apparatus method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111567248.2A CN114281688A (en) | 2021-12-20 | 2021-12-20 | Codeless or low-code automatic case management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111567248.2A CN114281688A (en) | 2021-12-20 | 2021-12-20 | Codeless or low-code automatic case management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114281688A true CN114281688A (en) | 2022-04-05 |
Family
ID=80873247
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111567248.2A Pending CN114281688A (en) | 2021-12-20 | 2021-12-20 | Codeless or low-code automatic case management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114281688A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117724986A (en) * | 2024-02-08 | 2024-03-19 | 云账户技术(天津)有限公司 | Method and device for automatically operating kafka in use case execution |
-
2021
- 2021-12-20 CN CN202111567248.2A patent/CN114281688A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117724986A (en) * | 2024-02-08 | 2024-03-19 | 云账户技术(天津)有限公司 | Method and device for automatically operating kafka in use case execution |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2013329525B2 (en) | System and method for recursively traversing the internet and other sources to identify, gather, curate, adjudicate, and qualify business identity and related data | |
| US20170357486A1 (en) | Enhancing a crowdsourced integrated development environment application | |
| CN104081380A (en) | Identifying and ranking solutions from multiple data sources | |
| CN108762743B (en) | Data table operation code generation method and device | |
| CN113157315A (en) | Method, device, equipment and medium for identifying difference information of different versions of software | |
| CN107145538B (en) | Table data query method, device and system | |
| CN116560683A (en) | Software updating method, device, equipment and storage medium | |
| CN111651196A (en) | Document publishing method, device and server | |
| WO2022012327A1 (en) | Code analysis method and system, and computing device | |
| CN114281688A (en) | Codeless or low-code automatic case management method and device | |
| CN111984659B (en) | Data updating method, device, computer equipment and storage medium | |
| KR101104739B1 (en) | Semantic tagging server for supporting reuse of software artifacts, and methods thereof | |
| CN115544050A (en) | Operation log recording method, device, equipment and storage medium | |
| CN115291887A (en) | Code generation method, device, equipment and storage medium | |
| CN112069236A (en) | Associated file display method, device, equipment and storage medium | |
| CN112307736A (en) | Application project creating method, device, equipment and storage medium | |
| CN108132971B (en) | Analysis method and device for database fragment files | |
| CN111522627B (en) | Docker mirror image management method, device, equipment and medium | |
| CN109871231B (en) | Code sharing method and system | |
| CN116257819A (en) | Rapid open source license identification method, system and medium for large-scale software | |
| CN113177157A (en) | Label separation method, device, equipment and storage medium | |
| CN113377367A (en) | Data collection method and device, computer equipment and storage medium | |
| CN115052035A (en) | Message pushing method, device and storage medium | |
| CN116578389A (en) | Automatic generation method and device for container mirror image configuration file based on template representation | |
| CN117708385A (en) | Operation method and device of resource character string 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 |