Test item management method, device, equipment, storage medium and program product

Abstract

This disclosure provides a test project management method applicable to the fintech field or other fields. The method includes: acquiring requirement items; configuring a test project for a requirement item when its testing unit meets preset conditions, wherein each test project includes at least one requirement item, and the requirement items within the same test project have the same version information and the same project number; when at least one requirement item in the test project changes, collecting the content of the change and the number of requirement items involved in the change within the test project; and adjusting the test project based on the content of the change and the number of requirement items involved. This disclosure also provides a test project management device, equipment, storage medium, and program product. This disclosure enables automatic configuration and adjustment of test projects based on requirement items, improving testing efficiency.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically to a test project management method, apparatus, equipment, storage medium, and program product. Background Technology

[0002] In the internet age, to quickly adapt to business needs, project development processes have gradually shifted from traditional methods to agile development to meet the market demands for rapid product launches. Typically, each project consists of multiple requirements, and each requirement is developed and implemented collaboratively by one or more product applications.

[0003] Currently, during project development, developers can publish task orders through the system management platform. Based on these task orders, and drawing upon their architectural design and experience, developers can create test projects for development and testing. However, creating or adjusting test projects based on task orders requires offline communication between development and testing personnel and the development team, which is inefficient. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a test project management method, apparatus, equipment, storage medium and program product.

[0005] According to a first aspect of this disclosure, a test project management method is provided, comprising:

[0006] Obtain the required items;

[0007] When the test unit of the requirement item meets the preset conditions, a test project is configured for the requirement item. The test project includes at least one requirement item, wherein the version information of the requirement items in the same test project is the same, and the project number of the requirement items in the same test project is the same.

[0008] When at least one of the requirements in the test project changes, the content of the change and the number of the requirements involved in the test project are collected.

[0009] The test items are adjusted based on the content of the changes and the number of the requirements involved.

[0010] According to embodiments of this disclosure, the preset conditions include: the test unit includes a target test unit or the test unit is empty; configuring test items for the requirement item includes:

[0011] Based on the version information and project number of the requirement item, create the test project that includes the requirement item, or assign the requirement item to an existing test project.

[0012] According to embodiments of this disclosure, creating a test project including the requirement item based on the version information and project number of the requirement item, or assigning the requirement item to an existing test project, includes:

[0013] Based on the version information and project number of the aforementioned requirement item, as well as the version information and project number of the existing test project, determine the test project configuration decision;

[0014] Identify the project type of the required item;

[0015] When the project type is a technical project, the test project including the requirement item is created according to the test project configuration decision, or the requirement item is assigned to an existing test project;

[0016] When the project type is a business project, a to-do request is generated and sent to the reviewer;

[0017] In response to the reviewer's feedback on the pending request, the test project including the requirement item is created according to the determined test project configuration decision, or the requirement item is assigned to an existing test project.

[0018] According to embodiments of this disclosure, before determining whether the test unit of the requirement item meets the preset conditions, the test project management method further includes:

[0019] Obtain the creation unit of the aforementioned requirement item;

[0020] When the creation unit includes the target test unit, the step is to create the test project including the requirement item according to the version information and project number of the requirement item, or to assign the requirement item to an existing test project; when the creation unit does not include the target test unit, it is determined whether the test unit of the requirement item meets the preset conditions.

[0021] According to embodiments of this disclosure, the change includes a first change, which includes a change to the version information of the requirement item. Adjusting the test item based on the content of the change and the number of requirement items involved in the change includes:

[0022] When the first change involves all requirements in the test project, the version information of the test project is adjusted to make the version information of the test project consistent with the version information of the requirements after the first change; and / or,

[0023] The change includes a second change, which includes a change to the item number of the requirement item. Adjusting the test item based on the content of the change and the number of requirement items involved in the change includes:

[0024] When the second change involves all requirements in the test project, the project number of the test project is adjusted so that the project number of the test project is consistent with the project number of the requirements after the second change.

[0025] According to embodiments of this disclosure, when the change includes the first change, and the first change involves some of the requirements in the test project, adjusting the test project based on the content of the change and the number of requirements involved in the change further includes: for at least one requirement involved in the first change,

[0026] Remove the aforementioned requirement from the current test project;

[0027] Based on the version information of the requirement item after the first change, configure a test project for the requirement item; and / or,

[0028] When the change includes the second change, and the second change involves some of the requirements in the test project, adjusting the test project according to the content of the change and the number of requirements involved in the change further includes: for at least one requirement involved in the second change,

[0029] Remove the aforementioned requirement from the current test project;

[0030] Configure a test project for the requirement item based on the project number after the second change.

[0031] According to embodiments of this disclosure, the change includes a third change, which includes a change to the test unit of the requirement item. Adjusting the test item based on the content of the change and the number of requirement items involved in the change includes:

[0032] When the third change involves all requirements in the test project, and the test unit after the third change does not meet the preset conditions, the test project is invalidated.

[0033] According to embodiments of this disclosure, the change includes a fourth change, which includes a change to the status of the requirement item. Adjusting the test item based on the content of the change and the number of requirement items involved in the change includes:

[0034] When the fourth change involves some of the requirements in the test project, and the requirements are in an obsolete state after the fourth change, the requirements are deleted from the test project.

[0035] When the fourth change involves all requirements in the test project, and all requirements are in an invalid state after the fourth change, the test project is invalidated.

[0036] A second aspect of this disclosure provides a test project management apparatus, comprising:

[0037] The acquisition module is used to acquire the required items;

[0038] The test project configuration module is used to configure a test project for the requirement item when the test unit of the requirement item meets the preset conditions, wherein the version information of the requirement items in the same test project is the same, and the project number of the requirement items in the same test project is the same.

[0039] The data acquisition module is used to acquire the content of the change and the number of the requirement items involved in the test project when at least one of the requirement items in the test project changes.

[0040] The test item adjustment module is used to adjust the test item according to the content of the change and the number of the requirement items involved in the change.

[0041] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the test item management method described above.

[0042] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the test item management method described above.

[0043] The fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the test item management method described above.

[0044] One or more of the above embodiments have the following beneficial effects:

[0045] This disclosure enables automatic configuration and adjustment of test items based on requirements, eliminating the need for technical personnel to communicate offline with the development center to obtain test scope or change information. This improves testing efficiency and the timeliness of changes, and reduces production-related risks caused by low testing efficiency and untimely changes. Attached Figure Description

[0046] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0047] Figure 1 The illustration schematically depicts application scenarios of a test project management method, apparatus, device, storage medium, and program product according to embodiments of the present disclosure.

[0048] Figure 2 A flowchart illustrating a test project management method according to an embodiment of the present disclosure is shown schematically;

[0049] Figure 3 A flowchart illustrating the configuration test item according to an embodiment of the present disclosure is shown schematically;

[0050] Figure 4 The flowchart illustrating the configuration of a test project according to the version information and project number of the requirement item is shown schematically according to an embodiment of the present disclosure;

[0051] Figure 5 A flowchart illustrating the configuration of test items according to a creation unit is shown schematically according to an embodiment of the present disclosure;

[0052] Figure 6 This schematic diagram illustrates a structural block diagram of a test item management device according to an embodiment of the present disclosure;

[0053] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a test project management method according to an embodiment of the present disclosure. Detailed Implementation

[0054] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0055] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0056] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0057] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0058] It should be noted that the test project management methods, devices, equipment, storage media, and program products disclosed herein can be used in project development and testing in the financial sector, and can also be used in any sector other than the financial sector. The application areas of the test project management methods, devices, equipment, storage media, and program products disclosed herein are not limited.

[0059] Currently, a project is broken down into multiple versions and multiple task orders, with each version corresponding to one or more task orders. However, project requirements are not broken down synchronously with the task orders. Therefore, when the business development center creates or adjusts test projects based on task orders, the test scope of the test project needs to be confirmed offline with the development center separately. This is inefficient and prone to information discrepancies. On the one hand, it may lead to untimely adjustment of the test scope, resulting in insufficient testing. On the other hand, it may lead to the content of the test project not being a complete business function, resulting in the risk that the business cannot be launched after production.

[0060] This disclosure provides a test project management method, comprising: acquiring requirement items; configuring a test project for a requirement item when the test unit of the requirement item meets preset conditions, wherein the test project includes at least one requirement item, wherein the version information of requirement items in the same test project is the same, and the project number of requirement items in the same test project is the same; when at least one requirement item in the test project changes, collecting the content of the change and the number of requirement items involved in the change in the test project; and adjusting the test project according to the content of the change and the number of requirement items involved in the change.

[0061] The test project management method of this disclosure can realize automatic configuration and adjustment of test projects based on requirements. Since the requirements are derived from the breakdown of project requirements, technical personnel no longer need to communicate with the development center offline to obtain the test scope or change content, thereby improving testing efficiency and timeliness of changes, and reducing the risks related to production launch caused by low testing efficiency and untimely changes.

[0062] Figure 1 The illustration schematically depicts application scenarios of the test project management method, apparatus, device, storage medium, and program product according to embodiments of the present disclosure.

[0063] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, network 104, and server 105. Network 104 is used as a medium to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0064] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0065] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0066] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0067] It should be noted that the test project management method provided in this embodiment can generally be executed by server 105. Correspondingly, the test project management device provided in this embodiment can generally be located in server 105. The test project management method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the test project management device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0068] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0069] The following will be based on Figure 1 The described scene, through Figures 2-5 The test project management method of the disclosed embodiments is described in detail.

[0070] Figure 2 A flowchart illustrating a test project management method according to an embodiment of this disclosure is shown schematically, such as... Figure 2 As shown, the test project management method of this embodiment includes steps S210 to S240.

[0071] It should be noted that, although Figure 2 The steps in the diagram are shown sequentially as indicated by the arrows; however, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise explicitly stated herein, there is no strict order constraint on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the diagram may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0072] In step S210, the requirement items are obtained.

[0073] In this embodiment, a requirement item can be derived from a project during business development. For example, the project's processing can be broken down into a series of project units based on the functions and data processing logic implemented by the project. These project units can then be used as requirement items. Correspondingly, a requirement item can refer to any sub-development stage in the business project development process. A requirement item can directly interface with a technical document. Requirement items can be created by the development team (e.g., a development center) or the research and development team (e.g., a business research and development center). That is, the creation unit of a requirement item can include either the development center or the business research and development center.

[0074] In step S220, when the test unit of a requirement item meets the preset conditions, a test project is configured for the requirement item. The test project includes at least one requirement item, wherein the version information of the requirement items in the same test project is the same, and the project number of the requirement items in the same test project is the same.

[0075] In this embodiment of the disclosure, the preset conditions may include: determining whether the test unit is one of certain preset test units, that is, determining whether the test unit is a target test unit. The target test unit may include one or more units, which can be determined according to actual needs. Optionally, in this embodiment of the disclosure, the target test unit may be created by the R&D party (e.g., a business R&D center). Optionally, when the test unit of a requirement item does not meet the preset conditions, it indicates that the requirement item may be tested by other test units; therefore, the requirement item can be ignored, and newly acquired requirement items can continue to be monitored.

[0076] In this embodiment of the disclosure, version information may include the version plan of a requirement item. A test project may include one or more requirement items. When a test project includes multiple requirement items, the version plans of the multiple requirement items are the same. Optionally, configuring a test project for a requirement item may include creating a test project for the requirement item, or assigning the requirement item to an existing test project. For example, it can be determined whether to create a new test project for the requirement item or assign the requirement item to an existing test project based on whether there is a test project with the same version plan (and project number) as the obtained requirement item in the existing test projects.

[0077] In step S230, when at least one requirement item in the test project changes, the content of the change and the number of requirement items involved in the change are collected. When no requirement item in the test project needs to be changed, monitoring can continue to determine if any requirement item in the test project has changed.

[0078] In this embodiment of the disclosure, changes to a requirement item may include altering information such as the version information, project number, and testing unit of the requirement item. Each change may involve one or more requirement items within the test project. For example, when changing the version information of a requirement item, the version information of one requirement item in the test project may be changed, or the version information of some requirement items in the test project may be changed, or the version information of all requirement items in the test project may be changed. Specific details will be provided below and will not be elaborated upon here.

[0079] In step S240, the test items are adjusted according to the content of the change and the number of requirements involved in the change.

[0080] In this embodiment of the disclosure, a test project adjustment decision can be determined based on the content of the change and the number of requirements involved. Then, the test project is adjusted according to the test project adjustment decision. For example, when a test project involves only one change, the test project adjustment decision can be a single decision; when a test project involves multiple changes, the test project adjustment decision can be a combined decision. For example, when a test project involves only a change in version information, the test project adjustment decision can be a single decision; when a test project involves changes in both version information and project number, the test project adjustment decision can be a combined decision. Optionally, a combined decision may include multiple single decisions executed sequentially.

[0081] In a test project, the adjustment decisions may differ depending on the requirements affected by the change. For example, when the change involves all requirements in the test project, the adjustment decision may include directly adjusting the corresponding content of the test project. When the change only involves some requirements in the test project, the adjustment decision may include deleting the requirements that need to be changed from the test project and creating a new test project for the requirements that need to be changed, or assigning the requirements that need to be changed to other existing test projects, etc.

[0082] Compared to traditional technical solutions that configure test projects based on task lists, the test project management method of this disclosure can configure test projects based on requirement items. Since requirement items are directly derived from project requirements, and technical documents are also output based on requirement items, requirement items can be directly linked to technical documents. This allows technical personnel to accurately connect with business requirements while understanding technical modification methods through relevant technical documents, thereby determining the test scope. Furthermore, in this disclosure, test projects can be adjusted based on the changed content and the requirement items involved, thus adopting different adjustment decisions for different changes and effectively responding to various changes and adjustments to requirement items in test projects.

[0083] In summary, the test project management method of this disclosure can realize the automatic configuration and adjustment of test projects based on requirements, thereby eliminating the need for technical personnel to communicate offline with the development center to obtain the test scope or change content, thus improving testing efficiency and timeliness of changes, and reducing the risks related to production deployment caused by low testing efficiency and untimely changes.

[0084] The test project management method of this disclosure embodiment will be further described below.

[0085] In some specific embodiments, the preset conditions include: the test unit includes a target test unit, or the test unit is empty. In this embodiment of the disclosure, the test project management method can be deployed in the business R&D center, and the target test unit can include the business R&D center itself. When the test unit is empty, the test unit of the requirement item can be the default test unit. Optionally, the default test unit can include the business R&D center itself. That is, in this embodiment of the disclosure, when the test unit of the requirement item is the target test unit, or when the test unit is empty, it indicates that the test unit of the requirement item is the business R&D center.

[0086] Figure 3 A flowchart illustrating the configuration test item according to an embodiment of this disclosure is shown, such as Figure 3 As shown, in some specific embodiments, step S220 includes step S221.

[0087] In step S221, a test project including the requirement item is created based on the version information and project number of the requirement item, or the requirement item is assigned to an existing test project.

[0088] In this embodiment of the disclosure, for a obtained requirement item, if the version plan (or project number) of the requirement item is new, that is, if the version plan (or project number) does not exist in the existing test projects, a new test project can be created for the requirement item. If the version plan (or project number) exists in the existing test projects, the requirement item can be assigned to a test project that includes the version plan (or project number).

[0089] Figure 4 A flowchart illustrating the configuration of a test project based on version information and project number of a requirement item, according to an embodiment of this disclosure, is shown below. Figure 4 As shown, in some specific embodiments, step S221 includes steps S2211 to S2215.

[0090] In step S2211, the test project configuration decision is determined based on the version information and project number of the requirement item and the version information and project number of the existing test project.

[0091] In step S2212, the item type of the requirement item is identified.

[0092] In step S2213, when the project type is a technical project, a decision test project including decision requirement items is created according to the decision test project configuration decision, or the decision requirement items are assigned to an existing decision test project.

[0093] In step S2214, when the project type is a business project, a pending request is generated and sent to the reviewer.

[0094] In step S2215, in response to the reviewer's feedback operation on the pending request, a decision test project is created that includes decision requirement items, or the decision requirement items are assigned to an existing decision test project, according to the decision test project configuration decision.

[0095] In this embodiment of the disclosure, the test project configuration decision may include a first decision and a second decision. The first decision includes creating a new test project for the requirement item. The second decision includes assigning the requirement item to an existing test project. Specifically, when there is an existing test project whose version information (or project number) is the same as the version information (or project number) of the obtained requirement item, the test project configuration decision can be determined as the second decision, that is, in step S2213 or step S2215, the requirement item is assigned to an existing test project; when there is no existing test project whose version information (or project number) is the same as the version information (or project number) of the obtained requirement item, the test project configuration decision can be determined as the first decision, that is, in step S2213 or step S2215, a new test project is created for the requirement item.

[0096] In this embodiment, when the project type is a business project, a to-do request can be generated first and sent to an auditor for review. The auditor may include, for example, the project manager. After receiving the to-do request, the project manager can review the requirements and provide feedback based on the review results. For example, if the review is passed, the auditor's feedback may include confirming execution; if the review is failed, the auditor's feedback may include not executing. When the project type is a technical project, step S221 can be executed directly without a review process, thus improving testing efficiency.

[0097] Figure 5 A flowchart illustrating the configuration of test items according to the creation unit based on an embodiment of the present disclosure is shown, such as... Figure 5As shown, in some specific embodiments, before determining whether the test unit of the requirement item meets the preset conditions, the test project management method further includes steps S310 to S330.

[0098] In step S310, the creation unit of the requirement item is obtained.

[0099] In step S320, it is determined whether the created unit includes the target test unit. If the created unit includes the target test unit, step S330 is executed. If the created unit does not include the target test unit, it is determined whether the test unit of the requirement item meets the preset conditions, and step S220 is executed if the test unit meets the preset conditions.

[0100] In step S330, a test project including the requirement item is created based on the version information and project number of the requirement item, or the requirement item is assigned to an existing test project.

[0101] In this embodiment of the disclosure, the entity that creates the requirement item may include the developer, such as a development center, or the entity that creates the requirement item may include the research and development entity, such as a business research and development center.

[0102] In this embodiment of the disclosure, as described above, the test project management method can be deployed in the business R&D center. When the creation unit of a requirement item is the business R&D center, the requirement item is usually also tested in the business R&D center. Therefore, step S330 can be executed to directly configure test projects for the requirement item, thereby improving processing speed. It should be noted that step S330 is not described in detail in the above embodiments. For example, before step S330, the project type of the requirement item can be determined first, etc., which will not be elaborated here.

[0103] In some specific embodiments, in step S230, change information of each requirement item in the test project can be collected, and the changes involved in the test project can be determined based on the collected change information. Then, in step S240, it is determined which test project adjustment decision (e.g., single decision or combined decision) to select to adjust the test project.

[0104] Optionally, in this embodiment of the disclosure, key fields can be extracted by calling the information details table of the requirement items, the application list, the version list, the requirement item and project requirement relationship table, etc., and the changes in the test unit, version plan, project type, project number, creation unit, status and other information of at least one requirement item in the test project can be obtained through data comparison and identification. When one or more of the above information changes, it indicates that the test project involves corresponding changes.

[0105] Optionally, after determining which specific changes are involved in the test project, labels can be configured for the test project, and then the corresponding test project adjustment decisions can be made through the labels.

[0106] For example, after collecting change information for each requirement item in the test project, we find that the project number of all requirement items in the test project has changed from A to B, while other information remains unchanged. At this point, we can determine that the change involved in the test project is the change in project number. Therefore, we can assign a single decision label to the test project, and then determine the corresponding test project adjustment decision based on the single decision label, that is, execute the adjustment decision corresponding to the change in project number. The specific adjustment process will be described in detail below, and will not be elaborated here.

[0107] For example, after collecting change information for each requirement item in the test project, we find that: the project number of all requirement items has changed from A to B, and the version plan of all requirement items has changed from C to D, while other information remains unchanged. In this case, we can determine that the changes involved in the test project are the changes in project number and version plan. Therefore, we can assign a combined decision label to the test project, and then determine the corresponding test project adjustment decision based on the combined decision label. For example, we can sequentially execute the adjustment decision corresponding to the change in project number and the adjustment decision corresponding to the change in version plan. The specific adjustment process will be described in detail below, and will not be elaborated here.

[0108] The following section will first explain how to adjust test items through a single decision. Specifically, when a test item involves only one change, the test item adjustment decision can adopt the single decision method described above.

[0109] In some specific embodiments, the change includes a first change, which includes a change to the version information of the requirement item. Specifically, step S240 includes steps S2411 to S2413.

[0110] In step S2411, it is determined whether the first change involves all the requirements in the test project. If yes, step S2412 is executed; otherwise, step S2413 is executed.

[0111] In step S2412, the version information of the test item is adjusted so that the version information of the test item is consistent with the version information of the requirement item after the first change.

[0112] In step S2413, the requirement items involved in the first change are deleted from the current test project, and the test project is configured for the requirement items based on the version information of the requirement items after the first change.

[0113] In some specific embodiments, the variation includes a second variation, which includes a change to the item number of the requirement item. Specifically, step S240 includes steps S2421 to S2423.

[0114] In step S2421, it is determined whether the second change involves all the requirements in the test project. If yes, step S2422 is executed; otherwise, step S2423 is executed.

[0115] In step S2422, the item number of the test item is adjusted so that the item number of the test item is consistent with the item number of the requirement item after the second change.

[0116] In step S2423, the requirement items involved in the second change are deleted from the current test project, and a test project is configured for the requirement items according to the project number of the requirement items after the second change.

[0117] It should be noted that, in the above two embodiments, the detailed explanation of configuring test items for the requirement items can be found in the aforementioned embodiments, and will not be repeated here.

[0118] In some specific embodiments, the variation includes a third variation, which includes a change to the test unit of the requirement item. Specifically, step S240 includes steps S2431 to S2434.

[0119] In step S2431, determine whether the third change involves all the requirements in the test project. If yes, proceed to step S2432; otherwise, proceed to step S2433.

[0120] In step S2432, it is determined whether the test unit of the requirement item after the third change does not meet the preset conditions. If so, the test item is invalidated; otherwise, the test item is retained, and the information of the requirement item after the third change is updated.

[0121] In step S2433, it is determined whether there are still test units of the requirement items in the test project that meet the preset conditions. If so, the test project is retained and the information of the requirement items after the third change is updated; otherwise, the test project is invalidated.

[0122] In some specific embodiments, the variation includes a fourth variation, which includes a change to the state of the demand item. Specifically, step S240 includes steps S2441 to S2443.

[0123] In step S2441, it is determined whether the fourth change involves all the requirements in the test project. If yes, step S2442 is executed; otherwise, step S2443 is executed.

[0124] In step S2442, it is determined whether all requirement items are in an invalid state after the fourth change. If so, the test item is invalidated; otherwise, the test item is retained, and the information of the requirement items after the fourth change is updated.

[0125] In step S2443, if it is determined whether the requirement item involved in the fourth change is in an invalid state after the fourth change, then the requirement item is deleted from the test project; otherwise, the requirement item is retained and the information of the requirement item is updated.

[0126] The following describes the selection of a combination decision for adjusting test items. Specifically, when a test item involves multiple changes, the test item adjustment decision can adopt the combination decision described above. In this embodiment, the combination decision can include the sequential execution of multiple individual decisions. For each individual decision, its implementation process can refer to the foregoing embodiments.

[0127] For example, taking a test project where the project number of a requirement item changes from A to B and the version plan changes from C to D, while other key information remains unchanged, this embodiment of the present disclosure illustrates the use of combined decision-making to adjust test projects.

[0128] Specifically, an adjustment decision corresponding to the version information change (i.e., the first change) can be executed first. Specifically, step S240 includes steps S2451 to S2453.

[0129] In step S2451, it is determined whether the first change involves all the requirements in the test project. If yes, step S2452 is executed; otherwise, step S2453 is executed.

[0130] In step S2452, the version information of the test item is adjusted so that the version information of the test item is consistent with the version information of the requirement item after the first change.

[0131] In step S2453, the requirement items involved in the first change are deleted from the current test project, and the test project is configured for the requirement items based on the version information of the requirement items after the first change.

[0132] In some specific embodiments, configuring test items for the requirement item in step S2453 can refer to the foregoing embodiments. For example, step S2453 includes steps S2453a to S2453e.

[0133] In step S2453a, the test project configuration decision is determined based on the version information and project number of the requirement item and the version information and project number of the existing test items.

[0134] In step S2453b, the item type of the requirement item is identified.

[0135] In step S2453c, when the project type is a technical project, a test project including the requirement items is created according to the test project configuration decision, or the requirement items are assigned to an existing test project.

[0136] In step S2453d, when the project type is a business project, a pending request is generated and sent to the reviewer.

[0137] In step S2453e, in response to the reviewer's feedback on the pending request, a test project including the requirement items is created according to the test project configuration decision, or the requirement items are assigned to an existing test project.

[0138] Then, the adjustment decision corresponding to the change of project number (i.e., the second change) is executed to complete the combination adjustment of the test project. The process of executing the adjustment decision corresponding to the project number can be referred to the above embodiment, and will not be repeated here.

[0139] It should be noted that combined decision-making can include various combinations of the single decision-making methods described above, and these will not be listed one by one in the embodiments disclosed herein.

[0140] In some specific embodiments, the test project management method further includes:

[0141] Change notifications are sent to users. These notifications may include change information and decisions as described in the above embodiments, thereby automatically notifying relevant stakeholders of the project, enabling them to understand the changes in a timely manner, and ensuring that adjustments to the test scope are communicated promptly.

[0142] In some specific embodiments, the test project management method further includes:

[0143] In response to user actions, it intervenes in the adjustment of test projects, thereby providing manual assistance to adjust the process when the program is not handled properly or when the program is incomplete due to data problems, and improves the project assignment in real time to ensure the normal operation of the project process.

[0144] The test project management method in this embodiment of the invention can automatically identify and invalidate test projects. Furthermore, when invalidated content needs to be adjusted and tested again by the business R&D center, test project synchronization information can be configured in a timely manner for the corresponding requirement items to ensure the accuracy of the test scope.

[0145] Based on the above-described test project management method, this disclosure also provides a test project management device. The following will be combined with... Figure 6 The device is described in detail.

[0146] Figure 6A schematic diagram illustrating the structure of a test project management device according to an embodiment of the present disclosure is shown, such as... Figure 6 As shown, the test project management device 600 of this embodiment includes an acquisition module 610, a test project configuration module 620, a data acquisition module 630, and a test project adjustment module 640.

[0147] The acquisition module 610 is used to acquire the required items. In one embodiment, the acquisition module 610 can be used to perform step S210 described above, which will not be repeated here.

[0148] The test item configuration module 620 is used to configure a test item for a requirement item when the test unit of the requirement item meets preset conditions. Requirement items within the same test item have the same version information and the same item number. In one embodiment, the test item configuration module 620 can be used to execute step S220 described above, which will not be repeated here.

[0149] The data acquisition module 630 is used to acquire the content of the change and the number of requirement items involved in the change when at least one requirement item in the test project changes. In one embodiment, the data acquisition module 630 can be used to perform step S230 described above, which will not be repeated here.

[0150] The test item adjustment module 640 is used to adjust the test items according to the content of the changes and the number of requirements involved in the changes. In one embodiment, the test item adjustment module 640 can be used to execute step S240 described above, which will not be repeated here.

[0151] The test project management device of this disclosure can realize automatic configuration and adjustment of test projects based on requirements, so that technicians no longer need to communicate with the development center offline to obtain the test scope or change content, thereby improving test efficiency and timeliness of changes, and reducing the risks related to production launch caused by low test efficiency and untimely changes.

[0152] According to embodiments of this disclosure, any multiple modules among the acquisition module 610, test item configuration module 620, acquisition module 630, and test item adjustment module 640 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least some of the functions of one or more of these modules can be combined with at least some of the functions of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the acquisition module 610, test item configuration module 620, acquisition module 630, and test item adjustment module 640 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the acquisition module 610, test item configuration module 620, acquisition module 630, and test item adjustment module 640 may be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0153] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a test project management method according to an embodiment of the present disclosure, such as... Figure 7 As shown, an electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage portion 708 into a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0154] RAM 703 stores various programs and data required for the operation of electronic device 700. Processor 701, ROM 702, and RAM 703 are interconnected via bus 704. Processor 701 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 702 and / or RAM 703. It should be noted that programs may also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

[0155] According to embodiments of this disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to a bus 704. The electronic device 700 may also include one or more of the following components connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0156] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments, or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the test project management method according to the embodiments of this disclosure.

[0157] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 702 and / or RAM 703 and / or one or more memories other than ROM 702 and RAM 703 described above.

[0158] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the test project management method provided in the embodiments of this disclosure.

[0159] When the computer program is executed by the processor 701, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0160] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 709, and / or installed from a removable medium 711. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0161] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0162] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0163] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0164] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0165] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A test project management method, characterized in that, include: Obtain the required items; When the test unit of the requirement item meets the preset conditions, a test project is configured for the requirement item. The test project includes at least one requirement item, wherein the version information of the requirement items in the same test project is the same, and the project number of the requirement items in the same test project is the same. When at least one of the requirements in the test project changes, the content of the change and the number of the requirements involved in the test project are collected. The test items are adjusted according to the content of the changes and the number of the requirements involved in the changes; The preset conditions include: the test unit includes a target test unit or the test unit is empty; Configuring test items for the aforementioned requirements includes: Based on the version information and project number of the aforementioned requirement item, as well as the version information and project number of the existing test project, determine the test project configuration decision; Identify the project type of the required item; When the project type is a technical project, the test project including the requirement item is created according to the test project configuration decision, or the requirement item is assigned to an existing test project; When the project type is a business project, a to-do request is generated and sent to the reviewer; In response to the reviewer's feedback on the pending request, the test project including the requirement item is created according to the determined test project configuration decision, or the requirement item is assigned to an existing test project.

2. The test project management method according to claim 1, characterized in that, Before determining whether the test unit of the requirement item meets the preset conditions, the test project management method further includes: Obtain the creation unit of the aforementioned requirement item; When the creation unit includes the target test unit, the step is to create the test project including the requirement item according to the version information and project number of the requirement item, or to assign the requirement item to an existing test project; when the creation unit does not include the target test unit, it is determined whether the test unit of the requirement item meets the preset conditions.

3. The test project management method according to claim 1, characterized in that, The changes include a first change, which includes changes to the version information of the requirement items. Adjusting the test items based on the content of the changes and the number of requirement items involved in the changes includes: When the first change involves all requirements in the test project, the version information of the test project is adjusted to make the version information of the test project consistent with the version information of the requirements after the first change; and / or, The change includes a second change, which includes a change to the item number of the requirement item. Adjusting the test item based on the content of the change and the number of requirement items involved in the change includes: When the second change involves all requirements in the test project, the project number of the test project is adjusted so that the project number of the test project is consistent with the project number of the requirements after the second change.

4. The test project management method according to claim 3, characterized in that, When the change includes the first change, and the first change involves some of the requirements in the test project, adjusting the test project according to the content of the change and the number of requirements involved in the change further includes: for at least one requirement involved in the first change, Remove the aforementioned requirement from the current test project; Based on the version information of the requirement item after the first change, configure a test project for the requirement item; and / or, When the change includes the second change, and the second change involves some of the requirements in the test project, adjusting the test project according to the content of the change and the number of requirements involved in the change further includes: for at least one requirement involved in the second change, Remove the aforementioned requirement from the current test project; Configure a test project for the requirement item based on the project number after the second change.

5. The test project management method according to claim 1, characterized in that, The change includes a third change, which includes a change to the test unit of the requirement item. Adjusting the test items based on the content of the change and the number of requirement items involved in the change includes: When the third change involves all requirements in the test project, and the test unit after the third change does not meet the preset conditions, the test project is invalidated.

6. The test project management method according to claim 1, characterized in that, The change includes a fourth change, which includes a change to the status of the requirement item. Adjusting the test item based on the content of the change and the number of requirement items involved in the change includes: When the fourth change involves some of the requirements in the test project, and the requirements are in an obsolete state after the fourth change, the requirements are deleted from the test project. When the fourth change involves all requirements in the test project, and all requirements are in an invalid state after the fourth change, the test project is invalidated.

7. A test project management device, characterized in that, include: The acquisition module is used to acquire the required items; A test project configuration module is used to configure a test project for a requirement item when the test unit of the requirement item meets preset conditions. The requirement items within the same test project have the same version information and the same project number. The preset conditions include: the test unit includes a target test unit or the test unit is empty. Configuring a test project for the requirement item includes: determining a test project configuration decision based on the version information and project number of the requirement item and the version information and project number of existing test projects; identifying the project type of the requirement item; when the project type is a technical project, creating a test project including the requirement item according to the test project configuration decision, or assigning the requirement item to an existing test project; when the project type is a business project, generating a pending request and sending it to the reviewer; responding to the reviewer's feedback operation on the pending request, creating a test project including the requirement item according to the determined test project configuration decision, or assigning the requirement item to an existing test project. The data acquisition module is used to acquire the content of the change and the number of the requirement items involved in the test project when at least one of the requirement items in the test project changes. The test item adjustment module is used to adjust the test item according to the content of the change and the number of the requirement items involved in the change.

8. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors execute the test project management method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, It stores executable instructions that, when executed by a processor, cause the processor to perform the test project management method according to any one of claims 1 to 6.

10. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the test project management method according to any one of claims 1 to 6.

Images