CN108965053B - Method, device and system for testing software pressure of upper computer - Google Patents
Method, device and system for testing software pressure of upper computer Download PDFInfo
- Publication number
- CN108965053B CN108965053B CN201810708431.1A CN201810708431A CN108965053B CN 108965053 B CN108965053 B CN 108965053B CN 201810708431 A CN201810708431 A CN 201810708431A CN 108965053 B CN108965053 B CN 108965053B
- Authority
- CN
- China
- Prior art keywords
- upper computer
- computer software
- communication
- software
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/14—Arrangements for monitoring or testing data switching networks using software, i.e. software packages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Abstract
The embodiment of the application discloses host computer software includes a plurality of relatively independent communication modules, and different communication protocols are used to different modules, and every communication module communicates with an at least lower computer, and communication module communicates with the lower computer through the interface of host computer, has realized the simulation to communication protocol and communication mode among the operational environment of host computer software. When the upper computer software is started, the upper computer software and the lower computer perform data communication, and the simulation of the data volume of the communication data of the upper computer software and the lower computer is realized. That is to say, the upper computer software pressure testing method provided by the embodiment of the application simulates the operation environment of the upper computer at least from three aspects of a communication protocol, a communication mode and data volume, so that the pressure test of the upper computer software in a more complete operation environment is realized, and the effectiveness of the pressure test result of the upper computer software is improved.
Description
Technical Field
The application relates to the technical field of testing, in particular to a method, a device and a system for testing the pressure of upper computer software.
Background
After software is developed and before the software is released and used, in order to ensure that the upper computer software can carry out long-time error-free downlink communication and can adapt to various operating conditions on site, the software needs to be firstly subjected to pressure test to determine the reliability and stability of the software and to be improved when the defects of the tested software are found.
The existing software testing methods are all software pressure tests based on a single communication protocol (such as an HTTP protocol), but the pressure testing methods are not suitable for upper computer software in industrial control, and cannot perform effective pressure tests on the upper computer software in the industrial control.
Disclosure of Invention
The application aims to provide a method, a device and a system for testing the pressure of upper computer software, so as to at least partially overcome the technical problems in the prior art.
In order to achieve the purpose, the application provides the following technical scheme:
a method for testing the pressure of upper computer software comprises a plurality of relatively independent communication modules, wherein different communication modules use different communication protocols, each communication module is communicated with at least one lower computer, and the communication modules are communicated with the lower computers through interfaces of the upper computers; the method comprises the following steps:
step S21: starting the upper computer software to enable the upper computer software to carry out data communication with the lower computer, and carrying out log recording on a preset running node related to data transmission in the communication module; the communication data volume between the upper computer software and all the lower computers is larger than that between the on-site upper computer and all the on-site lower computers;
step S22: monitoring whether the upper computer software continuously operates or not, and recording a monitoring result;
step S23: and when the stop condition is reached, controlling the upper computer software to stop running.
In the above method, preferably, the communicating between each communication module and at least one lower computer includes:
each communication module communicates with at least one physical lower computer, or each communication module communicates with at least one virtual lower computer.
In the method, preferably, the upper computer software is further connected with the master station;
and after the software of the upper computer is started, the software of the upper computer is also in data communication with the main station.
Preferably, the monitoring whether the upper computer software continuously operates includes:
judging whether the identification mark of the process for operating the upper computer software can be acquired or not;
and if so, determining that the upper computer software is in operation, otherwise, determining that the upper computer software stops operating.
Preferably, the method further includes, after determining that the upper computer software stops operating:
and restarting the upper computer software.
In the above method, preferably, the upper computer software communicates with the lower computer through at least two types of interfaces, and each communication module communicates with at least one lower computer through one type of interface of the at least two types of interfaces; the steps S21 to S23 are executed at least three times, and specifically include:
corresponding to each type of interface in the at least two types of interfaces, when the lower computer is connected with the upper computer software only through the type of interface, executing the step S21 to the step S23 once;
and when the lower computer is connected with the upper computer software through the at least two types of interfaces, executing the steps S21 to S23 once.
A device for testing the pressure of upper computer software comprises a plurality of relatively independent communication modules, wherein different communication modules use different communication protocols, each communication module is communicated with at least one lower computer, and the communication modules are communicated with the lower computers through interfaces of the upper computers; the device comprises:
the starting module is used for starting the upper computer software so as to enable the upper computer software to carry out data communication with the lower computer, and carrying out log recording on a preset running node related to data transmission in the communication module; the communication data volume between the upper computer software and all the lower computers is larger than that between the on-site upper computer and all the on-site lower computers;
the monitoring module is used for monitoring whether the upper computer software continuously operates and recording a monitoring result;
and the stopping module is used for controlling the upper computer software to stop running when the stopping condition is reached.
Preferably, in the apparatus, each of the communication modules communicates with at least one lower computer, and the communication module includes:
each communication module communicates with at least one physical lower computer, or each communication module communicates with at least one virtual lower computer.
In the device, preferably, the upper computer software is further connected with the master station;
and after the software of the upper computer is started, the software of the upper computer is also in data communication with the main station.
The above device, preferably, the monitoring module includes:
the judging unit is used for judging whether the identification mark of the process for operating the upper computer software can be acquired or not;
and the determining unit is used for determining that the upper computer software runs if the judging result of the judging unit is positive, and otherwise, determining that the upper computer software stops running.
The above apparatus, preferably, further comprises:
and the restarting module is used for restarting the upper computer software when the determining unit determines that the upper computer stops running.
In the above apparatus, preferably, the upper computer software communicates with the lower computer through at least two types of interfaces, and each communication module communicates with at least one lower computer through one type of interface of the at least two types of interfaces; the starting module, the monitoring module and the stopping module run for at least three times, and the method specifically comprises the following steps:
corresponding to each type of interface in the at least two types of interfaces, when the lower computer is connected with the upper computer software only through the type of interface, the starting module, the monitoring module and the stopping module operate once in sequence;
and when the lower computer is connected with the upper computer software through the at least two interfaces, the starting module, the monitoring module and the stopping module sequentially run once.
A host computer software stress test system comprises: the system comprises an upper computer and a plurality of lower computers;
the upper computer is used for starting and operating the upper computer software so as to enable the upper computer software to carry out data communication with the lower computer, and log recording is carried out on a preset operation node related to data transmission in the communication module; monitoring whether the upper computer software continuously operates or not, and recording a monitoring result; when the stop condition is met, controlling the upper computer software to stop running;
the communication data volume between the upper computer software and all the lower computers is larger than that between the on-site upper computer and all the on-site lower computers; the upper computer software comprises a plurality of relatively independent communication modules, different communication modules use different communication protocols, each communication module is communicated with at least one lower computer, and the communication modules communicate with the lower computer through interfaces of the upper computer.
The system preferably further comprises a master station connected with the upper computer;
and after the software of the upper computer is started, the software of the upper computer is also in data communication with the main station.
According to the scheme, the method, the device and the system for testing the pressure of the upper computer software provided by the application simulate the operation environment of the upper computer software at least from three aspects of communication protocols, communication modes and data volumes, so that the pressure test of the upper computer software in a complete operation environment is realized, and the effectiveness of the pressure test result of the upper computer software in industrial control is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a host computer software pressure testing system according to an embodiment of the present disclosure;
fig. 2 is a flowchart of an implementation of a method for testing the software pressure of the upper computer according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a device for testing the software pressure of the upper computer provided in the embodiment of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be practiced otherwise than as specifically illustrated.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without inventive effort based on the embodiments of the present invention, are within the scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a host computer software pressure testing system provided in the present application. The upper computer software stress test system at least comprises:
an upper computer 11 and a plurality of lower computers 12 connected with the upper computer 11. The lower computers 12 may be connected to the upper computer 11 through Q (Q is a positive integer greater than or equal to 1) type interfaces, when Q is equal to 1, each of the lower computers 12 is connected to the upper computer 11 through the same type interface, and when Q is greater than 1, the plurality of lower computers 12 are divided into Q groups, each of which is connected to the upper computer 11 through one type interface. As an example, the lower computer in fig. 1 is connected to the upper computer 11 through two types of interfaces, which are a network port and a serial port. Wherein the content of the first and second substances,
the upper computer 11 is provided with upper computer software which can run on the upper computer 11. The upper computer software includes a plurality of relatively independent communication modules 111, that is, the functions of the communication modules 111 are relatively independent. The number of the communication modules 111 included in the upper computer software can be determined according to the category number of the communication protocols used by all the lower computers, that is, if the communication protocols used by all the lower computers have n categories, the number of the communication modules 111 included in the upper computer is n. The different communication modules 111 use different communication protocols, that is, each communication module 111 performs communication work for a certain type of lower computer (the certain type of lower computer refers to a lower computer using a certain type of communication protocol). Each communication module 111 communicates with at least one lower computer 12, and a communication method (i.e., a communication interface) of a certain type of lower computer is one of the Q-type interfaces or a part of the Q-type interfaces (i.e., the lower computer can communicate with the upper computer through any one of the part of the Q-type interfaces), so that the communication module 111 can communicate with the lower computer 12 through the part of the Q-type interfaces, specifically, which type of interface is used, according to the communication method (i.e., the type of interface) used by the lower computer in the use site of the upper computer software. When the upper computer software runs normally, all the communication modules 111 run in parallel.
For example, assuming that the lower computer 12 can communicate with the upper computer 11 through a network port or a serial port, regarding a certain type of lower computer, the lower computer 12 can communicate with the upper computer 11 only through the network port, or can communicate with the upper computer 11 only through the serial port, or can communicate with the upper computer 11 through the network port, or can communicate with the upper computer 11 through the serial port.
Before the upper computer software is subjected to the stress test, the functions of the communication module 111 of the upper computer software are analyzed to form a function flow chart or a function call block diagram. According to the functional flow diagram or the function calling diagram, a code for logging is added to the code of the communication module 111 by a tester at a position related to data transmission, so that in the running process of the upper computer software, information such as communication messages, communication states, communication errors and the like between the communication module 111 and the lower computer 12 can be recorded in a disk of the upper computer in the form of log files or printable files.
The process of analyzing the functions of the communication module 111 of the upper computer software may be implemented manually, that is, a tester checks the codes and manually arranges the function flow or the call relationship. The functions of the communication module 111 of the upper computer software can also be automatically analyzed by means of dedicated tool software, i.e. implemented in an automated manner.
The lower computer 12 may be a physical lower computer or a virtual lower computer. The plurality of lower computers 12 may be all entity lower computers, or may be all virtual lower computers, or may be part of entity lower computers and part of virtual lower computers.
In an alternative embodiment, in order to more effectively detect the defect of the software of the upper computer, the communication module 111 may communicate with at least two physical lower computers, or may communicate with at least five virtual lower computers. In particular, the method comprises the following steps of,
in all the communication modules 111, each communication module 111 may communicate with at least two physical lower computers, or each communication module 111 may communicate with at least five virtual lower computers, or some of the communication modules 111 may communicate with at least two physical lower computers and some of the communication modules may communicate with at least five virtual lower computers.
For the lower computers which use serial ports to communicate, the lower computer group which uses the same communication protocol is connected to the same serial port of the upper computer, and the upper computer distinguishes each lower computer through the address of the lower computer. The lower computers with different communication protocols cannot use the same serial port.
For a lower computer that performs communication using a network port, the lower computer is connected to an upper computer using a network of an exchange. The upper computer distinguishes each lower computer by the IP address and the port number.
In the actual use site of the software of the upper computer, the number of the lower computers using the same communication protocol is different, and the data volume uploaded to the upper computer by the lower computers using the same protocol is also different. For convenience of description, the minimum unit of the data uploaded by the lower computer is called a measurement point, and the data amount of each measurement point is usually between 1bit and 2 Byte. The minimum unit of the data uploaded by the lower computer is as follows: the minimum data that can represent a measurement value (e.g., temperature value, wind speed value, switch state, etc.) is typically 1bit to 2 Byte.
Before the upper computer software is subjected to pressure test, the total data communication amount between the upper computer software on the actual use site of the upper computer software and the actually applied lower computer is estimated. When the upper computer software is subjected to the pressure test, the communication data amount between the upper computer software and the test lower computer 12 is larger than the estimated data amount.
Generally, the number of measuring points of a single lower computer is 500-2000, and the total number of measuring points of all lower computers is NTP x m or more. The NTP is the maximum measuring point number of a single lower computer in the actual use field of the upper computer software; and m is the total number of the lower computers in the actual use field of the upper computer software. For example, if NTP is 2000 and m is 5, that is, there are 5 lower computers communicating with the upper computer software in total, and the number of measurement points of at least one of the 5 lower computers is 2000, and the number of measurement points of the other lower computers is less than or equal to 2000, then the total number of measurement points of all the lower computers 12 should be 2000 × 5 to 10000 or more during the test, and if the data amount of each measurement point is 2Byte, the communication data amount between the upper computer software and the lower computer 12 should be 20KB or more during the test.
In fig. 1, RSL represents an entity lower computer, RSL _ B represents an entity lower computer using a communication protocol B, and similarly, RSL _ C represents an entity lower computer using a communication protocol C. The SLS represents the virtual lower computer, and the SLS _ D represents the virtual lower computer using the communication protocol D. The network port lower computer group comprises a plurality of lower computers 12 using a communication protocol A, and each lower computer 12 is accessed to the network switch through one interface of the network switch.
Communication module A represents the communication module that uses communication protocol A, and similarly, communication module B represents the communication module that uses communication protocol B, communication module C represents the communication module that uses communication protocol C, and communication module D represents the communication module that uses communication protocol D.
In the embodiments of the present application, "between" referring to the data range includes the end point value unless otherwise specified.
Based on the above upper computer software pressure test system, an implementation flowchart of the upper computer software pressure test method provided by the present application is shown in fig. 2, and may include:
step S21: the upper computer software is started to enable the upper computer software to perform data communication with the lower computer 12, and the preset running node related to data transmission performs log recording in the communication module 111.
The upper computer software may be started by a first script running on the upper computer 11. In the running process of the upper computer software, the log record code in the communication module 111 outputs a log record, and at least the following information can be recorded in the log record: a communication message, an identification of whether the parsing of the communication message is correct (i.e., communication error information), and an identification of whether a communication failure has occurred (i.e., communication status information).
The data communication between the upper computer software and the lower computer 12 may include:
the upper computer software carries out remote measurement and remote signaling on the lower computer 12, so that data communication between the upper computer software and the lower computer 12 is realized. The tester can judge whether the remote measurement and remote signaling are normal by checking the log record.
Furthermore, after the software of the upper computer is started, the lower computer can be remotely tested. Specifically, the upper computer software may send a remote control instruction to the lower computer 12 in response to an operation of the tester, and if the lower computer 12 is an entity lower computer, the tester may determine whether the remote control is successful according to whether the lower computer 12 performs a predetermined action (e.g., whether a predetermined indicator light is on, or whether a relay acts), and if the lower computer 12 is a virtual lower computer, the tester may determine whether the remote control is successful according to whether the lower computer 12 returns a specific message. The tester can determine whether the lower computer 12 returns a specific message by checking the log.
Step S22: and monitoring whether the upper computer software continuously operates or not, and recording a monitoring result.
The upper computer software may be monitored by a second script running on the upper computer 11. The second script can monitor the identification mark (namely the process number) of the process of running the upper computer software every 30 seconds, namely, whether the identification mark of the process of running the upper computer software can be obtained or not is judged every 30 seconds, if the identification mark can be obtained, the upper computer software is operated, and if the identification mark cannot be obtained, the upper computer software stops operating.
According to the monitoring mode, the running state of the upper computer is recorded every 30s in the monitoring result, if the monitoring result has the record that the upper computer software stops running, the upper computer software does not run continuously, and if the monitoring result does not have the record that the upper computer software stops running, the upper computer software runs continuously.
The monitoring result can be stored in a log file.
Step S23: and when the stop condition is reached, controlling the upper computer software to stop running.
Reaching the stop condition may include either of the following two cases:
and receiving a user-triggered instruction for stopping running.
The total running time of the upper computer software reaches the preset time. The preset time is preset time for performing pressure test on the upper computer software, and is generally a value between 7 days and 30 days. Through long-time running test, the running state of the upper computer software can be effectively tracked through the log file.
According to the upper computer software pressure testing method provided by the embodiment of the application, the upper computer software comprises a plurality of relatively independent communication modules, different communication protocols are used by different modules, each communication module is communicated with at least one lower computer, and the communication modules are communicated with the lower computers through interfaces of the upper computers, so that simulation of various communication protocols and various communication modes in the operating environment of the upper computer software is realized. When the upper computer software is started, the upper computer software and the lower computer perform data communication, and the simulation of the data volume of the communication data of the upper computer software and the lower computer is realized. That is to say, the upper computer software pressure testing method provided by the embodiment of the application simulates the operation environment of the upper computer at least from three aspects of a communication protocol, a communication mode and data volume, so that the pressure test of the upper computer software in a more complete operation environment is realized, and the effectiveness of the pressure test result of the upper computer software is improved.
In addition, since each communication module 111 has a separate log file, whether the operation of each communication module 111 is normal can be effectively determined through the respective log files.
In the above embodiment, optionally, after the upper computer software is monitored to stop running, the upper computer software may be restarted through the third script, so that the pressure test on the upper computer software is continued.
Specifically, after the fact that the upper computer software stops running is monitored, whether the total running time of the upper computer software reaches a preset time or not can be judged, if the total running time does not reach the preset time, the test is not completed, the upper computer software is restarted through a third script, and if the total running time does not reach the preset time, the test is completed, and the upper computer software is not restarted.
In some application scenarios, the upper computer software communicates with the upper level master station of the upper computer in addition to the lower computer. Based on this, among the host computer software pressure test system that this application provided, still include:
and the master station 13, wherein the master station 13 is connected with the communication module 111 of the upper computer software through an interface (such as a network port) of the upper computer. After the upper computer software is started, the upper computer software also performs data communication with the master station 13 through the communication module 111.
Specifically, the upper computer software can forward real-time data uploaded by the upper computer 12 to the master station 13, and the upper computer software can also receive a command issued by the master station and remotely control the lower computer according to the command.
In an optional embodiment, the master station 13 may be an analog master station, the analog master station has a graphical interface, and the analog master station may display the communication message and the update condition of the data uploaded by the upper computer 11 in the process of communicating between the master station 13 and the upper computer 11. Based on this, the tester can check the information displayed on the display interface at the master station 13, thereby judging whether the communication between the upper computer 11 and the master station 13 is normal.
In addition, in the process of running the upper computer software, the communication module 111 communicating with the master station also records the communication message between the communication module 111 and the master station 13, and information such as communication state, communication error and the like can be recorded in the magnetic disk of the upper computer in the form of log files or printable files. Based on this, the tester can also check whether the communication between the upper computer software and the master station is normal through the log file of the communication module 111 communicating with the master station.
In the above embodiment, optionally, in order to more effectively perform the pressure test on the upper computer software, when the upper computer software communicates with the lower computer through at least two types of interfaces, and each communication module communicates with at least one lower computer through one type of interface of the at least two types of interfaces, the upper computer software may be respectively tested according to the situation, specifically:
corresponding to each type of interface in the at least two types of interfaces, when the lower computer is connected with the upper computer software only through the type of interface, executing the step S21 to the step S23 once;
and when the lower computer is connected with the upper computer software through the at least two types of interfaces, executing the steps S21 to S23 once.
Assuming that the upper computer software communicates with the lower computer through the interface of the type in P, P +1 times of tests are required in total.
In the embodiment of the application, besides testing various communication interfaces simultaneously, various communication interfaces are also tested respectively, so that the problems of various communication interfaces can be better positioned.
In an alternative embodiment, the upper computer software runs in the Linux operating system, and preferably, the upper computer software can run in the Linux operating system
Enterprise Linux 6.6 operating system. The operating system provides a kernel crash dump function, can record calling information of upper computer software before crash, and is generally recorded in a core file. After the upper computer software crashes, a tester can locate the file and the line number of the function executed by the upper computer software before the crash according to the core file, and search the crash reason so as to modify the corresponding code. After the modification, the steps S21 to S23 may be executed again.
Corresponding to the embodiment of the method, the application also provides a device for testing the pressure of the upper computer software, wherein the device for testing the pressure of the upper computer software is applied to an upper computer, and the upper computer is used for operating the upper computer software. The upper computer software comprises a plurality of relatively independent communication modules, different communication protocols are used by different communication modules, each communication module is communicated with at least one lower computer, and the communication modules are communicated with the lower computers through interfaces of the upper computer software; a schematic structural diagram of the upper computer software pressure testing apparatus provided in the embodiment of the present application is shown in fig. 3, and may include:
a starting module 31, configured to start the upper computer software, so that the upper computer software performs data communication with the lower computer, and performs log recording on a preset running node related to data transmission in the communication module; the communication data volume between the upper computer software and all the lower computers is larger than that between the on-site upper computer and all the on-site lower computers.
And the monitoring module 32 is used for monitoring whether the upper computer software continuously operates and recording a monitoring result.
And the stopping module 33 is used for controlling the upper computer software to stop running when the stopping condition is reached.
The application provides a host computer software pressure test device, host computer software include a plurality of relatively independent communication module, and different communication protocols are used to different modules, and every communication module communicates with an at least lower computer, and communication module communicates through the interface and the lower computer of host computer, has realized the simulation to communication protocol and communication mode among the operational environment of host computer software. When the upper computer software is started, the upper computer software and the lower computer perform data communication, and the simulation of the data volume of the communication data of the upper computer software and the lower computer is realized. That is to say, the upper computer software pressure testing method provided by the embodiment of the application simulates the operation environment of the upper computer at least from three aspects of a communication protocol, a communication mode and data volume, so that the pressure test of the upper computer software in a more complete operation environment is realized, and the effectiveness of the pressure test result of the upper computer software is improved.
In an optional embodiment, each communication module communicates with at least one lower computer, including:
each communication module communicates with at least one physical lower computer, or each communication module communicates with at least one virtual lower computer.
In an optional embodiment, the upper computer software is further connected with the master station;
and after the software of the upper computer is started, the software of the upper computer is also in data communication with the main station.
In an alternative embodiment, the monitoring module 32 may include:
the judging unit is used for judging whether the identification mark of the process for operating the upper computer software can be acquired or not;
and the determining unit is used for determining that the upper computer software is running if the judging result of the judging unit is positive, and otherwise, determining that the upper computer software stops running.
In an optional embodiment, the upper computer software pressure testing apparatus provided in the present application may further include:
and the restarting module is used for restarting the upper computer software when the determining unit determines that the upper computer stops running.
In an optional embodiment, the upper computer software communicates with the lower computer through at least two types of interfaces, and each communication module communicates with at least one lower computer through one type of interface in the at least two types of interfaces; the starting module, the monitoring module and the stopping module run for at least three times, and the method specifically comprises the following steps:
corresponding to each type of interface in the at least two types of interfaces, when the lower computer is connected with the upper computer software only through the type of interface, the starting module, the monitoring module and the stopping module operate once in sequence;
and when the lower computer is connected with the upper computer software through the at least two interfaces, the starting module, the monitoring module and the stopping module sequentially run once.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
It should be understood that the technical problems can be solved by combining and combining the features of the embodiments from the claims.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (14)
1. The upper computer software pressure testing method is characterized in that the upper computer software comprises a plurality of relatively independent communication modules, different communication modules use different communication protocols, each communication module is communicated with at least one lower computer, and the communication modules are communicated with the lower computers through interfaces of the upper computers; the method comprises the following steps:
step S21: starting the upper computer software to enable the upper computer software to carry out data communication with the lower computer, and carrying out log recording on a preset running node related to data transmission in the communication module; the communication data volume between the upper computer software and all the lower computers is larger than that between the on-site upper computer and all the on-site lower computers, and the communication data volume between the on-site upper computer and all the on-site lower computers is obtained by estimating the total data communication volume between the upper computer software which is actually used on site and the actually-applied lower computers before the pressure test is carried out on the upper computer software;
step S22: monitoring whether the upper computer software continuously operates or not, and recording a monitoring result;
step S23: and when the stop condition is reached, controlling the upper computer software to stop running.
2. The method of claim 1, wherein the each communication module communicating with at least one subordinate computer comprises:
each communication module communicates with at least one physical lower computer, or each communication module communicates with at least one virtual lower computer.
3. The method of claim 1, wherein the upper computer software is further connected to a master station;
and after the software of the upper computer is started, the software of the upper computer is also in data communication with the main station.
4. The method of claim 1, wherein the monitoring whether the upper computer software is running continuously comprises:
judging whether the identification mark of the process for operating the upper computer software can be acquired or not;
and if so, determining that the upper computer software is in operation, otherwise, determining that the upper computer software stops operating.
5. The method of claim 4, after determining that the upper computer software stops operating, further comprising:
and restarting the upper computer software.
6. The method according to any one of claims 1 to 5, wherein the upper computer software communicates with the lower computer through at least two types of interfaces, and each communication module communicates with at least one lower computer through one type of interface of the at least two types of interfaces; the steps S21 to S23 are executed at least three times, and specifically include:
corresponding to each type of interface in the at least two types of interfaces, when the lower computer is connected with the upper computer software only through the type of interface, executing the step S21 to the step S23 once;
and when the lower computer is connected with the upper computer software through the at least two types of interfaces, executing the steps S21 to S23 once.
7. The pressure testing device for the upper computer software is characterized in that the upper computer software comprises a plurality of relatively independent communication modules, different communication modules use different communication protocols, each communication module is communicated with at least one lower computer, and the communication modules are communicated with the lower computers through interfaces of the upper computers; the device comprises:
the starting module is used for starting the upper computer software so as to enable the upper computer software to carry out data communication with the lower computer, and carrying out log recording on a preset running node related to data transmission in the communication module; the communication data volume between the upper computer software and all the lower computers is larger than that between the on-site upper computer and all the on-site lower computers, and the communication data volume between the on-site upper computer and all the on-site lower computers is obtained by estimating the total data communication volume between the upper computer software which is actually used on site and the actually-applied lower computers before the pressure test is carried out on the upper computer software;
the monitoring module is used for monitoring whether the upper computer software continuously operates and recording a monitoring result;
and the stopping module is used for controlling the upper computer software to stop running when the stopping condition is reached.
8. The apparatus of claim 7, wherein each communication module communicates with at least one subordinate computer comprising:
each communication module communicates with at least one physical lower computer, or each communication module communicates with at least one virtual lower computer.
9. The device of claim 7, wherein the upper computer software is further connected with a master station;
and after the software of the upper computer is started, the software of the upper computer is also in data communication with the main station.
10. The apparatus of claim 7, wherein the monitoring module comprises:
the judging unit is used for judging whether the identification mark of the process for operating the upper computer software can be acquired or not;
and the determining unit is used for determining that the upper computer software runs if the judging result of the judging unit is positive, and otherwise, determining that the upper computer software stops running.
11. The apparatus of claim 10, further comprising:
and the restarting module is used for restarting the upper computer software when the determining unit determines that the upper computer stops running.
12. The device according to any one of claims 7 to 10, wherein the upper computer software communicates with the lower computer through at least two types of interfaces, and each communication module communicates with at least one lower computer through one type of interface of the at least two types of interfaces; the starting module, the monitoring module and the stopping module run for at least three times, and the method specifically comprises the following steps:
corresponding to each type of interface in the at least two types of interfaces, when the lower computer is connected with the upper computer software only through the type of interface, the starting module, the monitoring module and the stopping module operate once in sequence;
and when the lower computer is connected with the upper computer software through the at least two interfaces, the starting module, the monitoring module and the stopping module sequentially run once.
13. The utility model provides a host computer software stress test system which characterized in that includes: the system comprises an upper computer and a plurality of lower computers;
the upper computer is used for starting and operating the upper computer software so as to enable the upper computer software to carry out data communication with the lower computer, and log recording is carried out on a preset operation node related to data transmission in the communication module; monitoring whether the upper computer software continuously operates or not, and recording a monitoring result; when the stop condition is met, controlling the upper computer software to stop running;
the communication data volume between the upper computer software and all the lower computers is larger than that between the on-site upper computer and all the on-site lower computers, and the communication data volume between the on-site upper computer and all the on-site lower computers is obtained by estimating the total data communication volume between the upper computer software which is actually used on site and the actually-applied lower computers before the pressure test is carried out on the upper computer software; the upper computer software comprises a plurality of relatively independent communication modules, different communication modules use different communication protocols, each communication module is communicated with at least one lower computer, and the communication modules communicate with the lower computer through interfaces of the upper computer.
14. The system of claim 13, further comprising a master station connected to the host computer;
and after the software of the upper computer is started, the software of the upper computer is also in data communication with the main station.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810708431.1A CN108965053B (en) | 2018-07-02 | 2018-07-02 | Method, device and system for testing software pressure of upper computer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810708431.1A CN108965053B (en) | 2018-07-02 | 2018-07-02 | Method, device and system for testing software pressure of upper computer |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108965053A CN108965053A (en) | 2018-12-07 |
| CN108965053B true CN108965053B (en) | 2021-09-17 |
Family
ID=64485051
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810708431.1A Active CN108965053B (en) | 2018-07-02 | 2018-07-02 | Method, device and system for testing software pressure of upper computer |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108965053B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109712701A (en) * | 2018-12-10 | 2019-05-03 | 上海联影医疗科技有限公司 | Slave computer simulator and master system test method |
| CN111782358A (en) * | 2020-06-22 | 2020-10-16 | 北京北方华创微电子装备有限公司 | Software control method for semiconductor process equipment and semiconductor process equipment |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9081881B2 (en) * | 2008-12-18 | 2015-07-14 | Hartford Fire Insurance Company | Computer system and computer-implemented method for use in load testing of software applications |
| CN103513223B (en) * | 2013-10-15 | 2016-01-20 | 国家电网公司 | A kind of electric energy meter communication interface load capacity test system |
| CN204305072U (en) * | 2014-12-26 | 2015-04-29 | 广州杰赛科技股份有限公司 | A kind of Multi-protocol converter |
| CN105446860B (en) * | 2015-11-11 | 2017-12-15 | 上海欣方智能系统有限公司 | Pressure testing system and method for testing based on asynchronism and concurrency mechanism |
| CN105974331A (en) * | 2016-04-08 | 2016-09-28 | 江门职业技术学院 | LED driving power supply detection system |
| CN206133222U (en) * | 2016-05-25 | 2017-04-26 | 江苏斯菲尔电气股份有限公司 | Fire control device power monitored control system |
| CN108111265B (en) * | 2016-11-25 | 2020-08-18 | 株洲中车时代电气股份有限公司 | Automatic testing method for consistency of communication protocol |
| CN106603581B (en) * | 2017-02-22 | 2020-04-07 | 欣旺达电子股份有限公司 | Test method and device supporting multiple communication protocols |
-
2018
- 2018-07-02 CN CN201810708431.1A patent/CN108965053B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108965053A (en) | 2018-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107222362B (en) | Automatic test platform for finished vehicle CAN network and optimization method thereof | |
| WO2017000424A1 (en) | Protocol detection method and apparatus | |
| CN107241229B (en) | Service monitoring method and device based on interface testing tool | |
| ITTO940668A1 (en) | SYSTEM FOR MONITORING AND ANALYZING THE BEHAVIOR OF A SWITCHING SYSTEM CONTROLLED BY A STORED PROGRAM | |
| CN107370637B (en) | Vehicle-mounted ECU communication function automatic test system and method | |
| CN105223889A (en) | A kind of method being applicable to the automatic monitoring PMC RAID card daily record of producing line | |
| CN111881014B (en) | System test method, device, storage medium and electronic equipment | |
| CN109733238B (en) | Fault detection method, device, storage medium and processor | |
| CN108965053B (en) | Method, device and system for testing software pressure of upper computer | |
| CN112737886A (en) | Tool testing method and system | |
| CN111464376A (en) | Website availability monitoring method and device, storage medium and computer equipment | |
| CN110554940A (en) | Serial port detection tool and method based on electric energy meter communication | |
| CN111078484A (en) | Power-off test method, device, equipment and storage medium for system upgrading | |
| CN110825542B (en) | Method, device and system for detecting fault disc in distributed system | |
| CN110968517A (en) | Automatic test method, device, platform and computer readable storage medium | |
| CN110990289A (en) | Method and device for automatically submitting bug, electronic equipment and storage medium | |
| CN114138587B (en) | Method, device and equipment for verifying reliability of server power firmware upgrade | |
| CN114500178B (en) | Self-operation intelligent Internet of things gateway | |
| CN113608959B (en) | Method, system, terminal and storage medium for positioning fault hard disk | |
| CN114879647A (en) | ECU fault code test system, electronic controller and car | |
| CN111831496B (en) | System and method for presetting factory measurement parameters of direct broadcast satellite equipment | |
| CN114218011A (en) | Test simulation method and device, terminal equipment and storage medium | |
| CN114166265A (en) | Ground test method and system for satellite, storage medium and electronic equipment | |
| WO2016127483A1 (en) | Processing method and device for collection agent management subsystem | |
| CN113886165B (en) | Verification method, device and equipment for firmware diagnosis function and readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 274000 No. 199 Zhonghua Road, Shandong, Heze Applicant after: Heze Power Supply Company, State Grid Shandong Electric Power Co., Ltd. Applicant after: National Network Intelligent Technology Co., Ltd. Address before: 274000 No. 199 Zhonghua Road, Shandong, Heze Applicant before: Heze Power Supply Company, State Grid Shandong Electric Power Co., Ltd. Applicant before: Shandong Luneng Intelligent Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210210 Address after: Room 902, 9 / F, block B, Yinhe building, 2008 Xinluo street, high tech Zone, Jinan City, Shandong Province Applicant after: Shandong Luneng Software Technology Co.,Ltd. intelligent electrical branch Applicant after: State Grid Shandong Electric Power Company Heze Power Supply Co. Address before: 199 Zhonghua Road Heze Shandong 274000 Applicant before: State Grid Shandong Electric Power Company Heze Power Supply Co. Applicant before: National Network Intelligent Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| CB02 | Change of applicant information |
Address after: Room 902, 9 / F, block B, Yinhe building, 2008 Xinluo street, high tech Zone, Jinan City, Shandong Province Applicant after: Shandong luruan Digital Technology Co.,Ltd. smart energy branch Applicant after: State Grid Shandong Electric Power Company Heze Power Supply Co. Address before: Room 902, 9 / F, block B, Yinhe building, 2008 Xinluo street, high tech Zone, Jinan City, Shandong Province Applicant before: Shandong Luneng Software Technology Co.,Ltd. intelligent electrical branch Applicant before: State Grid Shandong Electric Power Company Heze Power Supply Co. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |