CN112506765A - Software testing method, device, equipment and storage medium - Google Patents
Software testing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112506765A CN112506765A CN202011385897.6A CN202011385897A CN112506765A CN 112506765 A CN112506765 A CN 112506765A CN 202011385897 A CN202011385897 A CN 202011385897A CN 112506765 A CN112506765 A CN 112506765A
- Authority
- CN
- China
- Prior art keywords
- software
- test
- strategy
- testing
- tested
- 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
- 238000013522 software testing Methods 0.000 title claims abstract description 108
- 238000000034 method Methods 0.000 title claims abstract description 69
- 238000012360 testing method Methods 0.000 claims abstract description 387
- 238000013461 design Methods 0.000 claims abstract description 259
- 230000007547 defect Effects 0.000 claims abstract description 22
- 238000011156 evaluation Methods 0.000 claims description 32
- 238000012163 sequencing technique Methods 0.000 claims description 30
- 239000012085 test solution Substances 0.000 claims description 26
- 238000001514 detection method Methods 0.000 claims description 13
- 238000010998 test method Methods 0.000 description 24
- 230000006870 function Effects 0.000 description 13
- 238000012795 verification Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 239000000243 solution Substances 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 230000001939 inductive effect Effects 0.000 description 1
- 238000013101 initial test Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000013139 quantization Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention belongs to the technical field of computers, and discloses a software testing method, a device, equipment and a storage medium. The software familiarity score and the test purpose of a tester to the software to be tested are obtained; generating a test scheme design strategy according to the familiar value and the test purpose of the software; determining a target test scheme design strategy according to a strategy selection instruction input by a tester based on the test scheme design strategy and the test scheme design strategy; determining a software testing scheme according to software information of software to be tested and a target testing scheme design strategy; and testing the software to be tested according to the software testing scheme. The design strategy of the test scheme is generated according to the software familiarity score and the test purpose of the tester for the software to be tested, so that different test purposes of the tester can be met, the tester unfamiliar with the software to be tested can quickly carry out test work, and the tester knowing the software to be tested deeply can dig out deep defects of the software to be tested.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a software testing method, apparatus, device, and storage medium.
Background
In the processes of computer software development, delivery, online and the like, software testing is required to be carried out on computer software, and the software testing is a process of operating the computer software under specified conditions to find bugs and defects of the computer software, measuring the quality of the software and evaluating whether the computer software can meet design requirements. For testers unfamiliar with the tested software, the time for designing a test scheme is extremely long, the testers cannot learn and understand the tested software quickly in a short time, and the testers cannot start testing quickly; and for testers who know programs deeply for tested software, along with the deepening of the test, the designed test scheme has limitations, the force after the test is insufficient, and the number of discovered defects is greatly reduced compared with the initial test period.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a software testing method, a device, equipment and a storage medium, and aims to solve the technical problems that a tester unfamiliar with software to be tested is difficult to quickly start testing work, and the tester is not competent enough to know a testing scheme of a deeper tester for the software to be tested.
In order to achieve the above object, the present invention provides a software testing method, comprising the steps of:
acquiring a software familiarity score of a tester for software to be tested, and acquiring a test purpose of the tester for testing the software to be tested;
generating a test scheme design strategy according to the software familiarity score and the test purpose;
receiving a strategy selection instruction input by the tester based on the test scheme design strategy;
determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
and testing the software to be tested according to the software testing scheme.
Optionally, before the step of receiving the policy selection instruction input by the tester based on the test solution design policy, the method further includes:
obtaining effective scores and efficiency scores corresponding to the design strategies of the test schemes;
and sequencing the test scheme design strategies according to the effective scores and the efficiency scores.
Optionally, the step of sorting the test solution design strategies according to the effective scores and the efficiency scores includes:
obtaining a strategy type corresponding to each test scheme design strategy;
grouping the test scheme design strategies according to the strategy types to obtain a design strategy subset;
sorting the design strategy subsets according to the strategy types;
and sequencing the test scheme design strategies in each sequenced design strategy subset according to the effective scores and the efficiency scores.
Optionally, the step of sorting the test solution design strategies in each sorted subset of design strategies according to the effective scores and the efficiency scores includes:
acquiring a preset effective score weight and a preset efficiency score weight;
carrying out weighted summation on the effective scores and the efficiency scores according to the preset effective score weights and preset efficiency score weights to obtain ranking evaluation scores;
and sequencing the test scheme design strategies in each sequenced design strategy subset according to the sequencing evaluation scores.
Optionally, after the step of testing the software to be tested according to the software testing scheme, the method further includes:
obtaining a test result of testing the software to be tested according to the software test scheme;
receiving a strategy adjusting instruction input by the tester based on the test result;
and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy.
Optionally, after the step of obtaining the test result of testing the software to be tested according to the software testing scheme, the method further includes:
analyzing the test result to determine the execution time of the scheme and the defect detection rate;
generating a software test evaluation report according to the scheme execution time and the defect detection rate, and displaying the software test evaluation report;
correspondingly, the step of receiving the policy adjustment instruction input by the tester based on the test result specifically includes:
and receiving a strategy adjusting instruction input by the tester based on the software test evaluation report.
Optionally, before the step of obtaining the software familiarity score of the tester for the software to be tested and obtaining the test purpose of the tester for testing the software to be tested, the method further includes:
acquiring historical software operation records and historical software test records of testers;
and determining the software familiarity score of the tester for the software to be tested according to the historical software operation record and the historical software test record.
Optionally, the step of generating a test scheme design policy according to the software familiarity score and the test purpose includes:
determining a policy type based on the software familiarity score;
determining a usable strategy according to the test purpose and the strategy type;
generating a test plan design strategy according to the available strategy.
Optionally, the step of determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy includes:
acquiring identification information in the strategy selection instruction;
acquiring strategy identification information corresponding to each test scheme design strategy;
matching the identification information with the strategy identification information;
and when the matching is successful, taking the test scheme design strategy corresponding to the successfully matched strategy identification information as a target test scheme design strategy.
Optionally, the step of determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design policy includes:
determining each interface to be tested according to the software information of the software to be tested;
generating a test case corresponding to each interface to be tested according to the target test scheme design strategy;
and constructing a software testing scheme according to the test case.
Optionally, after the step of generating the test solution design policy according to the software familiarity score and the test purpose, the method further includes:
and when a strategy detail checking instruction sent by the tester is received, displaying the strategy details of the test scheme design strategy corresponding to the strategy detail checking instruction.
Optionally, before the step of generating the test solution design policy according to the software familiarity score and the test purpose, the method further includes:
acquiring the user authority of the tester, and performing authority verification on the user authority;
and when the permission verification is passed, executing the step of generating a test scheme design strategy according to the software familiarity score and the test purpose.
In addition, in order to achieve the above object, the present invention further provides a software testing apparatus, which includes the following modules:
the system comprises an information acquisition module, a test module and a test module, wherein the information acquisition module is used for acquiring a software familiarity score of a tester for software to be tested and acquiring a test purpose of the tester for testing the software to be tested;
the strategy generating module is used for generating a test scheme design strategy according to the software familiarity score and the test purpose;
the instruction receiving module is used for receiving a strategy selection instruction input by the tester based on the test scheme design strategy;
the strategy determining module is used for determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
the scheme determining module is used for determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
and the automatic testing module is used for testing the software to be tested according to the software testing scheme.
Optionally, the policy generation module is further configured to obtain effective scores and efficiency scores corresponding to the test scheme design policies; and sequencing the test scheme design strategies according to the effective scores and the efficiency scores.
Optionally, the policy generation module is further configured to obtain a policy type corresponding to each test scheme design policy; grouping the test scheme design strategies according to the strategy types to obtain a design strategy subset; sorting the design strategy subsets according to the strategy types; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the effective scores and the efficiency scores.
Optionally, the policy generation module is further configured to obtain a preset effective score weight and a preset efficiency score weight; carrying out weighted summation on the effective scores and the efficiency scores according to the preset effective score weights and preset efficiency score weights to obtain ranking evaluation scores; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the sequencing evaluation scores.
Optionally, the automatic testing module is further configured to obtain a testing result of testing the software to be tested according to the software testing scheme; receiving a strategy adjusting instruction input by the tester based on the test result; and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy.
Optionally, the information obtaining module is further configured to obtain a historical software operation record and a historical software test record of a tester; and determining the software familiarity score of the tester for the software to be tested according to the historical software operation record and the historical software test record.
In addition, to achieve the above object, the present invention further provides a software testing apparatus, including: a memory, a processor and a software test program stored on the memory and executable on the processor, the software test program when executed by the processor implementing the steps of the software testing method as described above.
In addition, in order to achieve the above object, the present invention further provides a computer readable storage medium, on which a software testing program is stored, and the software testing program implements the steps of the software testing method as described above when executed.
The invention obtains the software familiarity value and the test purpose of the tester to the software to be tested; generating a test scheme design strategy according to the familiar value and the test purpose of the software; determining a target test scheme design strategy according to a strategy selection instruction input by a tester based on the test scheme design strategy and the test scheme design strategy; determining a software testing scheme according to software information of software to be tested and a target testing scheme design strategy; and testing the software to be tested according to the software testing scheme. The design strategy of the test scheme is generated according to the software familiarity score and the test purpose of the tester for the software to be tested, so that different test purposes of the tester can be met, the tester unfamiliar with the software to be tested can quickly carry out test work, and the tester knowing the software to be tested deeply can dig out deep defects of the software to be tested.
Drawings
Fig. 1 is a schematic structural diagram of an electronic device in a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a software testing method according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of a software testing method according to the present invention;
FIG. 4 is a flowchart illustrating a software testing method according to a third embodiment of the present invention
FIG. 5 is a block diagram of a software testing apparatus according to a first embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a software testing device in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the electronic device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) Memory, or may be a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a storage medium, may include therein an operating system, a network communication module, a user interface module, and a software test program.
In the electronic apparatus shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the electronic device according to the present invention may be disposed in a software testing device, and the electronic device calls a software testing program stored in the memory 1005 through the processor 1001 and executes a software testing method provided in the embodiment of the present invention.
An embodiment of the present invention provides a software testing method, and referring to fig. 2, fig. 2 is a schematic flow chart of a first embodiment of a software testing method according to the present invention.
In this embodiment, the software testing method includes the following steps:
step S10: acquiring a software familiarity score of a tester for software to be tested, and acquiring a test purpose of the tester for testing the software to be tested;
it should be noted that the execution subject of this embodiment may be the software testing device, and the software testing device may be an electronic device such as a personal computer, a server, and the like, and may also be other devices that can achieve the same or similar functions.
It should be noted that the tester may be a person who needs to perform a software test on the software to be tested by using the software testing apparatus. The software familiarity score may be a numerical value calculated from the tester's historical operating records to assess the tester's familiarity with the software under test. The test purpose may be the purpose of a tester testing the software to be tested, for example: and (4) quickly familiarizing the software or deeply mining software defects and the like.
Further, in order to obtain the familiar score of the software, before step S10, the method may further include:
acquiring historical software operation records and historical software test records of testers; and determining the software familiarity score of the tester for the software to be tested according to the historical software operation record and the historical software test record.
It should be noted that the historical software operation record is a historical record of normal use of the software to be tested by the tester. The historical software test record is the historical record of the tester testing the software to be tested.
It can be understood that the familiarity of the test software can be evaluated according to the historical software operation records and the historical software test records of the tester, and the more records, the higher the familiarity of the software tester with the software to be tested is, the higher the corresponding software familiarity score can be.
In actual use, the historical software operation records and the corresponding operation records or test records in the historical software test records may be divided according to the function modules, different scores are given according to the importance of the function modules, and finally, the software familiarity score is obtained through statistics, and how to divide the importance of the function modules and give the score is not limited in this embodiment.
For example: the software familiarity score corresponding to one operation record of the software core function is 3 points, the software familiarity score corresponding to one operation record of the software non-core function is 1 point, the software familiarity score corresponding to one test record of the software core function is 5 points, the software familiarity score corresponding to one test record of the software non-core function is 2 points, the history records of testers have 2 core function operation records, 1 core function test record and 1 non-core function test record in total, and the corresponding software familiarity score is 3 x 2+5+ 2-13 points.
Step S20: generating a test scheme design strategy according to the software familiarity score and the test purpose;
it should be noted that the test scheme design policy may be a policy for generating a test case according to information of software to be tested.
For example, as shown in table 1 below:
TABLE 1 test plan design strategy Table
In table 1, the tester types may be divided according to the software familiarity score, and the specific division rule may be set according to the actual need, which is not limited in this embodiment. The test types can be classified in an inductive way according to different test modes used by various test strategies. The recommended use sequence can be obtained by analyzing the effectiveness and the execution efficiency of each test strategy in the actual scene.
Further, in order to improve the safety of the software testing method, before step S20 in this embodiment, the method may further include:
acquiring the user authority of the tester, and performing authority verification on the user authority; and when the permission verification is passed, executing the step of generating a test scheme design strategy according to the software familiarity score and the test purpose.
It should be noted that the user right is a right that the account used by the tester to log in the software testing device possesses, and whether the currently logged-in account possesses the use right or not is determined by verifying the user right of the tester, so that the occurrence of conditions such as malicious attack or misoperation can be avoided.
Step S30: receiving a strategy selection instruction input by the tester based on the test scheme design strategy;
it can be understood that, after a plurality of test solution design strategies are generated, the generated test solution design strategies may be displayed in a display page for a tester to select, and the tester may input a strategy selection instruction in the display page to select an appropriate test solution design strategy.
Further, in order to facilitate the tester to select the test solution design strategy, before step S30, the method may further include:
and when a strategy detail checking instruction sent by the tester is received, displaying the strategy details of the test scheme design strategy corresponding to the strategy detail checking instruction.
It can be understood that when the generated test scheme design strategies are displayed, if the number of the generated test scheme design strategies is too large, details of all the test scheme design strategies cannot be displayed in unified display, and if the number of the generated test scheme design strategies is too large, a tester with insufficient experience cannot reasonably select the test scheme design strategies only by virtue of names and brief introduction of the test scheme design strategies, so that the software test equipment can display the strategy details of the test scheme design strategies corresponding to the strategy detail viewing instructions when receiving the strategy detail viewing instructions sent by the tester, and the tester can conveniently view the strategy details. For example: and when a strategy detail checking instruction sent by a tester is received, displaying the strategy details of the test scheme design strategy corresponding to the strategy detail checking instruction in a form of a pop window or a floating window.
Step S40: determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
it should be noted that the target test solution design strategy is a test solution design strategy selected according to the strategy selection instruction.
In actual use, the identification information in the policy selection instruction can be acquired; acquiring strategy identification information corresponding to each test scheme design strategy; matching the identification information with the strategy identification information; and when the matching is successful, taking the test scheme design strategy corresponding to the successfully matched strategy identification information as a target test scheme design strategy.
It will be appreciated that one or more of the individual test solution design strategies may be selected as target test solution design strategies according to the strategy selection instructions. For example: the total number of the generated test scheme design strategies is 9, and 1-9 test scheme design strategies can be matched as target test scheme design strategies according to different identification information in the strategy selection instruction.
Step S50: determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
it can be understood that the software information of the software to be tested can be obtained after the target test scheme design strategy is determined, part of functions to be tested in the software to be tested are determined through the software information, and then a corresponding software test scheme is constructed according to the target test design strategy and the part of functions to be tested.
In actual use, each interface to be tested can be determined according to the software information of the software to be tested; generating a test case corresponding to each interface to be tested according to the target test scheme design strategy; and constructing a software testing scheme according to the test case.
For example: and determining that the number of the interfaces to be tested is 3 according to the software information of the software to be tested, and the number of the target test scheme design strategies is 2, so that test cases can be respectively generated for the 3 interfaces to be tested according to the 2-item mapping test scheme design strategies, and then all the generated test cases are combined to construct a software test scheme.
Step S60: and testing the software to be tested according to the software testing scheme.
It can be understood that after the software testing scheme is designed, the software to be tested can be tested according to the testing steps in the software testing scheme and the testing result is recorded.
In the embodiment, the software familiarity value and the test purpose of a tester to the software to be tested are obtained; generating a test scheme design strategy according to the familiar value and the test purpose of the software; determining a target test scheme design strategy according to a strategy selection instruction input by a tester based on the test scheme design strategy and the test scheme design strategy; determining a software testing scheme according to software information of software to be tested and a target testing scheme design strategy; and testing the software to be tested according to the software testing scheme. The design strategy of the test scheme is generated according to the software familiarity score and the test purpose of the tester for the software to be tested, so that different test purposes of the tester can be met, the tester unfamiliar with the software to be tested can quickly carry out test work, and the tester knowing the software to be tested deeply can dig out deep defects of the software to be tested.
Referring to fig. 3, fig. 3 is a flowchart illustrating a software testing method according to a second embodiment of the present invention.
Based on the first embodiment, before the step S30, the software testing method of this embodiment further includes:
step S21: obtaining effective scores and efficiency scores corresponding to the design strategies of the test schemes;
it should be noted that the effective score is a score for quantifying the effectiveness of the test scheme design strategy in actual use; the efficiency score is a score for quantifying the execution efficiency of the test scenario generated according to the test scenario design strategy in actual use. The specific score quantization rule may be set according to actual needs, which is not limited in this embodiment.
Step S22: and sequencing the test scheme design strategies according to the effective scores and the efficiency scores.
It can be understood that whether the test scheme design strategy is effective or not and whether the test scheme design strategy is efficient or not is judged according to the effective score and the efficiency score, therefore, the test scheme design strategies can be generated and sorted according to the effective score and the efficiency score, the more the test scheme design strategy is sorted, the more the test scheme design strategy is recommended to be used for testing, certain suggestions can be given to testers, and the difficulty of selecting the test scheme design strategy by the testers is reduced.
Further, in order to better order the test solution design strategy, step S22 in this embodiment may be:
obtaining a strategy type corresponding to each test scheme design strategy; grouping the test scheme design strategies according to the strategy types to obtain a design strategy subset; sorting the design strategy subsets according to the strategy types; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the effective scores and the efficiency scores.
It should be noted that, in the specific sorting process, recommendation degrees of test scheme design strategies of different strategy types are also different, and the generated test scheme design strategies may be grouped according to the strategy types to obtain each design strategy subset, the design strategy subsets are sorted according to the different strategy types, and then the test scheme design strategies in each sorted design strategy subset are sorted according to the effective scores and the efficiency scores.
For example: taking the above table 1 as an example, if the generated test solution design strategy is: the compass test method, the selling point test method, the limit test method, the cancel test method, the lazy Chinese test method, the traitor test method, the destroy test method, the forced test method and the like are 8, the compass test method, the selling point test method, the limit test method, the cancel test method, the lazy Chinese test method, the traitor test method, the destroy test method, the forced test method and the like can be firstly divided into three subsets of a business area test subset, a districts test subset and a hotel area test subset according to the test types, the subsets are respectively corresponding to the business area test type, the districts test type and the hotel area test type, the subsets are firstly sequenced according to the test types, the sequence of the business area test subset, the hotel area test subset and the districts test subset is obtained after sequencing, then the test scheme design strategies in: 1 limit test method, 2 selling point test method, 3 compass test method, 4 cancel test method, 5 lazy Chinese test method, 6 anti-traitor test method, 7 destroy test method and 8 force test method.
Further, the step of sorting the test scheme design strategies in each sorted subset of design strategies according to the effective scores and the efficiency scores may be:
acquiring a preset effective score weight and a preset efficiency score weight; carrying out weighted summation on the effective scores and the efficiency scores according to the preset effective score weights and preset efficiency score weights to obtain ranking evaluation scores; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the sequencing evaluation scores.
It should be noted that the preset effective score weight a and the preset efficiency score weight b may be set according to actual usage requirements, where a + b is 1, for example: in practical use, the effectiveness of the test solution design strategy is more emphasized, a preset effective score weight a may be set to 0.7, and a preset efficiency score weight b may be set to 0.3, and if the effective score of the test solution design strategy is 70 and the efficiency score is 80 at this time, the corresponding ranking evaluation score is 70 × 0.7+80 × 0.3 — 73.
The method comprises the steps of obtaining effective scores and efficiency scores corresponding to design strategies of various test schemes; and sequencing the test scheme design strategies according to the effective scores and the efficiency scores. The test scheme design strategies with higher effective scores and efficiency scores can be placed in the front of the sequence, so that the tester can determine the recommended test scheme design strategies more intuitively, and the selection difficulty of the tester for selecting the target test scheme design strategies is reduced.
Referring to fig. 4, fig. 4 is a flowchart illustrating a software testing method according to a third embodiment of the present invention.
Based on the first embodiment, after step S60, the software testing method of this embodiment further includes:
step S70: and acquiring a test result of testing the software to be tested according to the software test scheme.
It should be noted that the test result may include a case test result corresponding to each different test case in the software test scheme, and after the test result is obtained, the test result may be displayed so as to facilitate analysis by a tester.
Step S80: and receiving a strategy adjusting instruction input by the tester based on the test result.
It can be understood that after analyzing the test result, the tester may determine whether the test scheme design strategy has a defect in actual use, and if so, the test scheme design strategy needs to be adjusted, and at this time, a strategy adjustment instruction may be sent to the software test device, and the software test device may receive the strategy adjustment instruction input by the tester based on the test result.
Further, in order to reduce the analysis difficulty of the tester, before step S80, the method may further include:
analyzing the test result to determine the execution time of the scheme and the defect detection rate; generating a software test evaluation report according to the scheme execution time and the defect detection rate, and displaying the software test evaluation report;
correspondingly, the step of receiving the policy adjustment instruction input by the tester based on the test result specifically includes:
and receiving a strategy adjusting instruction input by the tester based on the software test evaluation report.
It should be noted that the execution time of the scenario may be the time when the software test scenario is executed, where the execution time of each test case in the software test scenario may also include the time when the software test scenario is executed, and the defect detection rate may be a ratio of the number of detected defects to the number of detection interfaces.
It can be understood that the execution time can be estimated according to the software test scheme, the scheme execution time is compared with the estimated execution time, when the scheme execution time is greater than the estimated execution time, the execution time of each test case in the scheme execution time can be analyzed, the abnormal execution time is subjected to abnormal marking, a software test evaluation report is generated according to the scheme execution time and the defect detection rate, and the software test evaluation report is displayed, so that a tester can conveniently perform test analysis.
Step S90: and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy.
It can be understood that the software testing device may adjust the target testing scheme design strategy according to the strategy adjustment instruction after receiving the strategy adjustment instruction, and regenerate the software testing scheme for testing according to the adjusted target testing scheme design strategy.
In the embodiment, the test result of testing the software to be tested according to the software test scheme is obtained; receiving a strategy adjusting instruction input by the tester based on the test result; and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy. The design strategy of the test scheme can be continuously optimized, so that the design strategy of the test scheme is continuously optimized and perfected, the test efficiency is improved for testers, and the defects in the software to be tested are quickly detected.
In addition, an embodiment of the present invention further provides a storage medium, where a software testing program is stored on the storage medium, and the software testing program, when executed by a processor, implements the steps of the software testing method described above.
Referring to fig. 5, fig. 5 is a block diagram of a software testing apparatus according to a first embodiment of the present invention.
As shown in fig. 5, the software testing apparatus according to the embodiment of the present invention includes:
the information acquisition module 501 is configured to acquire a software familiarity score of a tester for software to be tested, and acquire a test purpose of the tester for testing the software to be tested;
a strategy generating module 502, configured to generate a test scheme design strategy according to the software familiarity score and the test purpose;
an instruction receiving module 503, configured to receive a policy selection instruction input by the tester based on the test scheme design policy;
a strategy determining module 504, configured to determine a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
a scheme determining module 505, configured to determine a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
and the automatic test module 506 is used for testing the software to be tested according to the software test scheme.
In the embodiment, the software familiarity value and the test purpose of a tester to the software to be tested are obtained; generating a test scheme design strategy according to the familiar value and the test purpose of the software; determining a target test scheme design strategy according to a strategy selection instruction input by a tester based on the test scheme design strategy and the test scheme design strategy; determining a software testing scheme according to software information of software to be tested and a target testing scheme design strategy; and testing the software to be tested according to the software testing scheme. The design strategy of the test scheme is generated according to the software familiarity score and the test purpose of the tester for the software to be tested, so that different test purposes of the tester can be met, the tester unfamiliar with the software to be tested can quickly carry out test work, and the tester knowing the software to be tested deeply can dig out deep defects of the software to be tested.
Further, the strategy generating module 502 is further configured to obtain effective scores and efficiency scores corresponding to the design strategies of the test solutions; and sequencing the test scheme design strategies according to the effective scores and the efficiency scores.
Further, the policy generating module 502 is further configured to obtain a policy type corresponding to each test scheme design policy; grouping the test scheme design strategies according to the strategy types to obtain a design strategy subset; sorting the design strategy subsets according to the strategy types; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the effective scores and the efficiency scores.
Further, the policy generating module 502 is further configured to obtain a preset effective score weight and a preset efficiency score weight; carrying out weighted summation on the effective scores and the efficiency scores according to the preset effective score weights and preset efficiency score weights to obtain ranking evaluation scores; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the sequencing evaluation scores.
Further, the automatic testing module 506 is further configured to obtain a testing result of testing the software to be tested according to the software testing scheme; receiving a strategy adjusting instruction input by the tester based on the test result; and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy.
Further, the automatic test module 506 is further configured to analyze the test result to determine a solution execution time and a defect detection rate; generating a software test evaluation report according to the scheme execution time and the defect detection rate, and displaying the software test evaluation report;
the automatic test module 506 is further configured to receive a policy adjustment instruction input by the tester based on the software test evaluation report.
Further, the information obtaining module 501 is further configured to obtain historical software operation records and historical software test records of a tester; and determining the software familiarity score of the tester for the software to be tested according to the historical software operation record and the historical software test record.
Further, the policy generation module 502 is further configured to determine a policy type according to the software familiarity score; determining a usable strategy according to the test purpose and the strategy type; generating a test plan design strategy according to the available strategy.
Further, the policy determining module 504 is further configured to obtain identification information in the policy selecting instruction; acquiring strategy identification information corresponding to each test scheme design strategy; matching the identification information with the strategy identification information; and when the matching is successful, taking the test scheme design strategy corresponding to the successfully matched strategy identification information as a target test scheme design strategy.
Further, the scheme determining module 505 is further configured to determine each interface to be tested according to the software information of the software to be tested; generating a test case corresponding to each interface to be tested according to the target test scheme design strategy; and constructing a software testing scheme according to the test case.
Further, the policy generating module 502 is further configured to, when receiving a policy detail checking instruction sent by the tester, display policy details of a test scheme design policy corresponding to the policy detail checking instruction.
Further, the information obtaining module 501 is further configured to obtain a user right of the tester, and perform right verification on the user right; and when the permission verification is passed, executing the step of generating a test scheme design strategy according to the software familiarity score and the test purpose.
It should be understood that the above is only an example, and the technical solution of the present invention is not limited in any way, and in a specific application, a person skilled in the art may set the technical solution as needed, and the present invention is not limited thereto.
It should be noted that the above-described work flows are only exemplary, and do not limit the scope of the present invention, and in practical applications, a person skilled in the art may select some or all of them to achieve the purpose of the solution of the embodiment according to actual needs, and the present invention is not limited herein.
In addition, the technical details that are not described in detail in this embodiment may refer to the software testing method provided in any embodiment of the present invention, and are not described herein again.
Further, it is to be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system 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 system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g. Read Only Memory (ROM)/RAM, magnetic disk, optical disk), and includes several instructions for enabling a terminal device (e.g. a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
The invention discloses a1 and a software testing method, which comprises the following steps:
acquiring a software familiarity score of a tester for software to be tested, and acquiring a test purpose of the tester for testing the software to be tested;
generating a test scheme design strategy according to the software familiarity score and the test purpose;
receiving a strategy selection instruction input by the tester based on the test scheme design strategy;
determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
and testing the software to be tested according to the software testing scheme.
A2, the software testing method as in A1, wherein before the step of receiving the policy selection instruction inputted by the tester based on the test solution design policy, the method further comprises:
obtaining effective scores and efficiency scores corresponding to the design strategies of the test schemes;
and sequencing the test scheme design strategies according to the effective scores and the efficiency scores.
A3, the software testing method of A2, the step of ordering the test solution design strategy according to the effective score and the efficiency score, comprising:
obtaining a strategy type corresponding to each test scheme design strategy;
grouping the test scheme design strategies according to the strategy types to obtain a design strategy subset;
sorting the design strategy subsets according to the strategy types;
and sequencing the test scheme design strategies in each sequenced design strategy subset according to the effective scores and the efficiency scores.
A4, the software testing method according to A3, wherein the step of sorting the test solution design strategies in each sorted subset of design strategies according to the effective scores and the efficiency scores comprises:
acquiring a preset effective score weight and a preset efficiency score weight;
carrying out weighted summation on the effective scores and the efficiency scores according to the preset effective score weights and preset efficiency score weights to obtain ranking evaluation scores;
and sequencing the test scheme design strategies in each sequenced design strategy subset according to the sequencing evaluation scores.
A5, the software testing method as in A1, further comprising after the step of testing the software to be tested according to the software testing scheme:
obtaining a test result of testing the software to be tested according to the software test scheme;
receiving a strategy adjusting instruction input by the tester based on the test result;
and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy.
A6, the software testing method as defined in a5, further comprising, after the step of obtaining the test result of the test of the software to be tested according to the software testing scheme:
analyzing the test result to determine the execution time of the scheme and the defect detection rate;
generating a software test evaluation report according to the scheme execution time and the defect detection rate, and displaying the software test evaluation report;
correspondingly, the step of receiving the policy adjustment instruction input by the tester based on the test result specifically includes:
and receiving a strategy adjusting instruction input by the tester based on the software test evaluation report.
The software testing method according to any one of a1-a6, as recited in a7, further includes, before the step of obtaining a software familiarity score of a tester with the software to be tested, and obtaining a test purpose for the tester to test the software to be tested:
acquiring historical software operation records and historical software test records of testers;
and determining the software familiarity score of the tester for the software to be tested according to the historical software operation record and the historical software test record.
A8, the method for testing software as defined in any one of A1-A6, the step of generating a test plan design strategy based on the software familiarity score and the test purpose, comprising:
determining a policy type based on the software familiarity score;
determining a usable strategy according to the test purpose and the strategy type;
generating a test plan design strategy according to the available strategy.
A9, the software testing method of any one of A1-A6, the step of determining a target test plan design strategy according to the strategy selection command and the test plan design strategy, comprising:
acquiring identification information in the strategy selection instruction;
acquiring strategy identification information corresponding to each test scheme design strategy;
matching the identification information with the strategy identification information;
and when the matching is successful, taking the test scheme design strategy corresponding to the successfully matched strategy identification information as a target test scheme design strategy.
A10, the software testing method according to any one of A1-A6, the step of determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy, comprising:
determining each interface to be tested according to the software information of the software to be tested;
generating a test case corresponding to each interface to be tested according to the target test scheme design strategy;
and constructing a software testing scheme according to the test case.
A11, the method for testing software as defined in any one of A1-A6, further comprising, after the step of generating a test solution design strategy based on the software familiarity score and the test purpose:
and when a strategy detail checking instruction sent by the tester is received, displaying the strategy details of the test scheme design strategy corresponding to the strategy detail checking instruction.
A12, the method for testing software according to any one of A1-A6, further comprising, before the step of generating a test solution design strategy according to the software familiarity score and the test purpose:
acquiring the user authority of the tester, and performing authority verification on the user authority;
and when the permission verification is passed, executing the step of generating a test scheme design strategy according to the software familiarity score and the test purpose.
The invention discloses a B13 software testing device, which comprises the following modules:
the system comprises an information acquisition module, a test module and a test module, wherein the information acquisition module is used for acquiring a software familiarity score of a tester for software to be tested and acquiring a test purpose of the tester for testing the software to be tested;
the strategy generating module is used for generating a test scheme design strategy according to the software familiarity score and the test purpose;
the instruction receiving module is used for receiving a strategy selection instruction input by the tester based on the test scheme design strategy;
the strategy determining module is used for determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
the scheme determining module is used for determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
and the automatic testing module is used for testing the software to be tested according to the software testing scheme.
B14, the software testing apparatus as described in B13, the policy generating module is further configured to obtain effective scores and efficiency scores corresponding to the design policies of each test solution; and sequencing the test scheme design strategies according to the effective scores and the efficiency scores.
B15, the software testing device as described in B14, the strategy generation module is further configured to obtain a strategy type corresponding to each test solution design strategy; grouping the test scheme design strategies according to the strategy types to obtain a design strategy subset; sorting the design strategy subsets according to the strategy types; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the effective scores and the efficiency scores.
B16, the software testing apparatus as in B15, the policy generating module being further configured to obtain a preset effective score weight and a preset efficiency score weight; carrying out weighted summation on the effective scores and the efficiency scores according to the preset effective score weights and preset efficiency score weights to obtain ranking evaluation scores; and sequencing the test scheme design strategies in each sequenced design strategy subset according to the sequencing evaluation scores.
B17, the software testing device as described in B13, the automatic testing module, further used to obtain the testing result of the software to be tested according to the software testing scheme; receiving a strategy adjusting instruction input by the tester based on the test result; and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy.
B18, the software testing device as B13, the information acquisition module is further used for acquiring historical software operation records and historical software testing records of testers; and determining the software familiarity score of the tester for the software to be tested according to the historical software operation record and the historical software test record.
The invention discloses C19, a software testing device, the software testing device includes: a memory, a processor and a software test program stored on the memory and executable on the processor, the software test program when executed by the processor implementing the steps of the software testing method as described above.
The invention discloses D20 and a computer readable storage medium, wherein a software testing program is stored on the computer readable storage medium, and the steps of the software testing method are realized when the software testing program is executed.
Claims (10)
1. A software testing method is characterized by comprising the following steps:
acquiring a software familiarity score of a tester for software to be tested, and acquiring a test purpose of the tester for testing the software to be tested;
generating a test scheme design strategy according to the software familiarity score and the test purpose;
receiving a strategy selection instruction input by the tester based on the test scheme design strategy;
determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
and testing the software to be tested according to the software testing scheme.
2. The software testing method of claim 1, wherein said step of receiving a policy selection instruction entered by said tester based on said test plan design policy is preceded by:
obtaining effective scores and efficiency scores corresponding to the design strategies of the test schemes;
and sequencing the test scheme design strategies according to the effective scores and the efficiency scores.
3. The method for software testing according to claim 2, wherein said step of ordering said test plan design strategy according to said effective score and said efficiency score comprises:
obtaining a strategy type corresponding to each test scheme design strategy;
grouping the test scheme design strategies according to the strategy types to obtain a design strategy subset;
sorting the design strategy subsets according to the strategy types;
and sequencing the test scheme design strategies in each sequenced design strategy subset according to the effective scores and the efficiency scores.
4. The software testing method of claim 3, wherein said step of sorting the test solution design strategies in each sorted subset of design strategies according to the effective scores and the efficiency scores comprises:
acquiring a preset effective score weight and a preset efficiency score weight;
carrying out weighted summation on the effective scores and the efficiency scores according to the preset effective score weights and preset efficiency score weights to obtain ranking evaluation scores;
and sequencing the test scheme design strategies in each sequenced design strategy subset according to the sequencing evaluation scores.
5. The software testing method of claim 1, wherein after the step of testing the software under test according to the software testing scheme, further comprising:
obtaining a test result of testing the software to be tested according to the software test scheme;
receiving a strategy adjusting instruction input by the tester based on the test result;
and adjusting the target test scheme design strategy according to the strategy adjusting instruction, and returning to the step of determining the software test scheme according to the software information of the software to be tested and the target test scheme design strategy.
6. The software testing method of claim 5, wherein after the step of obtaining the test result of the test of the software to be tested according to the software testing scheme, further comprising:
analyzing the test result to determine the execution time of the scheme and the defect detection rate;
generating a software test evaluation report according to the scheme execution time and the defect detection rate, and displaying the software test evaluation report;
correspondingly, the step of receiving the policy adjustment instruction input by the tester based on the test result specifically includes:
and receiving a strategy adjusting instruction input by the tester based on the software test evaluation report.
7. The method for testing software according to any one of claims 1-6, wherein the step of obtaining the software familiarity score of the tester for the software to be tested and obtaining the test purpose of the tester for testing the software to be tested further comprises:
acquiring historical software operation records and historical software test records of testers;
and determining the software familiarity score of the tester for the software to be tested according to the historical software operation record and the historical software test record.
8. A software testing device is characterized by comprising the following modules:
the system comprises an information acquisition module, a test module and a test module, wherein the information acquisition module is used for acquiring a software familiarity score of a tester for software to be tested and acquiring a test purpose of the tester for testing the software to be tested;
the strategy generating module is used for generating a test scheme design strategy according to the software familiarity score and the test purpose;
the instruction receiving module is used for receiving a strategy selection instruction input by the tester based on the test scheme design strategy;
the strategy determining module is used for determining a target test scheme design strategy according to the strategy selection instruction and the test scheme design strategy;
the scheme determining module is used for determining a software testing scheme according to the software information of the software to be tested and the target testing scheme design strategy;
and the automatic testing module is used for testing the software to be tested according to the software testing scheme.
9. A software testing device, characterized in that the software testing device comprises: memory, a processor and a software test program stored on the memory and executable on the processor, the software test program, when executed by the processor, implementing the steps of the software testing method according to any one of claims 1-7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a software test program which, when executed, implements the steps of the software testing method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011385897.6A CN112506765A (en) | 2020-12-01 | 2020-12-01 | Software testing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011385897.6A CN112506765A (en) | 2020-12-01 | 2020-12-01 | Software testing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112506765A true CN112506765A (en) | 2021-03-16 |
Family
ID=74968257
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011385897.6A Pending CN112506765A (en) | 2020-12-01 | 2020-12-01 | Software testing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112506765A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948255A (en) * | 2021-03-23 | 2021-06-11 | 北京鸿腾智能科技有限公司 | Distributed kernel fuzzing test system and method |
-
2020
- 2020-12-01 CN CN202011385897.6A patent/CN112506765A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948255A (en) * | 2021-03-23 | 2021-06-11 | 北京鸿腾智能科技有限公司 | Distributed kernel fuzzing test system and method |
| CN112948255B (en) * | 2021-03-23 | 2024-05-14 | 三六零数字安全科技集团有限公司 | Distributed kernel fuzzy test system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10963571B2 (en) | Privacy risk assessments | |
| CN110378749B (en) | Client similarity evaluation method and device, terminal equipment and storage medium | |
| CN109345417B (en) | Online assessment method and terminal equipment for business personnel based on identity authentication | |
| CN110569159A (en) | Baffle generation method, device, equipment and computer storage medium | |
| CN110096430B (en) | Third party SDK access test method, device, terminal and storage medium | |
| CN107729456A (en) | Sensitive information search method, server and storage medium | |
| CN109446837A (en) | Text checking method, equipment and readable storage medium storing program for executing based on sensitive information | |
| CN113553583A (en) | Information system asset security risk assessment method and device | |
| CN112529575A (en) | Risk early warning method, equipment, storage medium and device | |
| CN107688533A (en) | Applied program testing method, device, computer equipment and storage medium | |
| CN108306886A (en) | A kind of auth method, device and storage medium | |
| CN116340934A (en) | Terminal abnormal behavior detection method, device, equipment and storage medium | |
| CN106201857A (en) | The choosing method of test case and device | |
| CN112433936A (en) | Test method, test device and storage medium | |
| CN112000862B (en) | Data processing method and device | |
| CN112506765A (en) | Software testing method, device, equipment and storage medium | |
| CN111476446A (en) | Service state monitoring processing method, device, equipment and storage medium | |
| CN113312261A (en) | Test case screening method, test case screening equipment, storage medium and device | |
| CN107402883B (en) | A kind of data test treating method and apparatus | |
| CN112799956B (en) | Asset identification capability test method, device and system device | |
| CN111708698B (en) | Application program simulation recording method and related device | |
| CN113672497A (en) | Method, device and equipment for generating non-buried point event and storage medium | |
| CN113538130B (en) | Abnormality detection method, device and system | |
| CN118505066B (en) | Skill testing method and system based on prerecorded SaaS software operation skill | |
| CN113962328B (en) | Data comparison analysis method, device and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information |
Address after: 100020 1773, 15 / F, 17 / F, building 3, No.10, Jiuxianqiao Road, Chaoyang District, Beijing Applicant after: Sanliu0 Digital Security Technology Group Co.,Ltd. Address before: 100020 1773, 15 / F, 17 / F, building 3, No.10, Jiuxianqiao Road, Chaoyang District, Beijing Applicant before: Beijing Hongteng Intelligent Technology Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |