A test resource management method, device and medium for non-functional testing

Abstract

The present application discloses a test resource management method, device and medium for non-functional testing, which relates to the field of electrical digital data processing technology. It includes: determining the project type corresponding to the non-functional test project and the project mode corresponding to the project type; determining whether the non-functional test project needs to be tested according to the project mode and the project component assembly logic corresponding to the non-functional requirement category; if so, analyzing the test content corresponding to the non-functional test project to determine the target test items required to complete the test content, and establishing a connection between the non-functional test project and the preset continuous integration tool; predicting the test budget time required for the target test item, and allocating corresponding test resources to the non-functional test project according to the test budget time; when the preset trigger condition is met, triggering the test process for the target test item through the continuous integration tool to achieve non-functional testing of the non-functional test project.

Description

Technical Field

[0001] The present application relates to the technical field of electronic digital data processing, and in particular to a test resource management method, device and medium for non-functional testing. Background Art

[0002] In current software development, non-functional testing (NFR) plays a vital role in ensuring the stability, performance, availability and security of software systems. However, existing non-functional testing technologies are still insufficient in many aspects. For example, in the traditional waterfall development model, non-functional testing is often postponed to the later stages of the project, which increases project risks and costs. In addition, the definition and quantification of non-functional requirements is also a major challenge, especially in agile development, where non-functional requirements need to be repeatedly tested and verified in each short cycle, which places higher demands on resources and time.

[0003] In recent years, although some new technologies have attempted to better integrate non-functional testing in an agile environment, such as paying continuous attention to non-functional requirements in each development cycle and improving the definition of non-functional requirements by analyzing user behavior data and system operation data, these technologies still face challenges in dealing with dynamic demand changes and diverse test scenarios, especially the accurate estimation of test time and resources has not been effectively solved. Summary of the invention

[0004] In order to solve the above problems, the present application proposes a test resource management method for non-functional testing, including:

[0005] For a non-functional test item to be tested, determining a project type corresponding to the non-functional test item and a project mode corresponding to the project type;

[0006] Determine the non-functional requirement category corresponding to the project type, and determine whether the non-functional test project needs to be subjected to non-functional testing according to the project mode and the project component assembly logic corresponding to the non-functional requirement category;

[0007] If yes, analyze the test content corresponding to the non-functional test item to determine the target test items required to complete the test content, and establish a connection between the non-functional test item and a preset continuous integration tool;

[0008] Predicting the test budget time required for the target test item, and allocating corresponding test resources to the non-functional test item according to the test budget time;

[0009] Based on the test resources, when a preset trigger condition is met, the test process for the target test item is triggered through the continuous integration tool to implement non-functional testing of the non-functional test item.

[0010] In one implementation of the present application, determining whether the non-functional test project needs to be subjected to non-functional testing according to the project mode and the project component assembly logic corresponding to the non-functional requirement category specifically includes:

[0011] The project modes include new construction and reconstruction mode and transformation mode;

[0012] Obtaining the project component assembly logic corresponding to the non-functional requirement category, and determining whether the non-functional requirement category needs to be subjected to non-functional testing according to the project component assembly logic;

[0013] When the project mode is the new construction and reconstruction mode, or when some of the non-functional requirement categories need to be tested, determining that the non-functional test items need to be tested;

[0014] When the project mode is the transformation mode and all non-functional requirement categories do not require non-functional testing, it is determined that the non-functional test items do not require non-functional testing.

[0015] In one implementation of the present application, determining whether the non-functional requirement category needs to be tested for non-functionality according to the project component assembly logic specifically includes:

[0016] Determine, according to the project component assembly logic, at least one evaluation item corresponding to the non-functional requirement category and a test evaluation standard corresponding to the evaluation item;

[0017] Determine the minimum test scope corresponding to the test evaluation standard, and verify the test evaluation standard in turn according to the minimum test scope to determine whether the evaluation item meets the test evaluation standard; wherein the minimum test scope refers to the necessary test items required to complete the test evaluation standard;

[0018] If so, determine that the non-functional requirement category requires non-functional testing.

[0019] In one implementation of the present application, the test content corresponding to the non-functional test item is analyzed to determine the target test items required to complete the test content, specifically including:

[0020] Divide the test requirements corresponding to the non-functional test items, and determine the management granularity corresponding to the test resources according to the test requirements; wherein the management granularity includes fuzzy management granularity and fine management granularity;

[0021] Based on different management granularities, the test contents corresponding to the non-functional test items are analyzed to locate the target test items.

[0022] In one implementation of the present application, the test requirements corresponding to the non-functional test items are divided, and the management granularity corresponding to the test resources is determined according to the test requirements, specifically including:

[0023] Divide the test requirements corresponding to the non-functional test items, and determine the test unit level involved in the test requirements; wherein the test unit level includes an activity unit and a work sub-type unit;

[0024] In the case where the test unit level is the active unit, determining that the management granularity corresponding to the test resource is a fuzzy management granularity;

[0025] In the case where the test unit level is the work subtype unit, it is determined that the management granularity corresponding to the test resource is a fine management granularity.

[0026] In one implementation of the present application, the test content corresponding to the non-functional test item is analyzed to determine the target test items required to complete the test content, specifically including:

[0027] Based on the fuzzy management granularity, the non-functional test project is divided into a number of work stages, and a plurality of activity units included in the work stages are determined;

[0028] Based on the fine management granularity, the work subtypes covered by the activity unit are determined, and according to the test content corresponding to the non-functional test item, a specified work subtype is selected from the work subtypes as the target test item required to complete the test content.

[0029] In one implementation of the present application, the test content corresponding to the non-functional test item is analyzed to determine the target test items required to complete the test content, specifically including:

[0030] Based on the fuzzy management granularity, the non-functional test project is divided into a number of work stages, and a plurality of activity units included in the work stages are determined;

[0031] Based on the fine management granularity, the work subtypes covered by the activity unit are determined, and according to the test content corresponding to the non-functional test item, a specified work subtype is selected from the work subtypes as the target test item required to complete the test content.

[0032] In one implementation of the present application, after predicting the test budget time required for the target test item, the method further includes:

[0033] Determine the system type of the physical subsystem corresponding to the non-functional test item; wherein the system type includes an introduced system and a self-built system;

[0034] In the case where the system type is the introduced system, determining that the non-functional test items need to be subjected to a verification test, and determining a verification test time corresponding to the verification test;

[0035] The test budget time is updated according to the verification test time, so as to allocate corresponding test resources to the non-functional test items according to the updated test budget time.

[0036] An embodiment of the present application provides a test resource management device for non-functional testing, the device comprising:

[0037] at least one processor;

[0038] and, a memory communicatively coupled to the at least one processor;

[0039] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a test resource management method for non-functional testing as described in any one of the above items.

[0040] The embodiment of the present application provides a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as follows:

[0041] A test resource management method for non-functional testing as described in any one of the above items.

[0042] The test resource management method for non-functional testing proposed in this application can bring the following beneficial effects:

[0043] By classifying and quantitatively evaluating the non-functional requirements of different project types, we can accurately identify projects that require non-functional testing, avoid unnecessary waste of testing resources, ensure comprehensive test coverage, and promptly discover potential problems. By integrating a time calculation tool based on multiple dimensions, we can predict the test budget time of the target test items, so as to reasonably allocate test resources and ensure effective use of resources. Through automated test evaluation standards and continuous integration methods, non-functional testing is carried out throughout the entire development cycle, which not only improves the execution efficiency of the test, but also ensures comprehensive test coverage. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0045] Figure 1 A flowchart of a test resource management method for non-functional testing provided in an embodiment of the present application;

[0046] Figure 2 A structural diagram of a test resource management device for non-functional testing provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0048] In current software development practices, especially in complex enterprise-level system development, non-functional requirements testing faces the following key issues:

[0049] (1) The ambiguity and difficulty in quantifying non-functional requirements:

[0050] Non-functional requirements (such as performance, usability, maintainability, etc.) are often difficult to quantify and define clearly, which leads to these requirements being ignored or delayed in testing during the development cycle. This not only increases the risk of the project, but also causes problems to be discovered late in the project, making them costly to fix.

[0051] (2) Difficulty in accurately estimating non-functional testing time and resources:

[0052] Current non-functional testing methods lack accurate estimation tools for the time and resources required for non-functional testing, which leads to unreasonable test plans and improper resource allocation, which may ultimately lead to project delays or inadequate testing.

[0053] (3) Execution efficiency and coverage issues of non-functional testing:

[0054] In traditional development cycles, non-functional testing is often postponed to the later stages of the project, lacking continuous attention and comprehensive coverage, which leads to suboptimal testing results and may affect system stability and performance.

[0055] To solve the above problems, this application proposes a non-functional testing plan model (NFTP). Based on the NFTP model, non-functional testing of non-functional test items to be tested can not only greatly improve the accuracy, efficiency and resource utilization of non-functional testing, but also ensure the stability and high performance of the software system. This model is suitable for various complex software systems that require non-functional testing, especially in enterprise-level IT environments, and helps to improve the efficiency and quality of overall project management.

[0056] The core idea of ​​the NFTP model is to integrate non-functional testing into every stage of software development, rather than only conducting centralized testing in the later stages of the project. To this end, the model has designed the following key modules:

[0057] Non-functional requirements classification and quantification module: This module is responsible for classifying non-functional requirements of different project types and quantifying these requirements through a set of standardized methods. This ensures that all important non-functional requirements are clearly defined and verified in each project.

[0058] Automated test evaluation module: Through this module, the model provides a set of automated evaluation criteria for real-time monitoring and evaluation of the non-functional performance of the system. This module is tightly integrated with the development process through continuous integration tools (such as Jenkins, GitLabCI, etc.) to ensure that each code submission or change is verified by non-functional testing.

[0059] Test time estimation and resource allocation module: This module estimates the time and resources required for testing based on historical data and project characteristics, and provides scientific decision support for project managers. This module helps to arrange test plans reasonably by analyzing data from different dimensions such as test script development, performance testing, and capacity testing.

[0060] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0061] like Figure 1 As shown, a test resource management method for non-functional testing provided by an embodiment of the present application is applied to an NFTP model, including:

[0062] S101: For a non-functional test item to be tested, determine a project type corresponding to the non-functional test item and a project mode corresponding to the project type.

[0063] Non-functional testing is an important type of software testing, which focuses on the non-functional aspects of the system rather than the specific functional implementation. Among them, non-functional aspects include but are not limited to the system's performance, reliability, security, availability, maintainability, compatibility and scalability. Therefore, the system needs to perform non-functional testing during the development process to ensure the stable operation of the system. According to the test requirements of each system, corresponding non-functional testing projects can be formed, and due to the different types of systems, non-functional testing projects need to be divided into different project types. Among them, the project types can be divided into externally introduced new systems and internally built new systems according to the different ways of introducing the system. Externally introduced new systems refer to systems introduced from the outside that need to be secondary developed on this basis, while internally built new systems refer to systems newly developed within the enterprise according to business needs. The project mode corresponding to each project type will also be different due to different system types. Generally, there are two modes. One is the new reconstruction mode, which corresponds to the external introduction of new systems, which refers to the corresponding functional transformation based on the original development project. The other is the transformation mode, which corresponds to the internal self-built new system, which refers to the development of new projects.

[0064] S102: Determine the non-functional requirement category corresponding to the project type, and determine whether the non-functional test project needs to be subjected to non-functional testing according to the project mode and the project component assembly logic corresponding to the non-functional requirement category.

[0065] Different project types have different corresponding non-functional requirement categories, such as management requirements, risk rectification, system changes, etc. For different non-functional test projects, since their corresponding non-functional requirement categories are different and the project models may also be different, it is necessary to analyze them according to the actual situation to determine whether each non-functional test project needs non-functional testing. This process involves the project component assembly logic corresponding to the non-functional requirement category.

[0066] Specifically, the project component assembly logic corresponding to the non-functional requirement category is obtained, and according to the project component assembly logic, it is determined whether the non-functional requirement category needs to be tested non-functionally. The project component assembly logic is used to clarify which specific non-functional requirement categories the current non-functional test project mainly tests. In this process, according to the project component assembly logic, at least one evaluation item corresponding to each non-functional requirement category can be clarified. Each evaluation item has a corresponding test evaluation standard. If the current test requirement meets the test evaluation standard, it means that the non-functional requirement category corresponding to the evaluation item needs to be tested. This process needs to be carried out with the help of the minimum test scope. The minimum test scope refers to the necessary test items required to complete the test evaluation standard. In other words, it is only necessary to complete the standard evaluation within the minimum test scope to determine whether the evaluation standard of the current evaluation item is passed. Therefore, after verifying the test evaluation standard in turn according to the minimum test scope, it can be determined whether the evaluation item corresponding to each non-functional requirement category meets the test evaluation standard.

[0067] For example, for the non-functional requirement category of risk rectification, the corresponding evaluation item is production events or non-functional legacy defect repairs. The test evaluation standard is to evaluate whether to conduct non-functional testing based on the specific circumstances of the production events or defects. The minimum test scope is the test indicators determined by the production events or defect content and the content of this transformation. This process clarifies the test content to be evaluated. If the test indicators within the above range are evaluated according to the minimum test content and non-functional testing is required, then it can be determined that the non-functional requirement category of risk rectification needs to be tested.

[0068] If the project mode corresponding to the non-functional test project is the new reconstruction mode, the project involves a large number of new components and needs non-functional testing, or there are some non-functional requirement categories that need non-functional testing. At this time, functional testing of non-functional test projects is also required to ensure the overall performance and quality of the system. In the case of the transformation mode, if all non-functional requirement types do not require non-functional testing, it means that the currently introduced system does not need additional non-functional testing.

[0069] S103: If yes, the test content corresponding to the non-functional test project is analyzed to determine the target test items required to complete the test content, and the non-functional test project is connected to a preset continuous integration tool.

[0070] The above process verifies whether non-functional testing is required for non-functional testing projects. If non-functional testing projects are to be tested, it is also necessary to analyze the corresponding test content and clarify the target test items required to complete the test content. By splitting the test process into several target test items, it is possible to provide corresponding test resources for each target test item in a targeted manner, thereby improving allocation efficiency and accuracy. For projects that require non-functional testing, it is necessary to establish a connection between the non-functional testing project and the preset continuous integration tool, so as to realize the transformation of the traditional manual testing process into an automated testing mechanism that can provide real-time feedback.

[0071] In order to perform non-functional testing more efficiently, it is necessary to divide the test requirements more finely and determine the management granularity of test resources accordingly. Management granularity includes fuzzy management granularity and fine management granularity. Fuzzy management granularity indicates an approximate test scope, which is divided from the overall process of the test execution phase. Fine management granularity is based on fuzzy management granularity and more accurately locates the target test items that need to be executed in the divided overall process.

[0072] When dividing the test requirements, it is necessary to clarify the test unit level involved in each test requirement. The test unit level includes active units and work subtype units. When the test unit level is an active unit, the management granularity corresponding to the test resources is determined to be a fuzzy management granularity; when the test unit level is a work subtype unit, the management granularity corresponding to the test resources is determined to be a fine management granularity.

[0073] It is clear that at the level of fuzzy management granularity, the test content that needs to be determined is the various activities involved in non-functional testing, while at the level of fine management granularity, the test content that needs to be determined is the specific test items involved in the activity content. Therefore, based on the fuzzy management granularity, the non-functional test project is divided into several work stages, and the multiple activity units contained in the work stage are determined. Based on the fine management granularity, the work subtype covered by the activity unit is determined, and according to the test content corresponding to the non-functional test project, the specified work subtype is selected from the work subtype as the target test item required to complete the test content.

[0074] For example, non-functional testing projects can be divided into the following activity units: filling in non-functional design indicators, evaluating the necessity of non-functional testing, analyzing test requirements, formulating and reviewing non-functional testing plan cases, preparing the test environment, and executing non-functional testing. Different activity units may involve different sub-types of work. For each activity unit, specific activity content may be involved, such as script development and debugging, performance capacity and batch processing and data operations, availability database testing, availability batch testing, etc. Different work sub-types are covered under each activity content. For the availability database testing activity content, the covered work sub-types include the effectiveness of the database cluster switching mechanism, the effectiveness of the database automatic reconnection mechanism, the effectiveness of the application reconnection database mechanism, the effectiveness of the application sub-library and sub-table mechanism, and the effectiveness of the application cache to remove database dependency mechanism.

[0075] S104: Predict the test budget time required for the target test item, and allocate corresponding test resources to the non-functional test item according to the test budget time.

[0076] After clearly defining the target test items required to execute the non-functional test project, in order to better implement test resource management, it is necessary to estimate the test time corresponding to the non-functional test project, and then reasonably allocate corresponding test resources to each target test item based on the test time, providing scientific decision support for project managers.

[0077] In one embodiment, non-functional testing needs to be carried out on specific target test items. However, when performing non-functional testing, it is first necessary to make a fuzzy test time prediction based on each active unit, and then make a more detailed division and prediction of the sub-type of work that needs to be performed under each active unit. Therefore, it is necessary to first clarify the overall test time of each active unit, and then for each active unit, it is necessary to predict the local test time corresponding to the sub-type of work that needs to be performed in the active unit. Based on the local test time, calculate the test budget time required for the target test item. The test budget time is not greater than the overall test time.

[0078] The test time is mostly calculated from the following aspects: Script development and debugging: the time for writing and debugging the initial test script; Performance / capacity testing: time assessment to ensure that the system can operate normally under high load conditions; Usability testing: time assessment to test the user experience and operational convenience of the system; Maintainability testing: time assessment to evaluate the maintenance cost of the system in long-term operation; Scalability testing: time assessment to ensure that the system can expand as demand grows; Others: time assessment of other non-functional tests including security and compatibility; Acceptance testing: time spent on overall acceptance testing before final delivery; Problem and defect modification: time assessment for repairing and verifying problems and defects found during the test.

[0079] The above process only estimates the test time. It is also necessary to determine whether the non-functional test project requires other types of test content. Therefore, determine the system type of the physical subsystem corresponding to the non-functional test project; among them, the system type includes introduced system and self-built system. The introduced system usually refers to the part built by purchasing or integrating third-party services, software or hardware systems. These systems may have been tested and verified to a certain extent, but the non-functional characteristics (such as performance, security, reliability, etc.) for specific integration environments or business requirements still need to be verified. Therefore, for non-functional test projects of the introduced system type, it is necessary to determine the verification test time corresponding to the verification test. Since the verification test is not included in the initial test plan, the test budget time needs to be updated accordingly according to the verification test time. Based on the updated test budget time, reasonably allocate test resources, including testers, test environment, test tools, etc., to ensure that there are sufficient resources to support the smooth progress of test activities within the corresponding test time.

[0080] S105: Based on the test resources, when a preset trigger condition is met, a test process for a target test item is triggered through a continuous integration tool to implement non-functional testing of the non-functional test item.

[0081] When the preset trigger conditions are met, the continuous integration tool can respond to the corresponding operations and trigger the test process for the target test items, making the test more continuous and real-time. The trigger condition refers to the existence of a code submission operation or a test requirement change application. Therefore, during the development iteration of the non-functional test project, if the above two situations occur, the continuous development integration tool will automatically trigger the test process for the target test items. This step combines the developer's code submission operation with the non-functional test automation execution process to ensure that the test runs through the entire development cycle and defects are discovered and fixed in a timely manner.

[0082] It should be noted that the NFTP model can perform dynamic non-functional requirement management, that is, dynamically adjust the priority and test coverage of non-functional requirements. When the development requirement content module is changed midway or a new deployment unit is added, the model dynamically adjusts the transformation requirements and produces the latest test content and time plan to ensure that during the project development process, even if the requirements change, the test can be followed up in time.

[0083] The above are embodiments of the method proposed in this application. Based on the same idea, some embodiments of this application also provide devices and non-volatile computer storage media corresponding to the above methods.

[0084] Figure 2 A schematic diagram of the structure of a test resource management device for non-functional testing provided in an embodiment of the present application. Figure 2As shown, including:

[0085] at least one processor; and,

[0086] at least one processor is communicatively connected to a memory; wherein,

[0087] The memory stores instructions executable by at least one processor, and the instructions are executed by at least one processor so that the at least one processor can execute a test resource management method for non-functional testing as described in any one of the above items.

[0088] The embodiment of the present application provides a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as follows:

[0089] A test resource management method for non-functional testing as described in any one of the above items.

[0090] Each embodiment in this application 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 and 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.

[0091] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media 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 devices and media will not be repeated here.

[0092] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0093] The present application 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 the present application. 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 generate 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.

[0094] 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.

[0095] 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. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

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

[0098] 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 tape 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.

[0099] 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.

[0100] The above is only an embodiment of the present application 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 test resource management method for non-functional testing, characterized in that: The method comprises: For a non-functional test item to be tested, determining a project type corresponding to the non-functional test item and a project mode corresponding to the project type; Determine the non-functional requirement category corresponding to the project type, and determine whether the non-functional test project needs to be tested according to the project mode and the project component assembly logic corresponding to the non-functional requirement category; the project component assembly logic is used to clarify the specific non-functional requirement category that needs to be tested for the non-functional test project; If yes, analyze the test content corresponding to the non-functional test item to determine the target test items required to complete the test content, and establish a connection between the non-functional test item and a preset continuous integration tool; Predicting the test budget time required for the target test item, and allocating corresponding test resources to the non-functional test item according to the test budget time; Based on the test resources, when a preset trigger condition is met, the test process for the target test item is triggered through the continuous integration tool to implement non-functional testing of the non-functional test item; the trigger condition refers to the existence of a code submission operation or a test requirement change application; Determining whether the non-functional test item needs to be tested according to the project mode and the project component assembly logic corresponding to the non-functional requirement category, specifically includes: The project modes include new construction and reconstruction mode and transformation mode; Obtaining the project component assembly logic corresponding to the non-functional requirement category, and determining whether the non-functional requirement category needs to be subjected to non-functional testing according to the project component assembly logic; When the project mode is the new construction and reconstruction mode, or when some of the non-functional requirement categories need to be tested, determining that the non-functional test items need to be tested; When the project mode is the transformation mode and all non-functional requirement categories do not require non-functional testing, it is determined that the non-functional test items do not require non-functional testing.

2. A test resource management method for non-functional testing according to claim 1, characterized in that: Determine whether the non-functional requirement category needs to be tested according to the project component assembly logic, specifically including: Determine, according to the project component assembly logic, at least one evaluation item corresponding to the non-functional requirement category and a test evaluation standard corresponding to the evaluation item; Determine a minimum test scope corresponding to the test evaluation standard, and verify the test evaluation standard in turn according to the minimum test scope to determine whether the evaluation item meets the test evaluation standard; wherein the minimum test scope refers to the necessary test items required to complete the test evaluation standard; If so, determine that the non-functional requirement category requires non-functional testing.

3. A test resource management method for non-functional testing according to claim 1, characterized in that: Analyze the test content corresponding to the non-functional test items to determine the target test items required to complete the test content, including: Divide the test requirements corresponding to the non-functional test items, and determine the management granularity corresponding to the test resources according to the test requirements; wherein the management granularity includes fuzzy management granularity and fine management granularity; Based on different management granularities, the test contents corresponding to the non-functional test items are analyzed to locate the target test items.

4. A test resource management method for non-functional testing according to claim 3, characterized in that: The test requirements corresponding to the non-functional test items are divided, and the management granularity corresponding to the test resources is determined according to the test requirements, specifically including: Divide the test requirements corresponding to the non-functional test items, and determine the test unit level involved in the test requirements; wherein the test unit level includes an activity unit and a work sub-type unit; In the case where the test unit level is the active unit, determining that the management granularity corresponding to the test resource is a fuzzy management granularity; In the case where the test unit level is the work subtype unit, it is determined that the management granularity corresponding to the test resource is a fine management granularity.

5. A test resource management method for non-functional testing according to claim 4, characterized in that: Analyze the test content corresponding to the non-functional test items to determine the target test items required to complete the test content, including: Based on the fuzzy management granularity, the non-functional test project is divided into a number of work stages, and a plurality of activity units included in the work stages are determined; Based on the fine management granularity, the work subtypes covered by the activity unit are determined, and according to the test content corresponding to the non-functional test item, a specified work subtype is selected from the work subtypes as the target test item required to complete the test content.

6. A test resource management method for non-functional testing according to claim 5, characterized in that: Predict the test budget time required for the target test item, including: Determine the overall test time corresponding to the activity unit and the local test time corresponding to the target test item; The test budget time required for the target test item is calculated according to the local test time; wherein the test budget time is not greater than the overall test time.

7. A test resource management method for non-functional testing according to claim 1, characterized in that: After predicting the test budget time required for the target test item, the method further includes: Determine the system type of the physical subsystem corresponding to the non-functional test item; wherein the system type includes an introduced system and a self-built system; In the case where the system type is the introduced system, determining that the non-functional test items need to be subjected to a verification test, and determining a verification test time corresponding to the verification test; The test budget time is updated according to the verification test time, so as to allocate corresponding test resources to the non-functional test items according to the updated test budget time.

8. A test resource management device for non-functional testing, characterized in that: The device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a test resource management method for non-functional testing as described in any one of claims 1-7.

9. A non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer executable instructions are configured to: A test resource management method for non-functional testing as described in any one of claims 1 to 7.

Images