CN112596750B - Application testing method and device, electronic equipment and computer readable storage medium - Google Patents

Application testing method and device, electronic equipment and computer readable storage medium Download PDF

Info

Publication number
CN112596750B
CN112596750B CN202011586762.6A CN202011586762A CN112596750B CN 112596750 B CN112596750 B CN 112596750B CN 202011586762 A CN202011586762 A CN 202011586762A CN 112596750 B CN112596750 B CN 112596750B
Authority
CN
China
Prior art keywords
test
abnormal
mobile terminals
application
mobile terminal
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
Application number
CN202011586762.6A
Other languages
Chinese (zh)
Other versions
CN112596750A (en
Inventor
李昌
张玮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Anchnet Network Technology Co ltd
Original Assignee
Shanghai Anchnet Network Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Anchnet Network Technology Co ltd filed Critical Shanghai Anchnet Network Technology Co ltd
Priority to CN202011586762.6A priority Critical patent/CN112596750B/en
Publication of CN112596750A publication Critical patent/CN112596750A/en
Application granted granted Critical
Publication of CN112596750B publication Critical patent/CN112596750B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3692—Test management for test results analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Abstract

The embodiment of the application relates to an application testing method, an application testing device, electronic equipment and a computer readable storage medium, aiming at improving the testing efficiency, and the method comprises the following steps: acquiring the type of a system configured by each of a plurality of accessed mobile terminals; creating a plurality of application containers corresponding to the plurality of mobile terminals, wherein different application containers correspond to different mobile terminals and the application containers are isolated from each other; mirror-configuring a test file adapted to a system configured by each of the plurality of mobile terminals to mirror-associate the test file to the plurality of application containers; testing target applications installed by the mobile terminals based on a plurality of application containers associated with the test files; and updating the plurality of application containers related to the test file according to the respective test results of the plurality of mobile terminals.

Description

Application testing method and device, electronic equipment and computer readable storage medium
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to an application testing method, an application testing device, electronic equipment and a computer readable storage medium.
Background
In the related art, an application installed in a mobile terminal is generally tested, and the test method adopted is generally as follows: aiming at a plurality of mobile terminals, systems used by the mobile terminals may be different, and Android and IOS automatic test environments need to be built on a plurality of PCs. The mode of using a plurality of PCs can occupy a large amount of hardware service resources, and after the script runs, the CPU and the memory resources of the whole server end can be greatly consumed, so that the problem of low efficiency of testing the application on the mobile terminal is caused.
Disclosure of Invention
The embodiment of the application testing method and device, the electronic equipment and the computer readable storage medium aims to improve the efficiency of testing the application of the mobile terminal.
A first aspect of an embodiment of the present application provides an application testing method, where the method includes:
acquiring the type of a system configured by each of a plurality of accessed mobile terminals;
creating a plurality of application containers corresponding to the plurality of mobile terminals, wherein different application containers correspond to different mobile terminals and the application containers are isolated from each other;
mirror-configuring a test file adapted to a system configured by each of the plurality of mobile terminals to mirror-associate the test file to the plurality of application containers;
testing target applications installed by the mobile terminals based on a plurality of application containers associated with the test files;
and updating the plurality of application containers related to the test file according to the respective test results of the plurality of mobile terminals.
Optionally, mirror-configuring a test file adapted to a system configured by each of the plurality of mobile terminals, includes:
acquiring different types of test files;
and installing the test file images of the corresponding types to the plurality of application containers according to the adaptation relationship between the types of the systems configured by the plurality of mobile terminals and the types of the test files.
Optionally, after creating the application container corresponding to each of the plurality of mobile terminals, the method further includes:
monitoring connection states between the plurality of mobile terminals and the corresponding application containers;
when a first abnormal mobile terminal with abnormal connection exists, outputting abnormal connection information to restore the connection between the abnormal mobile terminal and the corresponding application container.
Optionally, the testing the target applications installed on the plurality of mobile terminals based on a plurality of application containers associated with the test file includes:
when detecting that the application containers corresponding to the mobile terminals are all associated with the test files, respectively issuing the application packages to be tested to the mobile terminals based on the application containers corresponding to the mobile terminals;
and when receiving the information that the plurality of mobile terminals successfully install the application package to be tested, running the test scripts in the test files corresponding to the plurality of mobile terminals respectively so as to test the target applications installed by the plurality of mobile terminals.
Optionally, the method further comprises:
in the process of testing the target application installed on the plurality of mobile terminals, obtaining test information corresponding to the plurality of mobile terminals respectively, wherein the test information at least comprises log records of a test script in the running process;
determining a second abnormal mobile terminal with abnormal test and the abnormal type of the second abnormal mobile terminal according to the test information respectively corresponding to the plurality of mobile terminals;
when the abnormal type of the second abnormal mobile terminal is determined to be a non-test abnormal type, continuing to test the second abnormal mobile terminal;
and stopping testing the second abnormal mobile terminal when the abnormal type of the second abnormal mobile terminal is determined to be the testing abnormal type.
Optionally, determining the abnormal type of the second abnormal mobile terminal includes:
screenshot is conducted on a display interface of the second abnormal mobile terminal;
determining the abnormal type of the second abnormal mobile terminal according to the recognition result of the screenshot;
the method further comprises the following steps:
generating abnormal information according to the abnormal type of the second abnormal mobile terminal;
and when the preset time arrives, sending the abnormal information to a client corresponding to the second abnormal mobile terminal.
Optionally, updating the plurality of application containers associated with the test file according to the test results of the plurality of mobile terminals includes:
deleting the application container and the test file corresponding to the normal mobile terminal for the normal mobile terminal with the test result as normal;
and resetting the application container and the test file corresponding to the abnormal mobile terminal for the abnormal mobile terminal with the abnormal test result so as to retest the abnormal mobile terminal.
In a second aspect of the embodiments of the present invention, there is provided an application testing apparatus, including:
the identification module is used for acquiring the types of the systems configured by the accessed mobile terminals;
the system comprises a container creating module, a storage module and a processing module, wherein the container creating module is used for creating a plurality of application containers corresponding to the mobile terminals, different application containers correspond to different mobile terminals, and the application containers are mutually isolated;
the environment building module is used for configuring a test file matched with a system configured by each of the plurality of mobile terminals in a mirror image mode so as to associate the test file mirror image to the plurality of application containers;
the test execution module is used for testing the target application installed by the mobile terminals based on the application containers related to the test files;
and the resource updating module is used for updating the plurality of application containers related to the test file according to the respective test results of the plurality of mobile terminals.
A third aspect of embodiments of the present application provides a readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps in the method according to the first aspect of the present application.
A fourth aspect of the embodiments of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the steps of the method according to the first aspect of the present application.
By adopting the application testing method provided by the application testing method, the types of the systems respectively configured by the accessed mobile terminals can be obtained, and a plurality of application containers which are in one-to-one correspondence with the mobile terminals are established, and the application containers are mutually isolated; then, configuring a test file adapted to a system configured by each of the plurality of mobile terminals in a mirror image manner, so as to associate the test file mirror image with the plurality of application containers; testing target applications installed by a plurality of mobile terminals based on a plurality of application containers associated with the test files; and finally updating the application containers of the associated test files according to the respective test results of the mobile terminals.
According to the embodiment of the application, the corresponding application container can be configured for each mobile terminal, and the test file of each mobile terminal is configured in a mirror image mode, so that the application test of a plurality of mobile terminals can be realized on one server, the test of the plurality of mobile terminals is supported based on the application container, and the occupation of test resources can be reduced. And the mode of mirror image configuration of the test file of each mobile terminal enables a plurality of mobile terminals with the same type of system to rapidly configure the test file, improves the efficiency of only testing configuration of the plurality of mobile terminals, and further improves the testing efficiency.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.
FIG. 1 is a diagram of an implementation environment of an application testing method according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating steps of a method for testing an application according to an embodiment of the present application;
FIG. 3 is a schematic overall flow chart of an application testing method according to an embodiment of the present application;
FIG. 4 is a schematic structural framework diagram of an application testing apparatus according to an embodiment of the present application;
fig. 5 is a block diagram of an application test apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related art, applications on the mobile terminal may need to be tested, and the testing of the applications is generally performed by a testing device. In the test, some mobile terminals may use the IOS system and some mobile terminals may use the android system due to different systems used by the mobile terminals. The test equipment will use different software for testing based on different systems.
In order to satisfy the test of the applications of a plurality of mobile terminals at the same time, one way is: the mobile terminals using different systems are connected to one test device respectively, and the test software adapted to the system of the mobile terminals is used for testing, so that a large amount of hardware resources are occupied, and the cost is high.
In addition, a plurality of mobile terminals are tested on one test device, in this way, appium services for two systems are generally started on the test device, and meanwhile, a plurality of virtual machines are arranged on the test device to meet the test requirements of the plurality of mobile terminals, but when the plurality of virtual machines are arranged, the process of installing test software is complicated and time-consuming, and in this way, a plurality of ports are exposed to the outside, so that hidden dangers are caused to the safety of the test device.
Referring to fig. 1, fig. 1 is a schematic diagram of an implementation environment of an embodiment of the present application, and as shown in fig. 1, the implementation environment includes a testing device and a plurality of mobile terminals, where the testing device may be a server or other intelligent terminals, the testing device may include a plurality of data interfaces, and the plurality of mobile terminals may be connected to the testing device through the data interfaces, and the data interfaces may be USB interfaces. The test equipment can identify the accessed mobile terminal through the USB interface, and further can test the applications installed in the mobile terminals. The mobile terminal can be a mobile phone, a tablet and other intelligent devices.
Referring to fig. 2, a flowchart of steps of an application testing method according to an embodiment of the present application is shown, where the application testing method is introduced with reference to fig. 1, and the application testing method may be applied to a testing device, and specifically may include the following steps:
step S201: and acquiring the type of a system configured by each of the accessed mobile terminals.
In this embodiment, the system configured by the mobile terminal may refer to an operating system of the mobile terminal, where the operating system may include an android system, an IOS system, a windows system, and of course, may also include other systems. Generally, an application installed in a mobile terminal runs under an operating system and is adapted to the operating system.
During specific implementation, the test equipment can discover the mobile terminals accessed according to the USB interfaces, and can determine the number of the accessed mobile terminals according to the number of the USB interfaces accessed to the mobile terminals. The device information of the mobile terminal can be acquired through the USB interface, and the type of the moving system is determined according to the device information. The acquired device information of the mobile terminal may at least include a system type, a system version, a device name, and the like, and the device information may be stored in a storage module of the test device.
Step S202: creating a plurality of application containers corresponding to the plurality of mobile terminals.
Wherein, different application containers correspond to different mobile terminals, and the application containers are isolated from each other.
In this embodiment of the application, the test device creates a corresponding number of application containers according to the number of the accessed mobile terminals, for example, if there are 5 accessed mobile terminals, 5 application containers may be created. The mobile terminal and the application container are in one-to-one correspondence, that is, different application containers correspond to different mobile terminals, and specifically, a binding relationship between a device name of the mobile terminal and a corresponding application container may be established, so that a correspondence relationship between the mobile terminal and the application container is established. So that one mobile terminal corresponds to one application container.
The created application containers are mutually isolated, so that the stability of each mobile terminal cluster can be ensured, namely, when the application tests are carried out on the mobile terminals, the application tests are mutually independent and mutually independent, the whole test automation execution process cannot be influenced due to the abnormal connection of a certain mobile terminal, and the stability of the application tests is ensured.
The application container can be a Docker container, and the Docker container can enable developers to pack their applications and dependency packages in a unified manner into a portable container, and then distribute the application and dependency packages to any server (including popular Linux machines and windows machines) provided with a Docker engine, and can also realize virtualization. The containers are fully sandboxed without any interface between each other (like apps of iphones). With little performance overhead, it can easily be run in machines and data centers.
Step S203: and mirror-image configuring a test file adapted to a system configured by each of the plurality of mobile terminals to mirror-associate the test file to the plurality of application containers.
In the embodiment of the application, the mobile terminals connected to the test device may store part of the mobile terminals using the android system, and the other part of the mobile terminals using the IOS system, for different systems, a test file of the adaptive system needs to be used during testing, and the test file may include various configuration information, application scripts and the like required for application testing. In specific implementation, in order to realize rapid configuration of the test files of the plurality of mobile terminals, the corresponding test files can be configured for the plurality of mobile terminals in a mirror image deployment manner. Wherein, the mirror image configuration may refer to: the same test file is mirrored for use with multiple mobile terminals of the same type of system.
After the test files are configured to the plurality of mobile terminals in a mirror image mode, because the application containers are already created, the test files of each mobile terminal can be uniformly packaged into the respective application containers, and therefore the association between the test files and the application containers is completed. Therefore, the whole testing process of the mobile terminals is completed through the application container, the additional testing interface is avoided in the testing process, and the testing efficiency is improved.
In one example, when mirror image configuration is performed on a test file adapted to a system configured by each of the plurality of mobile terminals, different types of test files may be acquired; and then, installing the test file images of the corresponding types to the plurality of application containers according to the adaptation relationship between the types of the systems configured by the plurality of mobile terminals and the types of the test files.
In this example, a test file adapted to multiple types of systems may be preset in the test device, for example, a test file of an IOS system and a test file of an android system are preset, and after creating multiple application containers and obtaining the types of the systems of multiple mobile terminals, a corresponding test file may be installed for at least one mobile terminal using the same system in a mirror image manner, specifically, the test file may be installed in the application container corresponding to the mobile terminal in a mirror image manner.
For example, as shown in fig. 1, assuming that mobile terminals 1 to 3 use an android system and mobile terminals 4 to 6 use an IOS system, for mobile terminals 1 to 3, a test file of the android system is mirrored into application containers of mobile terminals 1 to 3. For mobile terminals 4 to 6, the test files of the IOS system are mirrored into the application containers of mobile terminals 4 to 6.
Step S204: and testing the target application installed by the plurality of mobile terminals based on the plurality of application containers associated with the test file.
In this embodiment, after the application container is created and the test file is installed in a mirror image manner, the building of a test environment for testing the application is realized, in this case, the target application installed on the plurality of mobile terminals can be tested, and each mobile terminal has its own independent application container and test file, so that the parallel testing of the target applications of the plurality of mobile terminals can be realized.
In an example, when a target application installed on the plurality of mobile terminals is tested based on a plurality of application containers associated with the test file, when it is detected that the application containers corresponding to the plurality of mobile terminals are all associated with the test file, the application packages to be tested are respectively issued to the plurality of mobile terminals based on the application containers corresponding to the plurality of mobile terminals; and when receiving the information that the plurality of mobile terminals successfully install the application package to be tested, running the test scripts in the test files corresponding to the plurality of mobile terminals respectively so as to test the target applications installed by the plurality of mobile terminals.
In this example, when testing a plurality of mobile terminals, a tested application package may be issued to the mobile terminal through the respective application container of each mobile terminal, and the tested application package may be adapted to the test file, so that in the testing process, the application of the mobile terminal is tested through the cooperation between the tested application package and the test script in the test file.
In specific implementation, for each mobile terminal, after receiving a tested application package, the mobile terminal can automatically execute installation of the tested application package, and after the installation is completed, information of successfully installing the tested application package can be fed back to the test equipment, and then an application container of the mobile terminal can run a test script in a corresponding test file according to the information, so that a target application in the mobile terminal is tested through the test script.
The target application of the mobile terminal may refer to an application to be tested installed in the mobile terminal, for example, a native application, a web application and a hybrid application on an iOS-and Android-enabled or Windows desktop.
Step S205: and updating the plurality of application containers related to the test file according to the respective test results of the plurality of mobile terminals.
In this embodiment, the test device may obtain respective test results of the plurality of mobile terminals, and specifically, may determine the respective test results of the plurality of mobile terminals by obtaining log records reported after the test script of each mobile terminal is executed. And then, determining whether the target application of the mobile terminal has test abnormality according to the test result, if the test abnormality does not exist, representing that the test on the mobile terminal is successfully completed, and if the test abnormality exists, representing that the test on the mobile terminal is not successfully completed.
The test files and the application containers corresponding to the mobile terminals can be updated according to whether the test on the mobile terminals is successfully completed, so that the test resources of the test equipment can be dynamically updated, and the utilization rate of the test resources of the test equipment is improved.
The test resources of the test equipment may include software and hardware resources, such as memory resources and system resources, that the test equipment can provide for the test.
In one example, updating the plurality of application containers associated with the test file may refer to: deleting the application container and the test file corresponding to the normal mobile terminal for the normal mobile terminal with the test result as normal; and resetting the application container and the test file corresponding to the abnormal mobile terminal for the abnormal mobile terminal with the abnormal test result so as to retest the abnormal mobile terminal.
In this example, the normal mobile terminal with the normal test result may refer to a terminal that successfully completes the application test, and in practice, the application container and the associated test file corresponding to the normal mobile terminal may be deleted from the test device to release the test resources of the test device, so that the part of the test resources may be used for the application test of the new mobile terminal.
The abnormal mobile terminal with the abnormal test result may refer to a terminal that has not successfully completed the application test, and the representation shows that an abnormality occurs in the test process, and in practice, the application container and the associated test file corresponding to the abnormal mobile terminal may be reset, that is, restored to the initial state when the test is not started, and after the reset, the test on the abnormal mobile terminal may be restarted, so as to ensure that the test on the abnormal mobile terminal is successfully completed as much as possible.
Of course, in an example, after the test is completed, a test result report may be generated according to the test result, and the test result report is sent to a client corresponding to the mobile terminal, where the client may also be a mail client, or other social software clients.
By adopting the technical scheme of the embodiment of the application, the testing equipment can intelligently identify the mobile terminals of different systems, and the docker container and the mirror image installation test file are automatically deployed according to the system types of the mobile terminals, so that the automatic test environments required by the mobile terminals of different systems are quickly built, the whole test process can be completed in the docker container, the quick test on the application of the mobile terminals is realized, the test efficiency is improved, after the automatic test is completed, the application container can be quickly destroyed, the resources are released, and the occupation of the resources is reduced.
In some examples, in order to ensure stability of the test, connection states between the plurality of mobile terminals and the respective corresponding application containers may be monitored after the application containers corresponding to the plurality of mobile terminals are created; and when a first abnormal mobile terminal with abnormal connection exists, the connection between the abnormal mobile terminal and the corresponding application container is repaired.
In this example, when the mobile terminal is connected to the test device, the connection state between the mobile terminal and the application container may be monitored in real time, and specifically, the connection state between the mobile terminal and the application container may be determined by detecting the connection state between the test device and the mobile terminal in real time. The method and the device can collect abnormal connection information among a plurality of mobile terminals, if a certain mobile terminal has abnormal connection information, the abnormal connection information can be output, and the output abnormal connection information can include the name of the mobile terminal with abnormal connection, so that a user can conveniently check connection faults. The mobile terminal is the first abnormal mobile terminal, wherein the first abnormal mobile terminal can be reconnected by restarting the test equipment, so that the first abnormal mobile terminal is reconnected to the test equipment, and after the first abnormal mobile terminal is reconnected to the test equipment, a test environment can be set up for the abnormal mobile terminal again according to the equipment name of the first abnormal mobile terminal. Therefore, the stability of the test environment built for the plurality of mobile terminals is guaranteed.
By adopting the method, the stability of the test environment can be ensured on the basis of the framework of the test environment, so that the application test of the mobile terminal is successfully completed.
In still other examples, when a plurality of mobile terminals are started to be tested, in the testing process, test information corresponding to each of the plurality of mobile terminals may be obtained, where the test information at least includes log records of a test script in the running process.
In this embodiment, in the execution process of the test script, in order to track the test process, the test process of each mobile terminal may be monitored, specifically, the test information corresponding to the mobile terminal may be monitored in real time, and the test information may at least include a log record generated in the execution process of the test script. Specifically, log records generated in the running process of test scripts respectively corresponding to the plurality of mobile terminals can be monitored, and the log records can record execution information of the test scripts in the execution process, namely test data for testing the target application of the mobile terminal.
Wherein, through the log record, can find out in time whether the test appears unusually. Then, in the testing process, the testing process can be maintained in time according to whether the test is abnormal or not so as to ensure the success of the test.
Of course, the test information may include, in addition to the log record, container monitoring information for monitoring application containers corresponding to the plurality of mobile terminals, terminal monitoring information for monitoring connection states of the mobile terminals, file monitoring information for monitoring the test file, and the like. By detecting the monitoring information, the abnormity in the test process can be timely discovered.
Specifically, according to the test information respectively corresponding to the plurality of mobile terminals, a second abnormal mobile terminal with an abnormal test and an abnormal type of the second abnormal mobile terminal may be determined, and then, according to the abnormal type, the second abnormal mobile terminal with an abnormal test may be processed, specifically:
and when the abnormal type of the second abnormal mobile terminal is determined to be a non-test abnormal type, continuing the test of the second abnormal mobile terminal.
And stopping testing the second abnormal mobile terminal when the abnormal type of the second abnormal mobile terminal is determined to be the testing abnormal type.
In this example, the second abnormal mobile terminal is a mobile terminal that determines that an abnormality occurs in the test process according to the test information. In this embodiment, the exception type is defined as a non-test exception type and a test exception type according to a requirement.
In an optional implementation manner, when the abnormal type of a second abnormal mobile terminal is determined, screenshot can be performed on a display interface of the second abnormal mobile terminal; and determining the abnormal type of the second abnormal mobile terminal according to the recognition result of the screenshot.
In the implementation mode, when the abnormal condition is detected in real time according to the log record, the screenshot is performed on the display interface of the second abnormal mobile terminal, and the content of the screenshot can represent the service state of the mobile terminal when the second abnormal mobile terminal is in the abnormal test moment. In practice, the screenshot may be identified, specifically, the screenshot may be manually identified, or the screenshot may be input to a preset identification model to identify, so as to determine whether the screenshot includes service information unrelated to the target application, when it is determined that the screenshot includes the service information unrelated to the target application, it may be determined that the exception type is a non-test exception type, otherwise, it is determined that the exception type is a test exception type.
For example, when the mobile terminal 1 has a test exception, the mobile terminal 1 is subjected to screenshot, and whether service information irrelevant to the target application exists in the screenshot is identified, for example, an icon of a to-be-called call appears or an icon of an unread short message appears, the representation is that other services of the mobile phone cause the test exception, at this time, the exception type is determined to be a non-test exception type, otherwise, if the screenshot does not have service information irrelevant to the target application, the exception type is determined to be a test exception type.
In this example, the non-test exception type refers to a test exception caused by information unrelated to the test itself, and in this case, the running script of the second exception mobile terminal may be continuously executed to complete the test.
The test exception type refers to a test exception caused by a test script in the running process or an application container, a test file and the like. In this case, the test of the second abnormal mobile terminal may be stopped, and in practice, the test of the second abnormal mobile terminal may be continued after the test script, the application container, or the test file is reset.
By adopting the embodiment, the management and maintenance of the test data in the test script execution process can be realized, and the successful execution of the test script in the test process is ensured.
In this case, correspondingly, abnormal information may be generated according to the abnormal type of the second abnormal mobile terminal; and when the preset time arrives, the abnormal information is sent to the client corresponding to the second abnormal mobile terminal.
In this embodiment, after the script is abnormal, the abnormal information can be generated and reported according to the abnormal type, and certainly, when the abnormal type is the test abnormal type, the abnormal information can be generated and reported to the user of the mobile terminal in the form of a short message or an email. The client corresponding to the second abnormal mobile terminal may be a mail client, or other social software clients. The preset time may refer to a time negotiated in advance with a user of the mobile terminal, for example, if the user of the mobile terminal wants to obtain the test exception after sending the exception for three hours, the user sends the exception information after three hours, or the preset time refers to a time for completing the application test.
Referring to fig. 3, a general flow diagram of an application testing method according to an embodiment of the present application is shown, and as shown in fig. 3, a general description of an application testing method according to the present application mainly includes the following flows:
101. the server side identifies the smart phone system through the USB interface, and if the smart phone system can be identified, the number of the smart phones is acquired according to the USB interface, and hardware equipment information (system type, system version and equipment name) of the smart phones is acquired and stored. If the mobile phone cannot be identified, reporting the abnormity, restarting the test equipment to solve the problem of unstable USB interface connection, and thus re-identifying the mobile phone. For example, several types of handsets are identified in fig. 3, with N android handsets and 1 IOS handset.
102. According to the steps, hardware equipment information of the mobile phones is collected, the docker containers which are mutually isolated are created on the server, and each mobile phone is provided with one docker container, so that the stability of each mobile phone cluster is guaranteed. When a certain mobile phone is abnormal in connection, reporting the abnormal connection information through the collected abnormal connection information to manually check connection faults, so that the mobile phone is connected to the test equipment through the USB again. And pulling the automatic environments of different mobile phone systems to build a mirror image, and realizing the rapid deployment of the test environment by the mirror image installation of the IOS system and the mirror image installation of the android system.
103. And (3) test execution: after the automatic environment is built, the tested application packages are issued to all the mobile phones, and the tested application packages are installed at the mobile terminals. And feeding back the information of successful installation to the execution module, and executing the automatic test script after successful installation.
104. Monitoring: in the automatic execution process, the occupation of server resources in the execution process of the automatic script is monitored, such as the monitoring server, the monitoring terminal and the monitoring container in fig. 3; and acquiring log records and screenshots, defining abnormal levels according to different abnormal types after the script is abnormal, reporting abnormal information, and reporting the abnormal information to a user in a short message or mail mode. And after the test case is executed, reporting the execution result to the user in an email mode.
On the other hand, monitoring the test data management needs to manage and maintain the test data in the test script execution process to ensure successful execution, such as pulling the test data, the mirror image file, the application package, and the test script in fig. 3 to determine whether an exception occurs.
105. Resource recovery: after the execution is finished, the server resources which cannot be used are released, and the deployed docker environment and the test data need to be reset and deleted according to the script execution condition. And rapidly recovering the server resources and providing service resources for the next automatic script execution.
By adopting the application testing method, intelligent mobile phones (IOS & Android) with different systems can be intelligently identified, the docker containers are automatically deployed according to the types of mobile phone systems, the automatic testing environments required by the mobile phones with different systems are built, and the automatic testing scripts and the application packages are issued. Meanwhile, the automatic test execution process of the mobile phone is monitored, and the abnormality can be reported in time after the abnormality occurs. And recording an automatic execution log and an execution result, and generating an automatic test execution report. After the automatic execution is finished, the container is rapidly destroyed, and the server resources are released. Thus, automated application testing of multiple cell phones can be improved.
Based on the same inventive concept, an embodiment of the present application provides an application testing apparatus 400. Referring to fig. 4, fig. 4 is a schematic diagram of a 4-device according to an embodiment of the present application. As shown in fig. 4, the apparatus includes:
an identifying module 401, configured to obtain the number of a plurality of mobile terminals that are accessed and the types of systems configured by the plurality of mobile terminals;
a container creating module 402, configured to create a plurality of application containers corresponding to the plurality of mobile terminals, where different application containers correspond to different mobile terminals and the application containers are isolated from each other;
an environment building module 403, configured to configure a test file adapted to a system configured by each of the plurality of mobile terminals in a mirror image manner, so as to associate the test file mirror image with the plurality of application containers;
a test execution module 404, configured to test target applications installed on the plurality of mobile terminals based on a plurality of application containers associated with the test file;
a resource updating module 405, configured to update the multiple application containers associated with the test file according to respective test results of the multiple mobile terminals.
Optionally, the environment building module 403 may specifically include the following units:
the acquisition unit is used for acquiring different types of test files;
and the installation unit is used for installing the test file images of the corresponding types to the plurality of application containers according to the adaptive relationship between the types of the systems configured by the plurality of mobile terminals and the types of the test files.
Optionally, the apparatus may further include the following modules:
the monitoring module is used for monitoring the connection state between the plurality of mobile terminals and the corresponding application containers;
and the repairing module is used for outputting abnormal connection information when a first abnormal mobile terminal with abnormal connection exists so as to recover the connection between the abnormal mobile terminal and the corresponding application container.
Optionally, the test execution module 404 may specifically include the following units:
the issuing unit is used for issuing the application packages to be tested to the mobile terminals respectively based on the application containers corresponding to the mobile terminals when detecting that the application containers corresponding to the mobile terminals are all associated with the test files;
and the running unit is used for running the test scripts in the test files respectively corresponding to the mobile terminals when the information that the mobile terminals successfully install the tested application packages is received, so as to test the target applications installed by the mobile terminals.
Optionally, the apparatus may further include the following modules:
a log record obtaining module, configured to obtain test information corresponding to each of the plurality of mobile terminals during a process of testing a target application installed on the plurality of mobile terminals, where the test information at least includes a log record of a test script during an operation process;
the abnormality determining module is used for determining a second abnormal mobile terminal with abnormal test and the abnormal type of the second abnormal mobile terminal according to the test information respectively corresponding to the plurality of mobile terminals;
the first processing module is used for continuing testing the second abnormal mobile terminal when the abnormal type of the second abnormal mobile terminal is determined to be a non-testing abnormal type;
and the second processing module is used for stopping the test of the second abnormal mobile terminal when the abnormal type of the second abnormal mobile terminal is determined to be the test abnormal type.
Optionally, the abnormality determining module may specifically include the following units:
the screenshot unit is used for screenshot on a display interface of the second abnormal mobile terminal;
the identification unit is used for determining the abnormal type of the second abnormal mobile terminal according to the identification result of identifying the screenshot;
the apparatus may further include the following modules:
an abnormal information generating module, configured to generate abnormal information according to the abnormal type of the second abnormal mobile terminal;
and the information sending module is used for sending the abnormal information to a client corresponding to the second abnormal mobile terminal when the preset time arrives.
Optionally, the resource updating module 405 may specifically include the following units:
the first updating unit is used for deleting the application container and the test file corresponding to the normal mobile terminal for the normal mobile terminal with the normal test result;
and the second updating unit is used for resetting the application container and the test file corresponding to the abnormal mobile terminal for the abnormal mobile terminal with the abnormal test result so as to retest the abnormal mobile terminal.
Referring to fig. 5, a schematic diagram of a module architecture of a test device is shown, and as shown in fig. 5, a common configuration of the test device includes 6 module devices, specifically, an intelligent identification module device, a file management module device, an environment building module device, a test execution module device, a monitoring module device, and a resource management module device.
The smart identification module apparatus may include the identification module 401.
As shown in fig. 5, the file management module device may be used for managed application packages, and may include the log record obtaining module and the screenshot module. The file management module device can be used for mirror image management of software required to be depended on in an automatic environment, including mirror image management of test files required to be depended on in Android and IOS automatic tests. And automatic test script management, which is used for maintaining the automatic test script of the mobile terminal of the mobile phone. And log and screenshot management, which is used for tracking the whole script execution process and managing the execution log and screenshot of the script in the automatic script execution process. And the test data management is used for managing and maintaining the test data in the test script execution process, including the management of the test report and the test data, and ensuring that the test script is successfully executed in the test process.
The environment building module device may include the above-mentioned environment building module 403, the container building module 402, and a module for collecting hardware device information of the mobile terminal. According to the equipment identification of the mobile terminal, the docker containers which are mutually isolated are established on the server, and the stability of each mobile terminal cluster is ensured. When a certain mobile terminal is abnormal in connection, the collected abnormal connection information is reported to a user, so that the abnormal connection information is manually checked, the abnormal connection between the mobile terminal and the abnormal connection mobile terminal is restored, and the stability of USB connection is guaranteed. Meanwhile, according to the type and the number of the obtained mobile terminal devices, the corresponding number of docker containers is created according to the number, the automatic environments of different mobile phone systems are pulled through the file management module device to build mirror images, and quick deployment is achieved through mirror image installation.
The monitoring module device may include the monitoring module, the abnormality determining module, the first processing module and the second processing module, the abnormality information generating module, and the information sending module. The method is used for monitoring the execution process of the automatic script, the occupation of server resources, log recording and screenshot in the automatic execution process, can define the abnormal level according to different abnormal types after the script is abnormal, reports abnormal information and reports the abnormal information to a user in the form of short messages or mails. And after the test case is executed, reporting the execution result to the user in an email mode.
The resource recycling module device may include the resource updating module 405, configured to release unused server resources after the automatic script is executed, and reset and delete deployed docker environments and test data according to the script execution condition. And rapidly recovering the server resources and providing service resources for the next automatic script execution.
Thus, the test equipment shown in fig. 5 can realize application test of a plurality of mobile terminals, so as to improve test efficiency and save test resources.
Based on the same inventive concept, another embodiment of the present application provides a readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps in the application testing method according to any of the above embodiments of the present application.
Based on the same inventive concept, another embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and running on the processor, and when the processor executes the computer program, the electronic device implements the steps in the application testing method according to any of the above embodiments of the present application.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The application test method, device, equipment and storage medium provided by the application are introduced in detail, and a specific example is applied in the description to explain the principle and the implementation of the application, and the description of the embodiment is only used to help understand the method and the core idea of the application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims (8)

1. An application testing method, the method comprising:
acquiring the type of a system configured by each of a plurality of accessed mobile terminals;
establishing a corresponding number of application containers according to the number of the accessed mobile terminals, wherein different application containers correspond to different mobile terminals and the application containers are isolated from each other;
mirror-configuring a test file adapted to a system configured by each of the plurality of mobile terminals to mirror-associate the test file to the plurality of application containers; the test files comprise various configuration information, application scripts and the like required by application test, and the same test files are configured for a plurality of mobile terminals using the same system in a mirror image deployment mode;
testing target applications installed by the mobile terminals based on a plurality of application containers associated with the test files;
updating a plurality of application containers associated with the test files according to respective test results of the plurality of mobile terminals;
wherein the testing the target applications installed by the plurality of mobile terminals based on the plurality of application containers associated with the test file comprises:
when detecting that the application containers corresponding to the mobile terminals are all associated with the test files, respectively issuing the application packages to be tested to the mobile terminals based on the application containers corresponding to the mobile terminals;
when information that the plurality of mobile terminals successfully install the application package to be tested is received, running test scripts in test files corresponding to the plurality of mobile terminals respectively so as to test target applications installed by the plurality of mobile terminals;
the method further comprises the following steps:
in the process of testing the target application installed on the plurality of mobile terminals, obtaining test information corresponding to the plurality of mobile terminals respectively, wherein the test information at least comprises log records of a test script in the running process;
determining a second abnormal mobile terminal with abnormal test and the abnormal type of the second abnormal mobile terminal according to the test information respectively corresponding to the plurality of mobile terminals;
when the abnormal type of the second abnormal mobile terminal is determined to be a non-test abnormal type, continuing to test the second abnormal mobile terminal;
and stopping testing the second abnormal mobile terminal when the abnormal type of the second abnormal mobile terminal is determined to be the testing abnormal type.
2. The method of claim 1, wherein mirroring the test file adapted to the system configured by each of the plurality of mobile terminals comprises:
acquiring different types of test files;
and installing the test file images of the corresponding types to the plurality of application containers according to the adaptation relationship between the types of the systems configured by the plurality of mobile terminals and the types of the test files.
3. The method according to claim 1, wherein after creating the application container corresponding to each of the plurality of mobile terminals, the method further comprises:
monitoring connection states between the plurality of mobile terminals and the corresponding application containers;
when a first abnormal mobile terminal with abnormal connection exists, outputting abnormal connection information to restore the connection between the abnormal mobile terminal and the corresponding application container.
4. The method of claim 3, wherein determining the type of anomaly of the second anomalous mobile terminal comprises:
screenshot is conducted on a display interface of the second abnormal mobile terminal;
determining the abnormal type of the second abnormal mobile terminal according to the recognition result of the screenshot;
the method further comprises the following steps:
generating abnormal information according to the abnormal type of the second abnormal mobile terminal;
and when the preset time arrives, sending the abnormal information to a client corresponding to the second abnormal mobile terminal.
5. The method according to any of claims 1-4, wherein updating the plurality of application containers associated with the test file according to the test results of the plurality of mobile terminals comprises:
deleting the application container and the test file corresponding to the normal mobile terminal for the normal mobile terminal with the test result as normal;
and resetting the application container and the test file corresponding to the abnormal mobile terminal for the abnormal mobile terminal with the abnormal test result so as to retest the abnormal mobile terminal.
6. An application testing apparatus, the apparatus comprising:
the mobile terminal comprises an identification module, a processing module and a processing module, wherein the identification module is used for acquiring the number of a plurality of accessed mobile terminals and the types of systems configured by the mobile terminals;
the system comprises a container creating module, a container creating module and a container selecting module, wherein the container creating module is used for creating application containers with corresponding quantity according to the quantity of accessed mobile terminals, different application containers correspond to different mobile terminals, and a plurality of application containers are mutually isolated;
the environment building module is used for configuring a test file adaptive to a system configured by each of the plurality of mobile terminals in a mirror image manner so as to associate the test file mirror image with the plurality of application containers, wherein the test file comprises various configuration information, application scripts and the like required by application test, and the same test file is configured for the plurality of mobile terminals using the same system in a mirror image deployment manner;
the test execution module is used for testing the target application installed by the mobile terminals based on the application containers related to the test files;
the resource updating module is used for updating a plurality of application containers related to the test files according to respective test results of the plurality of mobile terminals;
wherein, the test execution module includes:
the issuing sub-module is used for issuing the application packages to be tested to the mobile terminals respectively based on the application containers corresponding to the mobile terminals when detecting that the application containers corresponding to the mobile terminals are all associated with the test files;
the test submodule is used for running test scripts in test files corresponding to the mobile terminals respectively when information that the mobile terminals successfully install the tested application packages is received, so that target applications installed by the mobile terminals are tested;
the device further comprises:
a log record obtaining module, configured to obtain test information corresponding to each of the plurality of mobile terminals during a process of testing a target application installed on the plurality of mobile terminals, where the test information at least includes a log record of a test script during an operation process;
the abnormality determining module is used for determining a second abnormal mobile terminal with abnormal test and the abnormal type of the second abnormal mobile terminal according to the test information respectively corresponding to the plurality of mobile terminals;
the first processing module is used for continuing testing the second abnormal mobile terminal when the abnormal type of the second abnormal mobile terminal is determined to be a non-testing abnormal type;
and the second processing module is used for stopping the test of the second abnormal mobile terminal when the abnormal type of the second abnormal mobile terminal is determined to be the test abnormal type.
7. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 5.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method according to any of claims 1 to 5 are implemented when the computer program is executed by the processor.
CN202011586762.6A 2020-12-28 2020-12-28 Application testing method and device, electronic equipment and computer readable storage medium Active CN112596750B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011586762.6A CN112596750B (en) 2020-12-28 2020-12-28 Application testing method and device, electronic equipment and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011586762.6A CN112596750B (en) 2020-12-28 2020-12-28 Application testing method and device, electronic equipment and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN112596750A CN112596750A (en) 2021-04-02
CN112596750B true CN112596750B (en) 2022-04-26

Family

ID=75203989

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011586762.6A Active CN112596750B (en) 2020-12-28 2020-12-28 Application testing method and device, electronic equipment and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN112596750B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113890846A (en) * 2021-09-23 2022-01-04 深圳Tcl新技术有限公司 Distribution network detection method, device and system, storage medium and terminal equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106407101A (en) * 2015-07-31 2017-02-15 三亚中兴软件有限责任公司 LXC-based continuous integration method and apparatus
CN106502905A (en) * 2016-10-26 2017-03-15 腾讯科技（深圳）有限公司 A kind of method of testing of application program, apparatus and system
CN110765026A (en) * 2019-10-31 2020-02-07 北京东软望海科技有限公司 Automatic testing method and device, storage medium and equipment
CN111679965A (en) * 2020-04-23 2020-09-18 平安国际智慧城市科技股份有限公司 Automatic testing method and device, computer equipment and storage medium
WO2020253079A1 (en) * 2019-06-17 2020-12-24 平安科技（深圳）有限公司 Jmeter-based distributed performance test method and apparatus, device, and storage medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106484620B (en) * 2016-10-12 2019-06-18 北京元心科技有限公司 Method for testing multi-system terminal equipment, control equipment and console
CN108376061B (en) * 2016-10-13 2019-12-10 北京百度网讯科技有限公司 Method and apparatus for developing unmanned vehicle applications
CN108829399B (en) * 2018-04-13 2022-05-20 杭州朗和科技有限公司 Application testing method, testing device, medium and computing equipment
CN110399307A (en) * 2019-07-31 2019-11-01 网宿科技股份有限公司 A kind of test method, test platform and destination server

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106407101A (en) * 2015-07-31 2017-02-15 三亚中兴软件有限责任公司 LXC-based continuous integration method and apparatus
CN106502905A (en) * 2016-10-26 2017-03-15 腾讯科技（深圳）有限公司 A kind of method of testing of application program, apparatus and system
WO2020253079A1 (en) * 2019-06-17 2020-12-24 平安科技（深圳）有限公司 Jmeter-based distributed performance test method and apparatus, device, and storage medium
CN110765026A (en) * 2019-10-31 2020-02-07 北京东软望海科技有限公司 Automatic testing method and device, storage medium and equipment
CN111679965A (en) * 2020-04-23 2020-09-18 平安国际智慧城市科技股份有限公司 Automatic testing method and device, computer equipment and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Container Cluster Model Development for Legacy Applications Integration in Scientific Software System;A. S. Trunov 等;《2018 IEEE International Conference "Quality Management, Transport and Information Security, Information Technologies" (IT&QM&IS)》;20181108;815-819 *
docker容器技术在MES系统部署中的应用;相铮 等;《制造业自动化》;20200602(第04期);116-119 *

Also Published As

Publication number Publication date
CN112596750A (en) 2021-04-02

Similar Documents

Publication Publication Date Title
CN108399132B (en) Scheduling test method, device and storage medium
CN102736978B (en) A kind of method and device detecting the installment state of application program
CN110471831B (en) Automatic method and device for compatibility test
US20150100829A1 (en) Method and system for selecting and executing test scripts
US20150100832A1 (en) Method and system for selecting and executing test scripts
CN110765018B (en) Automatic interface testing method and equipment
CN104765678A (en) Method and device for testing applications on mobile terminal
US20150100830A1 (en) Method and system for selecting and executing test scripts
US20150100831A1 (en) Method and system for selecting and executing test scripts
CN111881014B (en) System test method, device, storage medium and electronic equipment
CN111258913A (en) Automatic algorithm testing method and device, computer system and readable storage medium
CN111400125A (en) Memory overflow monitoring method, device, equipment and storage medium of JAVA process
CN114064208A (en) Method and device for detecting application service state, electronic equipment and storage medium
CN108108296B (en) Cloud testing method, server and client
CN112241360A (en) Test case generation method, device, equipment and storage medium
CN111813495A (en) Node testing method and device, storage medium and electronic device
CN114527996A (en) Multi-service deployment method and device, electronic equipment and storage medium
CN110618853B (en) Detection method, device and equipment for zombie container
CN112596750B (en) Application testing method and device, electronic equipment and computer readable storage medium
CN107357721B (en) Method and device for testing system
CN113238930A (en) Software system testing method and device, terminal equipment and storage medium
CN110990289B (en) Method and device for automatically submitting bug, electronic equipment and storage medium
CN107168819B (en) Method and device for restarting operating system
CN112269733B (en) Automatic aging test method for server and storage medium
CN115237441A (en) Upgrade test method, device and medium based on cloud platform

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
GR01 Patent grant
GR01 Patent grant