After obtaining the entity directory, one possible implementation of step S102 includes: acquiring an entity directory corresponding to a service system, wherein the entity directory comprises one or more entities to be tested; and configuring a test case template corresponding to each test scene according to the corresponding relation between the one or more entities to be tested and the one or more test scenes respectively.

One or more business processes to be tested are also in the scene to be tested. And establishing a corresponding relation between the scene to be tested and the covered one or more entities to be tested according to the one or more entities to be tested covered by the business process. The scene to be tested can be obtained according to the analysis result of the NLU on the requirement document. For example, taking the recruitment system as an example, the recruitment status is set to denied when the age of the applicant is less than 18, as described in the requirement document. In the description of the requirement design, a scene A to be tested can be obtained through an NLU (line of sight) technology, wherein the scene A to be tested covers the age attribute and the recruitment state attribute of an applicant of the entity to be tested, namely the entity to be tested corresponding to the scene A to be tested is the applicant, and the entity attribute of the entity to be tested is the age and the recruitment state.

The corresponding relationship may be in the form of a corresponding table of the to-be-tested scenes and the entity attributes of the to-be-tested entities, that is, an entity attribute list of one to-be-tested entity corresponds to each to-be-tested scene. Or when defining the scene to be tested, using the entity attribute of the entity to be tested as the key word to label the scene to be tested. For example, when a scene A to be tested is defined, the age and the recruitment state are used as keywords to label the scene A to be tested. Namely, the scene A to be tested corresponds to two entity attributes of age and recruitment state. And when defining the scene B to be tested, marking the scene B to be tested by taking the name and the academic calendar as key words.

If the corresponding relation is in a corresponding table mode, after a generation request of the test case is obtained, an entity attribute list corresponding to a scene to be tested in the corresponding table is read according to the scene to be tested indicated by the generation request, and one or more entity attributes are obtained. If the method is a keyword labeling mode, one or more keywords corresponding to the scene to be tested can be extracted, namely one or more entity attributes corresponding to the scene to be tested are obtained.

And determining one or more entity attributes corresponding to the scene to be tested according to the corresponding relation. And configuring a corresponding target test case template for the scene to be tested according to the one or more entity attributes. The test case template can be one or more types of test case templates, and the types of the test column templates can be predefined by a tester according to actual requirements.

In one embodiment of the present invention, the test case template type includes: the data verification type test case template and the data setting type test case template; the data verification type test case template is used for verifying whether the entity attribute value is in a preset data range or not; the data setting type test case template refers to a test case template used for setting an entity attribute value and verifying whether the setting operation is successful.

Meanwhile, one possible implementation of step S102 includes: the determining a target test case template corresponding to the scene to be tested from one or more pre-configured test case templates includes: and determining the target test case template corresponding to the entity attribute from the data verification type test case template and the data setting type test case template according to the entity attribute of the entity to be tested corresponding to the scene to be tested.

Taking the recruitment system as an example, the entity attributes corresponding to the scene B to be tested are name and academic calendar. For the name, which is an entity attribute, one or more test case templates can be determined from the data verification class test case templates as target test case templates. For example, one of the data verification class test case templates is used to verify whether the name is empty, and the other data verification class test case template is used to verify whether the name character range is out. For the entity attribute of the academic calendar, one or more test case templates can be determined from the data setting class test case templates as target test column templates. For example, one of the data setup class test case templates is used to set the academic story as a maverick and verify whether the setup operation was successful. Two types of test case templates can also be configured for the same entity attribute. For example, for the entity attribute of the academic calendar, the data setting type test case template can be used to set the academic calendar as a college or university subject, and then the data verification type test case template can be used to verify whether the value of the academic calendar is the college or university subject.

After determining the corresponding test case template type according to the entity attribute of the entity to be tested, determining one or more test case templates of the corresponding test case template type from one or more pre-configured test case templates, and using the test case template as a target test case template of the scene to be tested. Correspondingly, one or more entity attributes contained in the target test case template are also determined.

Step S103: and generating test data according to the historical data set and/or the entity directory corresponding to the target test case template.

Step S104: and filling the test data into the target test case template to generate a target test case corresponding to the scene to be tested so as to respond to the generation request.

When generating the test data, the test data may be generated directly according to the obtained entity directory, or may be generated by matching history data corresponding to the entity directory from a history data set and using the history data as the test data. And historical data can be used first, and more test data can be generated according to the actual test requirements and the entity directory according to the test results of the historical data.

In a preferred embodiment of step S103, preferentially using the historical data in the historical data set as the test data, and when the test result of the test data cannot meet the actual test requirement, generating the test data according to the entity directory, and incrementally updating the newly generated test data into the historical data set for use in the subsequent test. Along with the fact that the continuously updated historical data set is larger and larger, the generated test data are more and more in quantity, the accuracy and the matching degree of the test data are higher and higher, repetitive work can be avoided to a certain extent, the efficiency of generating the test data is improved, the test result is output more timely, the test progress is accelerated, and the test quality is improved.

Thus, one possible implementation of step S103 includes: determining one or more first target entities included in the target test case template; determining historical data corresponding to the one or more first target entities from the historical dataset; and taking the historical data as the test data.

And acquiring one or more first target entities and one or more entity attributes of the target entities, which are subjected to the coverage test of the target test case template, from the target test case template. And then searching and matching the historical data of the entity attributes in a historical data set, and taking the obtained historical data as the test data.

It is to be understood that the historical data set may be one or more data used to test entity attributes of the entity under test over a historical multiple test accumulation process.

Taking the recruitment system as an example, one target test case template of the scene B to be tested may be to set the name of the applicant as x (x is test data), and verify whether the name is empty. At this time, a set of history data corresponding to the name attribute is searched from the history data set, and the duration data is used as test data. For example, the history data may be one or more data, wherein the data may be character data consistent with the data type of the name attribute, and the character data may be character string data having a length exceeding a specific length, character string data meeting a length range requirement, or null character data. The historical data may already contain more diverse data due to the accumulation of historical multiple tests, including, for example, forward data, reverse data, normal range data, out-of-range data, and the like. Therefore, the historical data corresponding to the name attribute is obtained from the historical data set, and is used as the test data x of the name attribute, so that the efficiency of generating the test data is high, and the workload of testers is reduced to a certain extent.

And after the test data are obtained, filling the test data into the target test case template to generate one or more test cases corresponding to the scene to be tested.

Whether the generated test case meets the test requirement or not can be determined according to the actual test requirement. The test coverage rate of the test result can be measured, and the test coverage rate can also be measured according to the target number of the test cases set before the test starts.

In the prior art, because the efficiency of generating test data by adopting a manual mode is low, and the number of manually designed test data sets is often insufficient, the test coverage rate of a test result is likely to be not high enough, and more important defects of a service system are likely to be missed, so that the quality and the stability of the service system cannot be ensured.

In a preferred embodiment of the present invention, test coverage is used to determine whether the number of test cases is sufficient. Wherein the test coverage is a measure of the completion of the test. It typically scales the test case execution against some coverage criteria to determine whether the test is executed sufficiently. Test coverage may be statistically derived from the corresponding code coverage tool.

Therefore, in an embodiment of the present invention, after the filling the test data into the target test case template, the method further includes: performing pretesting by using the test case generated after filling to obtain a pretesting result; judging whether the test coverage rate in the pretest result is not less than a coverage rate threshold corresponding to the scene to be tested; and if so, taking the test case generated after the filling as the target test case. And the test data used for filling the target test case template is the test data obtained according to the historical data set.

It can be understood that, before the scene to be tested is tested, a coverage threshold may be preset, and the coverage threshold may be set according to historical test experience or actual test requirements. In early testing of the traffic system, the coverage threshold may be set to a relatively low value, for example 20%, and may be stepped up to 90% or more over multiple tests and iterations of the traffic system.

And filling the historical data serving as test data into the target test case template, and performing pretest by using the test case generated after filling to obtain a pretest result. The pretest result comprises a statistical result of the test coverage rate after the test case is executed. And if the test coverage rate is greater than or equal to the preset coverage rate threshold, using a test case generated by filling test data obtained from a historical data set as the target test case.

For example, taking a recruitment system as an example, setting the coverage threshold of the scene a to be tested to be 80%, matching a group of data y of the age attribute and a group of data z of the recruitment state attribute from the historical data set, and filling the y and the z as test data into a target test case template of the scene a to be tested to generate one or more test cases corresponding to the scene a to be tested. And using the test case in the pretest of the scene A to be tested, wherein the obtained test coverage rate is 90%, and the test coverage rate result of the pretest is greater than the coverage rate threshold value, so that the test case generated after filling by using y and z as test data is the target test case of the scene A to be tested.

On the contrary, if the test coverage in the pretest result of the to-be-tested scene a is less than 80%, in addition to the test data y and the test data z, more test data needs to be added to fill the target test case template of the to-be-tested scene a to generate more test cases, so as to obtain a higher test coverage result.

Therefore, in an embodiment of the present invention, in a case that the test coverage in the pretest result is smaller than the coverage threshold corresponding to the scene to be tested, the method further includes: circularly executing the following steps until the test coverage is not less than the coverage threshold: generating test data according to the entity directory corresponding to the target test case template, and filling the test case template with the generated test data and the test data obtained according to the historical data set; and performing pretesting by using the test case generated after filling to obtain a pretesting result.

The generating of the test data according to the entity directory corresponding to the target test case template includes: determining an entity directory corresponding to the target test case template by using an NLU (NLU) technology, wherein the entity directory comprises one or more second target entities; respectively determining data types and/or data structures corresponding to the one or more second target entities; and generating the test data according to the data type and/or data structure corresponding to the one or more second target entities.

The entity directory corresponding to the target test case template is determined by the NLU technology, and in fact, the entity directory corresponding to the target test case template is determined according to an analysis result obtained by analyzing a requirement document and a detailed design document of the business system by the NLU technology.

One or more second target entities, one or more entity attributes of the second target entities, and data types and/or data structures of the entity attributes are contained in the entity directory. For example, an entity list of applicants in the recruitment system as shown in table 1. And generating test data of the entity attribute according to the data type of the entity attribute. The test data of the name attribute of the alphabetic character string can be generated by a regular expression matching method, the test data of the mobile phone number attribute of the numeric character string can be generated by a regular expression matching method, a certain random rule can be written by using a script language to generate the test data, for example, the random integer data is generated for the test data of the age attribute, and the generation of the test data can be realized by means of a tool. In the process of generating the test data, a tester can review the generated test data, remove irrelevant data, formulate a rule for generating the test data according to the constraint and the limitation on the entity attribute and adjust the rule so that the generated test data better meets the test requirement, and the process is not repeated herein.

Merging the test data generated according to the data type and/or the data structure of the entity attribute in the entity directory with the test data obtained according to the historical data set, wherein repeated data may exist, removing the repeated data, filling the merged data into the target test case template to generate a test case, performing pretest, and determining whether to continue generating more test data according to the entity directory according to the comparison between the test coverage rate of the pretest result and the coverage rate threshold value until the test coverage rate of the subsequent pretest is not less than the coverage rate threshold value.

After the test of the scene to be tested is completed, in an embodiment of the present invention, the test data generated according to the entity directory is updated to the historical data set.

And when the obtained test coverage rate is greater than or equal to a coverage rate threshold value, namely after a target test case corresponding to the scene to be tested is obtained, updating the test data increment generated according to the entity directory into the historical data set so as to continuously increase the historical data set, so that the test data and the test case can be generated more quickly in subsequent tests, and the test efficiency is improved.

In an embodiment of the present invention, as the historical data set is continuously increased, there may be a large amount of data that one or more entity attributes match in the historical data set, and at this time, data corresponding to the entity attributes in the historical data set may be marked according to actual needs, for example, for some entity attribute values that occur in a business system at a high frequency, in the historical data set, corresponding data may be marked at a high frequency, so that when data of the entity attributes are subsequently matched from the historical data set, data with high frequency marks may be preferentially matched, so that accuracy and matching degree of test data may be improved.

In an embodiment of the present invention, it may also occur that when a plurality of service systems are tested, there may be an entity G to be tested existing in both the service system E and the service system F, and then the test data increment corresponding to the entity G to be tested in the historical data set used in the service system E may be updated to the historical data set used in the service system F. If the similarity of the service systems is very large, the historical data sets of the two service systems can be combined to form a larger historical data set, and the test data in the historical data set is continuously increased through multiple tests on the same service system or multiple tests on multiple service systems, so that the efficiency of generating test cases is improved.

As shown in fig. 2, an embodiment of the present invention provides a flow chart illustrating generation of test data of a scene to be tested.

Step S201: and carrying out syntactic and semantic analysis on the requirement document and the detailed design document of the business system through the NLU to obtain an analysis result.

Step S202: acquiring an entity directory of the entity to be detected according to the analysis result; and determining a target test case template corresponding to the scene to be tested.

Step S203: generating test data from the historical data set; and filling the test data into the target test case template to generate a target test case and perform pretesting.

And matching data corresponding to one or more entity attributes contained in the scene to be tested from a historical data set, filling the data serving as test data into the target test case template to generate one or more target test cases, executing the target test cases to perform pretesting, and acquiring a pretesting result.

Step S204: and judging whether the testing coverage rate of the pretest is smaller than a coverage rate threshold value.

And presetting a coverage rate threshold according to the actual test requirement. The test coverage is included in the pretest results.

Step S205: if so, namely the testing coverage rate of the pretest is smaller than the coverage rate threshold value, generating testing data according to the entity directory of the entity to be tested, and updating the testing data to the historical data set.

Updating the test data into the historical dataset is an incremental update, i.e., removing duplicate data.

After the history data set is updated, the process jumps to step S203 to continue execution.

Step S206: if not, namely the testing coverage rate of the pretest is greater than or equal to the coverage rate threshold value, the process of generating the testing data is stopped.

According to the method for generating the test case, provided by the embodiment of the invention, the test data can be generated according to the pre-configured test case template and the historical data set, and the target test case template is filled by using the test data to generate the target test case. Therefore, the automatic generation of the test case is realized, the workload of testers is reduced, the generation efficiency of the test case is improved, and the test efficiency can be improved.

As shown in fig. 3, an embodiment of the present invention provides anapparatus 300 for generating a test case, including: anacquisition module 301, adetermination module 302, ageneration module 303 and afilling module 304; wherein,

the obtainingmodule 301 is configured to obtain a generation request of a test case, where the generation request indicates a scene to be tested;

the determiningmodule 302 is configured to determine a target test case template corresponding to the scene to be tested from one or more pre-configured test case templates;

thegenerating module 303 is configured to generate test data according to a historical data set and/or an entity directory corresponding to the target test case template;

thefilling module 304 is configured to fill the test data into the target test case template, and generate a target test case corresponding to the scene to be tested, so as to respond to the generation request.

In an embodiment of the present invention, the determiningmodule 302 is configured to obtain an entity directory corresponding to a service system, where the entity directory includes one or more entities to be tested; and configuring a test case template corresponding to each test scene according to the corresponding relation between the one or more entities to be tested and the one or more test scenes respectively.

In an embodiment of the present invention, the determiningmodule 302 is configured to obtain an entity directory corresponding to a service system, and includes: analyzing a requirement document and a detailed design document of the business system through an NLU technology to determine one or more entities to be tested from the requirement document and the detailed design document; and generating the entity directory according to the analysis result.

In an embodiment of the present invention, the determiningmodule 302 is configured to determine the entity directory further includes: and the entity attribute of the entity to be tested and the data type of the entity attribute.

In an embodiment of the present invention, the determiningmodule 302, configured to determine the test case template type, includes: the data verification type test case template and the data setting type test case template; the data verification type test case template is used for verifying whether the entity attribute value is in a preset data range or not; the data setting type test case template refers to a test case template used for setting an entity attribute value and verifying whether the setting operation is successful.

In an embodiment of the present invention, the determiningmodule 302 is configured to determine, from one or more pre-configured test case templates, a target test case template corresponding to the scene to be tested, and includes: and determining the target test case template corresponding to the entity attribute from the data verification type test case template and the data setting type test case template according to the entity attribute of the entity to be tested corresponding to the scene to be tested.

In an embodiment of the present invention, thegenerating module 303 is configured to determine one or more first target entities included in the target test case template; determining historical data corresponding to the one or more first target entities from the historical dataset; and taking the historical data as the test data.

In an embodiment of the present invention, thegenerating module 303 is configured to determine an entity directory corresponding to a target test case template by using an NLU technology, where the entity directory includes one or more second target entities; respectively determining data types and/or data structures corresponding to the one or more second target entities; and generating the test data according to the data type and/or data structure corresponding to the one or more second target entities.

In an embodiment of the present invention, thepadding module 304 is configured to, after padding the test data into the target test case template, further include: performing pretesting by using the test case generated after filling to obtain a pretesting result; judging whether the test coverage rate in the pretest result is not less than a coverage rate threshold corresponding to the scene to be tested; and if so, taking the test case generated after the filling as the target test case. And the test data used for filling the target test case template is the test data obtained according to the historical data set.

In an embodiment of the present invention, the fillingmodule 304 is configured to, when the test coverage in the pretest result is smaller than a coverage threshold corresponding to the scene to be tested, further include: circularly executing the following steps until the test coverage is not less than the coverage threshold: generating test data according to the entity directory corresponding to the target test case template, and filling the target test case template with the generated test data and the test data obtained according to the historical data set; and performing pretesting by using the test case generated after filling to obtain a pretesting result.

In an embodiment of the present invention, the populatingmodule 304 is configured to update the test data generated according to the entity directory into the historical data set.

According to the device for generating the test case, provided by the embodiment of the invention, the test data can be generated according to the pre-configured test case template and the historical data set, and the target test case template is filled by using the test data so as to generate the target test case. Therefore, the automatic generation of the test case is realized, the workload of testing personnel is reduced, and the generation efficiency of the test case is improved.

Fig. 4 illustrates anexemplary system architecture 400 to which the method for test case generation or the apparatus for test case generation of an embodiment of the present invention may be applied.

As shown in fig. 4, thesystem architecture 400 may include aterminal device 401, anetwork 404, and

servers

402, 403. Thenetwork 404 serves as a medium for providing communication links between theterminal device 401 and the servers 402,403.Network 404 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use theterminal device 401 to interact with the

servers

402, 403 via thenetwork 404 to receive or send messages or the like.

Theterminal device 401 may be various electronic devices having a display screen and supporting information browsing, including but not limited to a tablet computer, a laptop portable computer, a desktop computer, and the like.

The

servers

402 and 403 may be servers that provide various services, and the backend management server may analyze and perform other processing on the received request for generating the test case and feed back the processing result (the result of generating the test case) to the server for testing. For example, theserver 402 may generate a corresponding target test case according to the test case generation request, and send the target test case to theserver 403 through thenetwork 404, and theserver 403 may perform a test according to the target test case.

It should be noted that the method for generating test cases provided by the embodiment of the present invention is generally executed by the

servers

402 and 403, and accordingly, the device for generating test cases is generally disposed in the

servers

402 and 403.

It should be understood that the number of terminal devices, networks, and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 5, shown is a block diagram of acomputer system 500 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 5, thecomputer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from astorage section 508 into a Random Access Memory (RAM) 503. In theRAM 503, various programs and data necessary for the operation of thesystem 500 are also stored. TheCPU 501,ROM 502, andRAM 503 are connected to each other via abus 504. An input/output (I/O)interface 505 is also connected tobus 504.

The following components are connected to the I/O interface 505: aninput portion 506 including a keyboard, a mouse, and the like; anoutput section 506 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; astorage portion 508 including a hard disk and the like; and acommunication section 509 including a network interface card such as a LAN card, a modem, or the like. Thecommunication section 509 performs communication processing via a network such as the internet. Thedriver 510 is also connected to the I/O interface 505 as necessary. Aremovable medium 501 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on thedrive 500 as necessary, so that a computer program read out therefrom is mounted into thestorage section 508 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through thecommunication section 509, and/or installed from theremovable medium 501. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 501.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes an acquisition module, a determination module, and a generation module. The names of these modules do not in some cases constitute a limitation on the module itself, and for example, the acquiring module may also be described as a "module that acquires a generation request".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: acquiring a generation request of a test case, wherein the generation request indicates a scene to be tested; determining a target test case template corresponding to the scene to be tested from one or more pre-configured test case templates; generating test data according to a historical data set and/or an entity directory corresponding to the target test case template; and filling the test data into the target test case template to generate a target test case corresponding to the scene to be tested so as to respond to the generation request.

According to the technical scheme of the embodiment of the invention, the test data can be generated according to the pre-configured test case template and the historical data set, and the target test case template is filled by using the test data to generate the target test case. Therefore, the automatic generation of the test case is realized, the workload of testing personnel is reduced, and the generation efficiency of the test case is improved.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for test case generation, comprising:

2. The method of claim 1,

determining one or more first target entities included in the target test case template;

and taking the historical data as the test data.

3. The method of claim 1,

determining an entity directory corresponding to the target test case template by using an NLU (NLU) technology, wherein the entity directory comprises one or more second target entities;

4. The method of claim 1, after populating the target test case template with the test data, further comprising:

5. The method of claim 4,

and the test data used for filling the target test case template is the test data obtained according to the historical data set.

6. The method of claim 5, wherein in a case that the test coverage in the pretest result is less than the coverage threshold corresponding to the scene to be tested, the method further comprises:

7. The method of claim 6, further comprising:

8. The method of claim 1, further comprising:

9. The method of claim 8, wherein the obtaining an entity directory corresponding to a service system comprises:

and generating the entity directory according to the analysis result.

10. The method according to claim 8 or 9,

the entity directory further comprises: and the entity attribute of the entity to be tested and the data type of the entity attribute.

11. The method of claim 10,

the test case template types include: the data verification type test case template and the data setting type test case template; wherein,

12. The method of claim 11, wherein determining a target test case template corresponding to the scene to be tested from one or more pre-configured test case templates comprises:

13. An apparatus for test case generation, comprising: the device comprises an acquisition module, a determination module, a generation module and a filling module; wherein,

14. An electronic device for generating test cases, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-12.

15. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-12.