CN108399132B - Scheduling test method, device and storage medium - Google Patents
Scheduling test method, device and storage medium Download PDFInfo
- Publication number
- CN108399132B CN108399132B CN201810237216.8A CN201810237216A CN108399132B CN 108399132 B CN108399132 B CN 108399132B CN 201810237216 A CN201810237216 A CN 201810237216A CN 108399132 B CN108399132 B CN 108399132B
- Authority
- CN
- China
- Prior art keywords
- task
- test
- tested
- module
- configuration file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses a scheduling test method, a scheduling test device and a storage medium, which are applied to the technical field of information processing. When first operation information of a certain task to be tested is received through the task scheduling platform, the task scheduling platform determines a configuration file of the task to be tested, wherein the configuration file comprises identification information and an execution sequence of a plurality of testing modules executing the task to be tested; and then calling the corresponding test module according to the configuration file, and executing the task to be tested by the called test module. Therefore, the method in the process of executing the test tasks is divided into a plurality of independent test modules, the sequence of each test module executing the test tasks is limited by the configuration file, and the method can not be limited to a specific method flow for executing a certain test task, so that a plurality of test tasks can be integrated by one task scheduling platform, the task scheduling platform is convenient to expand, and the test efficiency is greatly improved.
Description
Technical Field
The present invention relates to the field of information processing technologies, and in particular, to a scheduling test method, apparatus, and storage medium.
Background
In the process of developing the application program, the application program needs to be tested, and the application program can be tested by adopting a plurality of testing methods, each testing method corresponds to one set of task scheduling platform, specifically, the task scheduling platform is required to issue a corresponding testing task to an application terminal loaded with the application program, the application terminal executes the testing task, and the application terminal reports an execution result to the task scheduling platform.
Each existing task scheduling platform is constructed in an integrated mode, only single testing task issuing is supported, the flow of issuing the testing task is fixed, and if an application program needs to be tested by executing other testing tasks, a set of adaptive task scheduling platforms need to be redeveloped, so that the testing efficiency is low.
Disclosure of Invention
The embodiment of the invention provides a scheduling test method, a scheduling test device and a storage medium, which are used for calling a corresponding test module according to a determined configuration file and executing a task to be tested by the called test module.
A first aspect of an embodiment of the present invention provides a scheduling test method, including:
receiving first operation information of a task to be tested through a task scheduling platform;
determining a configuration file of the task to be tested according to the first operation information, wherein the configuration file comprises identification information and an execution sequence of a plurality of test modules executing the task to be tested;
and calling the corresponding testing module according to the configuration file, and executing the task to be tested by the called testing module.
A first aspect of an embodiment of the present invention provides a scheduling test apparatus, including:
the operation receiving unit is used for receiving first operation information of a task to be tested through the scheduling testing device;
the configuration determining unit is used for determining a configuration file of the task to be tested according to the first operation information, wherein the configuration file comprises identification information and an execution sequence of a plurality of test modules executing the task to be tested;
and the testing unit is used for calling the corresponding testing module according to the configuration file and executing the task to be tested by the called testing module.
A third aspect of the embodiments of the present invention provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the scheduling test method according to the first aspect of the embodiments of the present invention.
A fourth aspect of the embodiments of the present invention provides a terminal device, including a processor and a storage medium, where the processor is configured to implement each instruction;
the storage medium is configured to store a plurality of instructions, where the instructions are configured to be loaded by a processor and to perform the scheduling test method according to the first aspect of the embodiment of the present invention.
In the method of the embodiment, the task scheduling platform integrates a plurality of testing tasks, so that when first operation information of a certain task to be tested is received by the task scheduling platform, the task scheduling platform can determine a configuration file of the task to be tested, wherein the configuration file comprises identification information and an execution sequence of a plurality of testing modules executing the task to be tested; and then calling the corresponding test module according to the configuration file, and executing the task to be tested by the called test module. Therefore, the method in the process of executing the test tasks is divided into a plurality of independent test modules, the execution sequence of each test module used for executing different test tasks is limited by the configuration file, the method can not be limited to a specific method flow for executing a certain test task, so that a plurality of test tasks can be integrated by one task scheduling platform, when a certain test task is newly added, only the related information of the newly added test task needs to be stored in the task scheduling platform, the task scheduling platform is convenient to expand, and the test efficiency is greatly improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a task scheduling platform according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method for scheduling tests according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a user interface provided by the task scheduling platform in one embodiment of the invention;
FIG. 4a is a schematic structural diagram of a task scheduling platform provided in an embodiment of the present invention;
FIG. 4b is a diagram illustrating test modules in a task scheduling platform according to an embodiment of the present invention;
FIG. 5 is a flowchart of a method executed by modules and test modules in a sub-process in an embodiment of the present invention;
FIG. 6 is a flow chart of a main thread included in a sub-process and each test module executing a task to be tested in an embodiment of the present invention;
FIG. 7 is a flow chart of a method performed by a service module in an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a scheduling test apparatus according to an embodiment of the present invention;
FIG. 9 is a schematic structural diagram of another scheduling test apparatus according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be 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 invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The embodiment of the invention provides a scheduling test method, which is mainly applied to a task scheduling platform shown in figure 1, wherein the task scheduling platform comprises: the system comprises a main control module and a plurality of test modules (illustrated by taking n execution modules as an example in fig. 1), wherein the main control module is used for determining a configuration file of each test task and sequentially calling the corresponding test modules according to the configuration file; each test module is used for executing a corresponding method, and the method executed by a certain test module is at least one step in the scheduling test process. The task scheduling platform of the embodiment of the invention integrates the issuing of various test tasks and the execution flow of the various test tasks, and has wide applicability.
In the embodiment of the present invention, the task scheduling platform may perform the scheduling test by the following method:
receiving first operation information of a task to be tested through a task scheduling platform; determining a configuration file of the task to be tested according to the first operation information, wherein the configuration file comprises identification information and an execution sequence of a plurality of test modules executing the task to be tested; and calling the corresponding test module according to the configuration file, and executing the task to be tested by the called test module.
Therefore, the method in the process of executing the test tasks is divided into a plurality of independent test modules, the execution sequence of each test module used for executing different test tasks is limited by the configuration file, the method can not be limited to a specific method flow for executing a certain test task, so that a plurality of test tasks can be integrated by one task scheduling platform, when a certain test task is newly added, only the related information of the newly added test task needs to be stored in the task scheduling platform, the task scheduling platform is convenient to expand, and the test efficiency is greatly improved.
The embodiment of the invention provides a scheduling test method, which is a method executed by the task scheduling platform, and the flow chart is shown in fig. 2, and comprises the following steps:
It can be understood that, in the implementation of the present invention, the main control module of the task scheduling platform may provide a user operation interface to the user to initiate an execution process of each task to be tested, for example, the task scheduling platform may provide the user operation interface as shown in fig. 3, where the user operation interface includes a first selection interface of the task to be tested, and may also include a second selection interface of an application program corresponding to the task to be tested, and the like. The first selection interface and the second selection interface may be in any form, and what is shown in fig. 3 is only one specific implementation manner, that is, the pull-down keys (i.e., inverted triangles in the drawing) are used to represent that when a user clicks a first pull-down key, the task scheduling platform may display information of test tasks (i.e., test task 1 to test task p) that can be selected by the user, and when the user clicks a second pull-down key, the task scheduling platform may display information of application programs (i.e., application program 1 to application program m) that can be selected by the user.
Therefore, a user can select any test task through the first selection interface on the user operation interface and click the 'confirm' button, so that the main control module receives the first operation information of the task to be tested through the first selection interface. Further, the user may also select at least one application program of the testing task through a second selection interface on the user operation interface, and click the "ok" button, so that the main control module receives second operation information of the at least one application program through the second selection interface, and the at least one application program may be an application program relied on for executing the task to be tested.
The test task is for testing the application program, and may specifically include, but is not limited to, any of the following information: the method comprises the following steps of performance testing, memory leakage testing, installation package checking, static code scanning testing, data reporting testing, User Interface (UI) stuck testing, strictness mode (strictmode) checking, diamond scanning, robotiummonkey and google monkey stability testing and the like. The application program may be a program that implements a certain function, such as a news program, or a video program, etc.
For example, the monkey stability test covers the functions used by the application, but focuses on whether the application crashes (crash), the memory leak test covers all the functions of the application, and the memory overflow test focuses on whether all the functions are traversed.
In the implementation of the present invention, a plurality of test modules in the task scheduling platform may be divided according to a plurality of references, for example, according to the reference of the method sequence of executing the test tasks, the test modules may be divided as follows: the system comprises a task state reporting module (reporttasskstatus), a screenshot module (makeScreenShot), a log reporting module (log), an installation tested application module (installPackage), a running test tool module (runTestTool), a download tested application module (downloadTestPackage) and a download test tool module (downloadTestTool), wherein the test tool is the type of executing the test task, and the tested application is an application program.
For another example, the test module may be divided into the following test modules according to the externally dependent reference for executing the test task: an installation package module (which may perform download, installation, uninstallation, etc.) and a tool module (which may perform start, stop, etc.) and the like. The external dependency for executing the test task refers to a program outside the task scheduling platform that is relied on in the process of executing the test task, for example, the installation package module mainly depends on the application program, and the tool module mainly depends on the test tool.
Each test module is an independent executable program and can be independently called, and the information of each test module is independently stored in a local database of the task scheduling platform.
When executing this step, the main control module of the task scheduling platform may determine the configuration file according to the execution policy corresponding to the task to be tested, where different test tasks correspond to different configuration files, where the configuration files may include: the method comprises the following steps of executing which test modules are needed by a task to be tested, and specifically indicating the needed test modules through identification information of the test modules; and the execution sequence of the test modules, where the plurality of test modules executing the tasks to be tested may be all the test modules included in the task scheduling platform or may be part of the test modules. The execution strategy corresponding to each task to be tested can be preset on the task scheduling platform by a user. Therefore, when the task scheduling platform needs to expand a new test task, only the information of the newly added test task needs to be stored in the task scheduling platform, and the information of the newly added test task includes an execution strategy corresponding to the newly added test task and also can include identification information of the newly added test task and the like.
Further, since a certain test module in the task scheduling platform may execute at least one method, for example, the task state reporting module may execute a state in which the task to be tested starts to be executed, and may also report a state in which the task to be tested ends to be executed, if the configuration file determined in this step includes the identification information of the task state reporting module, a specific method in the process of executing the task to be tested by the task state reporting module is also required to be included in the configuration file.
In some cases, a configuration file may include parameters or the like on which a plurality of test modules performing tasks to be tested rely on to perform respective methods. For example, downloading parameters on which the application under test module depends may include: project identification, system and package identification of the application, and the like; installing parameters on which the application module under test depends may include: device identification, system of application, package identification and package name, etc.
And 103, calling the corresponding test module according to the configuration file, and executing the task to be tested by the called test module.
Specifically, after the main control module in the task scheduling platform determines the configuration file, the corresponding test modules are sequentially called according to the configuration file, and the called test modules execute the corresponding methods. In the process of calling the test module, if the test module is called for the first time, the main control module loads the test module firstly, namely, information of the test module is cached in a memory of the task scheduling platform, and then the test module is operated; if the test module is not called for the first time, the main control module can directly jump to the operation test module because the information of the test module is loaded in the memory of the task scheduling platform.
It should be noted that, the above steps 101 to 103 are methods for executing a task to be tested when a user initiates the task to be tested through a user operation interface provided by the task scheduling platform. In a specific application embodiment, a user may simultaneously initiate a plurality of tasks to be tested through a user operation interface provided by the task scheduling platform, so that the task scheduling platform may execute the plurality of tasks to be tested in parallel according to the methods of the above steps 101 to 103.
It can be seen that, in the method of this embodiment, the task scheduling platform integrates multiple testing tasks, so that when the task scheduling platform receives the first operation information of a certain task to be tested, the task scheduling platform determines a configuration file of the task to be tested, including identification information and an execution sequence of a plurality of testing modules executing the task to be tested; and then calling the corresponding test module according to the configuration file, and executing the task to be tested by the called test module. Therefore, the method in the process of executing the test tasks is divided into a plurality of independent test modules, the execution sequence of each test module used for executing different test tasks is limited by the configuration file, the method can not be limited to a specific method flow for executing a certain test task, so that a plurality of test tasks can be integrated by one task scheduling platform, when a certain test task is newly added, only the related information of the newly added test task needs to be stored in the task scheduling platform, the task scheduling platform is convenient to expand, and the test efficiency is greatly improved.
It should be noted that, in the method of the above embodiment, the user initiates the process of executing the task to be tested independent of other application programs outside the task scheduling platform through the task scheduling platform, and in other specific embodiments, the user may also initiate the process of executing the task to be tested dependent on at least one application program outside the task scheduling platform through the task scheduling platform. In this way, before the main control module of the task scheduling platform executes the step 102, second operation information of at least one application program corresponding to the task to be tested can be received through the task scheduling platform; when the corresponding test module is called as the first test module according to the configuration file when the step 103 is executed, the first test module sends the task to be tested to the application terminal corresponding to the application program for execution according to the second operation information. Here, the application terminal of the at least one application may be a physical application terminal in which the at least one application is loaded; or at least one physical application terminal respectively loading at least one application program; it is also possible that a plurality of physical terminals are each loaded with at least one application. And the first testing module is a module for performing a task to be tested.
When the step 103 is executed, if the corresponding test module is called as the second test module according to the configuration file, the second test module receives the execution information of the task to be tested, which is reported by the application terminal of the at least one application program. The execution information may include a log (log) of executing the task to be tested, screenshot information when executing the task to be tested, a flag (flag) generated during the execution of the task to be tested, and the like. Here, the second testing module is a module for acquiring the report information.
A specific application example is used to describe the scheduling test method, as shown in fig. 4a, the task scheduling platform in this embodiment may include a sub-process (sub process) main control module, a service (server) module, a plurality of test modules, and a database, and the plurality of test modules in this embodiment are divided according to the reference of the method sequence executed by the test tasks, as shown in fig. 4b, the scheduling test method specifically includes the following modules: a task state reporting module, a screenshot module, a log (log) reporting module, a tested application installing module, a test tool running module, a tested application downloading module and a test tool downloading module.
The subprocess master control module is used for determining the configuration file of each test task and calling the corresponding test module in sequence according to the configuration file.
And the service module is used for managing data transmitted between the subprocess main control module and each test module, managing data transmitted between each test module and the like.
A database for storing information, such as program codes, of the respective test modules independently; and may also store tags (flag), logs, screenshots, etc. during the execution of the test tasks. The database may specifically be a sqlite database.
The label is used for linking each test module, for example, after the test tool module finishes downloading the test tool, a label is generated, and the label records the information that the test tool finishes downloading and a downloading path; the running test tool module then executes the test tool only if the tag is read.
The log reporting module is used for reporting logs in the execution process of the test task, and mainly reports information such as problems encountered in the execution process of the test task; and the report module is also used for informing the report log module to stop reporting.
And the task state reporting module is used for reporting the state of starting execution of the test task and also reporting the state of ending execution of the test task.
And the screenshot module is used for starting to capture the picture, conveniently positioning problems in the test task execution process and informing the screenshot module to stop screenshot.
And installing the tested application module for installing the tested application and uninstalling the tested application (namely the application program).
The test tool module is run for executing the test tool, i.e. the test task.
And the downloading tested application module is used for downloading the tested application.
And the downloading test tool module is used for downloading the test tool.
Each of the test modules may be roughly divided into a block module and a non-block module, where the non-block module is a module that does not need to wait for a result to be returned after being called, for example, the screenshot module belongs to the non-block module when executing a step of starting to capture a picture; the blocking module refers to a module that is called in sequence, and the execution of the current module must be executed after the previous module is successfully executed, for example, the above-mentioned downloading of the application module to be tested and the downloading of the testing tool module.
In this embodiment, the test tasks that the task scheduling platform can issue may include at least one of the following test tasks: the method comprises the following steps of performance testing, memory leakage testing, installation package inspection, static code scanning testing, data reporting testing, UI pause testing, strictmode inspection, diamond scanning, robotiummonkey and google monkey stability testing and the like. Some of the test tasks are device monitoring tasks, which refer to tasks executed by devices outside the task scheduling platform, that is, the devices outside the task scheduling platform need to be connected in the process of executing the test tasks, an application program is loaded on the devices, and the application program executes the test tasks, such as google monkey stability test. Some test tasks are non-device tasks, which refer to tasks that do not depend on devices outside the task scheduling platform, and the task scheduling platform executes the test tasks, such as static code scanning test and the like.
Referring to fig. 5, the sub-process main control module and each test module of this embodiment may be executed according to the following method:
in step 201, the sub-process main control module may provide a user operation interface, and a user may initiate a process of a task to be tested through the user operation interface.
After the main thread determines the configuration file, it may first check whether each test module is the test module of the latest version, and if not, it needs to download the test module of the latest version.
And 203, the main thread calls the corresponding test modules according to the configuration files in the database according to a certain sequence, and runs the called test modules, and the test modules jointly execute the tasks to be tested.
For each blocking module in the test modules, after the execution of another test module is finished, the current blocking module is operated, the operation result of the current blocking module is obtained, the operation result is stored in the database, and the process is ended; and each non-blocking module can directly end the flow after the execution is finished.
Specifically, the main thread and each test module may execute the task to be tested through the following steps a to D, and a flowchart is shown in fig. 6 and includes:
step A, the main thread reads a configuration file corresponding to the task to be tested from the database through an interface of the database, wherein the configuration file comprises identification information of the test modules to be used, an execution method and an execution sequence of each test module, and some necessary parameters during the operation of the test modules.
And step B, after the main thread reads the configuration files, the configuration files are analyzed, and file directories are established in the database according to the configuration files, wherein one test module corresponds to one directory.
And step C, the main thread acquires the identification information, the execution method and the execution sequence of each test module from the configuration file, and also has some necessary parameters.
And D, calling the corresponding test module by the main thread according to the information acquired in the step C, and executing the task to be tested by the corresponding test module. And after the task to be tested is executed, ending the process.
When the management thread determines whether the blocking module fails to operate, the management thread may determine according to the operation result of each blocking module obtained by the blocking module.
And step 205, ending the process and ending the operation of each test module.
Referring to fig. 7, the service module of this embodiment may be implemented as follows:
at step 301, the service module opens a port (e.g., 60080 port) and listens to the port, and the service module maintains a queue for temporarily buffering information stored in the database.
An embodiment of the present invention further provides a test invoking device, such as the task scheduling platform, where a schematic structural diagram of the test invoking device is shown in fig. 8, and the test invoking device specifically includes:
an operation receiving unit 10, configured to receive, by the scheduling test apparatus, first operation information of a task to be tested.
A configuration determining unit 11, configured to determine a configuration file of the task to be tested according to the first operation information received by the operation receiving unit 10, where the configuration file includes identification information and an execution sequence of a plurality of test modules executing the task to be tested.
The configuration determining unit 11 is specifically configured to determine the configuration file according to the execution policy corresponding to the task to be tested.
Wherein the plurality of test modules comprise any combination of: the device comprises a task state reporting module, a screenshot module, a log reporting module, a tested application installing module, a test tool running module, a tested application downloading module and a test tool downloading module.
Or, the plurality of test modules comprise tool modules, or comprise tool modules and installation pack modules; the installation package module is used for acquiring, installing and uninstalling the application program, and the tool module is used for starting to execute the task to be tested and stopping executing the task to be tested.
The testing unit 12 is configured to call a corresponding testing module according to the configuration file determined by the configuration determining unit 11, and the called testing module executes the task to be tested.
Further, the operation receiving unit 10 is further configured to receive, by the scheduling testing apparatus, second operation information of at least one application program corresponding to the task to be tested; when the testing unit 12 calls the corresponding testing module as the first testing module according to the configuration file, the first testing module sends the task to be tested to the application terminal corresponding to the at least one application program for execution according to the second operation information.
And when the testing unit 12 calls the corresponding testing module as a second testing module according to the configuration file, the second testing module receives the execution information of the task to be tested, which is reported by the application terminal of the at least one application program.
It can be seen that, in the apparatus of this embodiment, a plurality of test tasks are integrated, so that when the operation receiving unit 10 receives the first operation information of a certain task to be tested by scheduling the test apparatus, the configuration determining unit 11 determines the configuration file of the task to be tested, which includes the identification information and the execution sequence of the plurality of test modules executing the task to be tested; then, the testing unit 12 calls the corresponding testing module according to the configuration file, and the called testing module executes the task to be tested. Therefore, the method in the process of executing the test tasks is divided into a plurality of independent test modules, the execution sequence of each test module used for executing different test tasks is limited by the configuration file, the method can not be limited to a specific method flow for executing a certain test task, so that a plurality of test tasks can be integrated by one task scheduling platform, when a certain test task is newly added, only the related information of the newly added test task needs to be stored in the scheduling test device, the expansion of the task scheduling platform is convenient, and the test efficiency is greatly improved.
Referring to fig. 9, in a specific embodiment, the scheduling test apparatus may further include, in addition to the structure shown in fig. 8: an interface providing unit 13 and a storage unit 14, wherein:
the interface providing unit 13 is configured to provide a user operation interface, where the user operation interface includes a first selection interface of the task to be tested; the operation receiving unit 10 is specifically configured to receive the first operation information of the task to be tested through the first selection interface provided by the interface providing unit 13.
The storage unit 14 is configured to store information of a newly added test task, where the information of the newly added test task includes an execution policy corresponding to the newly added test task. Thus, when the configuration determining unit 11 determines the configuration file of the newly added test task, the configuration file is determined according to the execution policy stored in the storage unit 14.
The present invention further provides a terminal device, a schematic structural diagram of which is shown in fig. 10, where the terminal device may generate a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 20 (e.g., one or more processors) and a memory 21, and one or more storage media 22 (e.g., one or more mass storage devices) storing the application programs 221 or the data 222. Wherein the memory 21 and the storage medium 22 may be a transient storage or a persistent storage. The program stored in the storage medium 22 may include one or more modules (not shown), each of which may include a series of instruction operations for the terminal device. Still further, the central processor 20 may be arranged to communicate with the storage medium 22, and to execute a series of instruction operations in the storage medium 22 on the terminal device.
Specifically, the application program 221 stored in the storage medium 22 includes an application program for scheduling test, and the program may include the operation receiving unit 10, the configuration determining unit 11, the testing unit 12, the interface providing unit 13, and the storage unit 14 in the scheduling test apparatus, which will not be described herein again. Further, the central processor 20 may be configured to communicate with the storage medium 22, and execute a series of operations corresponding to the application program of the scheduled test stored in the storage medium 22 on the terminal device.
The terminal equipment may also include one or more power supplies 23, one or more wired or wireless network interfaces 24, one or more input-output interfaces 25, and/or one or more operating systems 223, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and the like.
The steps executed by the scheduling test apparatus in the above method embodiment may be based on the structure of the terminal device shown in fig. 10.
The embodiment of the present invention further provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the scheduling test method executed by the scheduling test apparatus.
The embodiment of the invention also provides terminal equipment, which comprises a processor and a storage medium, wherein the processor is used for realizing each instruction;
the storage medium is used for storing a plurality of instructions which are used for being loaded by the processor and executing the scheduling test method executed by the scheduling test device.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The scheduling test method, apparatus and storage medium provided by the embodiment of the present invention are described in detail above, and a specific example is applied in the description to explain the principle and the embodiment of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, 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 invention.
Claims (12)
1. A method for scheduling testing, comprising:
receiving first operation information of a task to be tested through a task scheduling platform;
determining a configuration file of the task to be tested according to the first operation information, wherein the configuration file comprises identification information and an execution sequence of a plurality of test modules executing the task to be tested, and parameters on which the plurality of test modules execute corresponding methods; wherein each test module is an independent executable program, and the determining the configuration file of the task to be tested specifically includes: determining the configuration file according to the execution strategy corresponding to the task to be tested;
calling a corresponding testing module according to the configuration file, and executing the task to be tested by the called testing module;
the method further comprises the following steps: and storing the information of the newly added test tasks, wherein the information of the newly added test tasks comprises the execution strategies corresponding to the newly added test tasks.
2. The method of claim 1, wherein prior to receiving, by the task scheduling platform, the first operational information for the task to be tested, the method further comprises:
providing a user operation interface, wherein the user operation interface comprises a first selection interface of the task to be tested;
receiving, by the task scheduling platform, first operation information of a task to be tested, which specifically includes: and receiving first operation information of the task to be tested through the first selection interface.
3. The method of claim 1, wherein the plurality of test modules comprises any combination of:
the device comprises a task state reporting module, a screenshot module, a log reporting module, a tested application installing module, a test tool running module, a tested application downloading module and a test tool downloading module.
4. The method of claim 1, wherein the plurality of test modules comprises a tool module;
the tool module is used for starting to execute the task to be tested and stopping executing the task to be tested.
5. The method of claim 4, wherein the plurality of test modules further comprises an installation package module for obtaining, installing, and uninstalling applications.
6. The method of any one of claims 1 to 5,
before determining the configuration file of the task to be tested, the method further comprises: receiving second operation information of at least one application program corresponding to the task to be tested through the task scheduling platform;
when the corresponding test module is called as the first test module according to the configuration file, the called test module executes the task to be tested, which specifically includes: and the first testing module sends the task to be tested to an application terminal corresponding to the at least one application program for execution according to the second operation information.
7. The method of claim 6,
when the corresponding test module is called as a second test module according to the configuration file, the called test module executes the task to be tested, which specifically includes: and the second testing module receives the execution information of the task to be tested, which is reported by the application terminal of the at least one application program.
8. A dispatch test apparatus, comprising:
the operation receiving unit is used for receiving first operation information of a task to be tested;
a configuration determining unit, configured to determine, according to the first operation information, a configuration file of the task to be tested, where the configuration file includes identification information and an execution sequence of a plurality of test modules that execute the task to be tested, and parameters on which the plurality of test modules execute corresponding methods; each test module is an independent executable program, and the configuration determining unit is specifically configured to determine the configuration file according to an execution policy corresponding to the task to be tested;
the testing unit is used for calling the corresponding testing module according to the configuration file and executing the task to be tested by the called testing module;
the device further comprises: and the storage unit is used for storing the information of the newly added test tasks, and the information of the newly added test tasks comprises the execution strategies corresponding to the newly added test tasks.
9. The apparatus of claim 8,
the interface providing unit is used for providing a user operation interface, and the user operation interface comprises a first selection interface of the task to be tested;
the operation receiving unit is specifically configured to receive the first operation information of the task to be tested through the first selection interface.
10. The device according to any of the claims 8 to 9,
the operation receiving unit is further configured to receive, by the scheduling testing apparatus, second operation information of at least one application program corresponding to the task to be tested;
when the test unit calls the corresponding test module as a first test module according to the configuration file, the first test module sends the task to be tested to an application terminal corresponding to the at least one application program for execution according to the second operation information;
and when the test unit calls the corresponding test module as a second test module according to the configuration file, the second test module receives the execution information of the task to be tested, which is reported by the application terminal of the at least one application program.
11. A computer-readable storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the method of scheduling tests of any of claims 1 to 7.
12. A terminal device, comprising a processor and a memory, wherein the processor is configured to implement instructions;
the memory is configured to store a plurality of instructions for loading and executing the method of scheduling tests of any of claims 1 to 7 by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810237216.8A CN108399132B (en) | 2018-03-21 | 2018-03-21 | Scheduling test method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810237216.8A CN108399132B (en) | 2018-03-21 | 2018-03-21 | Scheduling test method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108399132A CN108399132A (en) | 2018-08-14 |
| CN108399132B true CN108399132B (en) | 2021-01-08 |
Family
ID=63091557
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810237216.8A Active CN108399132B (en) | 2018-03-21 | 2018-03-21 | Scheduling test method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108399132B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109710508B (en) * | 2018-08-20 | 2024-03-15 | 天航长鹰(江苏)科技有限公司 | Test method, test device, test apparatus, and computer-readable storage medium |
| CN111435227B (en) * | 2018-12-25 | 2023-07-21 | 中移（杭州）信息技术有限公司 | Smart home equipment testing method, device, equipment and medium |
| CN110704311B (en) * | 2019-09-24 | 2023-11-21 | 卓米私人有限公司 | Application program testing method and device, electronic equipment and readable storage medium |
| CN111008124B (en) * | 2019-10-25 | 2023-01-24 | 武汉迎风聚智科技有限公司 | Task scheduling method and device for database test |
| CN110968504A (en) * | 2019-11-07 | 2020-04-07 | 京东数字科技控股有限公司 | Test method, test platform, electronic device and computer storage medium |
| CN111352668A (en) * | 2020-02-27 | 2020-06-30 | 珠海格力智能装备有限公司 | Device testing method and device based on plug-in and testing system based on plug-in |
| CN111580989B (en) * | 2020-04-30 | 2023-05-02 | 成都新潮传媒集团有限公司 | File processing method and device |
| CN112527312B (en) * | 2020-12-15 | 2022-03-01 | 西安中朗智控科技有限公司 | Test method and test device for embedded system |
| CN113535560A (en) * | 2021-07-14 | 2021-10-22 | 杭州网易云音乐科技有限公司 | Test execution method and device, storage medium and computing equipment |
| CN114356771A (en) * | 2021-12-31 | 2022-04-15 | 龙芯中科(武汉)技术有限公司 | Operation method, device and equipment of data processing entity |
| CN115623077B (en) * | 2022-10-18 | 2023-08-18 | 开元华创科技(集团)有限公司 | Autonomous controllable test system |
| CN116594884B (en) * | 2023-05-16 | 2023-10-27 | 上海安般信息科技有限公司 | Fuzzy test method and device based on concurrent mode |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107577527A (en) * | 2017-08-30 | 2018-01-12 | 北京金山安全软件有限公司 | Task generation and scheduling method and device |
| CN107608878A (en) * | 2017-08-11 | 2018-01-19 | 北京奇虎科技有限公司 | A kind of Web automated testing methods and device |
| CN108334454A (en) * | 2018-03-02 | 2018-07-27 | 东信和平科技股份有限公司 | A kind of automatic scheduling method and system of smart card test platform |
-
2018
- 2018-03-21 CN CN201810237216.8A patent/CN108399132B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107608878A (en) * | 2017-08-11 | 2018-01-19 | 北京奇虎科技有限公司 | A kind of Web automated testing methods and device |
| CN107577527A (en) * | 2017-08-30 | 2018-01-12 | 北京金山安全软件有限公司 | Task generation and scheduling method and device |
| CN108334454A (en) * | 2018-03-02 | 2018-07-27 | 东信和平科技股份有限公司 | A kind of automatic scheduling method and system of smart card test platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108399132A (en) | 2018-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108399132B (en) | Scheduling test method, device and storage medium | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| CN106844136B (en) | Method and system for collecting program crash information | |
| CN108595329B (en) | Application testing method and device and computer storage medium | |
| US7512933B1 (en) | Method and system for associating logs and traces to test cases | |
| CN111324423B (en) | Method and device for monitoring processes in container, storage medium and computer equipment | |
| CN111090536A (en) | Method, device, medium and electronic equipment for acquiring memory leakage information | |
| CN110225078B (en) | Application service updating method, system and terminal equipment | |
| CN107045475B (en) | Test method and device | |
| CN102999343A (en) | Method and device for forbidding self-starting of startup project | |
| US10579513B2 (en) | Test run control method and apparatus | |
| US20150100831A1 (en) | Method and system for selecting and executing test scripts | |
| US20130185596A1 (en) | Serialized Error Injection Into a Function Under Test | |
| CN111159031A (en) | Method for applying mobile terminal automation test, computer device and computer readable storage medium | |
| CN113050984A (en) | Resource calling method and device, electronic equipment and storage medium | |
| CN112199284A (en) | Program automation testing method and corresponding device, equipment and medium | |
| CN103019706A (en) | Method and device for processing startup item | |
| CN109783284A (en) | Information acquisition method, system and server, computer readable storage medium | |
| CN112256588A (en) | Resource allocation method for application program test, computer readable storage medium and tester | |
| CN109739756B (en) | Method and equipment for testing application of mobile terminal | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN112463574A (en) | Software testing method, device, system, equipment and storage medium | |
| CN115454856A (en) | Multi-application security detection method, device, medium and electronic equipment | |
| CN115525568A (en) | Code coverage rate inspection method and device, computer equipment and storage medium | |
| CN111209197B (en) | Application continuous integration test method, system, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |