CN108108297B - Method and device for automatic testing - Google Patents

Method and device for automatic testing Download PDF

Info

Publication number
CN108108297B
CN108108297B CN201611054093.1A CN201611054093A CN108108297B CN 108108297 B CN108108297 B CN 108108297B CN 201611054093 A CN201611054093 A CN 201611054093A CN 108108297 B CN108108297 B CN 108108297B
Authority
CN
China
Prior art keywords
test
scene
configuration
environment
xml
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
CN201611054093.1A
Other languages
Chinese (zh)
Other versions
CN108108297A (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.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen 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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201611054093.1A priority Critical patent/CN108108297B/en
Publication of CN108108297A publication Critical patent/CN108108297A/en
Application granted granted Critical
Publication of CN108108297B publication Critical patent/CN108108297B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management

Abstract

The invention relates to an automatic testing method and a device, comprising the following steps: receiving a test request, wherein the test request comprises test task information, and the test task information comprises test environment configuration information and test scene configuration information; acquiring an extensible markup language (XML) environment configuration file, analyzing the XML environment configuration file to acquire environment configuration parameters matched with the test environment configuration information, and establishing a corresponding test environment according to the environment configuration parameters; acquiring an XML scene configuration file, analyzing the XML scene configuration file to acquire scene configuration parameters matched with the test scene configuration information, and calling a scene trigger interface to trigger a corresponding test scene according to the scene configuration parameters; and acquiring test configuration resource data, and testing in the test environment and the test scene according to the test configuration resource data, so that the construction efficiency of the test environment is improved, and the test scene can be constructed quickly and conveniently.

Description

Method and device for automatic testing
Technical Field
The invention relates to the technical field of computers, in particular to an automatic testing method and device.
Background
With the development of computer technology, a large number of client applications are released, and before the release, the functions of the applications need to be tested and detected, so that faults are eliminated. The operation configuration test refers to a test which can be performed only by acquiring resource configuration, for example, a computer housekeeper displays a vulnerability repair test scene after lightning disinfection is completed, and acquires a scene name, a vulnerability repair icon, edited characters and the like of the lightning disinfection, so as to display corresponding vulnerability repair icons and characters after the lightning disinfection is completed.
According to the traditional test method, a test scenario of a client is constructed through a test script, the test script needs to be continuously maintained along with the updating of the application, the compiling complexity of the test script is high, the construction of the test scenario is difficult, and the maintenance cost is high. Different test environments are often needed for operation configuration tests, a virtual machine is adopted in the traditional tests to construct the test environments, and operation time consumption for recovering the virtual machine, copying files and the like is long, so that the operation configuration tests with high requirements on timeliness are seriously influenced.
Disclosure of Invention
Therefore, it is necessary to provide a method and an apparatus for automated testing to solve the above technical problems, so as to improve the efficiency of building a testing environment and quickly and conveniently build a testing scenario.
A method of automated testing, the method comprising:
receiving a test request, wherein the test request comprises test task information, and the test task information comprises test environment configuration information and test scene configuration information;
acquiring an extensible markup language (XML) environment configuration file, analyzing the XML environment configuration file to acquire environment configuration parameters matched with the test environment configuration information, and establishing a corresponding test environment according to the environment configuration parameters;
acquiring an XML scene configuration file, analyzing the XML scene configuration file to acquire scene configuration parameters matched with the test scene configuration information, and calling a scene trigger interface to trigger a corresponding test scene according to the scene configuration parameters;
and acquiring test configuration resource data, and testing in the test environment and the test scene according to the test configuration resource data.
An apparatus for automated testing, the apparatus comprising:
the device comprises a test request receiving module, a test request receiving module and a test processing module, wherein the test request receiving module is used for receiving a test request, the test request comprises test task information, and the test task information comprises test environment configuration information and test scene configuration information;
the test environment establishing module is used for acquiring an extensible markup language (XML) environment configuration file, analyzing the XML environment configuration file to acquire environment configuration parameters matched with the test environment configuration information, and establishing a corresponding test environment according to the environment configuration parameters;
the test scene triggering module is used for acquiring an XML scene configuration file, analyzing the XML scene configuration file to acquire a scene configuration parameter matched with the test scene configuration information, and calling a scene triggering interface to trigger a corresponding test scene according to the scene configuration parameter;
and the test module is used for acquiring test configuration resource data and testing in the test environment and the test scene according to the test configuration resource data.
The method and the device for the automatic test receive the test request, the test request comprises test task information, the test task information comprises test environment configuration information and test scene configuration information, an extensible markup language (XML) environment configuration file is obtained, the XML environment configuration file is analyzed to obtain environment configuration parameters matched with the test environment configuration information, a corresponding test environment is established according to the environment configuration parameters, the XML scene configuration file is obtained, the XML scene configuration file is analyzed to obtain scene configuration parameters matched with the test scene configuration information, a scene trigger interface is called according to the scene configuration parameters to trigger a corresponding test scene, test configuration resource data is obtained, tests are carried out in the test environment and the test scene according to the test configuration resource data, the test environment is established through the XML environment configuration file, and the problems that a virtual machine is recovered when the test environment is restored by adopting the virtual machine are avoided, The method has the advantages that the problem that operation time is long due to copying of files and the like is solved, the efficiency of establishing the test environment is greatly improved, meanwhile, scene configuration parameters are obtained through the XML scene configuration file, the scene trigger interface is called to trigger the test scenes, each test scene is not needed to compile corresponding test scripts, different test scenes are needed to be generated, only different scene configuration parameters need to be transmitted, simplicity and convenience are achieved, the maintenance cost of the test scripts is reduced, and the test scenes can be established quickly and conveniently.
Drawings
FIG. 1 is a diagram of an application environment for a method of automated testing in one embodiment;
FIG. 2 is a diagram illustrating an internal structure of the terminal of FIG. 1 according to one embodiment;
FIG. 3 is a flow diagram of a method for automated testing in one embodiment;
FIG. 4 is a flow diagram of establishing a test environment in one embodiment;
FIG. 5 is a flow diagram of obtaining scene configuration parameters in one embodiment;
FIG. 6 is a flow diagram of a trigger test scenario in one embodiment;
FIG. 7 is a flow diagram of obtaining test configuration resources in one embodiment;
FIG. 8 is a diagram illustrating an exemplary automated testing process in accordance with an exemplary embodiment;
FIG. 9 is a diagram illustrating the acquisition of target test configuration resources in an exemplary embodiment;
FIG. 10 is a block diagram showing the structure of an apparatus for automated testing in one embodiment;
FIG. 11 is a block diagram showing the structure of an apparatus for automated testing in another embodiment;
FIG. 12 is a block diagram that illustrates the structure of a test environment setup module in one embodiment;
FIG. 13 is a block diagram illustrating the structure of a test scenario trigger module in one embodiment;
FIG. 14 is a block diagram of the structure of a test module in one embodiment;
FIG. 15 is a block diagram showing an apparatus for automated testing in still another embodiment.
Detailed Description
FIG. 1 is a diagram of an application environment in which a method for automated testing operates, according to one embodiment. As shown in fig. 1, the application environment includes a terminal 110 and a server 120, wherein the terminal 110 and the server 120 communicate via a network.
The terminal 110 may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, and the like. The server 120 is configured to send a test request to the terminal 110, where the terminal 110 establishes a corresponding test environment and triggers a corresponding test scenario according to configuration information carried in the test request, obtains test configuration resource data from the server 120, and performs a test in the test environment and the test scenario according to the test configuration resource data.
In one embodiment, the internal structure of the terminal 110 in fig. 1 is as shown in fig. 2, and the terminal 110 includes a processor, a graphic processing unit, a storage medium, a memory, a network interface, a display screen, and an input device, which are connected through a system bus. The storage medium of the terminal 110 stores an operating system, and further includes an automatic testing apparatus, which is used to implement an automatic testing method for the terminal. The processor is used to provide computational and control capabilities that support the operation of the entire terminal 110. The graphic processing unit in the terminal 110 is configured to at least provide a drawing capability of a display interface, the memory provides an environment for operating an automated testing apparatus in the storage medium, and the network interface is configured to perform network communication with the server 120, such as receiving a test request and test resource configuration data sent by the server 120. The display screen is used for displaying an application interface and the like, such as a test scene interface for displaying trigger, and the input device is used for receiving commands or data input by a user. For a terminal 110 with a touch screen, the display screen and input device may be a touch screen.
In one embodiment, as shown in fig. 3, there is provided an automated testing method, which is exemplified by a terminal applied in the application environment, and includes the following steps:
step S210, receiving a test request, where the test request includes test task information, and the test task information includes test environment configuration information and test scenario configuration information.
Specifically, when a test is required, the server sends a test request to the test terminal, where the test request includes test task information, and the test task information includes a test task identifier for distinguishing multiple test tasks and configuration information of the test tasks. The test environment configuration information is used for configuring a test environment, and the test scenario configuration information is used for configuring a test scenario, wherein the test environment refers to a general term of computer hardware, software, network equipment and historical data which are necessary for completing a test task. The test scenario refers to a current state of a product to be tested, which is necessary for completing a test task, such as a commonly used test scenario, for example, a scenario when the test scenario is idle. The test environment configuration information may include a test environment attribute keyword and a key value, where the test environment attribute keyword may be a test environment name keyword, a test environment identification keyword, and the like, and the key values corresponding to different keywords may be different character types, such as a test environment name keyword corresponding to a chinese character type, and a test environment identification keyword corresponding to a numeric type. The test scenario configuration information may include test scenario attribute keywords and key values, where the test scenario attribute keywords may be test scenario name keywords, test scenario identification keywords, and the like, and the key values corresponding to different keywords may be different character types, such as test scenario name keywords corresponding to chinese character types, and test scenario identification keywords corresponding to numeric types. Specifically, which type of keyword is used to identify the target test environment and the target test scenario may be customized as desired.
Different test tasks correspond to different test environment configuration information and test scenario configuration information. Before sending the test request, the server acquires the test environment configuration information and the test scene configuration information, and generates test task information according to the test environment configuration information and the test scene configuration information. The test environment configuration information and the test scenario configuration information can be generated by the configuration of operators in the background.
Step S220, obtaining an extensible markup language (XML) environment configuration file, analyzing the XML environment configuration file to obtain environment configuration parameters matched with the test environment configuration information, and establishing a corresponding test environment according to the environment configuration parameters.
Specifically, an Extensible Markup Language (XML) is a Markup Language used for marking a file to make the file have a structure, and an XML environment configuration file carries environment configuration data through the XML Language, may include environment configuration parameters corresponding to a plurality of different test environments, and distinguishes, through a certain structure and a certain tag, the positions of each different test environment and the matched environment configuration parameters in the XML environment configuration file. As the tags of the XML are not predefined, the tags can be defined by self according to the needs, so that the XML environment configuration file is more flexible and convenient to generate. During testing, the XML environment configuration file is only needed to be analyzed, and the target environment configuration parameters matched with the test environment configuration information are searched to establish the corresponding test environment. When the XML environment configuration file is analyzed, the boundary position of the configuration parameter corresponding to each testing environment can be obtained by searching the testing environment label, and then the testing environment attribute key word and the key value which are consistent with the target testing environment attribute key word and the target key value corresponding to the testing environment configuration information are searched in the environment configuration parameters corresponding to each testing environment, so that the target environment configuration parameter corresponding to the target testing environment is determined. The type of the test environment attribute key words can also be set as a fixed type, and the corresponding target environment configuration parameters can be obtained only by searching the position of the target key value in the XML environment configuration file.
The XML environment configuration file can be obtained from the version management tool SVN in real time, and the XML environment configuration file is guaranteed to be the latest configuration file and can be directly used. The XML environment configuration file may also be obtained from the terminal, and the XML environment configuration file obtained from the terminal is often encrypted and needs to be decrypted first to obtain the original data. The environment configuration parameters have different types, such as a file type and a registration phenotype, and different operations can be performed according to the specific types of the environment parameters so as to establish different test environments. The test environment is established through the XML environment configuration file, the problem that the time consumption is long due to operations such as virtual machine recovery and file copying when the test environment is restored by the virtual machine is solved, and the efficiency of establishing the test environment is greatly improved.
Step S230, acquiring an XML scene configuration file, parsing the XML scene configuration file to acquire a scene configuration parameter matching the test scene configuration information, and calling a scene trigger interface to trigger a corresponding test scene according to the scene configuration parameter.
Specifically, the XML scene configuration file carries scene configuration data through an XML language, and may include scene configuration parameters corresponding to a plurality of different test scenes, and the positions of the different test scenes and the matched scene configuration parameters in the XML environment configuration file are distinguished through a certain structure and a certain label. As the tags of the XML are not predefined, the tags can be defined according to the needs, so that the XML scene configuration file is more flexible and convenient to generate. During testing, the XML scene configuration file is only needed to be analyzed, the target scene configuration parameters matched with the test scene configuration information are searched, and therefore the target scene configuration parameters call the scene trigger interface to trigger the corresponding test scene. When the XML scene configuration file is analyzed, the boundary position of the configuration parameter corresponding to each test scene can be obtained by searching the test scene label, and then the test scene attribute key word and the key value which are consistent with the target test scene attribute key word and the target key value corresponding to the test scene configuration information are searched in the scene configuration parameter corresponding to each test scene, so that the target scene configuration parameter corresponding to the target scene environment is determined. The XML scene configuration file can be obtained from the version management tool SVN in real time, and the XML scene configuration file is guaranteed to be the latest configuration file and can be directly used. The XML scene configuration file can also be acquired from the terminal, and the XML scene configuration file acquired from the terminal is often encrypted and needs to be decrypted to obtain original data.
The scene trigger interface is a method corresponding to various events forming the test scene, which are provided for the outside to call the internal package. The scene trigger interface triggers different events in sequence according to different scene configuration parameters, so that methods corresponding to different events are called to complete generation of each intermediate scene, and a target test scene is finally generated. The method corresponding to each event is packaged in the form of an interface, a corresponding test script does not need to be written in each test scene, different test scenes only need to be generated, different scene configuration parameters only need to be transmitted, and the method is simple and convenient, so that the maintenance cost of the test scripts is reduced. And the target test scene can be reached at one time, when a plurality of intermediate test scenes exist, the target test scene can be automatically and continuously generated, the problem that the scene is triggered to depend on a client control when a control clicking mode is adopted is avoided, and if the client is subjected to edition changing, a script is rewritten and the stability is not high is solved.
Step S240, acquiring the testing configuration resource data, and testing in the testing environment and the testing scene according to the testing configuration resource data.
Specifically, the test configuration resource data is used to provide resources required by the test, including icons, text, control data, video data, and the like. Different test scenarios correspond to different test configuration resource data. A test configuration resource data acquisition request may be sent to the server, thereby acquiring corresponding test configuration resource data from the server. The incidence relation between the test scene and the test configuration resource data can be established, so that the test configuration resource data matched with the test scene is obtained. And when the test environment and the test scene are successfully established and the test configuration resource data is successfully acquired, the corresponding test task can be completed to obtain the current test result.
In one embodiment, the test task information further includes expected test result information, and after step S240, further includes: and acquiring a current test result, and generating a test report according to the current test result and the expected test result information.
Specifically, the expected test result information is carried in the test task information and can be in one-to-one correspondence with the test task identifiers, so that the expected test result information corresponding to the current test task is obtained when the current test result is obtained. The expected test result information corresponds to different types of information according to different types of current test tasks, such as whether a window is popped up or not, whether a preset file exists or not, whether a preset control is displayed or not, a target information summary md5(Message Digest Algorithm 5) value of the file, and the like. After the expected test result information is extracted from the test task information, the expected test result information, the test environment configuration information and the test scene configuration information can be respectively stored in different tables of a terminal database, and the incidence relation among the tables is established.
And comparing and analyzing the expected test result with the current test result to obtain a test report, and if the current test result is inconsistent with the expected test result, analyzing the fault reason. The test report in a preset format, such as an HTML test report, may be generated and sent to the operation configuration server, or sent to the corresponding user through an email or an instant messaging tool.
In this embodiment, by receiving a test request including test task information, where the test task information includes test environment configuration information and test scenario configuration information, obtaining an XML environment configuration file in an XML markup language, parsing the XML environment configuration file to obtain environment configuration parameters matching the test environment configuration information, establishing a corresponding test environment according to the environment configuration parameters, obtaining an XML scenario configuration file, parsing the XML scenario configuration file to obtain scenario configuration parameters matching the test scenario configuration information, invoking a scenario trigger interface according to the scenario configuration parameters to trigger a corresponding test scenario, obtaining test configuration resource data, performing a test in the test environment and the test scenario according to the test configuration resource data, and establishing the test environment through the XML environment configuration file, the virtual machine is prevented from being recovered, and the test environment is prevented from being restored when the test environment is restored by the virtual machine, The method has the advantages that the problem that operation time is long due to copying of files and the like is solved, the efficiency of establishing the test environment is greatly improved, meanwhile, scene configuration parameters are obtained through the XML scene configuration file, the scene trigger interface is called to trigger the test scenes, each test scene is not needed to compile corresponding test scripts, different test scenes are needed to be generated, only different scene configuration parameters need to be transmitted, simplicity and convenience are achieved, the maintenance cost of the test scripts is reduced, and the test scenes can be established quickly and conveniently.
In one embodiment, step S210 is followed by: writing the test task information into a database, analyzing the test task information stored in the database, establishing a task management queue according to the test task information, putting the test task corresponding to the test task information into the task management queue, and triggering a first test task in the task management queue to execute.
Specifically, the test task information may be written into a table in the database, where different data carried in the test task information may be written into different tables, for example, the test environment configuration information is written into the environment configuration table, the test scenario configuration information is written into the scenario configuration table, and the expected test result information is written into the verification information table, so that corresponding data may be quickly obtained from different tables in the following. And pulling up the task scheduling module when the test task information is successfully written into the database. The task management queue is used for managing the test tasks, and the task scheduling module can determine the number of the test tasks according to the test task information, so that the task management queue with the matched length is established, and the test tasks are placed in the task management queue. And judging whether the currently executed test task exists or not, if so, waiting for the current test task to be executed, and executing the next test task in the task management queue. If the waiting time exceeds the preset threshold, the current test task fails to be executed and encounters a fault, the current test task can be deleted, and the next test task in the task management queue is executed. The task management queue can ensure that all test tasks are executed in order.
In one embodiment, as shown in fig. 4, step S220 includes:
step S221, a target test environment attribute key word and a first target key value are obtained according to the test environment configuration information.
Specifically, the target test environment attribute key is used for describing and identifying the type of the test environment, and for example, a test environment can be uniquely identified by a test environment name, a test application name and a test application user name. The first target key value is used for describing specific content corresponding to the target test environment attribute key word, and if the target test environment attribute key word is protokaley and the first target key value is fitstgame, it indicates that the test environment to be configured uses protokaley as a key word and is named fitstgame. The number of the target test environment attribute keywords and the first target key values can be multiple, and each target test environment attribute keyword is provided with a corresponding target key value, so that the test environment is determined from multiple dimensions. If the target test environment attribute key further comprises an "ID", a target key value corresponding to the "ID" is "14", which indicates that the name of the test environment to be configured is fitsgame, and the version number is 14. When there are multiple test versions of the first gaming fitstgame application, the test environments required by the different versions may be distinguished by the ID.
Step S222, matching the target test environment attribute keyword and the first target key value with the test environment attribute keyword and the key value in the XML environment configuration file, and if the matching is successful, acquiring the environment configuration parameter corresponding to the first target key value from the XML environment configuration file.
Specifically, if the XML environment configuration file also has a test environment attribute keyword and a key value that are the same as the target test environment attribute keyword and the first target key value, if protocalley is fitsgame, the matching is successful, and the environment configuration parameter corresponding to the first target key value "fitsgame" may be obtained according to the position of the first target key value in the XML environment configuration file and the preset rule. In a specific embodiment, as shown in the figure, a fragment diagram of an XML environment configuration file is shown, where the XML environment configuration file includes a test environment attribute key "protokaley" and a corresponding key value "fitsgame", the target test environment attribute key "protokaley" and a first target key value "fitsgame" are successfully matched with "protokaley ═ fitsgame" in the XML environment configuration file, so that it is determined that the environment configuration parameter includes that checkfile ═ 1 represents a file configuration parameter, file ═ firstqame represents a file name, and keypath represents a file path, so that a test environment can be constructed.
Step S223, if the environment configuration parameter includes a file configuration parameter, creating a corresponding file according to the file configuration parameter.
Specifically, if the environment configuration parameter includes a file configuration parameter, first path information and a file name corresponding to the file configuration parameter are acquired, a first target position is acquired according to the first path information, a corresponding file is created, and one or more files can be created successively according to the file configuration parameter.
Step S224, if the environment configuration parameters include registry configuration parameters, then call an application programming interface provided by the operating system to create a corresponding registry according to the registry configuration parameters.
Specifically, the registry configuration parameters may create addresses for the registries, and the registry configuration parameters are transferred to the application programming interface provided by the operating system, so as to create the corresponding registries. And after all the environment configuration parameters are set circularly, the test environment is successfully established.
In this embodiment, the corresponding environment configuration parameters are acquired through the test environment attribute keywords and the corresponding key values, so that the acquisition of the environment configuration parameters is more flexible and diversified, and the requirements of different test environments are met.
In one embodiment, as shown in fig. 5, step S230 includes:
step S231, obtaining the target test scenario attribute keyword and the second target key value according to the test scenario configuration information.
Specifically, the target test scenario attribute keyword is used for describing and identifying the type of the test scenario, and for example, a test environment can be uniquely identified by the test scenario name, the test scenario specific description, and the test scenario number. The second target key value is used for describing specific content corresponding to the target test scenario attribute keyword, and if the target test scenario attribute keyword is "adpos" and the second target key value is "scc _ idle", it indicates that the test scenario to be configured is a scenario in which scc _ idle is used as a keyword, that is, an idle-time scenario. The number of the target test scenario attribute keywords and the number of the second target key values can be multiple, and each target test scenario attribute keyword is provided with a corresponding target key value, so that the test scenario can be determined or explained from multiple dimensions. If the target test scenario attribute keyword further includes "name", the corresponding target key value is "idle time scenario", which indicates that the name of the test scenario to be configured is the idle time scenario.
Step S232, matching the target test scenario attribute keyword and the second target key value with the test scenario attribute keyword and the key value in the XML scenario configuration file, and if the matching is successful, acquiring a scenario configuration parameter corresponding to the second target key value from the XML environment configuration file.
Specifically, if the XML environment configuration file also has a test scenario attribute keyword and a key value that are the same as the target test scenario attribute keyword and the second target key value, and if an adpos is "scc _ idle", the matching is successful, and the scenario configuration parameter corresponding to the "idle scenario" of the second target key value may be obtained according to the position of the second target key value in the XML environment configuration file and the preset rule. In a specific embodiment, as shown in the figure, a fragment diagram of an XML scene configuration file is shown, where the XML scene configuration file includes a test scene attribute keyword "name" and a corresponding key value "idle scene", the test scene attribute keyword "adpos" and a corresponding key value "scc _ idle", the target test scene attribute keyword "adpos" and a second target key value "scc _ idle" are successfully matched with "adpos _ scc _ idle" in an XML environment configuration file, so as to determine that the scene configuration parameters include AppId _ scene center and EventId 3000002, and determine an application identifier and an event identifier for constructing a test scene.
In an embodiment, the test scenario needs to be generated sequentially through a plurality of intermediate test scenarios, as shown in fig. 6, the step of invoking the scenario trigger interface according to the scenario configuration parameter to trigger the corresponding test scenario in step S230 includes:
in step S233, the scene trigger interface acquires the scene configuration parameter corresponding to the first intermediate test scene as the current scene configuration parameter.
Specifically, the test scenes need to be generated sequentially through a plurality of intermediate test scenes, wherein each intermediate test scene has a corresponding scene configuration parameter, and according to the time generation sequence of each intermediate test scene, the scene configuration parameter corresponding to the first intermediate test scene is firstly acquired as the current scene configuration parameter.
In step S234, the scene trigger interface triggers the corresponding current event according to the current scene configuration parameters to generate a current intermediate test scene.
Specifically, each current scene configuration parameter has a corresponding event, and a method corresponding to the event is executed by triggering the event, so that a corresponding operation is completed to generate a current intermediate test scene.
In step S235, the scene trigger interface obtains the scene configuration parameter corresponding to the next intermediate test scene as the current scene configuration parameter, and step S234 is performed until the scene configuration parameter corresponding to the last intermediate test scene triggers the event to complete the generation of the target test scene.
Specifically, after the first intermediate test scenario is generated, the scenario configuration parameters corresponding to the next intermediate test scenario are acquired as the current scenario configuration parameters, and the next intermediate test scenario is continuously generated, all the intermediate test scenarios share one scenario trigger interface, and events and event responses corresponding to different scenario configuration parameters are encapsulated in the scenario trigger interface, so that the generation of each intermediate test scenario can be automatically completed until the target test scenario is generated only by transmitting different scenario configuration parameters to the scenario trigger interface, the target test scenario can be conveniently generated at one time without knowing the generation rule of each intermediate test scenario and the continuity of different intermediate test scenarios, and the generation efficiency of the target test scenario is improved.
In an embodiment, the test task information further includes a resource configuration identifier, as shown in fig. 7, the step of obtaining the test configuration resource data in step S240 includes:
step S241, an uplink protocol is sent to the server, where the uplink protocol carries the resource configuration identifier.
Specifically, the resource configuration identifier is used to uniquely identify one resource configuration, where one resource configuration includes a test configuration resource file, an XML environment configuration file, an XML scene configuration file, and the like, and the resource configuration identifier may be carried in the test request. The resource configuration completed at a time at the background server is called one release, and the background server may include a plurality of releases, each release having a unique resource configuration identifier.
Step S242, receiving the test configuration resource corresponding to the resource configuration identifier returned by the server.
Specifically, the server acquires the corresponding test configuration resource according to the resource configuration identifier, so that each test task can acquire the specified test configuration resource according to the resource configuration identifier, the problem that the test configuration resource is randomly issued in the same scene to cause the execution failure of the test task is avoided, and the problem that the positioning and the problem elimination are difficult due to the random issue is avoided.
In an embodiment, the uplink protocol further includes a test configuration parameter, so that the server determines whether the test configuration parameter indicates a test state, if so, obtains a test configuration resource corresponding to the resource configuration identifier, and otherwise, obtains a random configuration resource.
Specifically, the test configuration parameters may be test flag bits, such as 0 and 1, where 0 indicates that the current terminal belongs to a non-test state, and only needs to randomly issue the configuration resources, and 1 indicates that the current terminal belongs to a test state and needs to issue the specified test configuration resources. Different issued resources can be selected according to the test configuration parameters, and the flexibility of resource acquisition is improved.
In one embodiment, the uplink protocol further includes a filtering parameter, and the step of obtaining the test configuration resource data in step S240 further includes: and receiving the target test configuration resource returned after the server filters the initial test configuration resource corresponding to the resource configuration identifier according to the filtering parameter.
Specifically, the filtering parameter is used to describe the filtering condition, and some limiting conditions can be filtered out through the filtering condition, for example, the background has a logic limiting condition that the testing configuration resource is issued only when the version number is the preset version number, if the version number of the current testing machine does not satisfy the condition, the server will not issue the testing configuration resource, and if the background server receives the filtering parameter to indicate that the limiting condition is filtered out, the background server will issue the testing configuration resource regardless of whether the version number satisfies the condition or not. Some limiting conditions can be filtered out through the filtering parameters, so that the issuing of the resources is more flexible.
In one embodiment, the test task information further includes expected test result information, and after step S240, further includes: and acquiring a current test result, and generating a test report according to the current test result and the expected test result information.
Specifically, the expected test result information is used to describe an expected test result corresponding to the test task, such as popping up a specific window, generating a preset file, where the integrity check value md5 of the file is equal to the first preset value, and the like. If the current test result is matched with the expected test result, the test product reaches the expected function, if the current test result is not matched with the expected test result, the test product does not reach the expected function and has a fault, and the fault can be analyzed and positioned according to specific test result data and logs to generate a test report. The generation format of the test report can be customized, such as generating html (HyperText Markup Language) format report. The test report can be sent to a responsible person through an instant messaging tool, a mail and the like so as to timely and effectively inform a test result.
In a specific embodiment, in conjunction with fig. 8 and 9, the method for automated testing specifically proceeds as follows:
1. receiving a test request sent by an operation configuration platform, putting a test task into a task management queue, writing configuration information corresponding to the test task into a task information taskinfo table in a database, and writing expected test result information corresponding to the test task into a check information checkinfo table in the database.
2. Analyzing the test task information, and triggering a test task to execute the test according to the task management queue.
3. And acquiring test environment configuration information from the taskinfo table, acquiring a client code updated in real time from the SVN, and acquiring an XML environment configuration file updated in real time from the client code.
4. Analyzing the XML environment configuration file, judging whether an environment configuration parameter matched with the test environment configuration information exists, if so, acquiring a corresponding environment configuration parameter, judging whether the environment configuration parameter is a file configuration parameter or a registry configuration parameter, if so, creating a corresponding file, if so, creating a corresponding registry, and if not, failing to create the test environment.
5. And acquiring test scene configuration information from the taskinfo table, and acquiring an XML scene configuration file updated in real time from the client code.
6. Analyzing the XML scene configuration file, judging whether scene configuration parameters matched with the test scene configuration information exist or not, if yes, acquiring the corresponding scene configuration parameters, calling a scene trigger interface according to the scene configuration parameters to trigger the corresponding test scene, and if the scene configuration parameters matched with the test scene configuration information do not exist or the triggering fails through the trigger interface, establishing the test scene fails.
7. Sending an uplink protocol carrying a resource configuration identifier to a server so that the server judges whether the uplink protocol carries a test flag, if so, obtaining the resource configuration identifier, obtaining an initial test configuration resource corresponding to the resource configuration identifier, if not, randomly sending a first test configuration resource as a target test configuration resource, judging whether the uplink protocol carries a filter parameter, if so, filtering the initial test configuration resource according to the filter parameter to obtain a second test configuration resource as a target test configuration resource, and if not, obtaining the target test configuration resource by the initial test configuration resource.
8. And receiving target test configuration resources sent by the server, and testing in a test environment and a test scene according to the target test configuration resource data.
In one embodiment, as shown in fig. 10, there is provided an apparatus for automated testing, comprising:
the test request receiving module 310 is configured to receive a test request, where the test request includes test task information, and the test task information includes test environment configuration information and test scenario configuration information.
The testing environment establishing module 320 is configured to obtain an XML environment configuration file of the XML language, parse the XML environment configuration file to obtain an environment configuration parameter matching the testing environment configuration information, and establish a corresponding testing environment according to the environment configuration parameter.
The test scenario triggering module 330 is configured to obtain an XML scenario configuration file, parse the XML scenario configuration file to obtain a scenario configuration parameter matching the test scenario configuration information, and invoke a scenario triggering interface to trigger a corresponding test scenario according to the scenario configuration parameter.
The testing module 340 is configured to obtain the testing configuration resource data, and perform testing in the testing environment and the testing scenario according to the testing configuration resource data.
In one embodiment, as shown in fig. 11, the apparatus further comprises:
and the task scheduling module 350 is configured to write the test task information into the database, analyze the test task information stored in the database, establish a task management queue according to the test task information, place the test task corresponding to the test task information into the task management queue, and trigger execution of a first test task in the task management queue.
In one embodiment, as shown in FIG. 12, the test environment setup module 320 includes:
an environment configuration parameter obtaining unit 321, configured to obtain a target test environment attribute keyword and a first target key value according to the test environment configuration information, match the target test environment attribute keyword and the first target key value with the test environment attribute keyword and the first target key value in the XML environment configuration file, and if the matching is successful, obtain an environment configuration parameter corresponding to the first target key value from the XML environment configuration file.
A first creating unit 322, configured to create a corresponding file according to the file configuration parameters if the environment configuration parameters include the file configuration parameters.
A second creating unit 323, configured to, if the environment configuration parameter includes a registry configuration parameter, call an application programming interface provided by an operating system according to the registry configuration parameter to create a corresponding registry.
In an embodiment, the test scenario triggering module 330 is further configured to obtain a target test scenario attribute keyword and a second target key value according to the test scenario configuration information, match the target test scenario attribute keyword and the second target key value with the test scenario attribute keyword and the key value in the XML scenario configuration file, and if the matching is successful, obtain a scenario configuration parameter corresponding to the second target key value from the XML environment configuration file.
In one embodiment, the test scenario needs to be generated sequentially through a plurality of intermediate test scenarios, as shown in fig. 13, the test scenario triggering module 330 includes:
the current scene configuration parameter obtaining unit 331 is configured to obtain, by the scene trigger interface, a scene configuration parameter corresponding to the first intermediate test scene as a current scene configuration parameter.
And an intermediate test scenario generating unit 332, configured to trigger, by the scenario trigger interface, a corresponding current event according to the current scenario configuration parameter to generate a current intermediate test scenario.
And the circulating unit 333 is configured to obtain a scene configuration parameter corresponding to the next intermediate test scene as a current scene configuration parameter by the scene trigger interface, and enter the intermediate test scene generating unit.
And the target test scenario generating unit 334 is configured to generate a target test scenario until the scenario configuration parameter trigger event corresponding to the last intermediate test scenario is completed.
In one embodiment, the test task information further includes a resource configuration identifier, and as shown in fig. 14, the test module 340 includes:
the protocol sending unit 341 is configured to send an uplink protocol to the server, where the uplink protocol carries the resource configuration identifier.
The receiving unit 342 is configured to receive the test configuration resource corresponding to the resource configuration identifier returned by the server.
In an embodiment, the uplink protocol further includes a filtering parameter, and the receiving unit 342 is further configured to receive a target test configuration resource returned by the server after filtering the initial test configuration resource corresponding to the resource configuration identifier according to the filtering parameter.
In one embodiment, the test task information further includes expected test result information, and as shown in fig. 15, the apparatus further includes:
the test result generating module 360 is configured to obtain a current test result, and generate a test report according to the current test result and the expected test result information.
It will be understood by those skilled in the art that all or part of the processes in the methods of the embodiments described above may be implemented by hardware related to instructions of a computer program, which may be stored in a computer readable storage medium, for example, in the storage medium of a computer system, and executed by at least one processor in the computer system, so as to implement the processes of the embodiments including the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (18)

1. An automated testing method is applied to a terminal, and comprises the following steps:
receiving a test request, wherein the test request comprises test task information, and the test task information comprises test environment configuration information and test scene configuration information;
acquiring an extensible markup language (XML) environment configuration file, analyzing the XML environment configuration file to acquire environment configuration parameters matched with the test environment configuration information, and establishing a corresponding test environment according to the environment configuration parameters;
acquiring an XML scene configuration file, analyzing the XML scene configuration file to acquire scene configuration parameters matched with the test scene configuration information, calling a scene trigger interface to trigger a corresponding test scene according to the scene configuration parameters, wherein the scene trigger interface triggers different events according to different scene configuration parameters, so that methods corresponding to different events are called to complete generation of each intermediate scene, and a target test scene is finally generated;
and acquiring test configuration resource data, and testing in the test environment and the test scene according to the test configuration resource data.
2. The method of claim 1, wherein the step of receiving a test request is further followed by:
writing the test task information into a database;
analyzing the test task information stored in the database, establishing a task management queue according to the test task information, putting the test task corresponding to the test task information into the task management queue, and triggering a first test task in the task management queue to execute.
3. The method according to claim 1, wherein the parsing the XML environment configuration file to obtain the environment configuration parameters matching the testing environment configuration information, and the step of establishing the corresponding testing environment according to the environment configuration parameters comprises:
acquiring a target test environment attribute key word and a first target key value according to the test environment configuration information;
matching the target test environment attribute key word and a first target key value with the test environment attribute key word and the key value in the XML environment configuration file, and if the matching is successful, acquiring an environment configuration parameter corresponding to the first target key value from the XML environment configuration file;
if the environment configuration parameters comprise file configuration parameters, creating a corresponding file according to the file configuration parameters;
and if the environment configuration parameters comprise registry configuration parameters, calling an application programming interface provided by an operating system according to the registry configuration parameters to create a corresponding registry.
4. The method according to claim 1, wherein the step of parsing the XML scene configuration file to obtain the scene configuration parameters matching the test scene configuration information comprises:
acquiring a target test scene attribute keyword and a second target key value according to the test scene configuration information;
and matching the target test scene attribute key word and a second target key value with the test scene attribute key word and the key value in the XML scene configuration file, and if the matching is successful, acquiring the scene configuration parameters corresponding to the second target key value from the XML environment configuration file.
5. The method according to claim 1, wherein the test scenario needs to be generated sequentially through a plurality of intermediate test scenarios, and the step of invoking a scenario trigger interface according to the scenario configuration parameter to trigger the corresponding test scenario comprises:
the scene trigger interface acquires a scene configuration parameter corresponding to a first intermediate test scene as a current scene configuration parameter;
s1: the scene trigger interface triggers a corresponding current event according to the current scene configuration parameters to generate a current intermediate test scene;
s2: the scene trigger interface obtains the scene configuration parameters corresponding to the next intermediate test scene as the current scene configuration parameters, and step S1 is executed until the scene configuration parameter trigger event corresponding to the last intermediate test scene is completed to generate the target test scene.
6. The method of claim 1, wherein the test task information further includes a resource configuration identifier, and wherein the step of obtaining test configuration resource data includes:
sending an uplink protocol to a server, wherein the uplink protocol carries a resource configuration identifier;
and receiving the test configuration resource corresponding to the resource configuration identifier returned by the server.
7. The method of claim 6, wherein the uplink protocol further includes a filter parameter, and wherein the step of obtaining test configuration resource data further includes:
and receiving the target test configuration resource returned after the server filters the initial test configuration resource corresponding to the resource configuration identifier according to the filtering parameter.
8. The method of claim 1, wherein the test task information further includes expected test result information, and wherein the step of performing the test in the test environment and test scenario according to the test configuration resource data further comprises:
and acquiring a current test result, and generating a test report according to the current test result and the expected test result information.
9. An automatic testing device applied to a terminal, the device comprising:
the device comprises a test request receiving module, a test request receiving module and a test processing module, wherein the test request receiving module is used for receiving a test request, the test request comprises test task information, and the test task information comprises test environment configuration information and test scene configuration information;
the test environment establishing module is used for acquiring an extensible markup language (XML) environment configuration file, analyzing the XML environment configuration file to acquire environment configuration parameters matched with the test environment configuration information, and establishing a corresponding test environment according to the environment configuration parameters;
the test scene triggering module is used for acquiring an XML scene configuration file, analyzing the XML scene configuration file to acquire scene configuration parameters matched with the test scene configuration information, calling a scene triggering interface to trigger a corresponding test scene according to the scene configuration parameters, and triggering different events by the scene triggering interface according to different scene configuration parameters, so that methods corresponding to different events are called to complete generation of each intermediate scene, and a target test scene is finally generated;
and the test module is used for acquiring test configuration resource data and testing in the test environment and the test scene according to the test configuration resource data.
10. The apparatus of claim 9, further comprising:
and the task scheduling module is used for writing the test task information into a database, analyzing the test task information stored in the database, establishing a task management queue according to the test task information, putting the test task corresponding to the test task information into the task management queue, and triggering a first test task in the task management queue to execute.
11. The apparatus of claim 9, wherein the test environment setup module comprises:
an environment configuration parameter obtaining unit, configured to obtain a target test environment attribute keyword and a first target key value according to the test environment configuration information, match the target test environment attribute keyword and the first target key value with the test environment attribute keyword and the key value in the XML environment configuration file, and if the matching is successful, obtain an environment configuration parameter corresponding to the first target key value from the XML environment configuration file;
the first creating unit is used for creating a corresponding file according to the file configuration parameters if the environment configuration parameters comprise the file configuration parameters;
and the second creating unit is used for calling an application programming interface provided by an operating system to create a corresponding registry according to the registry configuration parameters if the environment configuration parameters comprise the registry configuration parameters.
12. The apparatus of claim 9, wherein the test scenario trigger module is further configured to obtain a target test scenario attribute keyword and a second target key value according to the test scenario configuration information, match the target test scenario attribute keyword and the second target key value with the test scenario attribute keyword and the key value in the XML scenario configuration file, and if the matching is successful, obtain a scenario configuration parameter corresponding to the second target key value from the XML environment configuration file.
13. The apparatus of claim 9, wherein the test scenario requires generation sequentially through a plurality of intermediate test scenarios, and wherein the test scenario triggering module comprises:
a current scene configuration parameter obtaining unit, configured to obtain, by the scene trigger interface, a scene configuration parameter corresponding to the first intermediate test scene as a current scene configuration parameter;
the intermediate test scene generating unit is used for generating a current intermediate test scene by the scene trigger interface according to the current event corresponding to the trigger of the current scene configuration parameters;
the circulating unit is used for the scene trigger interface to acquire the scene configuration parameters corresponding to the next intermediate test scene as the current scene configuration parameters and enter the intermediate test scene generating unit;
and the target test scene generation unit is used for generating the target test scene until the scene configuration parameter trigger event corresponding to the last intermediate test scene is finished.
14. The apparatus of claim 9, wherein the test task information further comprises a resource configuration identifier, and wherein the test module comprises:
a protocol sending unit, configured to send an uplink protocol to a server, where the uplink protocol carries a resource configuration identifier;
and the receiving unit is used for receiving the test configuration resource which is returned by the server and corresponds to the resource configuration identifier.
15. The apparatus of claim 14, wherein the uplink protocol further includes a filtering parameter, and the receiving unit is further configured to receive a target test configuration resource returned by the server after filtering an initial test configuration resource corresponding to the resource configuration identifier according to the filtering parameter.
16. The apparatus of claim 14, wherein the test task information further includes expected test result information, the apparatus further comprising:
and the test result generating module is used for acquiring the current test result and generating a test report according to the current test result and the expected test result information.
17. A computer arrangement, comprising a storage medium and a processor, the storage medium having stored thereon a computer program that, when executed by the processor, causes the processor to carry out the steps of the method of any of claims 1 to 8.
18. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 8.
CN201611054093.1A 2016-11-25 2016-11-25 Method and device for automatic testing Active CN108108297B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611054093.1A CN108108297B (en) 2016-11-25 2016-11-25 Method and device for automatic testing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611054093.1A CN108108297B (en) 2016-11-25 2016-11-25 Method and device for automatic testing

Publications (2)

Publication Number Publication Date
CN108108297A CN108108297A (en) 2018-06-01
CN108108297B true CN108108297B (en) 2021-05-18

Family

ID=62204114

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611054093.1A Active CN108108297B (en) 2016-11-25 2016-11-25 Method and device for automatic testing

Country Status (1)

Country Link
CN (1) CN108108297B (en)

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108990047B (en) * 2018-07-03 2021-06-29 中国联合网络通信集团有限公司 Test method, device and medium for subscription relationship management data preparation platform
CN109240924B (en) * 2018-09-03 2024-03-08 中国平安人寿保险股份有限公司 Application program testing method and device
CN109376073B (en) * 2018-09-14 2021-08-03 珠海金山网络游戏科技有限公司 Test environment memory and recovery method
CN109542757A (en) * 2018-09-29 2019-03-29 中国平安人寿保险股份有限公司 Interface testing environment determines method, apparatus, electronic equipment and storage medium
CN109684203A (en) * 2018-11-27 2019-04-26 平安科技(深圳)有限公司 Program running parameter configuration method, device, computer equipment and storage medium
CN109726119A (en) * 2018-12-04 2019-05-07 北京奇艺世纪科技有限公司 Test scene creation method, application method, device, client and server
CN111309584B (en) * 2018-12-11 2024-02-23 迈普通信技术股份有限公司 Data processing method, device, electronic equipment and storage medium
CN111338926A (en) * 2018-12-18 2020-06-26 北京奇虎科技有限公司 Patch testing method and device and electronic equipment
CN109806592B (en) * 2019-01-18 2022-09-30 网易(杭州)网络有限公司 Game resource monitoring method and device
CN112131094A (en) * 2019-06-25 2020-12-25 比亚迪汽车工业有限公司 Method and device for testing track signal system software and storage medium
CN110532170B (en) * 2019-07-18 2023-08-08 北京文渊佳科技有限公司 Method and device for building test environment, electronic equipment and medium
CN110659202A (en) * 2019-08-12 2020-01-07 网宿科技股份有限公司 Client automatic testing method and device
CN110781090B (en) * 2019-10-31 2023-09-12 望海康信(北京)科技股份公司 Control method and device for data processing test, computer equipment and storage medium
CN111175601A (en) * 2020-01-03 2020-05-19 云南电网有限责任公司电力科学研究院 Modular functional test system
CN111240992B (en) * 2020-01-20 2023-04-25 网易(杭州)网络有限公司 Test method and device, storage medium and electronic equipment
CN111651349B (en) * 2020-05-26 2023-07-14 泰康保险集团股份有限公司 Test method and device
CN111666214B (en) * 2020-06-02 2023-09-22 广州酷狗计算机科技有限公司 Client fault tolerance test method, device, terminal, server and storage medium
CN111693090A (en) * 2020-06-10 2020-09-22 上海有个机器人有限公司 Robot pavement environment aging test method, medium, terminal and device
CN111831567B (en) * 2020-07-17 2023-08-22 中国工商银行股份有限公司 Application test environment configuration method, device, system and medium
CN112100052B (en) * 2020-08-07 2023-08-18 北京奇艺世纪科技有限公司 Playback method and device of interface test scene
CN112699020A (en) * 2020-12-11 2021-04-23 浙江中控技术股份有限公司 Industrial real-time database API (application program interface) interface testing method
CN112799954B (en) * 2021-02-09 2024-04-16 上海云轴信息科技有限公司 Method, apparatus and computer readable medium for quickly constructing test environment
CN112905534B (en) * 2021-02-25 2023-09-05 北京安天网络安全技术有限公司 Sample analysis method and device based on sandbox environment
CN113220597B (en) * 2021-06-18 2024-04-16 中国农业银行股份有限公司 Test method, test device, electronic equipment and storage medium
CN113608994A (en) * 2021-06-30 2021-11-05 天津五八到家货运服务有限公司 Request processing method and system
CN114416589B (en) * 2022-01-27 2022-09-16 北京永信至诚科技股份有限公司 Network target range comprehensive detection method, device, equipment and readable storage medium
CN114579473B (en) * 2022-05-09 2022-09-02 太平金融科技服务(上海)有限公司深圳分公司 Application testing method, device, equipment and storage medium
CN115150310A (en) * 2022-07-01 2022-10-04 北京百度网讯科技有限公司 Request generation method, processing method, device, electronic equipment and storage medium
CN115687162B (en) * 2023-01-03 2023-03-21 北京集度科技有限公司 Software testing device and method and electronic device
CN116627849B (en) * 2023-07-24 2024-01-26 中邮消费金融有限公司 System test method, device, equipment and storage medium
CN117093503B (en) * 2023-10-17 2024-02-06 杭银消费金融股份有限公司 Client test management method and system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101042673A (en) * 2007-04-20 2007-09-26 北京航空航天大学 Software testing system and testing method
CN101266566A (en) * 2007-03-13 2008-09-17 中国电信股份有限公司 Multi- test scene automatic dispatch system and method
CN105446865A (en) * 2014-07-09 2016-03-30 阿里巴巴集团控股有限公司 Test method and device under multi-environment
CN106021111A (en) * 2016-05-30 2016-10-12 上海携程商务有限公司 Interface testing method and system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9959200B2 (en) * 2012-09-06 2018-05-01 Red Hat Israel, Ltd. User interface for composing test scenarios
CN105068933B (en) * 2015-08-25 2018-06-26 北京京东尚科信息技术有限公司 For the browser driving method and equipment of test
CN105677568A (en) * 2016-01-11 2016-06-15 上海富欣智能交通控制有限公司 Test scene generating method for railway signal computer interlocking system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101266566A (en) * 2007-03-13 2008-09-17 中国电信股份有限公司 Multi- test scene automatic dispatch system and method
CN101042673A (en) * 2007-04-20 2007-09-26 北京航空航天大学 Software testing system and testing method
CN105446865A (en) * 2014-07-09 2016-03-30 阿里巴巴集团控股有限公司 Test method and device under multi-environment
CN106021111A (en) * 2016-05-30 2016-10-12 上海携程商务有限公司 Interface testing method and system

Also Published As

Publication number Publication date
CN108108297A (en) 2018-06-01

Similar Documents

Publication Publication Date Title
CN108108297B (en) Method and device for automatic testing
CN106415480B (en) High-speed application for installation on a mobile device for enabling remote configuration of the mobile device
US8839107B2 (en) Context based script generation
CN107562556B (en) Failure recovery method, recovery device and storage medium
CN105302722B (en) CTS automatic testing method and device
US20170177466A1 (en) Volume testing
US20120159446A1 (en) Verification framework for business objects
US10509719B2 (en) Automatic regression identification
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
JP7423942B2 (en) information processing system
CN111078567A (en) Report generation method, terminal and storage medium of automatic test platform
CN111475390A (en) Log collection system deployment method, device, equipment and storage medium
CN111831542A (en) API application debugging method and device and storage medium
CN112650688A (en) Automated regression testing method, associated device and computer program product
CN113590454A (en) Test method, test device, computer equipment and storage medium
CN110543429A (en) Test case debugging method and device and storage medium
CN104484176B (en) A kind of Android system window object acquisition methods and device
WO2023151397A1 (en) Application program deployment method and apparatus, device, and medium
JP2016071398A (en) Test execution device, test execution method, and computer program
CN114297057A (en) Design and use method of automatic test case
CN113468050A (en) Canvas-based testing method and device, computer equipment and storage medium
CN113157554A (en) Software automation question making test method and related equipment
CN112667491A (en) Function test method and device of virtual machine
CN110048940A (en) Sending method, device, server and the readable storage medium storing program for executing of instant communication message

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