Software testing system construction method and device and electronic equipment

Abstract

The invention discloses a construction method and device of a software testing system and electronic equipment. The method comprises the following steps: deploying an infrastructure; based on the infrastructure and insurance business requirements, constructing a specialized test capability system; and constructing a standardized test management system based on the infrastructure, the test maturity model integration and the insurance business requirements. According to the method, when a software test system is constructed, starting from two aspects of specialized test capability system construction and standardized test management system construction on the basis of deployed infrastructures, a full-life-cycle software test system is constructed in combination with insurance service requirements and internationally widely accepted test maturity model integration; the software testing efficiency in the field of insurance and finance is improved, and all-around coverage of tested content is achieved.

Description

Technical Field

[0001] This application belongs to the field of software testing technology, and in particular relates to a method, apparatus and electronic equipment for constructing a software testing system. Background Technology

[0002] In recent years, with the continuous deepening of financial system reforms, higher standards have been set for various sub-sectors, including the insurance industry. To ensure the high-quality and efficient delivery of insurance software products, a comprehensive testing system needs to be established.

[0003] Most existing software testing system construction methods are general-purpose and unsuitable for the insurance and finance industry. Therefore, the industry urgently needs a software testing system construction solution applicable to the insurance and finance sector. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus, and electronic device for constructing a software testing system, so as to solve the problem that the construction of software testing systems in related technologies cannot be applied to the insurance and financial industry.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions: In a first aspect, embodiments of this application provide a method for constructing a software testing system, comprising: deploying infrastructure; constructing a professional testing capability system based on the infrastructure and insurance business requirements; and constructing a standardized testing management system based on the infrastructure, integrated testing maturity model, and the insurance business requirements.

[0006] Secondly, embodiments of this application provide a software testing system construction apparatus, comprising: a deployment module for deploying infrastructure; a first construction module for constructing a professional testing capability system based on the infrastructure and insurance business requirements; and a second construction module for constructing a standardized testing management system based on the infrastructure, test maturity model integration, and the insurance business requirements.

[0007] Thirdly, embodiments of this application provide an electronic device, including: a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0008] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects: In constructing the software testing system, this application's embodiments, based on the deployed infrastructure, start from two aspects: building a professional testing capability system and a standardized testing management system. Combining insurance business needs with internationally recognized test maturity models, a full lifecycle software testing system is created, achieving improved software testing efficiency and comprehensive coverage of tested content in the insurance and financial field. Attached Figure Description

[0009] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A flowchart illustrating a method for constructing a software testing system according to an embodiment of this application; Figure 2 A schematic diagram illustrating the construction of a software testing system according to an embodiment of this application; Figure 3 A schematic diagram illustrating the construction of a specialized testing capability system provided in one embodiment of this application; Figure 4 A schematic diagram illustrating the construction of a standardized test management system provided in one embodiment of this application; Figure 5 A schematic diagram of a construction apparatus for a software testing system provided in one embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0010] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0011] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein. Furthermore, "and / or" in this application indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship. It should be noted that all data involved in this application was obtained with the user's authorization.

[0012] The technical solutions provided in the embodiments of this application are described in detail below with reference to the accompanying drawings.

[0013] Figure 1 This is a flowchart illustrating a method for constructing a software testing system, as provided in one embodiment of this application. Figure 1 As shown, the method for constructing a software testing system according to an embodiment of this application may specifically include the following steps: S101, deploying infrastructure.

[0014] In this embodiment, the execution entity of the software testing system construction method is a software testing system construction device, which can be located in an electronic device. This electronic device can be a terminal device or a server. The terminal device can be a mobile phone, tablet computer, desktop computer, laptop, in-vehicle device, etc.; the server can be a standalone server or a server cluster composed of multiple servers. For example, in the insurance business field, the software testing system construction device can be located in an insurance business software testing intelligent platform.

[0015] The construction of the entire software testing system relies on a sound continuous integration infrastructure. Therefore, the first step is to deploy the infrastructure required for the construction of the entire software testing system.

[0016] Among them, such as Figure 2 As shown, the deployed infrastructure may include, but is not limited to, at least one of the following: a Development Operations (DevOps) platform, a Continuous Integration / Continuous Delivery / Continuous Deployment (CI / CD) pipeline, testing tools, a testing environment, and a configuration management system.

[0017] DevOps is a set of methodologies and practices that enable rapid and reliable software delivery by facilitating collaboration, communication, and automated processes between development and operations teams.

[0018] S102, based on the needs of infrastructure and insurance business, builds a professional testing capability system.

[0019] In the embodiments of this application, such as Figure 2 As shown, the purpose of this application embodiment is to build a sensitive and stable dual-state software testing system suitable for the insurance industry, combining the two core directions of specialization and standardization to support and empower business development.

[0020] In terms of professional testing capabilities, based on the infrastructure deployed in step S101, a comprehensive professional testing capability system is built to meet the needs of insurance business, covering various functional and non-functional testing methods.

[0021] As a possible implementation method, such as Figure 2 , Figure 3 As shown, step S102 may specifically include the following steps: Based on infrastructure and insurance business needs, build at least one of the following specialized testing capabilities: unit testing capability, static code scanning capability, smoke testing capability, performance testing capability, automated testing capability, compatibility testing capability, chaos testing capability, and precision testing capability. Figure 2 , Figure 3 (not shown in the image) and AI (Artificial Intelligence) testing capabilities ( Figure 2 , Figure 3 (not shown in the image), etc.

[0022] Specifically, in terms of building professional testing capabilities, we should not only continue to strengthen conventional testing capabilities, such as unit testing, static code scanning, performance testing, automated testing, and compatibility testing, but also combine them with cutting-edge testing capabilities, such as smoke testing, chaos testing, precision testing, and intelligent AI testing, to comprehensively improve the depth and breadth of testing.

[0023] In terms of performance testing, a comprehensive overview of key system performance indicators is established. Through systematic performance monitoring and evaluation, the stability, response speed, and resource utilization of critical systems are ensured to reach optimal levels, providing a solid guarantee for the efficient operation of business.

[0024] In terms of automated testing, we take interface automation as the core and supplement it with UI automation of the main process, replay testing and AI testing, etc., to build a multi-level and multi-dimensional automated testing system to improve testing efficiency and coverage.

[0025] In terms of compatibility testing, the focus is on comprehensive coverage of key systems, especially domestically developed systems, to ensure their stable operation under different operating systems, browsers, devices and network environments, and to provide users with a consistent and smooth user experience.

[0026] In terms of chaos testing, we proactively inject hardware or software faults into application systems through an internal chaos testing platform to expose system weaknesses, develop optimization plans, and collaborate with R&D, testing, and operations departments to develop and promote emergency plans and the construction of observability capabilities.

[0027] In terms of platform support, it mainly relies on a unified DevOps collaborative development platform to achieve the digital transformation of the entire process test management system. This includes a project progress visualization management system based on agile development, a full lifecycle quality control system, and multi-dimensional performance indicator monitoring and analysis, which can effectively improve the traceability of the R&D process and the data support capability for management decisions.

[0028] Regarding efficiency improvements in tools, the main focus is on addressing the complex business characteristics of insurance, especially in core business processes such as underwriting, policy maintenance, and claims settlement. Traditional manual policy issuance methods are inefficient and carry a high risk of human error. This application's implementation develops a multi-channel, multi-scenario policy issuance tool platform to effectively support the needs of large-scale testing operations. For example... Figure 3 As shown, the order generation tool enables customized order generation across multiple channels, the general tool enables data anonymization, the business tool enables message conversion, and the version management tool enables version release.

[0029] In terms of test environment management, it is necessary to completely separate the R&D and test environments, fully control version changes of the test environment, and combine it with continuous integration to effectively improve delivery efficiency and quality.

[0030] Furthermore, such as Figure 2 As shown, the method for constructing a software testing system in this application embodiment may further include the following steps for constructing traditional functional testing capabilities: based on infrastructure and insurance business requirements, construct functional testing capabilities to establish and maintain a test case library and systematically manage test scenarios, test strategies, test resources and test risks, etc., to ensure comprehensive and efficient test coverage.

[0031] At the same time, it can standardize the management of test environment, artifacts, configurations, data and other assets to improve the standardization and reusability of the testing process.

[0032] Furthermore, such as Figure 2 As shown, the method for constructing a software testing system according to an embodiment of this application may further include the following steps for constructing testing capabilities: based on infrastructure and insurance business requirements, constructing at least one of the following testing capabilities: integration testing capability, system testing capability, and acceptance testing capability.

[0033] S103 establishes a standardized test management system based on infrastructure, test maturity model integration, and insurance business requirements.

[0034] In this embodiment of the application, regarding standardized test management, based on the infrastructure deployed in step S101, starting from the internationally recognized Test Maturity Model Integration (TMMi) test standard system, and combined with the actual business needs of the insurance industry, a scientific and standardized test standard system is formulated. That is, a standardized test management system is built vertically from top-level design to specific execution, and a quality control framework with mandatory binding force is established.

[0035] TMMi is a maturity model developed by the TMMi Foundation that is independent of any organization and is used to improve testing processes and assess an organization’s testing capabilities.

[0036] As a possible implementation method, such as Figure 2 As shown, the system under test can be evaluated and categorized from multiple dimensions such as business importance, system characteristics, and resource allocation. Three testing modes—authorized testing mode, pre-testing mode, and third-party testing mode—can be established to adapt to various application systems. For each testing mode, detailed work guidelines and operating procedures must be developed to ensure the standardization and executability of the testing process.

[0037] Correspondingly, such as Figure 4 As shown, step S103 may specifically include the following steps: Based on infrastructure, test maturity model integration, and insurance business requirements, set access standards and exit standards at different nodes in the entire software development lifecycle (including requirements analysis, design, development, testing, and production). The access standards include at least one of the following standards: pre-test access standards, authorized test access standards, and third-party test access standards.

[0038] Specifically, in terms of implementation and follow-up, a three-pronged approach is adopted: authorization, pre-implementation, and third-party collaboration. Entry and exit criteria are set at different stages of the software development lifecycle (including requirements analysis, design, development, testing, and deployment). Entry criteria vary depending on the model and agility / stability requirements, primarily in the number of testing rounds and deliverables. Exit criteria, regardless of the model, adhere to a relatively unified and rigorous standard, covering multiple dimensions such as code quality, functional completeness, test coverage, performance standards, compatibility standards, and business acceptance assessment, thus controlling the quality checkpoint before system deployment.

[0039] Furthermore, such as Figure 4As shown, step S103 may specifically include the following steps: Based on infrastructure, test maturity model integration, and insurance business requirements, construct a Deming cycle (Plan-Do-Check-Act, abbreviated as PDCA) management process. The Deming cycle management process includes test plan formulation, test plan implementation, test plan follow-up, and test plan review.

[0040] The PDCA cycle is a scientific work procedure that achieves continuous improvement and optimization of work through the repeated cycles of four stages: Plan, Do, Check, and Act.

[0041] Furthermore, taking the typical case of inserting an urgent requirement as an example, step S103 may specifically include the following steps: when formulating the test plan, for foreseeable urgent requirements, standardize the requirement scheduling stage in the entire software development life cycle to avoid inserting foreseeable urgent requirements; for unforeseeable urgent requirements, preset a dynamic resource pool with a target proportion in the test resource planning to promptly accept unforeseeable urgent requirements.

[0042] Specifically, in terms of process management, it is necessary to clearly define and categorize development plans, test plans, routine requirements, and emergency requirements, forming a standardized PDCA management system to minimize frequent adjustments to the schedule. Taking the typical case of emergency requirement insertion as an example, for foreseeable emergency requirements, the requirement scheduling stage throughout the entire software development lifecycle can be standardized, fully referencing historical key business scenarios to reduce emergency requirements inserted due to insufficient human consideration. A multi-level approval system should be established to raise the threshold for inserting emergency requirements, thereby avoiding the insertion of foreseeable emergency requirements. For unforeseeable emergency requirements, a flexible manpower capacity management mechanism should be established, with a target proportion (e.g., approximately 20%) of a dynamic resource pool preset in the (e.g., monthly) test resource planning to accommodate high-priority, unforeseeable emergency requirements at any time.

[0043] Furthermore, such as Figure 4 As shown, step S103 may specifically include the following steps: based on at least one of the following dimensions: project, personnel and organization, and using at least one of the following indicators: quality indicators, schedule indicators and efficiency indicators, to measure the implementation status of each stage of the software development life cycle, and optimize the test plan implementation process based on the measurement results.

[0044] Specifically, in terms of implementation measurement, a digital measurement system covering the entire value chain can be established based on the methodology of the testing process improvement. This system measures the implementation status of each stage of the software development lifecycle (e.g., requirements, development, and testing phases) from multiple dimensions, including project, personnel, and organization. A monthly review mechanism should be implemented to closely monitor fluctuations in key indicators (e.g., quality, schedule, and performance indicators), revealing potential problems and highlights through data analysis. Based on this dynamic information, strategies can be flexibly adjusted, targeted improvement measures implemented, and timely feedback provided to stakeholders to ensure the project progresses steadily towards its established goals. Through a continuous cycle of monitoring and feedback, processes can be continuously optimized, efficiency improved, and the high-quality completion of the project ensured.

[0045] It should be noted that in order to ensure the software testing system is implemented as expected, it is also necessary to recruit various talents, such as testing technology experts, testing business experts, and insurance business experts.

[0046] In summary, the software testing system construction method of this application, based on the deployed infrastructure, focuses on two aspects: building a professional testing capability system and a standardized testing management system. It integrates insurance business needs with internationally recognized test maturity models to create a full lifecycle software testing system, achieving improved software testing efficiency and comprehensive coverage of tested content in the insurance and financial sector. Regarding professional testing capability construction, it continuously strengthens conventional testing capabilities while incorporating cutting-edge testing capabilities, comprehensively enhancing the depth and breadth of testing. In traditional functional testing, it establishes and maintains a test case library and systematically manages test scenarios, test strategies, test resources, and test risks, ensuring comprehensive and efficient test coverage. It establishes three testing modes—authorization, pre-testing, and third-party testing—to adapt to various application systems. Through the cyclical implementation of the PDCA (Plan-Do-Check-Act) cycle, continuous improvement and optimization are achieved. Standardized PDCA management based on urgent needs minimizes frequent adjustments to scheduling plans. Regular reviews allow for flexible strategy adjustments, implementation of targeted improvement measures, increased efficiency, and ensure high-quality project completion.

[0047] This application also provides an apparatus for constructing a software testing system. For example... Figure 5 As shown, the software testing system construction apparatus 500 of this application embodiment may specifically include: a deployment module 501, a first construction module 502, and a second construction module 503. Wherein: Deployment module 501 is used to deploy infrastructure.

[0048] The first building module 502 is used to build a professional testing capability system based on infrastructure and insurance business needs.

[0049] The second building module 503 is used to build a standardized test management system based on infrastructure, test maturity model integration, and insurance business requirements.

[0050] In the embodiments of this application, the specific process by which each module implements its function can be found in the relevant description of any of the above-mentioned software testing system construction method embodiments, and will not be repeated here.

[0051] The software testing system construction apparatus of this application, when constructing the software testing system, focuses on two aspects based on the deployed infrastructure: the construction of a professional testing capability system and a standardized testing management system. It integrates insurance business needs with internationally recognized test maturity models to create a full lifecycle software testing system, achieving improved software testing efficiency and comprehensive coverage of tested content in the insurance and financial sector. Regarding the construction of professional testing capabilities, it continuously strengthens conventional testing capabilities while incorporating cutting-edge testing capabilities, comprehensively enhancing the depth and breadth of testing. In terms of traditional functional testing, it establishes and maintains a test case library and systematically manages test scenarios, test strategies, test resources, and test risks, ensuring comprehensive and efficient test coverage. It establishes three testing modes: authorization, pre-testing, and third-party testing, adaptable to various application systems. Through the cyclical implementation of the PDCA (Plan-Do-Check-Act) cycle, continuous improvement and optimization are achieved. Standardized PDCA management based on urgent needs minimizes frequent adjustments to scheduling plans. Regular reviews allow for flexible strategy adjustments, implementation of targeted improvement measures, increased efficiency, and ensure high-quality project completion.

[0052] This application also provides an electronic device. For example... Figure 6 As shown, the electronic device 600 can vary considerably due to differences in configuration or performance. It may include one or more processors 601 and memory 602, with memory 602 storing one or more programs or instructions. Memory 602 may be temporary or permanent storage. The program stored in memory 602 may include one or more modules (not shown), each module including a series of computer-executable instructions for the electronic device 600. Furthermore, processor 601 may be configured to communicate with memory 602, executing the series of programs or computer-executable instructions in memory 602 on the electronic device 600. The electronic device 600 may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input / output interfaces 605, and one or more keyboards 606.

[0053] Specifically, in the embodiments of this application, the electronic device includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor. When the program or instructions are executed by the processor, they implement the steps of any of the above-described software testing system construction method embodiments.

[0054] The electronic devices in this application, when constructing a software testing system, focus on two aspects based on the deployed infrastructure: building a professional testing capability system and a standardized testing management system. Integrating insurance business needs with internationally recognized test maturity models, a full lifecycle software testing system is created, achieving improved software testing efficiency and comprehensive coverage of tested content in the insurance and financial sector. Regarding the construction of professional testing capabilities, conventional testing capabilities are continuously strengthened, while cutting-edge testing capabilities are incorporated, comprehensively enhancing the depth and breadth of testing. In terms of traditional functional testing, a test case library is established and maintained, and test scenarios, test strategies, test resources, and test risks are systematically managed, ensuring comprehensive and efficient test coverage. Three testing modes—authorization, pre-launch, and third-party—are established to adapt to various application systems. Through the cyclical implementation of the PDCA (Plan-Do-Check-Act) cycle, continuous improvement and optimization are achieved. Standardized PDCA management based on urgent needs minimizes frequent adjustments to scheduling plans. Regular reviews allow for flexible strategy adjustments, implementation of targeted improvement measures, increased efficiency, and ensure high-quality project completion.

[0055] This application also proposes a readable storage medium storing one or more computer programs or instructions that, when executed by a processor in an electronic device, enable the processor in the electronic device to perform the steps of any of the above-described software testing system construction method embodiments.

[0056] The readable storage medium in this application embodiment, when constructing a software testing system, focuses on two aspects based on the deployed infrastructure: building a professional testing capability system and a standardized testing management system. It integrates insurance business needs with internationally recognized test maturity models to create a full lifecycle software testing system, achieving improved software testing efficiency and comprehensive coverage of tested content in the insurance and financial sector. Regarding the construction of professional testing capabilities, it continuously strengthens conventional testing capabilities while incorporating cutting-edge testing capabilities, comprehensively enhancing the depth and breadth of testing. In terms of traditional functional testing, it establishes and maintains a test case library and systematically manages test scenarios, test strategies, test resources, and test risks, ensuring comprehensive and efficient test coverage. It establishes three testing modes: authorization, pre-launch, and third-party, adaptable to various application systems. Through the cyclical implementation of the PDCA (Plan-Do-Check-Act) cycle, continuous improvement and optimization are achieved. Standardized PDCA management based on urgent needs minimizes frequent adjustments to scheduling plans. Regular reviews allow for flexible strategy adjustments, implementation of targeted improvement measures, increased efficiency, and ensure high-quality project completion.

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

[0058] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0059] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0060] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0061] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0062] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0064] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0065] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0066] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

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

[0068] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0069] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for constructing a software testing system, characterized in that, include: Deploy infrastructure; Based on the aforementioned infrastructure and insurance business needs, a professional testing capability system will be built; Based on the aforementioned infrastructure, test maturity model integration, and insurance business requirements, a standardized test management system is constructed.

2. The method according to claim 1, characterized in that, Based on the aforementioned infrastructure and insurance business requirements, a professional testing capability system is constructed, including: Based on the aforementioned infrastructure and the insurance business requirements, at least one of the following specialized testing capabilities shall be constructed: unit testing capability, static code scanning capability, smoke testing capability, performance testing capability, automated testing capability, compatibility testing capability, chaos testing capability, precision testing capability, and intelligent artificial intelligence testing capability.

3. The method according to claim 1, characterized in that, Also includes: Based on the aforementioned infrastructure and insurance business requirements, functional testing capabilities are built to establish and maintain a test case library and to systematically manage test scenarios, test strategies, test resources, and test risks. Based on the infrastructure and the insurance business requirements, at least one of the following testing capabilities shall be constructed: integration testing capability, system testing capability, and acceptance testing capability.

4. The method according to claim 1, characterized in that, Based on the aforementioned infrastructure, test maturity model integration, and insurance business requirements, a standardized test management system is constructed, including: Based on the infrastructure, the test maturity model integration, and the insurance business requirements, admission and exit criteria are set at different nodes in the software development lifecycle. The admission criteria include at least one of the following criteria: pre-test admission criteria, authorized test admission criteria, and third-party test admission criteria.

5. The method according to claim 1, characterized in that, Based on the aforementioned infrastructure, test maturity model integration, and insurance business requirements, a standardized test management system is constructed, including: Based on the aforementioned infrastructure, the integration of the test maturity model, and the insurance business requirements, a Deming Cycle management process is constructed, which includes test plan development, test plan implementation, test plan follow-up, and test plan review.

6. The method according to claim 5, characterized in that, The construction of a standardized test management system based on the aforementioned infrastructure, test maturity model integration, and insurance business requirements also includes: When formulating the test plan, for foreseeable urgent needs, the requirement scheduling stage in the entire software development lifecycle should be standardized to avoid the insertion of foreseeable urgent needs. For unforeseen emergency needs, a dynamic resource pool with a target proportion is preset in the test resource planning to promptly accommodate such unforeseen emergency needs.

7. The method according to claim 1, characterized in that, Based on the aforementioned infrastructure, test maturity model integration, and insurance business requirements, a standardized test management system is constructed, including: Based on at least one of the following dimensions: project, personnel, and organization, and using at least one of the following indicators: quality indicators, schedule indicators, and performance indicators, the implementation status of each stage of the software development lifecycle is measured, and the test plan implementation process is optimized based on the measurement results.

8. The method according to claim 1, characterized in that, The infrastructure includes at least one of the following: The platform develops an integrated operations and maintenance platform, a continuous integration delivery and deployment pipeline, testing tools, testing environments, and configuration management systems.

9. A device for constructing a software testing system, characterized in that, include: The deployment module is used to deploy infrastructure; The first building module is used to build a professional testing capability system based on the aforementioned infrastructure and insurance business needs; The second building module is used to build a standardized test management system based on the infrastructure, test maturity model integration, and insurance business requirements.

10. An electronic device, characterized in that, include: A processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as claimed in any one of claims 1-8.

Images