Software testing method and equipment for photovoltaic system
By setting monitoring nodes and analyzing operating information in the photovoltaic system software, the problem of poor testing results in the existing technology is solved, and more efficient and reliable software testing is achieved.
Patent Information
- Application Number
- CN202510227305.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-27
- Publication Date
- 2025-06-13
AI Technical Summary
Existing photovoltaic system software testing methods rely on artificial black box testing, resulting in poor test results and it is difficult to detect random events and vulnerabilities in the software.
By obtaining the two-dimensional architecture portrait of the photovoltaic system software, select the corresponding control process template from the control process template for each business logic, set up the monitoring node of the functional module, monitor the operation information, and parse and verify to obtain the test results.
It improves the accuracy and reliability of the test, and can more fully expose the logical blind spots and vulnerabilities in the software, ensuring the stability of the software under different scenarios and conditions.
Smart Images
Figure CN120144459A_ABST
Abstract
Description
Technical Field
[0001] This application mainly relates to the technical field of software testing, and particularly relates to a software testing method and device for a photovoltaic system. Background Art
[0002] Currently, the software in a photovoltaic system is usually tested by the manual black box testing method. For example, by manually operating to compare whether the input parameters and output parameters of the software under test in a certain test environment can meet the actual requirements. However, due to the limited number of manual operations, the discovery rate of various random events of the software under test by this testing method is low, there is a problem that some loopholes cannot be detected, and the testing effect is not good. Summary of the Invention
[0003] The purpose of this application is to provide a software testing method and device for a photovoltaic system, which is used to solve the technical problem of poor testing effect in the prior art.
[0004] In a first aspect, this application provides a software testing method for a photovoltaic system, including:
[0005] Obtain a two-dimensional architecture portrait of the software under test in the photovoltaic system, where the two-dimensional architecture portrait includes: multiple business logics and multiple function modules of the software under test, and the association relationships between the multiple business logics and the multiple function modules;
[0006] For each business logic, select the control flow template corresponding to the business logic from the control flow template set, and set monitoring nodes for each function module associated with the business logic according to the control flow template, and use the monitoring nodes to monitor the running information of each function module associated with the business logic;
[0007] Analyze and verify each piece of monitored running information to obtain the test result of the corresponding business logic.
[0008] In some embodiments, the control flow template includes a closed-loop control flow template and an open-loop control flow template; where:
[0009] The closed-loop control flow template corresponds to a scenario where there is at least one closed loop between multiple function modules associated with the business logic;
[0010] The open-loop control flow template corresponds to a scenario where there is no closed loop between multiple function modules associated with the business logic.
[0011] In some embodiments, setting monitoring nodes for each function module associated with the business logic according to the control flow template includes any one or combination of the following:
[0012] Set monitoring nodes at the output interfaces of each function module;
[0013] Set monitoring nodes at the input interfaces of each functional module; and,
[0014] Set monitoring nodes in the internal programs of each functional module.
[0015] In some embodiments, use monitoring nodes to monitor the running information of each functional module associated with the business logic, including:
[0016] Obtain the data sources of the business logic, where the data sources include data sources obtained from the virtual interfaces and / or physical interfaces of the software under test;
[0017] Generate the business operation process of the business logic according to the connection relationship between the data sources and the multiple functional modules associated with the business logic;
[0018] Use monitoring nodes to monitor the business operation process and obtain the running information of each functional module associated with the business logic.
[0019] In some embodiments, using monitoring nodes to monitor the business operation process includes:
[0020] Randomly simulate the fault environment of the business operation process;
[0021] Use monitoring nodes and / or custom monitoring probes to monitor the business operation process and obtain the running information of each functional module associated with the business logic in the fault environment.
[0022] In some embodiments, parsing includes standard protocol parsing and / or custom protocol parsing;
[0023] Verification includes mechanism verification and / or data verification, where mechanism verification is used to verify the event occurrence of each functional module in the business operation process, and data verification is used to verify the running information of each functional module in the business operation process.
[0024] In some embodiments, after parsing and verifying each monitored running information to obtain the test results of the corresponding business logic, it further includes:
[0025] Combine the test results of multiple business logics according to the connection relationship between the business logics to obtain the global test results of the software under test.
[0026] In a second aspect, the present application provides a software testing device for a photovoltaic system, including:
[0027] An acquisition module, configured to acquire a two-dimensional architecture portrait of the software under test in the photovoltaic system, where the two-dimensional architecture portrait includes: multiple business logics and multiple functional modules of the software under test, as well as the association relationships between the multiple business logics and the multiple functional modules;
[0028] A monitoring module, which is configured to select, for each business logic, a control flow template corresponding to the business logic from a control flow template set, and set monitoring nodes for each functional module associated with the business logic according to the control flow template, and monitor the operation information of each functional module associated with the business logic by using the monitoring nodes;
[0029] A testing module, which is configured to parse and verify each piece of monitored operation information to obtain a test result of the corresponding business logic.
[0030] In a third aspect, the present application provides an electronic device, including a memory and a processor. Instructions are stored in the memory. When the instructions are called by the processor, the processor is caused to execute the method according to any one of the above first aspects.
[0031] In a fourth aspect, the present application provides a storage medium, including computer program instructions, and the computer program instructions are used to cause a computer to execute the method according to any one of the above first aspects.
[0032] Compared with the prior art, the present application has the following advantages:
[0033] The present application provides a software testing method and device for a photovoltaic system. By monitoring the operation information of each functional module associated with each business logic, the testing process can pay attention to more logical dead corners and vulnerabilities in the software to be tested, and fully expose the problems that may occur in the software to be tested under different scenarios and conditions. At the same time, by setting monitoring nodes for specific functional modules, the problems found can be accurately located, thereby improving the accuracy and reliability of the test results. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Including the drawings is to provide a further understanding of the present application. They are incorporated and constitute a part of the present application. The drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the drawings:
[0035] Figure 1 Exemplarily shows a flowchart of a software testing method for a photovoltaic system;
[0036] Figure 2 Exemplarily shows a schematic diagram of a two-dimensional architecture portrait;
[0037] Figure 3 Exemplarily shows a schematic diagram of a closed-loop control flow template;
[0038] Figure 4 Exemplarily shows a schematic diagram of an open-loop control flow template
[0039] Figure 5 Exemplarily shows a schematic diagram of implanting a monitoring probe;
[0040] Figure 6 An exemplary schematic diagram of a software testing device for a photovoltaic system is shown;
[0041] Figure 7 An exemplary schematic diagram of an electronic device is shown. Detailed implementation manners
[0042] To more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the accompanying drawings required for the description of the embodiments. Obviously, the accompanying drawings in the following description are only some examples or embodiments of the present application. For those of ordinary skill in the art, without creative efforts, the present application can also be applied to other similar scenarios based on these drawings. Unless obvious from the language context or otherwise stated, the same reference numerals in the drawings represent the same structure or operation.
[0043] As shown in the present application and the claims, unless the context clearly indicates an exception, words such as "a", "an", "one" and / or "the" are not specifically singular and may also include plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the clearly identified steps and elements, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.
[0044] In addition, it should be noted that the use of words such as "first" and "second" to limit components is only for the convenience of distinguishing the corresponding components. Without further declaration, the above words have no special meaning, so it cannot be understood as a limitation on the protection scope of the present application. In addition, although the terms used in the present application are selected from well-known and commonly used terms, some of the terms mentioned in the description of the present application may be selected by the applicant according to his or her judgment, and their detailed meanings are described in the relevant parts of this description. In addition, it is required to understand the present application not only through the actual terms used, but also through the meaning implied by each term.
[0045] In this embodiment, the "photovoltaic system" refers to a photovoltaic electric control system equipped with software or that can be controlled by software. For example, a tracking bracket, etc., and there is no limitation on this.
[0046] See Figure 1 , a flowchart of a software testing method for a photovoltaic system is shown, including:
[0047] S101, obtaining a two-dimensional architecture portrait of the software to be tested in the photovoltaic system.
[0048] Among them, the software to be tested is, for example, embedded software in the photovoltaic system.
[0049] The two-dimensional architecture portrait includes multiple business logics and multiple functional modules of the software to be tested, as well as the association relationships between the multiple business logics and the multiple functional modules.
[0050] In some embodiments, the two-dimensional architecture portrait can be in the form of a table. Refer to Figure 2 , which shows a schematic diagram of a two-dimensional architecture portrait. The first row in the two-dimensional architecture portrait shows 6 business logics of the software to be tested, namely: Business A, Business B... Business F. The first column in the two-dimensional architecture portrait shows 11 functional modules, namely: Functional Module 1, Functional Module 2... Functional Module 11.
[0051] Among them, "√" indicates that there is an association relationship between the corresponding business logic and the functional module. For example, there is an association relationship between Business A and Functional Module 2, Functional Module 5, and Functional Module 6. There is an association relationship between Business B and Functional Module 4, Functional Module 7, and Functional Module 9.
[0052] S102, for each business logic, select the control flow template corresponding to the business logic from the control flow template set, and set monitoring nodes for each functional module associated with the business logic according to the control flow template, and use the monitoring nodes to monitor the running information of each functional module associated with the business logic.
[0053] In some embodiments, the control flow template includes a closed-loop control flow template and an open-loop control flow template; where: the closed-loop control flow template corresponds to the scenario where there is at least one closed loop among multiple functional modules associated with the business logic. The open-loop control flow template corresponds to the scenario where there is no closed loop among multiple functional modules associated with the business logic.
[0054] For example, when the business logic can perform real-time rectification, correction, or compensation on the overall business by introducing external parameters, the closed-loop control flow template can be adopted. Refer to Figure 3 , which shows a schematic diagram of a closed-loop control flow template. In this closed-loop control flow template, the multiple functional modules associated with the business logic include: a correction module, a control arbitration, a controlled object, a feedback element, and a measurement element. Among them, the control arbitration, the controlled object, and the feedback element form a closed loop. The correction module, the control arbitration, the controlled object, and the measurement element form a closed loop.
[0055] Also, for example, when the input of the business logic is not affected by the output, the open-loop control flow template can be adopted. Refer to Figure 4 , which shows a schematic diagram of an open-loop control flow template. In this open-loop control flow template, the multiple functional modules associated with the business logic include: a control arbitration and a controlled object.
[0056] In some embodiments, monitoring nodes are set for each functional module associated with the service logic according to the control flow template, including any one or combination of the following:
[0057] Set monitoring nodes at the output interface of each functional module;
[0058] Set monitoring nodes at the input interface of each functional module; and,
[0059] Set monitoring nodes in the internal program of each functional module.
[0060] Exemplarily, assuming the service logic is to rotate the photovoltaic support to a specified angle according to the sun angle, and this service logic adopts a closed-loop control flow template, then monitoring nodes can be set at the output interface, input interface, and / or internal program of the calibration module, control arbitration, controlled object, feedback element, and measurement element, so as to monitor the respective operation information of the calibration module, control arbitration, controlled object, feedback element, and measurement element. Among them, the operation information is the data to be monitored for the corresponding functional module. For example, the operation information of the calibration module may include the time, longitude and latitude provided by the GPS module, and the comparison between the current support angle provided by the inclinometer module and the target angle obtained by the control arbitration. The operation information of the control arbitration may include the target angle of the support provided by the astronomical algorithm module and the motor speed obtained by the motor drive module. The operation information of the controlled object may include the motor state. The operation information of the feedback element may include the motor current measurement module, that is, the motor speed. The operation information of the measurement element may include the current angle of the support provided by the inclinometer module and the motor rotation result, including the angle and speed.
[0061] Another example, assuming the service logic is to control the working mode of the support through the NCU, and this service logic adopts an open-loop control flow template, then monitoring nodes can be set at the output interface, input interface, and / or internal program of the control arbitration and the controlled object to monitor the operation information. Among them, the operation information of the control arbitration may include, for example, the host computer command and the specific control information obtained after the NCU-host computer protocol processing module parses the command. The operation information of the controlled object may include, for example, the working state of the TCU, and there is no limitation to this.
[0062] Based on the above method, in this embodiment, monitoring nodes can be set in each functional module in depth, so as to be able to grasp the real-time situation of the service logic during the intermediate operation process and facilitate accurate problem positioning.
[0063] In some embodiments, monitoring nodes are used to monitor the operation information of each functional module associated with the service logic, including:
[0064] Obtain the data source of the service logic, where the data source includes the data sources obtained from the virtual interface and / or physical interface of the software under test;
[0065] Generate the business operation process of the business logic according to the connection relationship between multiple functional modules associated with the data source and the business logic;
[0066] Use a monitoring node to monitor the business operation process and obtain the operation information of each functional module associated with the business logic.
[0067] Among them, the virtual interface is, for example, a virtual interface recognizable by a computer such as RS232, RS485, TCP / UDP, UART, etc. The physical interface is, for example, a communication conversion line, such as a UART to USB line, etc., and there is no limitation on this.
[0068] In some embodiments, using a monitoring node to monitor the business operation process includes:
[0069] Randomly simulate the fault environment of the business operation process;
[0070] Use a monitoring node and / or a custom monitoring probe to monitor the business operation process and obtain the operation information of each functional module associated with the business logic in the fault environment.
[0071] Among them, randomly simulating the fault environment of the business operation process is, for example, introducing a random quantity at a random node in the business operation process. For example, randomly delay the input quantity or feedback quantity of a certain closed loop, or use garbled characters for replacement. It can also be to interfere with the process of the software under test by means of data concurrency, etc., so as to verify the robustness of the software under test.
[0072] The monitoring probe can be implanted at a position customized by the user. For example, see Figure 5 , which shows a schematic diagram of implanting a monitoring probe. The monitoring probe is set between the control arbitration and the controlled object according to actual needs and is used to monitor the wireless communication data received via the TCU.
[0073] S103, Parse and verify each piece of monitored operation information to obtain the test result of the corresponding business logic.
[0074] In some embodiments, parsing includes standard protocol parsing and / or custom protocol parsing;
[0075] Verification includes mechanism verification and / or data verification, where mechanism verification is used to verify the event occurrence of each functional module in the business operation process, and data verification is used to verify the operation information of each functional module in the business operation process.
[0076] Standard protocol parsing is, for example, ModBusRTU, ModBusTCP, CAN bus, etc. The original values of the corresponding monitoring parameters within the data packet can be parsed through the specified protocol. For custom protocols, the user needs to specify the positions of the monitoring parameters within the data packet, and there are no restrictions on this.
[0077] The occurrence of events, for example, refers to whether a functional module executes a specified task, or whether a functional module sends specified data, etc. If a specified event occurs in a certain functional module, it can indicate that the functional module passes the mechanism verification; otherwise, it fails. Verification of operation information, for example, refers to whether the operation information of the verification functional module conforms to the specified value or meets the specified requirements. If the operation information of a certain functional module meets the requirements, the functional module passes the data verification; otherwise, it fails.
[0078] In some embodiments, after parsing and verifying each piece of monitored operation information to obtain the test results of the corresponding business logic, it further includes:
[0079] Combining the test results of multiple business logics according to the connection relationships between the business logics to obtain the global test result of the software under test.
[0080] The connection relationships between business logics are, for example, parallel, progressive, synchronous, asynchronous, etc. Combining the test results of multiple business logics can obtain the global test result, which is convenient for overall evaluation of the test results at the software level.
[0081] See Figure 6 , which shows a software testing device for a photovoltaic system, including an acquisition module 601, a monitoring module 602, and a testing module 603; where:
[0082] The acquisition module 601 is used to acquire the two-dimensional architecture portrait of the software under test in the photovoltaic system, where the two-dimensional architecture portrait includes: multiple business logics and multiple functional modules of the software under test, as well as the association relationships between multiple business logics and multiple functional modules;
[0083] The monitoring module 602 is used to, for each business logic, select the control flow template corresponding to the business logic from the control flow template set, and set the monitoring nodes of each functional module associated with the business logic according to the control flow template, and monitor the operation information of each functional module associated with the business logic using the monitoring nodes;
[0084] The testing module 603 is used to parse and verify each piece of monitored operation information to obtain the test results of the corresponding business logic.
[0085] In some embodiments, the monitoring module 602 is used to perform any one or combination of the following:
[0086] Set monitoring nodes at the output interfaces of each functional module;
[0087] Set monitoring nodes at the input interfaces of each functional module; and,
[0088] Set monitoring nodes in the internal programs of each functional module.
[0089] In some embodiments, the monitoring module 602 is used for:
[0090] Obtain the data sources of the business logic, where the data sources include the data sources obtained from the virtual interfaces and / or physical interfaces of the software under test;
[0091] Generate the business operation process of the business logic according to the connection relationships between multiple functional modules associated with the data sources and the business logic;
[0092] Monitor the business operation process using the monitoring nodes to obtain the operation information of each functional module associated with the business logic.
[0093] In some embodiments, the monitoring module 602 is used for:
[0094] Randomly simulate the fault environment of the business operation process;
[0095] Monitor the business operation process using the monitoring nodes and / or custom monitoring probes to obtain the operation information of each functional module associated with the business logic in the fault environment.
[0096] In some embodiments, the testing module 603 is further used for:
[0097] Combine the test results of multiple business logics according to the connection relationships between the business logics to obtain the global test result of the software under test.
[0098] Furthermore, as Figure 7 , an exemplary embodiment of the present application further provides an electronic device, including a memory 701 and a processor 702. Instructions are stored in the memory 701, and when the instructions are executed by the processor 702, the processor 702 executes the method according to any item in the first aspect.
[0099] It should be understood that the processor mentioned in the embodiments of the present application may be a CPU, or may also be other general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0100] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronous link dynamic random access memory, and direct memory bus random access memory.
[0101] The present application also provides a storage medium storing computer program instructions, which, when executed by a processor of a computer, cause the computer to perform the steps of any of the methods mentioned above.
[0102] A computer-readable medium may include a propagated data signal having computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take many forms, including electromagnetic, optical, and the like, or any suitable combination thereof. The computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which can be connected to an instruction execution system, apparatus, or device to effect communication, propagation, or transmission for use of the program. The program code located on the computer-readable medium may be propagated through any appropriate medium, including radio, cable, fiber optic cable, radio frequency signal, or similar media, or any combination of the foregoing.
[0103] The basic concepts have been described above. Obviously, for those skilled in the art, the above invention disclosure is only an example and does not constitute a limitation to the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and corrections to the present application. Such modifications, improvements, and corrections are proposed in the present application, so such modifications, improvements, and corrections still fall within the spirit and scope of the exemplary embodiments of the present application.
[0104] Meanwhile, this application uses specific terms to describe the embodiments of this application. For example, "an embodiment", "one embodiment", and / or "some embodiments" mean a certain feature, structure, or characteristic related to at least one embodiment of this application. Therefore, it should be emphasized and noted that the "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more at different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this application can be appropriately combined.
[0105] Some aspects of this application can be executed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above-mentioned hardware or software can all be referred to as "data blocks", "modules", "engines", "units", "components", or "systems". The processor can be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. In addition, aspects of this application may be embodied as a computer product located in one or more computer-readable media, which includes computer-readable program code. For example, the computer-readable medium may include, but is not limited to, magnetic storage devices (such as hard disks, floppy disks, magnetic tapes...), optical discs (such as compact discs CD, digital versatile discs DVD...), smart cards, and flash memory devices (such as cards, sticks, key drives...).
[0106] The computer-readable medium may contain a propagated data signal containing computer program code, such as on a baseband or as part of a carrier wave. This propagated signal may have various forms of representation, including electromagnetic form, optical form, etc., or a suitable combination of forms. The computer-readable medium can be any computer-readable medium other than a computer-readable storage medium, which can be connected to an instruction execution system, apparatus, or device to achieve communication, propagation, or transmission for use of the program. The program code located on the computer-readable medium can be propagated through any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar media, or any combination of the above media.
[0107] Similarly, it should be noted that, in order to simplify the presentation of this application disclosure and thus help the understanding of one or more embodiments of the invention, in the foregoing description of the embodiments of this application, sometimes multiple features are merged into one embodiment, drawing, or description thereof. However, this disclosure method does not mean that the features required by the object of this application are more than those mentioned in the claims. In fact, the features of the embodiment are less than all the features of the single embodiment disclosed above.
[0108] In some embodiments, numbers are used to describe components and the quantity of attributes. It should be understood that such numbers used in the description of embodiments are, in some examples, modified by the modifiers "about", "approximately" or "substantially". Unless otherwise specified, "about", "approximately" or "substantially" indicate that the said numbers allow a variation of ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may vary according to the characteristics required by individual embodiments. In some embodiments, the numerical parameters should consider the specified significant digits and adopt the method of retaining the general number of digits. Although the numerical ranges and parameters used in some embodiments of the present application to confirm the breadth of their scope are approximate values, in specific embodiments, such numerical settings are made as precise as possible within the feasible range.
[0109] Although the present application has been described with reference to the current specific embodiments, those of ordinary skill in the art should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions can be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the scope of the spirit of the present application, they will fall within the scope of the claims of the present application.
Claims
1. A software testing method for a photovoltaic system, characterized in that: include: Acquire a two-dimensional architecture portrait of the software to be tested in the photovoltaic system, wherein the two-dimensional architecture portrait includes: multiple business logics and multiple functional modules of the software to be tested, and associations between the multiple business logics and the multiple functional modules; For each of the business logics, a control process template corresponding to the business logic is selected from a control process template set, and a monitoring node of each of the functional modules associated with the business logic is set according to the control process template, and the monitoring node is used to monitor the operation information of each of the functional modules associated with the business logic; Analyze and verify each of the monitored operation information to obtain the corresponding test results of the business logic.
2. The method according to claim 1, characterized in that The control process template includes a closed-loop control process template and an open-loop control process template; wherein: The closed-loop control process template corresponds to a scenario where there is at least one closed loop between the multiple functional modules associated with the business logic; The open-loop control process template corresponds to a scenario where there is no closed loop between the multiple functional modules associated with the business logic.
3. The method according to claim 2, characterized in that The setting of the monitoring node for each of the functional modules associated with the business logic according to the control process template includes any one or combination of the following: Setting the monitoring node at the output interface of each functional module; The monitoring node is set at the input interface of each functional module; and The monitoring node is set in the internal program of each of the functional modules.
4. The method according to claim 1, characterized in that The adopting the monitoring node to monitor the operation information of each functional module associated with the business logic includes: Acquire the data source of the business logic, wherein the data source includes a data source obtained from a virtual interface and / or a physical interface of the software to be tested; Generate a business operation process of the business logic according to the connection relationship between the data source and multiple functional modules associated with the business logic; The monitoring node is used to monitor the business operation process to obtain the operation information of each functional module associated with the business logic.
5. The method according to claim 4, characterized in that The adopting the monitoring node to monitor the business operation process includes: Randomly simulate the failure environment of the business operation process; The monitoring node and / or the customized monitoring probe are used to monitor the business operation process to obtain the operation information of each functional module associated with the business logic in the fault environment.
6. The method according to claim 4, characterized in that The analysis includes standard protocol analysis and / or custom protocol analysis; The verification includes mechanism verification and / or data verification, wherein the mechanism verification is used to verify the event occurrence of each functional module in the business operation process, and the data verification is used to verify the operation information of each functional module in the business operation process.
7. The method according to claim 1, characterized in that After parsing and verifying each of the monitored operation information and obtaining the corresponding test result of the business logic, the process further includes: The test results of each of the plurality of business logics are combined according to the connection relationship between the business logics to obtain a global test result of the software to be tested.
8. A software testing device for a photovoltaic system, characterized in that: include: An acquisition module is used to acquire a two-dimensional architecture portrait of the software to be tested in the photovoltaic system, wherein the two-dimensional architecture portrait includes: multiple business logics and multiple functional modules of the software to be tested, and associations between the multiple business logics and the multiple functional modules; A monitoring module, for selecting, for each of the business logics, a control flow template corresponding to the business logic from a control flow template set, and setting a monitoring node for each of the functional modules associated with the business logic according to the control flow template, and using the monitoring node to monitor the operation information of each of the functional modules associated with the business logic; The test module is used to parse and verify each of the monitored operation information to obtain the corresponding test results of the business logic.
9. An electronic device, characterized in that: The method comprises a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is called by the processor individually or collectively, the processor executes the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are called by a computer, the computer executes the method according to any one of claims 1 to 7.