Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present invention, the technical solutions in the embodiments of the present invention will be described clearly and completely 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 embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention shall fall within the scope of the protection of the embodiments of the present invention.
The following further describes specific implementation of the embodiments of the present invention with reference to the drawings.
Fig. 1A is a schematic flowchart of a software testing method according to a first embodiment of the present invention. The software testing method of fig. 1A includes:
110: installing a test program developed by utilizing a development framework of a first non-embedded operating system in a local embedded operating system, wherein the test program is used for carrying out black box test on an application program to be tested installed in the embedded operating system;
120: and receiving a drive control message sent from a driver installed in a second non-embedded operating system of the second device through the secure communication connection with the second device, wherein the drive control message indicates the embedded operating system to drive the test program.
It should be understood that non-embedded operating systems herein include, but are not limited to, desktop operating systems or server operating systems. Such as a UNIX operating system, a LINUX operating system, a WINDOWS desktop operating system, a WINDOWS server operating system, a MAC desktop operating system, a MAC server operating system, and the like. The embedded operating system includes, but is not limited to, any embedded operating system such as an android system, an IOS system. The embodiment of the present invention is not limited thereto.
It should also be understood that the black box test herein is a functional test, as opposed to a white box test, such as code level debugging. The black box test is used for purposes such as testing a user interface. In addition, the first non-embedded operating system and the second non-embedded operating system may be the same operating system or different operating systems. The embodiment of the present invention is not limited thereto.
For example, when the first non-embedded operating system is a MAC system, the development framework is Xcode. For example, the test program is a UI test program developed based on XCUItest. For example, the second non-embedded operating system may be any of a UNIX operating system, a LINUX operating system, a WINDOWS desktop operating system, a WINDOWS server operating system, a MAC desktop operating system, a MAC server operating system.
For example, the connection may be a connection verification based on a mobile communication network or the internet such as a local area network or a wide area network, and when the verification is passed, the secure communication connection is completed. For example, the connection may be based on a secure connection of the server, e.g., a connection with a cloud server. It should be understood that the secure connection is deployed by the cloud server, which is beneficial to improving the test scale and the test efficiency. For example, the connection may be a device-to-device (D2D) connection, e.g., via near field communication such as the bluetooth standard. For example, a wired connection, such as a USB interface. For example, an encrypted connection, implemented by wired or wireless means.
It should also be understood that the program installed in the embedded operating system may be implemented by an installer of the installation package. The generation of the installation package can be realized in any mode based on a development framework in the text or other installation package generation programs. The test program may generate a case subprogram such as an installation package by being compiled by a compiler, or the test program may directly generate the installation package without being compiled. The programming process may be implemented by the development framework described above, or may be implemented by a special compiler. In one implementation of the invention, the test program is compiled through the development framework to generate an installation package. For example, the installation package is used as a basic package to test other application programs to be tested.
It should also be understood that the functionality of the test program includes, but is not limited to, screenshots, manipulations of the embedded operating system, obtaining interface element information, and the like. The embodiment of the present invention is not limited thereto.
The scheme of the embodiment of the invention can install the test program developed by the development framework of the non-embedded operating system in the embedded operating system and control according to the drive control message sent by the drive program installed in the non-embedded operating system. The driver installed in the non-embedded operating system is used for driving, so that the cross-platform test of the application program in the embedded operating system is realized.
In one implementation manner of the invention, the first device is not provided with the first non-embedded operating system, the first device is connected with the third device, the third device is provided with the first non-embedded operating system, and the test program is developed. The first device obtains the test program from a third device via a connection with the third device. Alternatively, the first device is provided with a first non-embedded operating system, and the test program is a program developed by adopting a development framework of the first non-embedded operating system in the first device.
In one implementation of the present invention, before installing the test program developed by the development framework of the first non-embedded operating system in the local embedded operating system, the method further comprises: establishing a secure communication connection with a first device; the method comprises the following steps of acquiring an installation program of a test program from a first device to the local based on the secure communication connection with the first device, and installing the test program developed by using a development framework of a first non-embedded operating system in a local embedded operating system, wherein the method comprises the following steps: and installing an installation program of the test program so as to install the test program in the local embedded operating system. For example, the secure communication connection is a USB-based secure communication connection.
In one implementation manner of the present invention, receiving a driver control message sent from a driver installed in a second non-embedded operating system of a second device through a secure communication connection with the second device includes: transmitting the installation information of the test program in the local embedded operating system to the second equipment through the secure communication connection with the second equipment; and receiving a drive control message sent by the driver based on the installation information. It will be appreciated that the secure communication connection with the second device may be the same type of connection as the secure communication connection with the first device. Furthermore, the secure communication connection may also be a different type of connection.
In one implementation manner of the present invention, before transmitting installation information of the test program in the local embedded operating system to the second device through the secure communication connection with the second device, the method further includes: and receiving a request message of the driver through the secure communication connection with the second device, wherein the request message comprises the identification of the test program for obtaining the installation information. For example, the installation information includes a method name, a program name, an installation package name, and the like of the test program. The installation information may also include an installation path of the test program, for example, an installation path in an embedded system. The installation information may also include other information related to the embedded system so that the embedded system makes calls to the test program.
In one implementation of the invention, the method further comprises: performing a transport layer connection with the second device via a transport layer communication protocol; establishing a secure communication connection with the second device using a key agreement algorithm based on the transport layer connection. For example, where the embedded operating system is an IOS, the transport layer communication may be a TCP protocol. For example, the USBMUX service may be initiated based on the TCP protocol. The service may connect the associated connections through corresponding programs in a non-embedded operating system, such as a WINDOWS system. It should be understood that the above embodiments are only exemplary, and the present invention is not limited thereto.
Establishing a secure communication connection with the second device using a key agreement algorithm, for example, based on the transport layer connection, includes: receiving a pairing message transmitted by the second equipment by calling a cross-platform secure communication method based on the transmission layer connection; after pairing is established in response to the pairing message, a secret key agreement algorithm is used to determine an agreed password with the second device to establish a secure communication connection with the second device. For example, the key agreement algorithm may determine a symmetric key or an asymmetric key, which is not limited in the embodiments of the present invention. For example, after the transport layer connection is established and after the agreed password is determined, a secure connection may be established in a three-step handshake manner, and specific connection interaction may refer to corresponding steps in fig. 1C.
Fig. 1B is a schematic diagram of a software testing method according to a first embodiment of the present invention. In this embodiment, the first non-embedded operating system is used as the MAC system. The embedded operating system is an IOS system, and the equipment in which the embedded operating system is located is IOS equipment. The second non-embedded operating system is a WINDOWS operating system, and is installed in a target Personal Computer (PC). The following describes the implementation scenario of fig. 1B with reference to the flowchart of fig. 1C. It should be understood that the embedded operating system and the non-embedded operating system of embodiments of the present invention are not limited to the above examples. Specifically, an embedded operating system and a non-embedded operating system can be explained and explained with reference to fig. 1A. It should be appreciated that in this example, the foundation package for automated testing is generated based on the foundation functionality of XCUITest written under the Mac system. The interaction method of the embodiment comprises the following steps:
step 101: the IOS device connects into the operating system of the target PC. For example, through a USBMUX service connection, or through other transmission means.
Step 102: the IOS device automatically starts the USBMUX service. It should be understood that the program corresponding to the service is installed in the operating system of the target PC. Thus, the operating system at the target PC establishes a service for which the operating system communicates with the IOS over TCP as USB in the device.
Step 103: and installing the written and generated basic package into the IOS equipment by utilizing the installation service provided by the IOS system after the step is performed.
Step 104: the XCUItest-based base package is background-activated (i.e., activated on the target PC side) by an automated test driver written in the operating system of the target PC. The sub-steps ofstep 104 are shown in fig. 1D. Fig. 1D is a schematic flowchart of a background activation method according to an embodiment of the present invention, which includes the following sub-steps:
step 1041: the target PC calls the USBMUX service through TCP and initiates a message of pairing with the IOS equipment.
Step 1042: and after the target PC is successfully paired, the target PC exchanges a secret key for encrypted communication with the IOS equipment by adopting a secret key negotiation algorithm.
Step 1043: the IOS device creates a message for the automation service, encrypts handshake information for opening the service using the key obtained in step 1042, and sends a handshake message request to the target PC.
Step 1044: after receiving the handshake message request, the target PC sends a response message to the handshake message request to the IOS device.
Step 1045: the IOS device receives the response message. It should be appreciated that when the response message is received, a secure connection is established.
Step 1046: the IOS device starts the automatic service, distributes a TCP port to the service, and encrypts and replies to the target PC.
1047: the IOS device sends information such as the package name and the installation path of the basic package to the target PC.
Step 1048: and after the IOS equipment starts the automatic test service, returning a result to the target PC.
In one implementation of the invention, the application to be tested is a program developed using a development framework of the first non-embedded operating system.
FIG. 2A is a schematic block diagram of a software testing method according to a second embodiment of the present invention; the software testing method of fig. 2A, comprising:
210: determining a driver of a test program in a local second non-embedded operating system, wherein the test program is developed by utilizing a development framework of the first non-embedded operating system, is installed in an embedded operating system of embedded equipment and is used for carrying out black box test on an application program to be tested installed in the embedded operating system;
220: and sending a drive control message to the embedded equipment by using the drive program through the safe communication connection with the embedded equipment, wherein the drive control message indicates the embedded operating system to drive the test program.
The scheme of the embodiment of the invention can install the test program developed by the development framework of the non-embedded operating system in the embedded operating system and control according to the drive control message sent by the drive program installed in the non-embedded operating system. The driver installed in the non-embedded operating system is used for driving, so that the cross-platform test of the application program in the embedded operating system is realized.
In one implementation manner of the present invention, before determining a driver of a test program in a local second non-embedded operating system, the method includes: installing the obtained portable container in a local second non-embedded operating system; the acquired driver is installed into the portable container. For example, the portable container is a container such as DOCKER, and it should be understood that the portable container may also be other virtual machines or may be other virtual machines, which is not limited in this embodiment of the present invention. Because the transplantable method is adopted, large-scale test deployment can be performed, and cross-platform test is further realized.
FIG. 2B is a schematic block diagram of a software testing method according to a second embodiment of the present invention; the software testing method of fig. 2B, comprising:
260: acquiring a first confirmation operation of a user on an interactive interface of local embedded equipment aiming at a pairing request sent by first equipment, wherein the first equipment is provided with a first non-embedded operating system;
270: responding to the first confirmation operation, establishing a secure communication connection with the first equipment so as to receive an installation program of a software testing program, wherein the software testing program is used for carrying out black box testing on an application program to be tested installed in the embedded equipment;
280: and acquiring the installation operation of the user on the installation program on the interactive interface so as to install the software test program into an embedded operating system in the embedded equipment.
The scheme of the embodiment of the invention can install the test program developed by the development framework of the non-embedded operating system in the embedded operating system and control according to the drive control message sent by the drive program installed in the non-embedded operating system. The driver installed in the non-embedded operating system is used for driving, so that the cross-platform test of the application program in the embedded operating system is realized.
It should be understood that the obtaining of the confirmation operation of the user and/or the installation operation of the user in this document may be a user operating on an interactive interface (e.g., a touch interface) of the embedded device. The confirmation operation and the installation operation in the embodiment of the present invention include, but are not limited to, at least one of a slide touch, a click touch, a long-press touch, and a short-press touch performed in the touch area, and the embodiment of the present invention includes, but is not limited to, any form of touch operation, and includes combinations between different forms. Fig. 2C is an interactive interface diagram illustrating an example of a software testing method according to a second example of the second embodiment of the present invention. Fig. 2D is a schematic interactive interface diagram illustrating another example of the software testing method according to the second embodiment of the present invention. As shown in fig. 2C and 2D, the installation operation and the confirmation operation may be performed in a touch manner as shown.
It should also be understood that the above-described interaction operation of the present invention is not limited to a touch manner, and manners such as voice interaction or face recognition are also applicable to the embodiments of the present invention.
It should also be understood that the specific operation steps and processes of the embodiments of the present invention correspond to the embodiments, and the corresponding or similar steps are not described herein again.
For the secure communication connection described above, for example, a transport layer connection is made with the first device via a transport layer communication protocol; a secure communication connection is established with the first device using a key agreement algorithm based on the transport layer connection. For example, where the embedded operating system is an IOS, the transport layer communication may be a TCP protocol. For example, the USBMUX service may be initiated based on the TCP protocol. The service may connect the associated connections through corresponding programs in a non-embedded operating system, such as a WINDOWS system. It should be understood that the above embodiments are only exemplary, and the present invention is not limited thereto.
In one implementation of the invention, the method further comprises: and responding to the second confirmation operation, and establishing a secure communication connection with the first equipment so as to receive the driver of the installation program.
Fig. 3 is a schematic block diagram of an electronic device according to a third embodiment of the present invention; the electronic device of fig. 3 includes:
the installation module 310 is used for installing a test program developed by using a development framework of a first non-embedded operating system in a local embedded operating system, wherein the test program is used for carrying out black box test on an application program to be tested installed in the embedded operating system;
the receiving module 320 receives, through a secure communication connection with the second device, a driver control message sent from a driver installed in a second non-embedded operating system of the second device, where the driver control message indicates that the embedded operating system drives the test program.
The scheme of the embodiment of the invention can install the test program developed by the development framework of the non-embedded operating system in the embedded operating system and control according to the drive control message sent by the drive program installed in the non-embedded operating system. The driver installed in the non-embedded operating system is used for driving, so that the cross-platform test of the application program in the embedded operating system is realized.
In one implementation of the invention, the test program is a program compiled into a program suitable for installation in the embedded operating system using a development framework of the first non-embedded operating system.
In an implementation manner of the present invention, the first device is installed with the first non-embedded operating system, and the test program is a program developed in the first device by using a development framework of the first non-embedded operating system.
In one implementation of the present invention, the electronic device further includes a communication module configured to: establishing a secure communication connection with a first device before installing the test program developed by the development framework of the first non-embedded operating system in the local embedded operating system; based on the secure communication connection with the first device, the installation module 310 is specifically configured to obtain an installation program of the test program from the first device to the local: and installing the installation program of the test program so as to install the test program in the local embedded operating system.
In an implementation manner of the present invention, the communication module is specifically configured to: transmitting installation information of the test program in a local embedded operating system to the second equipment through a secure communication connection with the second equipment; the receiving module 320 is specifically configured to: and receiving the drive control message sent by the driver based on the installation information.
In one implementation manner of the present invention, the receiving module 320 is further configured to: receiving a request message of the driver through a secure communication connection with the second device before transmitting installation information of the test program in a local embedded operating system to the second device through the secure communication connection with the second device, wherein the request message comprises an identification of the test program for acquiring the installation information.
In one implementation of the present invention, the communication module is further configured to: performing a transport layer connection with the second device via a transport layer communication protocol; establishing a secure communication connection with the second device using a key agreement algorithm based on the transport layer connection.
In one implementation manner of the present invention, the communication module is specifically configured to: receiving a pairing message transmitted by the second device invoking a cross-platform secure communication method based on the transport layer connection; after pairing is established in response to the pairing message, determining an agreed password with the second device using the key agreement algorithm to establish a secure communication connection with the second device.
In one implementation manner of the invention, the application program to be tested is a program developed by utilizing a development framework of the first non-embedded operating system.
In an implementation manner of the present invention, the embedded operating system is an IOS system, the first non-embedded operating system is an MAC system, the development framework is an Xcode, and the test program is a UI test program developed based on an xcuisitest.
In one implementation of the invention, the second non-embedded operating system is any one of a MAC system, a LINUX system, and a WINDOWS system.
Fig. 3B is a schematic block diagram of an electronic device according to a third embodiment of the present invention; the embedded device of FIG. 3B, comprising:
the first obtaining module 360 is configured to obtain a first confirmation operation of a pairing request sent by a user on an interactive interface, where the pairing request is sent by a first device, and the first device is provided with a first non-embedded operating system;
a communication establishing module 370, configured to establish a secure communication connection with the first device in response to the first confirmation operation, so as to receive an installation program of a software testing program, where the software testing program is configured to perform a black box test on an application program to be tested installed in the embedded device;
the second obtaining module 380 obtains the installation operation of the user on the installation program on the interactive interface, so as to install the software testing program into the embedded operating system in the embedded device.
The scheme of the embodiment of the invention can install the test program developed by the development framework of the non-embedded operating system in the embedded operating system and control according to the drive control message sent by the drive program installed in the non-embedded operating system. The driver installed in the non-embedded operating system is used for driving, so that the cross-platform test of the application program in the embedded operating system is realized.
Fig. 4 is a schematic block diagram of an electronic apparatus according to a fourth embodiment of the present invention; the electronic device of fig. 4 includes:
the determining module 410 is configured to determine a driver of a test program in a local second non-embedded operating system, where the test program is developed by using a development framework of the first non-embedded operating system, is installed in an embedded operating system of the embedded device, and is used to perform black box testing on an application program to be tested installed in the embedded operating system;
the sending module 420 sends a driving control message to the embedded device by using the driver through the secure communication connection with the embedded device, where the driving control message indicates the embedded operating system to drive the test program.
The scheme of the embodiment of the invention can install the test program developed by the development framework of the non-embedded operating system in the embedded operating system and control according to the drive control message sent by the drive program installed in the non-embedded operating system. The driver installed in the non-embedded operating system is used for driving, so that the cross-platform test of the application program in the embedded operating system is realized.
The software testing method of the present embodiment may be performed by any suitable electronic device having data processing capabilities, including but not limited to: server, mobile terminal (such as mobile phone, PAD, etc.), PC, etc.
In an implementation manner of the present invention, the electronic device further includes an obtaining module and an installing module, where the obtaining module is configured to install the obtained portable container in the local second non-embedded operating system before determining a driver of the test program in the local second non-embedded operating system; the installation module is used for installing the acquired driver into the portable container.
The electronic device of this embodiment is used to implement the corresponding software testing method in the foregoing method embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described herein again. In addition, the functional implementation of each module in the electronic device of this embodiment can refer to the description of the corresponding part in the foregoing method embodiment, and is not repeated here.
Fig. 5 is a schematic structural diagram of an electronic device in a fifth embodiment of the present application; the electronic device may include:
one ormore processors 501;
a computer-readable medium 502, which may be configured to store one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the software testing method as described in the first or second embodiment above.
Fig. 6 is a hardware structure of an electronic device according to a sixth embodiment of the present application; as shown in fig. 4, the hardware structure of the electronic device may include: aprocessor 601, acommunication interface 602, a computer-readable medium 603, and acommunication bus 604;
wherein theprocessor 601, thecommunication interface 602, and the computerreadable medium 603 communicate with each other via acommunication bus 604;
alternatively, thecommunication interface 602 may be an interface of a communication module;
theprocessor 601 may be specifically configured to: installing a test program developed by utilizing a development framework of a first non-embedded operating system in a local embedded operating system, wherein the test program is used for carrying out black box test on an application program to be tested installed in the embedded operating system; receiving, through a secure communication connection with a second device, a drive control message sent from a driver installed in a second non-embedded operating system of the second device, the drive control message instructing the embedded operating system to drive the test program, or,
determining a driver of a test program in a local second non-embedded operating system, wherein the test program is developed by utilizing a development framework of a first non-embedded operating system, is installed in an embedded operating system of embedded equipment, and is used for performing black box test on an application program to be tested installed in the embedded operating system; and sending a drive control message to the embedded equipment by using the drive program through the secure communication connection with the embedded equipment, wherein the drive control message instructs the embedded operating system to drive the test program.
TheProcessor 601 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The computer-readable medium 603 may be, but is not limited to, a Random Access Memory (RAM), a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code configured to perform the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section, and/or installed from a removable medium. The computer program, when executed by a Central Processing Unit (CPU), performs the above-described functions defined in the method of the present application. It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access storage media (RAM), a read-only storage media (ROM), an erasable programmable read-only storage media (EPROM or flash memory), an optical fiber, a portable compact disc read-only storage media (CD-ROM), an optical storage media piece, a magnetic storage media piece, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code configured to carry out operations for the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may operate over any of a variety of networks: including a Local Area Network (LAN) or a Wide Area Network (WAN) -to the user's computer, or alternatively, to an external computer (e.g., through the internet using an internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions configured to implement the specified logical function(s). In the above embodiments, specific precedence relationships are provided, but these precedence relationships are only exemplary, and in particular implementations, the steps may be fewer, more, or the execution order may be modified. That is, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present application may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a receiving module and a first presentation module. Wherein the names of the modules do not in some cases constitute a limitation of the module itself.
As another aspect, the present application also provides a computer-readable medium on which a computer program is stored, the program, when executed by a processor, implementing the software testing method as described in the first or second embodiment.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the apparatus described in the above embodiments; or may be present separately and not assembled into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to: installing a test program developed by utilizing a development framework of a first non-embedded operating system in a local embedded operating system, wherein the test program is used for carrying out black box test on an application program to be tested installed in the embedded operating system;
receiving, through a secure communication connection with a second device, a drive control message sent from a driver installed in a second non-embedded operating system of the second device, the drive control message instructing the embedded operating system to drive the test program, or,
determining a driver of a test program in a local second non-embedded operating system, wherein the test program is developed by utilizing a development framework of a first non-embedded operating system, is installed in an embedded operating system of embedded equipment, and is used for performing black box test on an application program to be tested installed in the embedded operating system; and sending a drive control message to the embedded equipment by using the drive program through the secure communication connection with the embedded equipment, wherein the drive control message instructs the embedded operating system to drive the test program.
The expressions "first", "second", "said first" or "said second" used in various embodiments of the present disclosure may modify various components regardless of order and/or importance, but these expressions do not limit the respective components. The above description is only configured for the purpose of distinguishing elements from other elements. For example, the first user equipment and the second user equipment represent different user equipment, although both are user equipment. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the present disclosure.
When an element (e.g., a first element) is referred to as being "operably or communicatively coupled" or "connected" (operably or communicatively) to "another element (e.g., a second element) or" connected "to another element (e.g., a second element), it is understood that the element is directly connected to the other element or the element is indirectly connected to the other element via yet another element (e.g., a third element). In contrast, it is understood that when an element (e.g., a first element) is referred to as being "directly connected" or "directly coupled" to another element (a second element), no element (e.g., a third element) is interposed therebetween.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.