A product testing method, device, equipment and medium

Abstract

The embodiments of this specification disclose a product testing method, apparatus, equipment and medium. The product testing method includes: obtaining a product requirement file, determining requirement description data and a product prototype page according to the product requirement information, and sending the requirement description data and the product prototype page to a terminal; obtaining a product test file, determining a product test code and product description data according to the product test file; running the product test code to generate a product test page, and determining a correspondence between the product prototype page and the product test page according to the requirement description data and the product description data; verifying each product prototype page with the corresponding product test page according to the correspondence to determine a test result.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a product testing method, device, equipment and medium. Background Art

[0002] In the prior art, after a product is developed, it is necessary to manually test the developed product to determine whether the developed product meets the requirements. Since a single product often corresponds to multiple requirements, it takes a lot of time to manually test each requirement separately, and there may be omissions, low test efficiency, and poor test results.

[0003] In light of this, more effective and efficient product testing methods are needed. Summary of the invention

[0004] The embodiments of this specification provide a product testing method, device, equipment and medium to solve the technical problem of how to perform product testing more effectively and efficiently.

[0005] To solve the above technical problems, the embodiments of this specification provide the following technical solutions:

[0006] The present invention provides a product testing method, including:

[0007] Acquire a product requirement document, determine requirement description data and a product prototype page according to the product requirement information, and send the requirement description data and the product prototype page to the terminal;

[0008] Obtain a product test file, and determine a product test code and product description data according to the product test file;

[0009] Running the product test code to generate a product test page, and determining a corresponding relationship between the product prototype page and the product test page according to the requirement description data and the product description data;

[0010] Each product prototype page is verified with the corresponding product test page according to the corresponding relationship to determine the test result.

[0011] The present invention provides a product testing device, including:

[0012] A product requirement module, used to obtain a product requirement document, determine requirement description data and a product prototype page according to the product requirement information, and send the requirement description data and the product prototype page to the terminal;

[0013] A product acquisition module, used to acquire a product test file, and determine a product test code and product description data according to the product test file;

[0014] The product testing module is used to run the product testing code, generate a product testing page, and determine the correspondence between the product prototype page and the product testing page according to the requirement description data and the product description data; and verify each product prototype page with the corresponding product testing page according to the correspondence to determine the test result.

[0015] The present invention provides a product testing device, including:

[0016] at least one processor;

[0017] as well as,

[0018] a memory communicatively coupled to the at least one processor;

[0019] in,

[0020] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to execute the above-mentioned product testing method.

[0021] An embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the above-mentioned product testing method is implemented.

[0022] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:

[0023] Through the above technical solution, the device can automatically test the product and can accurately test each page, thereby improving the product testing effect and efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments of this specification or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0025] Figure 1 It is a schematic diagram of the execution body of the product testing method in the first embodiment of this specification.

[0026] Figure 2 It is a flowchart of the product testing method in the first embodiment of this specification.

[0027] Figure 3 It is a schematic diagram of the page structure in the first embodiment of this specification.

[0028] Figure 4 It is a structural schematic diagram of a product testing device in the second embodiment of this specification. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0030] In the prior art, various products (products generally refer to applications) are developed to meet business needs. For example, e-commerce products are developed to meet e-commerce business needs; instant messaging products are developed to meet social business needs. Before the developed product is actually put online, it is generally necessary to test the product to determine whether the developed product meets the needs.

[0031] At present, developed products are generally tested manually, that is, testers perform various operations on developed products to determine whether the products meet the requirements. However, in the prior art, a single product often bears multiple business requirements. For example, a product must have both social functions and e-commerce functions, so it is necessary to manually test the various requirements corresponding to a single product separately, which takes a lot of time and may result in test omissions, low test efficiency, and poor test results.

[0032] The first embodiment of this specification (hereinafter referred to as "this embodiment") provides a test method. The execution subject of this embodiment can be a terminal (including but not limited to a mobile phone, computer, pad, TV) or a server or an operating system or a test platform or a test system or an application, etc., that is, the execution subject can be various and can be set, used or changed as needed. In addition, there can also be a third-party application to assist the execution subject in executing this embodiment. For example Figure 1 As shown, the test method in this embodiment can be executed by a server, and an application corresponding to the server can be installed on a terminal (held by the user). Data can be transmitted between the terminal or the application and the server, and data can be collected, input or output, or pages or information processing can be performed (to the user) through the terminal or the application, thereby assisting the server in executing the test method in this embodiment.

[0033] like Figure 2 As shown, the product testing method provided in Example 1 includes:

[0034] S101: (Executing entity) obtains a product requirement document, determines requirement description data and a product prototype page according to the product requirement information, and sends the requirement description data and the product prototype page to a terminal;

[0035] In Embodiment 1, the execution subject may obtain a product requirement document. There are many ways for the execution subject to obtain the product requirement document, for example, the product requirement document may be manually transferred to the execution subject through an operation terminal or application, or the execution subject may grab the product requirement document from the terminal or application by itself. Embodiment 1 does not limit how the execution subject obtains the product requirement document. The product requirement document may be in a format readable by the execution subject, such as a document format, or the execution subject may convert the format of the product requirement document in order to read the product requirement document. Embodiment 1 does not limit the format or form of the product requirement document.

[0036] The execution entity of Example 1 can determine the requirement description data based on the product requirement file. For example, the requirement description data can have a specific format, so that the execution entity can extract the requirement description data from the product requirement file; or the requirement description data can be a separate file in the product requirement file, so that the execution entity can identify the requirement description data from the product requirement file (including but not limited to identification through the file suffix).

[0037] The product requirement description data can be used to define the function and / or jump logic and / or structure of the product. The product that is expected to be produced and meets the product requirement description data is referred to as the target product below. Since the target product is generally an application, and the application includes one or more pages, the product requirement description data can be used to define the function and / or jump logic (the jump logic of the page can refer to the jump relationship between pages, the same below) and / or structure (the following structure can refer to the following component structure or component style, the same below) of each page of the target product.

[0038] In the first embodiment, the execution subject can also determine the product prototype page according to the product demand information, and the function of the product prototype page is to provide a reference for the page of the target product. Generally speaking, the product prototype page is relatively rough or simple compared to the actual product page. For example, if the structure of a certain (a certain means any one, the same below) page to be generated is a three-column structure of pictures, charts, and menus, then the product prototype page does not need to actually display these structures. It can just use characters (such as text) at the corresponding position to indicate the structure that should be here, for example Figure 3 shown.

[0039] As described above, the product requirement description data is used to define the function and / or jump logic and / or structure of each page of the target product, and the product prototype page is the reference prototype corresponding to the target product page defined by the product requirement description data. Therefore, the product prototype page and the requirement description data correspond to each other, and the requirement description data also defines the function and / or jump logic and / or structure of each product prototype page. Specifically, the requirement description data may include the function data of the product prototype page, which is used to define the function of each product prototype page; and / or, the requirement description data may include the jump logic data of the product prototype page, which is used to define the jump logic of each product prototype page; and / or, the requirement description data may include the structure data of the product prototype page, which is used to define the structure of each product prototype page.

[0040] In the first embodiment, the number of pages included in the target product can be defined in the requirement description data, and the number of product prototype pages can be the same as or different from the number of pages defined in the requirement description data. Generally speaking, if the number of product prototype pages is the same as the number of pages defined in the requirement description data, it means that for each page of the target product defined in the requirement description data, there is a corresponding product prototype page as a reference; if the number of product prototype pages is less than the number of pages defined in the requirement description data, it means that among the target product pages defined in the requirement description data, only some pages have corresponding product prototype pages as references; if the number of product prototype pages is more than the number of pages defined in the requirement description data, it means that among the target product pages defined in the requirement description data, at least one target product page has multiple corresponding product prototype pages as references.

[0041] Assume that the target product is an instant messaging application, and the target product has m product prototype pages (the product prototype pages may have serial numbers). The corresponding relationship between the requirement description data and the product prototype pages may be as shown in Table 1 (Table 1 is only an example):

[0042]

[0043] Table 1

[0044] In the first embodiment, the execution subject determines the requirement description data and the product prototype page corresponding to the requirement description data, and can send the requirement description data and the product prototype page to a (preset or specified) terminal. The terminal can be a terminal owned by a developer, or an application for product development can be installed on the terminal, and the application can interact with the execution subject of the first embodiment. In the first embodiment, sending data to an application installed on a terminal is regarded as sending data to the terminal.

[0045] The terminal or application obtains the demand description data and product prototype page sent by the execution subject of the first embodiment, and can display the demand description data and product prototype page obtained (in an appropriate form). The demand description data and product prototype page assist and refer to each other and provide guidance for the development of the target product.

[0046] S103: (Executing entity) obtains a product test file, and determines a product test code and product description data according to the product test file;

[0047] In an actual scenario, the terminal can display the demand description data and product prototype page sent to it by the executive body of Example 1, and the user or developer develops the product according to the guidance of the demand description data and / or the product prototype page. Generally speaking, after a new product is developed, it is necessary to test the new product, and it will not be operated or released online or actually used until the test passes. The products that need to be tested are referred to as test products below. In Example 1, the test product is a product developed based on the demand description data and / or the product prototype page.

[0048] After the test product is generated, the user or developer can send the test product to the execution entity of Example 1 by operating the terminal or application, or the execution entity of Example 1 can grab the test product from the terminal or application by itself. Example 1 does not limit how the execution entity obtains the test product.

[0049] In the first embodiment, the test product may be transmitted in the form of a file and acquired by the execution subject of the first embodiment. The file may be called a product test file.

[0050] The product test file may include a code for testing a product (hereinafter referred to as a product test code). The execution subject of the first embodiment may generate a test product by running the product test code.

[0051] The execution subject of the first embodiment can determine the product description data according to the product test file, and the product description data can be used to define the function and / or jump logic and / or structure of the test product. The product description data can have a specific format, so that the execution subject can extract the product description data from the product test file; or the product description data can be a separate file in the product test file, so that the execution subject can identify the product description data from the product test file (including but not limited to identifying by the file suffix name).

[0052] The test product is generally an application, which includes one or more pages to be tested. Each page to be tested of the test product can be called a product test page, so that the product description data can be used to define the function and / or jump logic and / or structure of each product test page of the test product.

[0053] Since the execution subject of the first embodiment can generate a test product through the product test code in the product test file and determine the function and / or jump logic and / or structure of the test product through the product description data in the product test file, the product test file can represent the test product.

[0054] S105: (Executing body) running the product test code to generate a product test page, and determining the correspondence between the product prototype page and the product test page according to the requirement description data and the product description data;

[0055] As described above, the execution subject of Example 1 can generate a test product by running the product test code, and the test product includes one or more product test pages. Therefore, the execution subject of Example 1 runs the product test code, which is equivalent to generating the one or more product test pages. As mentioned above, the product description data can be used to define the function and / or jump logic and / or structure of each product test page of the test product, so that the product test page and the product description data correspond. Specifically, the product description data may include functional data of the product test page, which is used to define the function of each product test page; and / or, the product description data may include jump logic data of the product test page, which is used to define the jump logic of each product test page; and / or, the product description data may include structural data of the product test page, which is used to define the structure of each product test page.

[0056] Assuming that the test product is an instant messaging application, the execution subject of the first embodiment runs the product test code to generate n product test pages (the product test pages may have serial numbers), and the corresponding relationship between the product description data and the product test pages may be as shown in Table 2 (Table 2 is only an example):

[0057]

[0058] Table 2

[0059] After the execution subject of the first embodiment generates the product test page, since the product description data corresponds to the product test page, and the requirement description data corresponds to the product prototype page, the execution subject of the first embodiment can determine the corresponding relationship between the product prototype page and the product test page according to the requirement description data and the product description data. Specifically, the requirement description data defines the function and / or jump logic and / or structure of each product prototype page, and the product description data defines the function and / or jump logic and / or structure of each product test page, so the execution subject of the first embodiment can determine the corresponding relationship between the product prototype page and the product test page according to the keywords of the requirement description data and the product description data. For example, the requirement description data defines a product prototype page as a home page, and the product description data defines a product test page as the home page, then the product prototype page defined as the home page and the product test page defined as the home page correspond to each other; for another example, the requirement description data defines a product prototype page as a payment page, and the product description data defines a product test page as a payment page, then the product prototype page defined as the payment page and the product test page defined as the payment page correspond to each other; for another example, the requirement description data defines a product prototype page as the first secondary page to be jumped from the home page, and the product description data defines a product test page as the first secondary page to be jumped from the home page, then the product prototype page defined as the first secondary page to be jumped from the home page and the product test page defined as the first secondary page to be jumped from the home page correspond to each other.

[0060] S107: (Executing entity) Verify each product prototype page with the corresponding product test page according to the corresponding relationship to determine the test result.

[0061] In the first embodiment, after the correspondence between the product prototype page and the product test page is determined, the execution subject of the first embodiment can verify each product prototype page with the corresponding product test page according to the correspondence between the product prototype page and the product test page. The verification includes but is not limited to functional verification and / or jump logic verification and / or structural verification, which are described below respectively:

[0062] 1.1 Functional verification

[0063] In the first embodiment, verifying each product prototype page with the corresponding product test page according to the corresponding relationship may include: performing a functional verification on each product prototype page with the corresponding product test page according to the corresponding relationship. That is, for any product test page, performing a functional verification on the product test page and the corresponding product prototype page.

[0064] Functional verification can be divided into two stages. The first stage is to verify whether the function of the product test page is the same as the function of its corresponding product prototype page. If so, the first stage verification of the product test page passes. If not, the functional verification of the product test page fails.

[0065] The second stage is to verify whether the product test page can achieve the functional effect of its corresponding product prototype page; if so, the functional verification of the product test page passes; if not, the functional verification of the product test page fails. In actual scenarios, only the first or second stage functional verification can be performed.

[0066] For example, according to the product description data, a certain product test page has a payment function; according to the demand description data, the product prototype page corresponding to the product test page has a payment function, then the product test page and the product prototype page corresponding to the product test page can be subjected to payment tests respectively (for example, the execution subject of the first embodiment can simulate clicks on the product test page and the corresponding product prototype page of the test product respectively to perform payment verification or payment testing), thereby performing payment function verification on the product test page and the corresponding product prototype page. If the product test page can achieve the payment effect of the corresponding product prototype page, the functional verification of the product test page passes; if the product test page cannot achieve the payment effect of the corresponding product prototype page, the functional verification of the product test page fails.

[0067] 1.2. Jump logic check

[0068] In the first embodiment, verifying each product prototype page with the corresponding product test page according to the corresponding relationship may include: performing a jump logic check on each product prototype page with the corresponding product test page according to the corresponding relationship. That is, for any product test page, a jump logic check is performed on the product test page and the product prototype page corresponding thereto. If the product test page can achieve the jump effect of the corresponding product prototype page, the jump logic check of the product test page passes; if the product test page cannot achieve the jump effect of the corresponding product prototype page, the jump logic check of the product test page fails.

[0069] For example, according to the product description data, the product test page a can jump to another page b with a payment function, and according to the demand description data, the product prototype page a' corresponding to the product test page a can jump to another page b' with a payment function. Then, the product test page a and the product prototype page a' corresponding to the product test page can be subjected to jump tests respectively (for example, the execution subject of the first embodiment can simulate clicks on the product test page and the corresponding product prototype page of the test product respectively to perform jump verification or jump testing), thereby performing jump logic verification on the product test page a and the corresponding product prototype page a'. If the product test page a can achieve the jump effect of the corresponding product prototype page a', the jump logic verification of the product test page a passes; if the product test page a cannot achieve the jump effect of the corresponding product prototype page a', the jump logic verification of the product test page a fails.

[0070] 1.3. Structural verification

[0071] In the first embodiment, verifying each product prototype page with the corresponding product test page according to the corresponding relationship may include: performing a structural verification on each product prototype page with the corresponding product test page according to the corresponding relationship. That is, for any product test page, a structural verification is performed on the product test page and the corresponding product prototype page. If the product test page has the structure or style of the corresponding product prototype page, the structural verification of the product test page passes; if the product test page does not have the structure or style of the corresponding product prototype page, the structural verification of the product test page fails.

[0072] For example, according to the product description data, a product test page has a three-column structure, with pictures in the upper column, charts in the middle column, and a menu in the lower column; according to the requirement description data, the product prototype page corresponding to the product test page has a three-column structure, with pictures in the upper column, charts in the middle column, and a menu in the lower column. If the product test page has the same structure as its corresponding product prototype page, the structural verification of the product test page passes; if the product test page has a different structure from its corresponding product prototype page, the structural verification of the product test page fails.

[0073] In the first embodiment, each product prototype page is verified with the corresponding product test page according to the corresponding relationship, and the execution subject of the first embodiment can determine the verification result, which is the test result of the product test page or the test product. If the verification of each product prototype page with the corresponding product test page passes, the test result can indicate that each product test page has passed the test or the test product has passed the test.

[0074] If one or more product test pages fail the functional verification (failed verification means failed test, the same below), the test result is used to indicate the product test page that failed the functional verification, and the test result is also used to indicate the functional description information corresponding to the product test page that failed the functional verification. For example, if a product test page fails the functional verification, the test result is used to indicate that the product test page fails the functional verification, and the test result is also used to indicate the functional description information corresponding to the product test page, and the functional description information includes the expected functional description of the product test page (the expected functional description is the description of the expected function), and the functional description information may also include a functional error description of the product test page. Since the expected functional effect of the product test page is the functional effect of the product prototype page corresponding to the product test page, the expected function of the product test page is the function of the product prototype page corresponding to the product test page, and the expected functional description of the product test page is the functional data of "the product prototype page corresponding to the product test page" contained in the requirement description data.

[0075] If one or more product test pages fail the jump logic check, the test result is used to indicate the product test pages that fail the jump logic check, and the test result is also used to indicate the jump logic description information corresponding to the product test page that fails the jump logic check. For example, if a product test page fails the jump logic check, the test result is used to indicate that the product test page fails the jump logic check, and the test result is also used to indicate the jump logic description information corresponding to the product test page, and the jump logic description information includes the expected jump logic description of the product test page (the expected jump logic description is the description of the expected jump logic), and the jump logic description information may also include the jump logic error description of the product test page. Since the expected jump effect of the product test page is the jump effect of the product prototype page corresponding to the product test page, the expected jump logic of the product test page is the jump logic of the product prototype page corresponding to the product test page, and the expected jump logic description of the product test page is the jump logic data of "the product prototype page corresponding to the product test page" contained in the demand description data.

[0076] If one or more product test pages fail the structural verification, the test result is used to indicate the product test pages that fail the structural verification, and the test result is also used to indicate the structural description information corresponding to the product test page that fails the structural verification. For example, if a product test page fails the structural verification, the test result is used to indicate that the product test page fails the structural verification, and the test result is also used to indicate the structural description information corresponding to the product test page, and the functional description information includes the expected structural description of the product test page (the expected structural description is the description of the expected structure), and the functional description information may also include a structural error description of the product test page. Since the expected structure of the product test page is the structure of the product prototype page corresponding to the product test page, the expected structural description of the product test page is the structural data of "the product prototype page corresponding to the product test page" contained in the requirement description data.

[0077] When verifying the product test page, the test product is still in the form of an application, and the product test page is tested or verified as a page of the test product. After the execution subject of the first embodiment determines the test result, the test result can be sent to the terminal or application so that the user can view or understand the test result through the terminal or application, and modify the product test page that fails the verification.

[0078] The terminals recorded in the above different places may be the same or different terminals, and the applications recorded in the above different places may be the same or different applications.

[0079] In Example 1, the execution entity can determine the correspondence between the product prototype page and the product test page according to the demand description data and the product description data, and automatically verify each product prototype page with the corresponding product test page according to the correspondence, thereby improving product testing efficiency; in Example 1, each page can be tested accurately, thereby improving product testing results; in Example 1, the function and / or jump logic and / or structure of each page can be performed to ensure the comprehensiveness of the test, thereby improving the test effect and efficiency; in Example 1, the expected function and / or jump logic and / or structure and error description can be performed on the page that fails the test, so that users can accurately understand the function and / or jump logic and / or structure and error points that the page that fails the test should have, thereby improving product development efficiency and results.

[0080] like Figure 4 As shown, the second embodiment of this specification provides a product testing device, including:

[0081] The product requirement module 202 is used to obtain a product requirement document, determine requirement description data and a product prototype page according to the product requirement information, and send the requirement description data and the product prototype page to the terminal;

[0082] A product acquisition module 204, used to acquire a product test file, and determine a product test code and product description data according to the product test file;

[0083] The product testing module 206 is used to run the product testing code, generate a product testing page, and determine the correspondence between the product prototype page and the product testing page according to the requirement description data and the product description data; and verify each product prototype page with the corresponding product testing page according to the correspondence to determine the test result.

[0084] Optionally, the demand description data includes functional data of the product prototype page; and verifying each product prototype page with a corresponding product test page according to the corresponding relationship includes:

[0085] Function verification is performed on each product prototype page and the corresponding product test page according to the corresponding relationship.

[0086] Optionally, if one or more product test pages fail the functional verification, the test result is used to indicate the product test pages that fail the functional verification, and the test result is also used to indicate the functional description information corresponding to the product test pages that fail the functional verification.

[0087] Optionally, the demand description data includes jump logic data of the product prototype page; and verifying each product prototype page with a corresponding product test page according to the corresponding relationship includes:

[0088] A jump logic check is performed on each product prototype page and the corresponding product test page according to the corresponding relationship.

[0089] Optionally, if one or more product test pages fail the jump logic check, the test result is used to indicate the product test page that fails the jump logic check, and the test result is also used to indicate the jump logic description information corresponding to the product test page that fails the jump logic check.

[0090] Optionally, the demand description data includes structural data of the product prototype page; and verifying each product prototype page with a corresponding product test page according to the corresponding relationship includes:

[0091] A structure check is performed on each product prototype page and the corresponding product test page according to the corresponding relationship.

[0092] Optionally, if one or more product test pages fail the structural verification, the test result is used to indicate the product test pages that failed the structural verification, and the test result is also used to indicate the structural description information corresponding to the product test pages that failed the structural verification.

[0093] The third embodiment of this specification provides a product testing device, including:

[0094] at least one processor;

[0095] as well as,

[0096] a memory communicatively coupled to the at least one processor;

[0097] in,

[0098] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor, so that the at least one processor can execute the product testing method described in the first embodiment.

[0099] A fourth embodiment of the present specification provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the product testing method described in the first embodiment is implemented.

[0100] The above embodiments may be used in combination, and modules with the same name between different embodiments or within the same embodiment may be the same or different modules.

[0101] The above describes specific embodiments of the present specification, and other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily have to be performed in the specific order or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0102] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer-readable storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0103] The apparatus, device, non-volatile computer-readable storage medium and method provided in the embodiments of this specification correspond to each other, and therefore, the apparatus, device, and non-volatile computer storage medium also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the corresponding apparatus, device, and non-volatile computer storage medium will not be repeated here.

[0104] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0105] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0106] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0107] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0108] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may be in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0109] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0110] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0111] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0112] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0113] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0114] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0115] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0116] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0117] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0118] The above is only an embodiment of this specification and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A product testing method, comprising: Obtain a product requirement document, determine requirement description data and a product prototype page according to the product requirement information, and send the requirement description data and the product prototype page to the terminal; Acquire a product test file, and determine a product test code and product description data according to the product test file; the product description data defines the function and / or jump logic and / or structure of each product test page; Running the product test code to generate a product test page, and determining the correspondence between the product prototype page and the product test page according to the demand description data and the product description data; the product test page is each page to be tested of the test product; Each product prototype page is verified with the corresponding product test page according to the corresponding relationship to determine the test result.

2. The method according to claim 1, wherein the demand description data includes functional data of the product prototype page; and verifying each product prototype page with the corresponding product test page according to the corresponding relationship comprises: Function verification is performed on each product prototype page and the corresponding product test page according to the corresponding relationship.

3. According to the method as claimed in claim 2, if one or more product test pages fail the functional verification, the test result is used to indicate the product test page that fails the functional verification, and the test result is also used to indicate the functional description information corresponding to the product test page that fails the functional verification.

4. The method according to claim 1, wherein the demand description data includes jump logic data of the product prototype page; and verifying each product prototype page with the corresponding product test page according to the corresponding relationship comprises: A jump logic check is performed on each product prototype page and the corresponding product test page according to the corresponding relationship.

5. According to the method as described in claim 4, if one or more product test pages fail the jump logic check, the test result is used to indicate the product test page that fails the jump logic check, and the test result is also used to indicate the jump logic description information corresponding to the product test page that fails the jump logic check.

6. The method according to claim 1, wherein the demand description data includes structural data of the product prototype page; and verifying each product prototype page with the corresponding product test page according to the corresponding relationship comprises: A structure check is performed on each product prototype page and the corresponding product test page according to the corresponding relationship.

7. According to the method as claimed in claim 6, if one or more product test pages fail the structural verification, the test result is used to indicate the product test pages that fail the structural verification, and the test result is also used to indicate the structural description information corresponding to the product test pages that fail the structural verification.

8. A product testing device, comprising: A product requirement module, used to obtain a product requirement document, determine requirement description data and a product prototype page according to the product requirement information, and send the requirement description data and the product prototype page to the terminal; A product acquisition module, used to acquire a product test file, and determine a product test code and product description data according to the product test file; the product description data defines the function and / or jump logic and / or structure of each product test page; A product testing module is used to run the product testing code, generate a product testing page, and determine the correspondence between the product prototype page and the product testing page according to the requirement description data and the product description data; and verify each product prototype page with the corresponding product testing page according to the correspondence to determine the test result; the product testing page is each page to be tested of the test product.

9. A product testing device comprising: at least one processor; as well as, a memory communicatively coupled to the at least one processor; in, The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to perform the product testing method according to any one of claims 1 to 7. 10 . A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are executed by a processor to implement the product testing method according to claim 1 .

Images