CN111026665A - Test range analysis method, device and equipment - Google Patents
Test range analysis method, device and equipment Download PDFInfo
- Publication number
- CN111026665A CN111026665A CN201911253592.7A CN201911253592A CN111026665A CN 111026665 A CN111026665 A CN 111026665A CN 201911253592 A CN201911253592 A CN 201911253592A CN 111026665 A CN111026665 A CN 111026665A
- Authority
- CN
- China
- Prior art keywords
- menu
- data
- test
- information
- target
- 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.)
- Granted
Links
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/3676—Test management for coverage analysis
-
- 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 provides a test range analysis method, a test range analysis device and test range analysis equipment, and relates to the technical field of data processing. According to the invention, the menu test coverage monitoring result and the menu data of the current day and the previous day are obtained, and based on the menu identification, the menu information which changes relative to the menu data of the previous day in the menu data of the current day is determined to be the target menu information, and then the target menu information with the corresponding menu identification in the menu test coverage monitoring result is determined to be covered by the test, so that the test coverage range can be accurately determined by taking the menu as the dimension and taking the target menu information as the standard. Compared with the prior art, the method has the advantages that the test range analysis process is simplified, the test range analysis result is accurate, and the completeness of the service function test can be effectively improved.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method, a device and equipment for analyzing a test range.
Background
The financial business system has complex and variable business scenes, and the transaction amount and the data amount are large. In order to ensure that the financial business system is orderly performed, the business function test of the financial business system is required. The financial business function test generally refers to the test and verification of various functions of a product, such as: the functions of the product can be tested item by item according to the preset test case, so that whether the product has the user requirements or not can be checked. The consistency of interfaces between products, the correctness and the safety of service realization and system operation and the like can be verified through the service function test, so that the function of the application system is ensured to meet the requirements of users.
In order to ensure the integrity of the service function test, the service function test range is usually analyzed. Currently, the business function test range is generally analyzed by analyzing the transaction code test range. However, the transaction code is complex and various, part of the transaction code cannot represent the main transaction purpose of the transaction line, and the transaction code can only be used for back-end test analysis, so that the method often depends on the recognition degree of a test manager on the service and the system.
However, in the prior art, the service function test range is analyzed depending on the recognition degree of the test manager on the service and the system, which results in a relatively large uncertainty of the analysis result of the service function test range and affects the completeness of the service function test.
Disclosure of Invention
The invention provides a method, a device and equipment for analyzing a test range, which can realize the analysis of a service function test range.
In a first aspect, an embodiment of the present invention provides a test range analysis method, where the method includes: acquiring a menu test coverage monitoring result, wherein the menu test coverage monitoring result comprises at least one group of transaction data, and each group of transaction data comprises a corresponding transaction identifier and a menu identifier to which the transaction identifier belongs; acquiring menu data of the current day and the previous day, wherein the menu data comprises at least one group of menu information, and each group of menu information comprises a corresponding menu identification; determining that the changed menu information in the menu data of the current day is target menu information relative to the menu data of the previous day based on the menu identification; and determining that the target menu information with the corresponding menu identification in the menu test coverage monitoring result is covered by the test.
Optionally, the obtaining of the menu test coverage monitoring result includes: acquiring transaction data, a transaction identifier corresponding to the transaction data and a menu identifier to which the transaction identifier belongs; and generating a menu test coverage monitoring result according to the transaction data, the transaction identifier and the menu identifier.
Optionally, the determining that the target menu information having the corresponding menu identifier exists in the menu test coverage monitoring result is covered by the test includes: inquiring whether a menu mark corresponding to the target menu information exists in a menu test coverage monitoring result; if yes, determining that the target menu information is covered by the test; and if not, determining that the target menu information is not covered by the test.
Optionally, the determining, based on the menu identifier, that, in the menu data of the current day, the menu information that changes with respect to the menu data of the previous day is the target menu information includes: aiming at any menu information in the menu data of the current day and the previous day: judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day; and if so, determining the menu information as the target menu information.
Optionally, the method further comprises: if the menu identification corresponding to the menu information does not meet the requirements: if the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day, judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day and the menu data of the previous day, and the menu identification is different from the corresponding menu information in the menu data of the current day and the menu data of the previous day respectively; and if so, determining the menu information as the target menu information.
Optionally, the menu information includes: menu code, menu path, menu name, menu level, and menu source.
Optionally, the method further comprises: generating a test coverage result according to the target menu information which is tested to be covered and the transaction data corresponding to the target menu information which is tested to be covered in the menu test coverage monitoring result; and displaying the test coverage result through an interface.
Optionally, the method further comprises: and respectively displaying the menu test coverage monitoring result and the target menu information through an interface.
In a second aspect, an embodiment of the present invention provides a test range analysis apparatus, including:
the first acquisition module is used for acquiring a menu test coverage monitoring result, wherein the menu test coverage monitoring result comprises at least one group of transaction data, and each group of transaction data comprises a corresponding transaction identifier and a menu identifier to which the transaction identifier belongs; the second acquisition module is used for acquiring menu data of the current day and the previous day, the menu data comprises at least one group of menu information, and each group of menu information comprises a corresponding menu identifier; the first determining module is used for determining that the menu information which changes relative to the menu data of the previous day in the menu data of the current day is the target menu information based on the menu identification; and the second determining module is used for determining that the target menu information with the corresponding menu identification in the menu test coverage monitoring result is covered by the test.
Optionally, the first obtaining module is specifically configured to obtain the transaction data, a transaction identifier corresponding to the transaction data, and a menu identifier to which the transaction identifier belongs, and generate a menu test coverage monitoring result according to the transaction data, the transaction identifier, and the menu identifier.
Optionally, the second determining module is specifically configured to query whether a menu identifier corresponding to the target menu information exists in the menu test coverage monitoring result; if yes, determining that the target menu information is covered by the test; and if not, determining that the target menu information is not covered by the test.
Optionally, the first determining module is specifically configured to, for any menu information in the menu data of the current day and the previous day: judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day; and if so, determining the menu information as the target menu information.
Optionally, the first determining module is further specifically configured to, if the menu identifier corresponding to the menu information does not satisfy: if the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day, judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day and the menu data of the previous day, and the menu identification is different from the corresponding menu information in the menu data of the current day and the menu data of the previous day respectively; and if so, determining the menu information as the target menu information.
Optionally, the menu information includes: menu code, menu path, menu name, menu level, and menu source.
Optionally, the apparatus further comprises: the generating module is used for generating a test coverage result according to the target menu information which is tested to be covered and the transaction data corresponding to the target menu information which is tested to be covered in the menu test coverage monitoring result; and the first display module is used for displaying the test coverage result through an interface.
Optionally, the apparatus further comprises: the second display module is used for displaying the menu test coverage monitoring result through an interface; and the third display module is used for displaying the target menu information through an interface.
In a third aspect, an embodiment of the present invention provides a test range analysis device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the test range analysis device is operating, the processor executing the machine-readable instructions to perform the test range analysis method according to the first aspect.
In a fourth aspect, an embodiment of the present invention further provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method for analyzing a test range according to the first aspect is performed.
The invention has the beneficial effects that:
according to the embodiment of the invention, the menu test coverage monitoring result and the menu data of the current day and the previous day are obtained, the menu information which changes relative to the menu data of the previous day in the menu data of the current day is determined to be the target menu information based on the menu identification, and then the target menu information with the corresponding menu identification in the menu test coverage monitoring result is determined to be covered by the test, so that the test coverage range can be accurately determined by taking the menu as the dimension and taking the target menu information as the reference. Compared with the prior art, the method has the advantages that the test range analysis process is simplified, the test range analysis result is accurate, and the completeness of the service function test can be effectively improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
FIG. 1 is a flow chart of a test range analysis method according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart illustrating a test range analysis method according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a menu test coverage monitoring result provided by an embodiment of the present invention;
FIG. 4 is a schematic flow chart illustrating a test range analysis method according to an embodiment of the present invention;
FIG. 5 is a schematic flow chart illustrating a test range analysis method according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a menu change baseline monitoring result provided by an embodiment of the invention;
FIG. 7 shows a further flowchart illustration of a test range analysis method provided by an embodiment of the invention;
FIG. 8 is a schematic flow chart illustrating a test range analysis method according to an embodiment of the present invention;
FIG. 9 is a schematic diagram illustrating test coverage results provided by an embodiment of the present invention;
FIG. 10 is a schematic flow chart diagram illustrating a test range analysis method provided by an embodiment of the invention;
fig. 11 is a schematic structural diagram of a test range analysis apparatus according to an embodiment of the present invention;
fig. 12 is a schematic structural diagram of a test range analysis apparatus according to an embodiment of the present invention;
fig. 13 is a schematic structural diagram of a test range analysis apparatus according to an embodiment of the present invention;
fig. 14 is a schematic structural diagram illustrating a test range analysis device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. In the description of the present invention, it should also be noted that the terms "first", "second", "third", and the like are used for distinguishing the description, and are not intended to indicate or imply relative importance.
The embodiment of the invention provides a test range analysis method which can be used for determining the test range of financial business function tests and enabling testers to more comprehensively perform the business function tests. The main body of the test range analysis method may be a server or a computer, for example, a server for processing test data, or may also be one or more processors in the server or the computer, which is not limited in this respect.
Fig. 1 shows a schematic flow chart of a test range analysis method provided by an embodiment of the present invention.
As shown in fig. 1, the test range analysis method may include:
and S101, acquiring a menu test coverage monitoring result.
Optionally, the menu test coverage monitoring result may include at least one set of transaction data, and the transaction data may refer to transaction information of each transaction record, for example, the transaction information of a certain transaction record may include a transaction success or a transaction failure, and correspondingly, the transaction data may include a success/failure flag bit for indicating the transaction information of the corresponding transaction record. Each set of transaction data may include a corresponding transaction identifier and a menu identifier to which the transaction identifier belongs. The transaction identifier may be a transaction code, and the transaction code may be a unique identifier of the set of transaction data (or the transaction record). The menu code may be used to represent unique identity information of a menu to which the transaction identifier of the set of transaction data belongs, and the menu codes corresponding to different menus are different, that is, the menu codes and the menus may be in a one-to-one correspondence relationship.
Fig. 2 is another schematic flow chart of the test range analysis method according to the embodiment of the present invention.
Optionally, as shown in fig. 2, the step of obtaining the menu test coverage monitoring result in step S101 may specifically include:
s201, acquiring transaction data, a transaction identifier corresponding to the transaction data, and a menu identifier to which the transaction identifier belongs.
S202, generating a menu test coverage monitoring result according to the transaction data, the transaction identifier and the menu identifier.
For example, the menu log data under various different test environments may be processed every day, each transaction record may include a success/failure flag, the same transaction (the transaction with the same transaction code is the same transaction) may be performed multiple times every day, and the success/failure flag of each transaction may be used to calculate the success and failure times of the same transaction, so as to obtain the transaction data. Then, according to the transaction code corresponding to the transaction data, the menu code of the menu to which the transaction code belongs can be obtained, and according to the transaction data, the transaction code and the menu code, a menu test coverage monitoring result is generated.
In some embodiments, the menu test coverage monitoring result may also be stored to generate a menu test coverage monitoring result database, so that when the service function test range is subsequently analyzed, the corresponding menu test coverage monitoring result may be directly called from the menu test coverage monitoring result database.
Optionally, after the menu test coverage monitoring result is obtained, the menu test coverage monitoring result may be displayed through an interface. For example, a display screen can be separately set, and the menu test coverage monitoring result can be sent to the display screen for displaying. Alternatively, the menu test coverage monitoring result may be directly displayed on a display of the computer, and the invention is not limited thereto.
Fig. 3 is a schematic diagram illustrating a menu test coverage monitoring result according to an embodiment of the present invention.
Take the first set of menu test coverage monitoring results shown in FIG. 3 as an example: in the set of menu test coverage monitoring results, the transaction code (i.e., transaction identifier) is "a 00210028"; the transaction data corresponding to the transaction code is that the transaction success frequency is 8 times, and the transaction failure frequency is 0 time; the menu code (i.e., menu identification, which may also be referred to as menu ID as shown in fig. 3) of the menu to which the transaction code belongs is "34 ccb.
And S102, acquiring menu data of the current day and the previous day.
The menu data may include at least one group of menu information, and each group of menu information may include a corresponding menu identifier.
Optionally, the menu information may include: the menu comprises a menu code, a menu path, a menu name, a menu level and a menu source, wherein the menu code is the menu identification. For example, the menu code (menu ID) may be "PDC 20300", "RAD 70025", or the like; the menu path may be a menu Uniform Resource Locator (URL) identifier, such as: action is "/P10/batch report? businessId ═ RAD _ R002 "; the menu name can be 'reference information', 'public warning tracking rate customer list' and the like; the menu level may be "3", "5", etc.; the menu source may be "VT".
Taking the current day as 2019, 12 months and 3 days as an example, the menu data acquired on the current day and the previous day may be: the menu data of day 3, 12 and 2019, and the menu data of day 2, 12 and 2019 are acquired.
S103, determining that the menu information which changes relative to the menu data of the previous day in the menu data of the current day is the target menu information based on the menu identification.
Fig. 4 is a schematic flow chart of a test range analysis method according to an embodiment of the present invention.
Optionally, as shown in fig. 4, in the step S103, the step of determining, based on the menu identifier, that the menu information that has changed with respect to the menu data of the previous day in the menu data of the current day is the target menu information may specifically include:
aiming at any menu information in the menu data of the current day and the previous day:
s401, judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day.
S402, if yes, determining the menu information as target menu information.
Taking the menu data of 12/3/2019 (that is, the current day) and the menu data of 12/2/2019 (that is, the previous day) as examples, for any menu information, it can be determined whether the menu sign corresponding to the menu information satisfies: if the data is only present in the menu data of 2019, 12/month and 3/day but not in the menu data of 2019, 12/month and 2/month, the menu information can be determined as the target menu information.
Fig. 5 is a schematic flow chart of a test range analysis method according to an embodiment of the present invention.
Alternatively, as shown in fig. 5, if it is determined in step S401 that the menu identifier corresponding to the menu information does not satisfy: the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day, the test range analysis method may further include:
s501, judging whether the menu identification corresponding to the menu information meets the following conditions: the menu mark exists in the menu data of the current day and the menu data of the previous day, and the menu mark is different from the corresponding menu information in the menu data of the current day and the menu data of the previous day.
And S502, if the menu information meets the requirement, determining the menu information as target menu information.
Similarly, taking the menu data of 12/3/2019 (that is, the current day) and the menu data of 12/2/2019 (that is, the previous day) as examples, for any menu information, if it is determined that the menu identifier corresponding to the menu information does not satisfy: only exists in the menu data of 12/3/2019, but does not exist in the menu data of 12/2/2019, it can be determined whether the menu identifier corresponding to the menu information satisfies: if the data exists in the menu data of 12/3/2019 and in the menu data of 12/2/2019, the menu information may be specified as the target menu information.
The following describes a specific determination process of the target menu information in a specific embodiment:
in this embodiment, the menu data under different test environments may be subjected to total statistics every day, and the total menu data of the previous day may be pulled, where the menu data may include at least one group of menu information, and the menu information may include information such as a menu code, a menu path, a menu name, a menu level, and a menu source. Then, the menu code may be used as a reference to compare the menu data of the current day with the menu data of the previous day, and the following four cases may be specifically included:
take the menu code as a for example:
1) if the menu information with the menu code of a exists in the menu data of the previous day and the menu information with the menu code of a does not exist in the menu data of the current day, the menu information with the menu code of a can be recorded, and the menu state of the menu information with the menu code of a is marked as 'deleted'.
2) If the menu information with the menu code of A does not exist in the menu data of the previous day and the menu information with the menu code of A exists in the menu data of the current day, the menu information with the menu code of A can be recorded, and the menu state of the menu information with the menu code of A is marked as 'new'.
3) If the menu information with the menu code of a exists in the menu data of the previous day, the menu information with the menu code of a also exists in the menu data of the current day, and the information such as the menu path, the menu name, the menu level, the menu source and the like of the menu information with the menu code of a is not completely the same (namely, different), the menu information with the menu code of a can be recorded, and the menu state of the menu information with the menu code of a is marked as 'change' or 'update'.
4) If the menu information with the menu code of a exists in the menu data of the previous day, the menu information with the menu code of a also exists in the menu data of the current day, and the information such as the menu path, the menu name, the menu level, the menu source and the like of the menu information with the menu code of a is completely the same (i.e., no change), the menu information with the menu code of a may not be recorded.
In the above cases 1), 2), and 3), the menu information whose menu state is marked as "delete", "add", or "change" may be determined as the target menu information, and the obtained target menu information may constitute a menu change baseline monitoring result, so as to be used in the subsequent step S104 to determine the service function test range according to the menu change baseline monitoring result. The menu data of the previous day may then be emptied and the menu data of the current day saved for use the next day.
Optionally, after the menu change baseline monitoring result is obtained, the menu change baseline monitoring result may also be displayed through an interface, and a specific display manner may be the same as the menu test coverage monitoring result, which is not described herein again. In addition, the menu change baseline monitoring result can be stored, and a menu change baseline monitoring result database is generated so as to be convenient for subsequent use.
Fig. 6 is a schematic diagram illustrating a menu change baseline monitoring result according to an embodiment of the present invention.
Taking the group 1 menu change baseline monitoring result and the group 6 menu change baseline monitoring result shown in fig. 6 as examples:
in the group 1 menu change baseline monitoring result, the menu code (ID) of the menu information is "PDC 20300"; menu source (URL) is null; a menu name "reference information"; menu level "3"; the menu state (modification type) is "update"; the modification date is '2019-04-1200: 00: 00'; the menu source is "VT". In the 6 th group menu change baseline monitoring result, the menu code (ID) of the menu information is "MCM 40233"; the menu source (URL) is empty "/ecpWeb/page/mssphy/mcht _ equality/scene/draft/scene _ list.jsp"; the menu name is 'draft box'; menu level "4"; the menu state (modification type) is "new"; the modification date is '2019-04-1200: 00: 00'; the menu source is "VT".
Optionally, in some embodiments of the present invention, as described in the foregoing embodiments, step S101 may be executed first, and then step S102 and step S103 are executed. In another embodiment, step S102 and step S103 may be executed first, and then step S101 may be executed. Alternatively, step S101 and step S102 and step S103 may be parallel steps, which is not limited in the present invention.
After determining that the menu test coverage monitoring result and the target menu information are obtained through the foregoing step S101, step S102, and step S103, the following step S104 may be executed to determine the service function test range.
And S104, determining that the target menu information with the corresponding menu identification in the menu test coverage monitoring result is covered by the test.
Fig. 7 is a schematic flow chart of a test range analysis method according to an embodiment of the present invention.
Optionally, as shown in fig. 7, in the step S104, the step of determining that the target menu information having the corresponding menu identifier in the menu test coverage monitoring result is covered by the test may specifically include:
s701, inquiring whether a menu mark corresponding to the target menu information exists in the menu test coverage monitoring result.
S702, if yes, determining that the target menu information is covered by the test.
And S703, if the target menu information does not exist, determining that the target menu information is not covered by the test.
Take the target menu information with the menu code (i.e. menu identification) as P as an example: whether a menu mark P exists or not can be inquired in a menu test coverage monitoring result, and if the menu mark P exists in the menu test coverage monitoring result, the target menu information with the menu mark P can be determined to be covered by the test; if the menu test coverage monitoring result does not have the menu mark P, it may be determined that the target menu information with the menu mark P is not covered by the test. Therefore, by judging each group of target menu information, which menu information is not covered by the test can be determined, and the test coverage can be analyzed.
As described above, in the embodiment of the present invention, the menu test coverage monitoring result and the menu data of the current day and the previous day are obtained, and based on the menu identifier, it is determined that the menu information that changes with respect to the menu data of the previous day in the menu data of the current day is the target menu information, and then it is determined that the target menu information corresponding to the menu identifier exists in the menu test coverage monitoring result is covered by the test. Compared with the prior art, the method has the advantages that the test range analysis process is simplified, the test range analysis result is accurate, and the completeness of the service function test can be effectively improved.
Fig. 8 is a schematic flow chart of a test range analysis method according to an embodiment of the present invention.
Optionally, as shown in fig. 8, the method for analyzing a test range may further include:
s801, generating a test coverage result according to the target menu information covered by the test and the transaction data corresponding to the target menu information covered by the test in the menu test coverage monitoring result.
And S802, displaying the test coverage result through an interface.
FIG. 9 shows a schematic diagram of test coverage results provided by an embodiment of the present invention.
Take the coverage results of the test in group 1 shown in FIG. 9 as an example:
the menu code (ID) may be "IDC 50067"; the menu name is null; the menu URL is "/ecpweb/page/idc/DebitCardOrderChooseCard/DebitCardOrderChooseCard.js p"; menu level "5"; the modification type is "delete"; the modification date is '2019-05-27'; the transaction code is "A00210029"; the number of successful trades is "1"; the number of transaction failures is "0".
According to the embodiment of the invention, the test coverage result is displayed through the interface, so that a tester can more intuitively know that: which menu information is covered by the test, that is, the service function test range can be obtained more intuitively.
In order to make the technical solution and the beneficial effects thereof provided by the embodiment of the present invention clearer, the embodiment of the present invention further provides a test range analysis method, and fig. 10 shows another schematic flow chart of the test range analysis method provided by the embodiment of the present invention.
As shown in fig. 10, the test range analysis method may include:
s1010, acquiring the transaction data, a transaction identifier corresponding to the transaction data and a menu identifier to which the transaction identifier belongs.
S1020, generating a menu test coverage monitoring result according to the transaction data, the transaction identifier and the menu identifier.
And S1030, acquiring menu data of the current day and the previous day.
Aiming at any menu information in the menu data of the current day and the previous day:
and S1040, judging whether the menu identification corresponding to the menu information only exists in the menu data of the current day.
If yes, go to step S1050; if not, go to step S1060.
And S1050, determining the menu information as target menu information.
The menu information determined as the target menu information may be recorded and stored.
S1060, judging whether the menu identification corresponding to the menu information exists in the menu data of the current day and the previous day at the same time.
If yes, go to step S1061; if not, go to S1050.
Need to explain: if the menu sign corresponding to the menu information is not present in the menu data of the current day and the previous day at the same time, or is not present in the menu data of the current day only, it is present in the menu data of the previous day only, and therefore, it can be directly determined as the target menu information.
S1061, judging whether the menu information respectively corresponding to the menu identification in the menu data of the current day and the previous day is different.
If yes, go to step S1050; if not, the process is ended.
And S1070, inquiring whether the menu test coverage monitoring result has a menu identifier corresponding to the target menu information.
If yes, executing S1080; if not, step 1090 is executed.
And S1080, determining that the target menu information is covered by the test.
And S1090, determining that the target menu information is not covered by the test.
The implementation principle and technical effect of the test range analysis method are the same as or similar to those described in the foregoing embodiments, and are not described herein again.
Based on the test range analysis method described in the foregoing method embodiment, an embodiment of the present invention further provides a test range analysis apparatus, and fig. 11 shows a schematic structural diagram of the test range analysis apparatus provided in the embodiment of the present invention.
As shown in fig. 11, the test range analysis device may include: the first obtaining module 11 is configured to obtain a menu test coverage monitoring result, where the menu test coverage monitoring result includes at least one set of transaction data, and each set of transaction data includes a corresponding transaction identifier and a menu identifier to which the transaction identifier belongs. The second obtaining module 12 is configured to obtain menu data of the current day and the previous day, where the menu data includes at least one group of menu information, and each group of menu information includes a corresponding menu identifier. The first determining module 13 is configured to determine, based on the menu identifier, that, in the menu data of the current day, the menu information that changes with respect to the menu data of the previous day is the target menu information. And a second determining module 14, configured to determine that the target menu information with the corresponding menu identifier in the menu test coverage monitoring result has been covered by the test.
Optionally, the first obtaining module 11 is specifically configured to obtain the transaction data, a transaction identifier corresponding to the transaction data, and a menu identifier to which the transaction identifier belongs, and generate a menu test coverage monitoring result according to the transaction data, the transaction identifier, and the menu identifier.
Optionally, the second determining module 14 is specifically configured to query whether a menu identifier corresponding to the target menu information exists in the menu test coverage monitoring result; if yes, determining that the target menu information is covered by the test; and if not, determining that the target menu information is not covered by the test.
Optionally, the first determining module 13 is specifically configured to, for any menu information in the menu data of the current day and the previous day: judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day; and if so, determining the menu information as the target menu information.
Optionally, the first determining module 13 is further specifically configured to, if the menu identifier corresponding to the menu information does not satisfy: if the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day, judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day and the menu data of the previous day, and the menu identification is different from the corresponding menu information in the menu data of the current day and the menu data of the previous day respectively; and if so, determining the menu information as the target menu information.
Optionally, the menu information includes: menu code, menu path, menu name, menu level, and menu source.
Fig. 12 is a schematic structural diagram of a test range analysis apparatus according to an embodiment of the present invention.
Optionally, as shown in fig. 12, the test range analysis apparatus may further include: and the generating module 15 is configured to generate a test coverage result according to the target menu information that has been covered by the test and the transaction data corresponding to the target menu information that has been covered by the test in the menu test coverage monitoring result. And the first display module 16 is used for displaying the test coverage result through an interface.
Fig. 13 is a schematic structural diagram of a test range analysis apparatus according to an embodiment of the present invention.
Optionally, as shown in fig. 13, the test range analysis apparatus may further include: and the second display module 17 is configured to display the menu test coverage monitoring result through an interface. And the third display module 18 is used for displaying the target menu information through the interface.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus described above may refer to the corresponding process of the method in the foregoing method embodiment, and is not described in detail herein.
The test range analysis device provided in the embodiment of the present invention corresponds to the test range analysis method described in the foregoing method embodiment, and therefore, the test range analysis device described in the device embodiment has all the beneficial effects of the test range analysis method described in the foregoing embodiment, and details are not repeated here.
An embodiment of the present invention further provides a test range analysis device, which may be the foregoing computer or server, but the present invention is not limited to this, and fig. 14 illustrates a schematic structural diagram of the test range analysis device provided in the embodiment of the present invention.
As shown in fig. 14, the test range analysis device may include: a processor 100, a storage medium 200 and a bus (not shown), wherein the storage medium 200 stores machine-readable instructions executable by the processor 100, and when the test range analysis device is operated, the processor 100 communicates with the storage medium 200 through the bus, and the processor 100 executes the machine-readable instructions to perform the test range analysis method as described in the foregoing method embodiment. The specific implementation and technical effects are similar, and are not described herein again.
For ease of illustration, only one processor is described in the above test range analysis apparatus. However, it should be noted that the test range analysis device in the present invention may also include a plurality of processors, and thus the steps performed by one processor described in the present invention may also be performed by a plurality of processors in combination or individually. For example, the processor of the electronic device executes step a and step B, it should be understood that step a and step B may also be executed by two different processors together or separately in one processor. For example, a first processor performs step a and a second processor performs step B, or the first processor and the second processor perform steps a and B together, etc.
In some embodiments, a processor may include one or more processing cores (e.g., a single-core processor (S) or a multi-core processor (S)). Merely by way of example, a Processor may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Set Processor (ASIP), a Graphics Processing Unit (GPU), a Physical Processing Unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller Unit, a Reduced Instruction Set computer (Reduced Instruction Set computer), a microprocessor, or the like, or any combination thereof.
An embodiment of the present invention further provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method for analyzing a test range as described in the foregoing method embodiment is performed. The specific implementation and technical effects are similar, and are not described herein again.
Alternatively, the storage medium may be a U disk, a removable hard disk, a ROM, a RAM, a magnetic or optical disk, or the like.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A test range analysis method, the method comprising:
acquiring a menu test coverage monitoring result, wherein the menu test coverage monitoring result comprises at least one group of transaction data, and each group of transaction data comprises a corresponding transaction identifier and a menu identifier to which the transaction identifier belongs;
acquiring menu data of the current day and the previous day, wherein the menu data comprises at least one group of menu information, and each group of menu information comprises a corresponding menu identification;
determining that the menu information which changes relative to the menu data of the previous day in the menu data of the current day is target menu information based on the menu identification;
and determining that the target menu information with the corresponding menu identification in the menu test coverage monitoring result is covered by the test.
2. The method of claim 1, wherein obtaining the menu test coverage monitoring result comprises:
acquiring transaction data, a transaction identifier corresponding to the transaction data and a menu identifier to which the transaction identifier belongs;
and generating a menu test coverage monitoring result according to the transaction data, the transaction identifier and the menu identifier.
3. The method of claim 2, wherein the determining that the target menu information with the corresponding menu identifier in the menu test coverage monitoring result is covered by the test comprises:
inquiring whether a menu mark corresponding to the target menu information exists in the menu test coverage monitoring result;
if yes, determining that the target menu information is covered by the test;
and if not, determining that the target menu information is not covered by the test.
4. The method according to claim 1, wherein the determining that the menu information that has changed with respect to the menu data of the previous day in the menu data of the current day is the target menu information based on the menu identifier includes:
aiming at any menu information in the menu data of the current day and the previous day:
judging whether the menu identification corresponding to the menu information meets the following conditions: the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day;
and if so, determining the menu information as target menu information.
5. The method of claim 4, further comprising:
if the menu identification corresponding to the menu information does not meet the requirements: if the menu identification exists in the menu data of the current day but does not exist in the menu data of the previous day, judging whether the menu identification corresponding to the menu information meets the following requirements:
the menu identification exists in the menu data of the current day and the menu data of the previous day, and the menu identification is different from the corresponding menu information in the menu data of the current day and the menu data of the previous day respectively;
and if so, determining the menu information as target menu information.
6. The method according to any of claims 1-5, wherein the menu information comprises: menu code, menu path, menu name, menu level, and menu source.
7. The method according to any one of claims 1-5, further comprising:
generating a test coverage result according to the target menu information which is tested to be covered and the transaction data corresponding to the target menu information which is tested to be covered in the menu test coverage monitoring result;
and displaying the test coverage result through an interface.
8. The method according to any one of claims 1-5, further comprising:
and respectively displaying the menu test coverage monitoring result and the target menu information through an interface.
9. A test range analysis apparatus, comprising:
the menu testing system comprises a first acquisition module, a second acquisition module and a monitoring module, wherein the first acquisition module is used for acquiring a menu testing coverage monitoring result, the menu testing coverage monitoring result comprises at least one group of transaction data, and each group of transaction data comprises a corresponding transaction identifier and a menu identifier to which the transaction identifier belongs;
the second acquisition module is used for acquiring menu data of the current day and the previous day, wherein the menu data comprises at least one group of menu information, and each group of menu information comprises a corresponding menu identifier;
a first determining module, configured to determine, based on the menu identifier, that, in the current-day menu data, menu information that changes with respect to the previous-day menu data is target menu information;
and the second determining module is used for determining that the target menu information with the corresponding menu identification in the menu test coverage monitoring result is covered by the test.
10. A test range analysis apparatus, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the test range analysis device is run, the processor executing the machine-readable instructions to perform the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911253592.7A CN111026665B (en) | 2019-12-09 | 2019-12-09 | Test range analysis method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911253592.7A CN111026665B (en) | 2019-12-09 | 2019-12-09 | Test range analysis method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111026665A true CN111026665A (en) | 2020-04-17 |
| CN111026665B CN111026665B (en) | 2023-02-28 |
Family
ID=70205151
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911253592.7A Active CN111026665B (en) | 2019-12-09 | 2019-12-09 | Test range analysis method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111026665B (en) |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090300587A1 (en) * | 2008-05-27 | 2009-12-03 | Microsoft Corporation | Determining domain data coverage in testing database applications |
| CN102736980A (en) * | 2012-06-29 | 2012-10-17 | 南京大学 | Random test case generation method facing Java program |
| CN103246600A (en) * | 2012-02-10 | 2013-08-14 | 广州博纳信息技术有限公司 | Fast verification method for software testing and evaluation |
| CN103699476A (en) * | 2012-09-27 | 2014-04-02 | 腾讯科技（深圳）有限公司 | Coverage rate testing method and system |
| JP2014127091A (en) * | 2012-12-27 | 2014-07-07 | Fujitsu Ltd | Test data generation method, program and device |
| CN104714882A (en) * | 2013-12-17 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Code information processing method and device |
| US20150169431A1 (en) * | 2013-12-18 | 2015-06-18 | Google Inc. | Process for displaying test coverage data during code reviews |
| US20160259715A1 (en) * | 2008-08-26 | 2016-09-08 | International Business Machines Corporation | Test coverage analysis |
| CN107085555A (en) * | 2017-04-19 | 2017-08-22 | 广州视源电子科技股份有限公司 | Code test method, device, terminal and storage medium |
| US20180101468A1 (en) * | 2015-04-15 | 2018-04-12 | Entit Software Llc | Code coverage information |
| CN108170610A (en) * | 2018-01-17 | 2018-06-15 | 北京网信云服信息科技有限公司 | The method and apparatus for determining test coverage |
| CN109426604A (en) * | 2017-08-22 | 2019-03-05 | 阿里巴巴集团控股有限公司 | The monitoring method and equipment of code development |
| JP2019144700A (en) * | 2018-02-16 | 2019-08-29 | Ｎｅｃプラットフォームズ株式会社 | Test system, test method and program |
| CN110287101A (en) * | 2019-05-22 | 2019-09-27 | 深圳壹账通智能科技有限公司 | User interface automated testing method, device, computer equipment and storage medium |
| CN110377522A (en) * | 2019-07-22 | 2019-10-25 | 中国工商银行股份有限公司 | The test method for scene of trading, calculates equipment and medium at device |
| CN110413506A (en) * | 2019-06-19 | 2019-11-05 | 平安普惠企业管理有限公司 | Test case recommended method, device, equipment and storage medium |
-
2019
- 2019-12-09 CN CN201911253592.7A patent/CN111026665B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090300587A1 (en) * | 2008-05-27 | 2009-12-03 | Microsoft Corporation | Determining domain data coverage in testing database applications |
| US20160259715A1 (en) * | 2008-08-26 | 2016-09-08 | International Business Machines Corporation | Test coverage analysis |
| CN103246600A (en) * | 2012-02-10 | 2013-08-14 | 广州博纳信息技术有限公司 | Fast verification method for software testing and evaluation |
| CN102736980A (en) * | 2012-06-29 | 2012-10-17 | 南京大学 | Random test case generation method facing Java program |
| CN103699476A (en) * | 2012-09-27 | 2014-04-02 | 腾讯科技（深圳）有限公司 | Coverage rate testing method and system |
| JP2014127091A (en) * | 2012-12-27 | 2014-07-07 | Fujitsu Ltd | Test data generation method, program and device |
| CN104714882A (en) * | 2013-12-17 | 2015-06-17 | 腾讯科技（深圳）有限公司 | Code information processing method and device |
| US20150169431A1 (en) * | 2013-12-18 | 2015-06-18 | Google Inc. | Process for displaying test coverage data during code reviews |
| US20180101468A1 (en) * | 2015-04-15 | 2018-04-12 | Entit Software Llc | Code coverage information |
| CN107085555A (en) * | 2017-04-19 | 2017-08-22 | 广州视源电子科技股份有限公司 | Code test method, device, terminal and storage medium |
| CN109426604A (en) * | 2017-08-22 | 2019-03-05 | 阿里巴巴集团控股有限公司 | The monitoring method and equipment of code development |
| CN108170610A (en) * | 2018-01-17 | 2018-06-15 | 北京网信云服信息科技有限公司 | The method and apparatus for determining test coverage |
| JP2019144700A (en) * | 2018-02-16 | 2019-08-29 | Ｎｅｃプラットフォームズ株式会社 | Test system, test method and program |
| CN110287101A (en) * | 2019-05-22 | 2019-09-27 | 深圳壹账通智能科技有限公司 | User interface automated testing method, device, computer equipment and storage medium |
| CN110413506A (en) * | 2019-06-19 | 2019-11-05 | 平安普惠企业管理有限公司 | Test case recommended method, device, equipment and storage medium |
| CN110377522A (en) * | 2019-07-22 | 2019-10-25 | 中国工商银行股份有限公司 | The test method for scene of trading, calculates equipment and medium at device |
Non-Patent Citations (2)
| Title |
|---|
| 兰孝文: "金融业务系统可回归测试框架研究", 《电脑知识与技术(学术交流)》 * |
| 索炜等: "聚焦业务流程 实现金融科技产品系统测试自动化设计", 《中国金融电脑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111026665B (en) | 2023-02-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110362473B (en) | Test environment optimization method and device, storage medium and terminal | |
| CN109976999B (en) | Method and device for measuring coverage rate of test cases | |
| CN111221727B (en) | Test method, test device, electronic equipment and computer readable medium | |
| US20150186195A1 (en) | Method of analysis application object which computer-executable, server performing the same and storage media storing the same | |
| CN114371974A (en) | Buried point data checking method and electronic equipment | |
| CN111367782A (en) | Method and device for automatically generating regression test data | |
| CN111026665B (en) | Test range analysis method, device and equipment | |
| CN113535538A (en) | Application full-link automatic testing method and device, electronic equipment and storage medium | |
| CN110866492B (en) | Baseline branch identification method and device and computer system | |
| US11567758B2 (en) | Configuration properties management for software | |
| CN112612674A (en) | Method, device, equipment and computer readable storage medium for monitoring buried point data | |
| CN113011858A (en) | Audit project configuration and execution method and device | |
| CN112579428A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN111290943A (en) | Code coverage rate processing method, device, server and storage medium | |
| CN112988560A (en) | Method and device for testing system robustness | |
| CN113821441B (en) | Execution method, device, equipment and storage medium based on document test case | |
| CN110688295A (en) | Data testing method and device | |
| CN113282751B (en) | Log classification method and device | |
| CN110362464A (en) | Software analysis method and equipment | |
| CN110018946B (en) | Performance data display method, device, equipment and computer readable storage medium | |
| CN112749767B (en) | Article inspection method and apparatus | |
| CN116521663A (en) | Prefabricated data center system management method and system | |
| CN115033474A (en) | Application program defect detection method and device, electronic equipment and storage medium | |
| CN114924969A (en) | Information processing method and device | |
| CN117057923A (en) | Butt joint test method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220908 Address after: 12 / F, 15 / F, 99 Yincheng Road, Pudong New Area pilot Free Trade Zone, Shanghai, 200120 Applicant after: Jianxin Financial Science and Technology Co.,Ltd. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |