CN116680177A - Method and device for testing functional product and storage medium - Google Patents

Method and device for testing functional product and storage medium Download PDF

Info

Publication number
CN116680177A
CN116680177A CN202310632645.6A CN202310632645A CN116680177A CN 116680177 A CN116680177 A CN 116680177A CN 202310632645 A CN202310632645 A CN 202310632645A CN 116680177 A CN116680177 A CN 116680177A
Authority
CN
China
Prior art keywords
product
tested
functional product
functional
test
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
Application number
CN202310632645.6A
Other languages
Chinese (zh)
Inventor
杜卉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bank of China Ltd
Original Assignee
Bank of China Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Bank of China Ltd filed Critical Bank of China Ltd
Priority to CN202310632645.6A priority Critical patent/CN116680177A/en
Publication of CN116680177A publication Critical patent/CN116680177A/en
Pending legal-status Critical Current

Links

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
    • 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/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application provides a method and a device for testing a functional product and a storage medium. The method comprises the following steps: acquiring a test analysis instruction, wherein the test analysis instruction comprises an identifier of a functional product to be tested; wherein the functional product to be tested is a functional product of a target business system; determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present; judging whether the functional product to be tested can be tested currently or not based on the latest deployment state of each functional product; and if the functional product to be tested can be tested currently, performing case test on the functional product to be tested to obtain a test result. The method of the application improves the accuracy of the test result of the functional product.

Description

Method and device for testing functional product and storage medium
Technical Field
The present application relates to software testing technologies, and in particular, to a method and apparatus for testing a functional product, and a storage medium.
Background
A financial system is a product that provides services for financial transactions, such as an internet banking. Financial systems typically include multiple services, each including multiple service systems, each including multiple functional products and each capable of implementing multiple service functions. For example, the financial system includes a subscription service including a user registration system, an administrator system, a user login system, and a user subscription system. The multiple functional products of the user registration system comprise a front-end user registration system and a corresponding multiple background, and the multiple background can be used for data analysis and processing, data reading and data storage respectively.
Before a certain functional product of a financial system is put into production and released, the functional product needs to be tested first to ensure that the functional product put into production and released is normally operated, so that a functional product testing method appears.
In the conventional manner, before a case test is performed on a functional product, whether the functional product is in a testable state is determined, specifically, by a tester of the functional product according to whether the tester has deployed a corresponding product version. When the tester determines that the functional product has deployed the corresponding product version, the tester performs a case test on the functional product.
However, each functional product in a business system is affected by each other when performing case testing, but the testers of each functional product are independent of each other when determining whether the corresponding functional product is testable, and do not know whether other functional products have versions deployed. Therefore, after the case test is performed on the functional product, the obtained test result of the functional product is not accurate enough.
Disclosure of Invention
The application provides a method and a device for testing a functional product and a storage medium, which are used for solving the technical problem that the test result of the functional product is not accurate enough in the prior art.
In a first aspect, the present application provides a method for testing a functional product, comprising:
acquiring a test analysis instruction, wherein the test analysis instruction comprises an identifier of a functional product to be tested; wherein the functional product to be tested is a functional product of a target business system;
determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present;
Judging whether the functional product to be tested can be tested currently or not based on the latest deployment state of each functional product;
and if the functional product to be tested can be tested currently, performing case test on the functional product to be tested to obtain a test result.
In one embodiment, before determining the latest deployment status of each functional product including the functional product to be tested in the target business system based on the identification of the functional product to be tested, the method further includes:
determining target product link data of the functional product to be tested based on the identification of the functional product to be tested; the target product link data comprises identifiers of a plurality of functional products in the target service system and an upstream-downstream relation when the functional products are subjected to data circulation;
determining, based on the identification of the functional product to be tested, a latest deployment state of each functional product including the functional product to be tested in the target service system, including:
searching in a product state database based on the identification of each functional product in the target product link data to determine the latest deployment state of each functional product including the functional product to be tested in the target service system; the product state database stores the identifiers of the functional products of the plurality of product link data and the corresponding latest deployment states.
In one embodiment, the determining whether the functional product to be tested can be tested currently based on the latest deployment status of each functional product includes:
judging whether the latest deployment state of each functional product is in a state that the corresponding product version is deployed;
if the functional products are determined to be in the state of being deployed with the corresponding product versions, determining that the functional products to be tested can be tested currently;
or alternatively, the process may be performed,
and if the latest deployment state of at least one functional product is determined to be a state which is not in a state where the corresponding product version is deployed, outputting an indication message to indicate that the functional product to be tested cannot be tested currently.
In one embodiment, before storing the most recent deployment status for each of the functional products in the product status database, the method further comprises:
sending detection data packets to deployment interfaces of all functional products in a target test environment through a state detection tool; the target test environment is a test environment where each functional product in the target service system is located;
for each functional product in the functional products, if a return signal of a deployment interface of the functional product is received, determining that the latest deployment state of the functional product is in a state in which a corresponding product version is deployed;
If the return signal of the deployment interface of the functional product is not received, determining that the latest deployment state of the functional product is not in a state in which the corresponding product version is already deployed.
In one embodiment, the performing a case test on the functional product to be tested to obtain a test result includes:
obtaining test data;
taking the test data as input, and executing case test on the functional product to be tested through a pre-constructed automatic test script to obtain a test output result;
and obtaining a test result according to the test output result and the expected output result.
In one embodiment, the test results include: whether the function to be tested has a code bug or not, and information of the code bug when the code bug exists.
In a second aspect, the present application provides a test device for a functional product, the device comprising:
the test instruction acquisition module is used for acquiring a test analysis instruction, wherein the test analysis instruction comprises an identifier of a functional product to be tested; wherein the functional product to be tested is a functional product of a target business system;
the deployment state determining module is used for determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present;
The testability judging module is used for judging whether the functional product to be tested can be tested currently or not based on the latest deployment state of each functional product;
and the test result acquisition module is used for executing case test on the functional product to be tested if the functional product to be tested can be tested currently, so as to obtain a test result.
In a third aspect, the present application provides a server comprising: a processor, a transceiver, and a memory communicatively coupled to the processor;
the transceiver is used for transmitting instructions and data;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method as described in the first aspect.
In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for performing the method according to the first aspect when executed by a processor.
In a fifth aspect, the application provides a computer program product comprising a computer program which, when executed by a processor, implements the method according to the first aspect.
According to the method, the device and the storage medium for testing the functional product, provided by the application, the test analysis instruction is obtained, and the test analysis instruction comprises the identification of the functional product to be tested; wherein the functional product to be tested is a functional product of a target business system; determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present; judging whether the functional product to be tested can be tested currently or not based on the latest deployment state of each functional product; and if the functional product to be tested can be tested currently, performing case test on the functional product to be tested to obtain a test result. After the test analysis instruction is acquired, determining the latest deployment state of each functional product in the target service system based on the identification of the functional product to be tested. And judging whether the functional product to be tested is currently measurable or not based on the latest deployment state of each functional product. And when the functional product to be tested can be tested currently, performing case test on the functional product to be tested to obtain a corresponding test result. Before the case test is executed, not only the latest deployment state of the functional product to be tested is considered, but also the latest deployment state of other functional products in the target service system is combined to determine whether the functional product to be tested can be tested currently, so that the test case is executed under the condition that corresponding product versions are deployed for all the functional products in the target service system. Therefore, after the functional product to be tested is subjected to the case test, a more accurate test result can be obtained.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is an application scenario diagram of a testing method for implementing a functional product according to an embodiment of the present application;
FIG. 2 is a flow chart of a testing method for realizing a functional product according to an embodiment of the application;
FIG. 3 is a flow chart of a testing method for realizing a functional product according to another embodiment of the present application;
FIG. 4 is a schematic diagram of a testing method for realizing a functional product according to the present application;
fig. 5 is a schematic diagram of a server in a test method for realizing a functional product.
Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
It should be noted that the method and the device for testing the functional product of the present application can be used in the financial field, and can also be used in any field other than the financial field, and the application field of the method and the device for testing the functional product of the present application is not limited.
For a clear understanding of the technical solutions of the present application, the prior art solutions will be described in detail first.
In the conventional manner, before a case test is performed on a functional product, whether the functional product is in a testable state is determined, specifically, by a tester of the functional product according to whether the tester has deployed a corresponding product version. When the tester determines that the functional product has deployed the corresponding product version, the tester performs a case test on the functional product.
However, each functional product in a business system is affected by each other when performing case testing, but the testers of each functional product are independent of each other when determining whether the corresponding functional product is testable, and do not know whether other functional products have versions deployed. Therefore, after the case test is performed on the functional product, the obtained test result of the functional product is not accurate enough.
The inventor has found after creative research that, in order to perform case test on functional products, the obtained test results are accurate. Therefore, when a certain functional product in the financial system is used as the functional product to be tested, before the case test is executed on the functional product to be tested, the latest deployment state of the functional product to be tested is considered, and the latest deployment state of other functional products in the target business system is combined to determine whether the functional product to be tested can be tested currently. Compared with the traditional mode, the functional products to be tested in the application are the execution test cases which are carried out again under the condition that corresponding product versions are deployed in each functional product in the target service system. Therefore, after the functional product to be tested is subjected to the case test, a more accurate test result can be obtained.
As shown in fig. 1, an application scenario of a testing method for a functional product provided by an embodiment of the present application includes a server 10 and a tester terminal 20 in a corresponding network architecture in the application scenario, where the server and the tester terminal are in communication connection.
When a tester needs to perform testability analysis on a certain functional product, a test analysis instruction is sent to the server 10 through the tester terminal 20, wherein the test analysis instruction comprises the identification of the functional product to be tested. After receiving the test analysis instruction, the server 10 can determine the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identifier of the functional product to be tested in the test analysis instruction. And judging whether the functional products to be tested can be tested currently or not based on the latest deployment state of each functional product. When it is determined that the functional product to be tested can be tested currently, a case test is performed on the functional product to be tested to obtain a test result, and the test result is issued to the tester terminal 20.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a schematic diagram of a testing method of a functional product according to an embodiment of the present application, and as shown in fig. 2, an execution subject of the testing method of the functional product according to the embodiment is a server. The test method of the functional product provided in the embodiment includes the following steps:
step 101, obtaining a test analysis instruction.
As mentioned above, a plurality of business systems are typically included in a financial system, each business system including a plurality of functional products, and in order to facilitate the testing platform in determining which functional product is currently being analyzed before testing, the test analysis instructions include an identification of the functional product to be tested. Therefore, the test platform can determine that the functional product to be tested is analyzed before the current test is performed according to the identification of the functional product to be tested. The functional product refers to a software product with certain functions and characteristics, and the target service system is a service system where the functional product to be tested is located. All business systems, including the target business system, typically require multiple functional products to be implemented in conjunction with data flow.
When the test platform receives the test analysis instruction, the test platform firstly judges whether the functional product to be tested is in a testable state, and when the testable state is confirmed, the case test can be executed on the functional product to be tested later.
Step 102, determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested.
Specifically, in order to determine whether the functional product to be tested is in a testable state, the latest deployment state of each functional product including the functional product to be tested in the target service system is determined based on the identification of the functional product to be tested.
The latest deployment state of the functional product refers to whether the current latest moment of the functional product is in a state that a corresponding product version is deployed. The latest deployment state of each functional product may be in a state in which the corresponding product version has been deployed or in a state in which the corresponding product version has not been deployed.
In testing of functional products, version deployment refers to the deployment of versions developed by a test team or development team into a specific test environment. Version deployments may be deployed by employing version control tools, automated deployment tools, and the like.
Step 103, based on the latest deployment state of each functional product, judging whether the functional product to be tested can be tested currently.
That is, before executing the test case for the functional product to be tested, it is determined whether the functional product to be tested can be tested currently according to the latest deployment state of each functional product determined previously.
Step 104, if it is determined that the functional product to be tested can be tested currently, performing a case test on the functional product to be tested to obtain a test result.
If it is determined that the functional product to be tested can be tested currently, performing case test on the functional product to be tested, and obtaining a corresponding test result after the test is completed. The test result comprises whether the function to be tested has a code bug or not and information of the code bug when the code bug exists.
In the application, a test analysis instruction is obtained, wherein the test analysis instruction comprises an identifier of a functional product to be tested; wherein the functional product to be tested is a functional product of a target business system; determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present; judging whether the functional product to be tested can be tested currently or not based on the latest deployment state of each functional product; and if the functional product to be tested can be tested currently, performing case test on the functional product to be tested to obtain a test result. After the test analysis instruction is acquired, determining the latest deployment state of each functional product in the target service system based on the identification of the functional product to be tested. And judging whether the functional product to be tested is currently measurable or not based on the latest deployment state of each functional product. And when the functional product to be tested can be tested currently, performing case test on the functional product to be tested to obtain a corresponding test result. Before the case test is executed, not only the latest deployment state of the functional product to be tested is considered, but also the latest deployment state of other functional products in the target service system is combined to determine whether the functional product to be tested can be tested currently, so that the test case is executed under the condition that corresponding product versions are deployed for all the functional products in the target service system. Therefore, after the functional product to be tested is subjected to the case test, a more accurate test result can be obtained.
In addition, as the testers of each functional product in the traditional mode independently test, the influence of other related functional products on the testers is not considered. If a problem occurs when a functional product to be tested is subjected to case test, whether the problem is caused by a product code problem or a version deployment problem of other products is difficult to determine, and the positioning problem needs to be checked from the two aspects, so that the positioning problem has a complex process and low efficiency. In the application, the latest deployment state of each functional product is already known before determining whether the functional product to be tested is measurable. Therefore, when a problem occurs in the case test of the functional product to be tested later, whether the problem is caused by the version deployment problem of other functional products can be quickly determined, so that the problem positioning process is relatively simple and the efficiency is higher. For example, in the case that there is no problem in the version deployment of other functional products, the problem can be definitely the functional product code of the functional product to be tested, and the problem can be located from the code. In the case that the version deployment of other functional products is problematic, it is also possible to quickly know which functional products are problematic in version deployment.
As an optional implementation manner, in this embodiment, before step 102, the method further includes a step 201 of determining, based on the identifier of the functional product to be tested, the target product link data where the functional product to be tested is located.
The product relation database is preset in the test platform and stores the identification of each business system in the financial system and the corresponding product link data of each business system. The product link data where the functional product to be tested is located is referred to as target product link data.
The target product link data comprises the identification of a plurality of functional products in the target service system and the upstream-downstream relation when the data flow is carried out among the plurality of functional products.
Accordingly, step 102 specifically includes: and searching in a product state database based on the identification of each functional product in the target product link data to determine the latest deployment state of each functional product including the functional product to be tested in the target service system.
The product state database is preset in the test platform, and the product state database stores the identifiers of all functional products in all product link data in the financial system and the corresponding latest deployment state. For example, the link data of the target product is A-B-C-D, and the latest deployment state corresponding to each functional product A, B, C and D can be determined by searching in the product state database according to the identifiers of the functional products A, B, C and D and the like.
In this embodiment, before determining, based on the identifier of the functional product to be tested, a latest deployment state of each functional product including the functional product to be tested in the target service system, determining, based on the identifier of the functional product to be tested, target product link data where the functional product to be tested is located. When the latest deployment state of each functional product including the functional product to be tested in the target business system is determined based on the identification of each functional product in the target product link data, the latest deployment state is determined by searching in a product state database based on the identification of each functional product in the target product link data. Based on the identification of each functional product in the target product link data, the latest deployment state of each functional product in the target service system is determined from the product state database, so that the accuracy of acquiring the latest deployment state can be ensured to a certain extent.
As an optional implementation manner, in this embodiment, the indication message includes a first indication message and a second indication message; step 103, comprising the steps of:
step 301, determining whether the latest deployment status of each functional product is in a status that the corresponding product version has been deployed.
Specifically, when the latest deployment of each functional product in the target service system is obtained from the product state database, the method can be used for judging whether the latest deployment state of each functional product is in a state that the corresponding product version is already deployed.
If it is determined that the latest deployment status of each functional product is in a status in which a corresponding product version has been deployed, step 302 is executed to determine that the functional product to be tested can be tested currently.
If it is determined that at least one of the latest deployment states of the functional products is not in a state in which the corresponding product version has been deployed, step 303 is executed to output an indication message to indicate that the functional product to be tested cannot be tested currently.
The content of the indication message may be "the functional product to be tested cannot be tested currently", or any other language description indicating the function of the functional product to be tested cannot be tested currently, and the content expression mode of the indication message is not specifically limited.
In this embodiment, it is determined whether the latest deployment state of each of the functional products is in a state in which a corresponding product version has been deployed; if the functional products are determined to be in the state of being deployed with the corresponding product versions, determining that the functional products to be tested can be tested currently; or if the latest deployment state of at least one functional product is determined to be a state which is not in a state of deploying the corresponding product version, outputting an indication message to indicate that the functional product to be tested cannot be tested currently. Based on the latest deployment state of each functional product, when all the functional products are in a state in which corresponding product versions are deployed, the functional products to be tested can be tested currently, so that case testing is performed on the functional products to be tested subsequently, and the accuracy of subsequent testing results can be improved.
As an alternative implementation manner, the present embodiment further includes, before storing the latest deployment status of each of the functional products in the product status database, the following steps:
step 401, sending a detection data packet to a deployment interface of each functional product in the target test environment through a state detection tool.
The state detection tool can be program codes, and can realize state detection of the functional product by controlling the running of the state detection tool. The target test environment is the test environment where each functional product in the target business system is located. The deployment interfaces of the functional products in the target service system are preset in the target test environment.
When the state of the functional product is detected, a detection data packet is sent to the deployment interface of each functional product in the target test environment. Here, the content in the detection packet is not limited.
For each of the functional products, if a return signal of the deployment interface of the functional product is received, step 402 is executed to determine that the latest deployment state of the functional product is in a state in which a corresponding product version has been deployed.
For each functional product of each functional product in the target service system, if the functional product is already deployed in the target test environment, the detection state tool may receive a return signal of the functional product when sending a detection data packet to a deployment interface corresponding to the functional product.
If the return signal of the deployment interface of the functional product is not received, step 403 is executed to determine that the latest deployment state of the functional product is not in a state in which the corresponding product version has been deployed.
Here, if the functional product is not deployed in the target test environment, no return signal is received when the detection status tool sends a detection data packet to the functional product.
And sending detection data packets to the deployment interfaces of the functional products in the target service system through the state detection tool, and determining whether the service functions in the target service system are in a state of deploying corresponding product versions according to whether the state detection tool can receive corresponding return signals.
The state detection tool can detect the deployment state of each functional product in the target service system according to the preset frequency. After each detection, the deployment state of each functional product in the target service system and the corresponding identification can be stored in a product state database.
In the embodiment, a detection data packet is sent to a deployment interface of each functional product in a target test environment through a state detection tool; the target test environment is a test environment where each functional product in the target service system is located; for each functional product in the functional products, if a return signal of a deployment interface of the functional product is received, determining that the latest deployment state of the functional product is in a state in which a corresponding product version is deployed; if the return signal of the deployment interface of the functional product is not received, determining that the latest deployment state of the functional product is not in a state in which the corresponding product version is already deployed.
As an alternative implementation, as shown in fig. 3, in this embodiment, step 104 includes the following steps:
in step 501, test data is obtained.
The test data is input data for verifying the service function of the functional product to be tested, and can be used for testing whether the service function of the functional product to be tested is normal or not and whether the service function of the functional product to be tested is successfully updated or not.
Step 502, taking the test data as input, and executing case test on the functional product to be tested through a pre-built automatic test script to obtain a test output result.
The test output result is an output result when verifying the service function of the functional product to be tested. And taking the test data as input, and executing case test on the functional product to be tested through the pre-built automatic test script to obtain a test output result.
The automation script is the most important part in the automation testing tool, and is used for simulating user operation, organizing the execution of test cases, collecting test results, supporting the generation of test reports and the like.
In particular, how to construct an automatic test script and execute case test on a functional product to be tested by the automatic test script to obtain a test output result is not described in detail in the prior art.
And step 503, obtaining a test result according to the test output result and the expected output result.
Wherein the expected output result is a defined output result when the automated test script is constructed. And comparing the test output result with the expected output result, and if the test output result is the same as the expected output result, determining that the code loophole does not exist in the functional product to be tested. If the test output result is different from the expected output result, the test result is the information of the code loopholes and the code loopholes in the functional product to be tested.
In this embodiment, test data is acquired; taking the test data as input, and executing case test on the functional product to be tested through a pre-constructed automatic test script to obtain a test output result; and obtaining a test result according to the test output result and the expected output result. The automatic test script is an industry mature tool for executing case test, and the automatic test script is used for executing case test on the functional product to be tested, so that the high efficiency and accuracy of the obtained test result can be ensured.
In one embodiment, for better control of different product test arrangements, the control granularity of the test task is refined so as to test the functional product to be tested later, and the time is distributed for the testers.
The number of days of the test person is the number of test days required by the test person for testing the functional product to be tested.
Number of days of the present test person= (total number of days of history test person/total number of days of history developer) number of days of the present task developer. The sum of the number of the historical tester days is the number of test days required by testers who test the functional products to be tested in the past. The sum of the historical development days is the total development days required by the developer who develops the functional product to be tested in the past. The number of days of the task developer is the number of development days required by the developer of the functional product to be tested in the test.
The number of days of the test analyst is the total number of days required by the analyst who analyzes the test result of the functional product to be tested.
The number of test analyst days = (sum of historical test analyst days/sum of historical developer days) the number of task developer days. The total number of days of historical test analysis is the total number of analysis days required by an analyst who analyzes the functional product to be tested in the past. The sum of the historical development days is the total development days required by the developer who develops the functional product to be tested in the past. The number of days of the task developer is the number of development days required by the developer of the functional product to be tested in the test.
The number of days for preparing the test data at this time refers to the number of preparation days required for preparing the test related data for the functional product to be tested at this time. Wherein the test related data is such as test cases, test data, environment configuration, interface documents, product design documents, etc.
The number of test data preparation days=the sum of the number of historical test data preparation days/the number of historical test tasks. The sum of the preparation days of the historical test data refers to the preparation days which are needed for preparing test related data for the functional product to be tested. The historical test task number refers to the task number of testing the functional product to be tested in a historical way.
The number of people needed in the test data preparation stage is the number of people needed to prepare data in the test data preparation stage.
The number of people needed in the current test data preparation stage= (sum of the number of days of historical test data preparation/number of historical test tasks)/number of days of current test data preparation. The sum of the number of days of preparing the historical test data refers to the sum of the number of days required by a plurality of testers for preparing test related data for the functional product to be tested. The historical test task number refers to the task number of testing the functional product to be tested in a historical way.
The number of days for debugging the environment is the number of days for debugging the test environment, which is the total number of days for debugging the test environment for testing the functional product to be tested.
The number of current environmental commissioning days = sum of environmental commissioning days/number of test tasks. The total number of days of environment debugging refers to the total number of days of debugging required when the environment debugging is performed for a plurality of business functions to be tested in the financial system. The test task number refers to the number of business functions to be tested in the financial system.
The number of people in the environment is the number of people in the environment when the environment is debugged for testing the functional product to be tested.
In this embodiment, the test task is subdivided into a test analysis stage, a data preparation stage, a test environment tuning-through stage and a test task execution stage, and fine granularity prediction analysis is performed according to the historical data, so that a test manager can conveniently perform high-precision and fine granularity test management. And on the basis of reducing resource waste, more scientific and lower-cost test resource allocation is realized.
In one embodiment, tester recommendations may also be made before the case is executed. And the recommended testers determine according to the scores of the product test database, and recommend the highest score preferentially.
Fig. 4 is a schematic structural diagram of a testing device for functional products according to an embodiment of the present application, as shown in fig. 4, in which the testing device 40 for functional products according to the embodiment is located in a server, the testing device 40 for functional products according to the embodiment includes:
a test instruction acquisition module 41, configured to acquire a test analysis instruction, where the test analysis instruction includes an identifier of a functional product to be tested; wherein the functional product to be tested is a functional product of a target business system;
a deployment state determining module 42, configured to determine, based on the identifier of the functional product to be tested, a latest deployment state of each functional product including the functional product to be tested in the target service system; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present;
a testability determination module 43, configured to determine whether the functional product to be tested can be tested currently based on the latest deployment status of each functional product;
and the test result obtaining module 44 is configured to perform a case test on the functional product to be tested to obtain a test result if it is determined that the functional product to be tested can be tested currently.
Optionally, the testing device 40 for functional products further includes a link data determining module, before determining, based on the identifier of the functional product to be tested, a latest deployment state of each functional product including the functional product to be tested in the target service system, the link data determining module is configured to: determining target product link data of the functional product to be tested based on the identification of the functional product to be tested; the target product link data comprises identifiers of a plurality of functional products in the target service system and an upstream-downstream relation when the functional products are subjected to data circulation.
Accordingly, the deployment state determining module 42 is specifically configured to, when determining, based on the identifier of the functional product to be tested, the latest deployment state of each functional product including the functional product to be tested in the target service system:
searching in a product state database based on the identification of each functional product in the target product link data to determine the latest deployment state of each functional product including the functional product to be tested in the target service system; the product state database stores the identifiers of the functional products of the plurality of product link data and the corresponding latest deployment states.
Optionally, the testability determination module 43 is specifically configured to, when determining whether the functional product to be tested can be tested currently based on the latest deployment status of each functional product:
judging whether the latest deployment state of each functional product is in a state that the corresponding product version is deployed;
if the functional products are determined to be in the state of being deployed with the corresponding product versions, determining that the functional products to be tested can be tested currently;
or alternatively, the process may be performed,
and if the latest deployment state of at least one functional product is determined to be a state which is not in a state where the corresponding product version is deployed, outputting an indication message to indicate that the functional product to be tested cannot be tested currently.
Optionally, the deployment status determining module 42 is further configured to, before storing the latest deployment status of each of the functional products in the product status database: sending detection data packets to deployment interfaces of all functional products in a target test environment through a state detection tool; the target test environment is a test environment where each functional product in the target service system is located;
for each functional product in the functional products, if a return signal of a deployment interface of the functional product is received, determining that the latest deployment state of the functional product is in a state in which a corresponding product version is deployed;
If the return signal of the deployment interface of the functional product is not received, determining that the latest deployment state of the functional product is not in a state in which the corresponding product version is already deployed.
Optionally, the test result obtaining module 44 is specifically configured to, when performing a case test on the functional product to be tested to obtain a test result: obtaining test data; taking the test data as input, and executing case test on the functional product to be tested through a pre-constructed automatic test script to obtain a test output result; and obtaining a test result according to the test output result and the expected output result.
Optionally, the test result includes: whether the function to be tested has a code bug or not, and information of the code bug when the code bug exists.
Fig. 5 is a block diagram of a server, which may be as shown in fig. 5, according to an exemplary embodiment, including: a memory 51, a processor 52 and a transceiver 54; memory 51 is a memory for storing processor-executable instructions; the processor 52 is operative to execute computer programs or instructions to implement the method of testing a functional product as provided in any of the embodiments above.
The memory 51 is used for storing programs. In particular, the program may include program code including computer-operating instructions. The memory 51 may comprise a high-speed RAM memory or may further comprise a non-volatile memory (non-volatile memory), such as at least one disk memory.
The processor 52 may be a central processing unit (Central Processing Unit, abbreviated as CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure.
The transceiver is used for transmitting instructions and data.
Alternatively, in a specific implementation, if the memory 51, the processor 52 and the transceiver 54 are implemented independently, the memory 51, the processor 52 and the transceiver 54 may be connected to each other and communicate with each other through the bus 53. The bus 53 may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus 53, an external device interconnect (Peripheral Component, abbreviated PCI) bus 53, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus 53, among others. The bus 53 may be classified into an address bus 53, a data bus 53, a control bus 53, and the like. For ease of illustration, only one thick line is shown in fig. 5, but not only one bus 53 or one type of bus 53.
Alternatively, in a specific implementation, if the memory 51, the processor 52 and the transceiver 54 are implemented on a single chip, the memory 51, the processor 52 and the transceiver 54 may perform the same communication through an internal interface.
A non-transitory computer readable storage medium, which when executed by a processor of a server, causes the server to perform the method of testing a functional product as described above.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims (12)

1. A method of testing a functional product, the method comprising:
acquiring a test analysis instruction, wherein the test analysis instruction comprises an identifier of a functional product to be tested; wherein the functional product to be tested is a functional product of a target business system;
determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present;
judging whether the functional product to be tested can be tested currently or not based on the latest deployment state of each functional product;
and if the functional product to be tested can be tested currently, performing case test on the functional product to be tested to obtain a test result.
2. The method of claim 1, wherein prior to determining the most recent deployment status of each functional product in the target business system, including the functional product to be tested, based on the identification of the functional product to be tested, the method further comprises:
Determining target product link data of the functional product to be tested based on the identification of the functional product to be tested; the target product link data comprises identifiers of a plurality of functional products in the target service system and an upstream-downstream relation when the functional products are subjected to data circulation;
determining, based on the identification of the functional product to be tested, a latest deployment state of each functional product including the functional product to be tested in the target service system, including:
searching in a product state database based on the identification of each functional product in the target product link data to determine the latest deployment state of each functional product including the functional product to be tested in the target service system; the product state database stores the identifiers of the functional products of the plurality of product link data and the corresponding latest deployment states.
3. The method of claim 2, wherein determining whether the functional product to be tested is currently able to be tested based on the latest deployment status of each of the functional products comprises:
Judging whether the latest deployment state of each functional product is in a state that the corresponding product version is deployed;
if the functional products are determined to be in the state of being deployed with the corresponding product versions, determining that the functional products to be tested can be tested currently;
or alternatively, the process may be performed,
and if the latest deployment state of at least one functional product is determined to be a state which is not in a state where the corresponding product version is deployed, outputting an indication message to indicate that the functional product to be tested cannot be tested currently.
4. The method of claim 2, wherein prior to storing the most recent deployment status for each of the functional products in the product status database, the method further comprises:
sending detection data packets to deployment interfaces of all functional products in a target test environment through a state detection tool; the target test environment is a test environment where each functional product in the target service system is located;
for each functional product in the functional products, if a return signal of a deployment interface of the functional product is received, determining that the latest deployment state of the functional product is in a state in which a corresponding product version is deployed;
If the return signal of the deployment interface of the functional product is not received, determining that the latest deployment state of the functional product is not in a state in which the corresponding product version is already deployed.
5. The method of claim 1, wherein performing a case test on the functional product to be tested to obtain test results comprises:
obtaining test data;
taking the test data as input, and executing case test on the functional product to be tested through a pre-constructed automatic test script to obtain a test output result;
and obtaining a test result according to the test output result and the expected output result.
6. The method of any one of claims 1-5, wherein the test results comprise: whether the function to be tested has a code bug or not, and information of the code bug when the code bug exists.
7. A device for testing a functional product, the device comprising:
the test instruction acquisition module is used for acquiring a test analysis instruction, wherein the test analysis instruction comprises an identifier of a functional product to be tested; wherein the functional product to be tested is a functional product of a target business system;
The deployment state determining module is used for determining the latest deployment state of each functional product including the functional product to be tested in the target service system based on the identification of the functional product to be tested; the latest deployment state of the functional product refers to whether the functional product is in a state of being deployed with a corresponding product version at present;
the testability judging module is used for judging whether the functional product to be tested can be tested currently or not based on the latest deployment state of each functional product;
and the test result acquisition module is used for executing case test on the functional product to be tested if the functional product to be tested can be tested currently, so as to obtain a test result.
8. The apparatus of claim 7, further configured to, prior to said determining, based on the identity of the functional product to be tested, a most recent deployment status of each functional product in the target business system including the functional product to be tested: determining target product link data of the functional product to be tested based on the identification of the functional product to be tested; the target product link data comprises identifiers of a plurality of functional products in the target service system and an upstream-downstream relation when the functional products are subjected to data circulation;
The deployment state determining module is specifically configured to, when determining, based on the identifier of the functional product to be tested, a latest deployment state of each functional product including the functional product to be tested in the target service system: searching in a product state database based on the identification of each functional product in the target product link data to determine the latest deployment state of each functional product including the functional product to be tested in the target service system; the product state database stores the identifiers of the functional products of the plurality of product link data and the corresponding latest deployment states.
9. The apparatus of claim 8, wherein the testability determination module, when determining whether the functional product to be tested is currently possible based on the latest deployment status of each of the functional products, is specifically configured to:
judging whether the latest deployment state of each functional product is in a state that the corresponding product version is deployed;
if the functional products are determined to be in the state of being deployed with the corresponding product versions, determining that the functional products to be tested can be tested currently;
Or alternatively, the process may be performed,
and if the latest deployment state of at least one functional product is determined to be a state which is not in a state where the corresponding product version is deployed, outputting an indication message to indicate that the functional product to be tested cannot be tested currently.
10. A server, comprising: a processor, a transceiver, and a memory communicatively coupled to the processor;
the transceiver is used for transmitting instructions and data;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1-6.
11. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1-6.
12. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-6.
CN202310632645.6A 2023-05-30 2023-05-30 Method and device for testing functional product and storage medium Pending CN116680177A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310632645.6A CN116680177A (en) 2023-05-30 2023-05-30 Method and device for testing functional product and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310632645.6A CN116680177A (en) 2023-05-30 2023-05-30 Method and device for testing functional product and storage medium

Publications (1)

Publication Number Publication Date
CN116680177A true CN116680177A (en) 2023-09-01

Family

ID=87783005

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310632645.6A Pending CN116680177A (en) 2023-05-30 2023-05-30 Method and device for testing functional product and storage medium

Country Status (1)

Country Link
CN (1) CN116680177A (en)

Similar Documents

Publication Publication Date Title
CN107145437B (en) Java annotation test method and device
CN106506283B (en) Business test method and device of bank and enterprise docking system
CN109634843A (en) A kind of distributed automatization method for testing software and platform towards AI chip platform
CN110058920B (en) Virtual machine performance detection method and device, electronic equipment and storage medium
CN110532185B (en) Test method, test device, electronic equipment and computer readable storage medium
CN111897724A (en) Automatic testing method and device suitable for cloud platform
CN108009085B (en) Channel package testing method
CN109558313B (en) Method and device for constructing abnormal test scene
CN115391228A (en) Precise test method, device, equipment and medium
CN111708712A (en) User behavior test case generation method, flow playback method and electronic equipment
CN112395182A (en) Automatic testing method, device, equipment and computer readable storage medium
CN116627849B (en) System test method, device, equipment and storage medium
CN117493188A (en) Interface testing method and device, electronic equipment and storage medium
CN112084108A (en) Test script generation method and device and related components
CN116431522A (en) Automatic test method and system for low-code object storage gateway
CN116680177A (en) Method and device for testing functional product and storage medium
CN114064510A (en) Function testing method and device, electronic equipment and storage medium
CN110618943B (en) Security service test method and device, electronic equipment and readable storage medium
CN113656314A (en) Pressure test processing method and device
US11816022B2 (en) Snapshot simulation of service module responses
CN112199281A (en) Data processing method and device, terminal equipment and readable storage medium
CN111597101A (en) SDK access state detection method, computer device and computer readable storage medium
CN116401113B (en) Environment verification method, device and medium for heterogeneous many-core architecture acceleration card
KR20200000684A (en) Test unified administration system and Controlling Method for the Same
CN110597736B (en) Test data generation method and device

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