CN111078558A - Log storage method and device for automatic test and computer readable storage medium - Google Patents

Log storage method and device for automatic test and computer readable storage medium Download PDF

Info

Publication number
CN111078558A
CN111078558A CN201911307284.8A CN201911307284A CN111078558A CN 111078558 A CN111078558 A CN 111078558A CN 201911307284 A CN201911307284 A CN 201911307284A CN 111078558 A CN111078558 A CN 111078558A
Authority
CN
China
Prior art keywords
case
tested
test
file
log
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.)
Granted
Application number
CN201911307284.8A
Other languages
Chinese (zh)
Other versions
CN111078558B (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.)
Guangzhou Pinwei Software Co Ltd
Original Assignee
Guangzhou Pinwei Software 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 Guangzhou Pinwei Software Co Ltd filed Critical Guangzhou Pinwei Software Co Ltd
Priority to CN201911307284.8A priority Critical patent/CN111078558B/en
Publication of CN111078558A publication Critical patent/CN111078558A/en
Application granted granted Critical
Publication of CN111078558B publication Critical patent/CN111078558B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • 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
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
    • G06F16/1815—Journaling file systems
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention discloses a log storage method for automatic test, which comprises the following steps: determining a to-be-tested case adopted in an automatic test, and determining first attribute information of the to-be-tested case; generating a file path of the case to be tested according to the first attribute information; and in the process of executing the case to be tested, storing the log generated by executing the case to be tested to the file corresponding to the file strength so as to be stored as a log file. The invention also discloses a log storage device and a computer readable storage medium for the automatic test. The invention can accurately position the log file of the test case with failed execution to find the reason of the failed execution of the test case.

Description

Log storage method and device for automatic test and computer readable storage medium
Technical Field
The invention relates to the technical field of automatic testing, in particular to a log storage method and device for automatic testing and a computer readable storage medium.
Background
If the execution of the test case fails in the automatic test, the execution log needs to be checked at the first time. The execution logs contain a lot of interference information such as project compiling and starting, all the execution logs are printed in one file, and for the concurrently executed automatic cases, the execution logs are more unordered, so that after the execution of the test cases fails, the execution logs of the failed test cases cannot be accurately positioned to find the reasons of the failure of the test cases.
Disclosure of Invention
The invention mainly aims to provide a log storage method and device for automatic testing and a computer readable storage medium, aiming at solving the problem that the execution log of a failed test case cannot be accurately positioned to search the reason of the failure of the test case.
In order to achieve the above object, the present invention provides a log storage method for an automatic test, which comprises the following steps:
determining a to-be-tested case adopted in an automatic test, and determining first attribute information of the to-be-tested case;
generating a file path of the case to be tested according to the first attribute information;
and in the process of executing the case to be tested, storing the log generated by executing the case to be tested to the file corresponding to the file strength so as to be stored as a log file.
In an embodiment, the step of generating the file path of the to-be-tested use case according to the first attribute information includes:
determining the type of the case to be tested;
and generating a file path of the use case to be tested according to the type and the first attribute information.
In an embodiment, the step of generating a file path of the use case to be tested according to the type and the first attribute information includes:
when the to-be-tested case is a common case, acquiring a case name of the to-be-tested case and a test method name corresponding to the to-be-tested case from the first attribute information;
and generating a file path of the to-be-tested use case according to the use case name and the test method name.
In an embodiment, the step of generating a file path of the use case to be tested according to the type and the first attribute information includes:
when the to-be-tested case is a data-driven case, acquiring the calling times of the to-be-tested case from the first attribute information;
and generating a file path of the use case to be tested according to the calling times.
In an embodiment, before the step of determining a case to be tested used in the automated test, the method further includes:
and deleting the file path corresponding to the last executed test case.
In an embodiment, after the step of storing the log generated by executing the use case to be tested to the file corresponding to the file strength to be saved as the log file, the method further includes:
after the test case with the execution failure is detected, second attribute information of the test case with the execution failure is obtained;
and determining and outputting a log file corresponding to the second attribute information.
In order to achieve the above object, the present invention further provides an automatic test log storage device, which includes a memory, a processor, and an automatic test log storage program stored in the memory and executable on the processor, and when executed by the processor, the automatic test log storage program implements the steps of the automatic test log storage method described above.
To achieve the above object, the present invention also provides a computer-readable storage medium storing a log storage program for an automation test, which when executed by a processor implements the steps of the log storage method for an automation test as described above.
According to the log storage method and device for the automatic test and the computer readable storage medium, the log storage device for the automatic test determines the to-be-tested case adopted in the automatic test, determines the first attribute information of the to-be-tested case, and generates the file path of the to-be-tested case according to the first attribute information, so that the log generated in the process of executing the to-be-tested case is stored to the file corresponding to the file path to be stored as the log file. The device can generate a corresponding file path for the test case to be tested so as to store the generated logs into the file corresponding to the file path in the execution of the test case to be tested, and also store the logs generated by the execution of each test case into different files, so that the device can be conveniently and accurately positioned to the log file of the test case with failed execution so as to find the reason of the failed execution of the test case.
Drawings
FIG. 1 is a diagram of a hardware architecture of a log storage device for automated testing according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a log storage method for an automated test according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a log storing method for automated testing according to a second embodiment of the present invention;
FIG. 4 is a flowchart illustrating a log storing method for an automated test according to a third embodiment of the present invention;
FIG. 5 is a flowchart illustrating a log storing method for an automated test according to a fourth embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The main solution of the embodiment of the invention is as follows: determining a to-be-tested case adopted in an automatic test, and determining first attribute information of the to-be-tested case; generating a file path of the case to be tested according to the first attribute information; and in the process of executing the case to be tested, storing the log generated by executing the case to be tested to the file corresponding to the file strength so as to be stored as a log file.
The device can generate a corresponding file path for the test case to be tested so as to store the generated logs into the file corresponding to the file path in the execution of the test case to be tested, and also store the logs generated by the execution of each test case into different files, so that the device can be conveniently and accurately positioned to the log file of the test case with failed execution so as to find the reason of the failed execution of the test case.
As one implementation, a log storage device for automated testing may be as shown in FIG. 1.
The embodiment scheme of the invention relates to a log storage device for automatic test, which comprises: a processor 101, e.g. a CPU, a memory 102, a communication bus 103. Wherein a communication bus 103 is used for enabling the connection communication between these components.
The memory 102 may be a high-speed RAM memory or a non-volatile memory (e.g., a disk memory). As shown in fig. 1, a log storage program for automated testing may be included in the memory 103 as a kind of computer storage medium; and the processor 101 may be configured to invoke a log storage program of the automated test stored in the memory 102 and perform the following operations:
determining a to-be-tested case adopted in an automatic test, and determining first attribute information of the to-be-tested case;
generating a file path of the case to be tested according to the first attribute information;
and in the process of executing the case to be tested, storing the log generated by executing the case to be tested to the file corresponding to the file strength so as to be stored as a log file.
In one embodiment, the processor 101 may be configured to invoke a log storage program of the automated test stored in the memory 102 and perform the following operations:
determining the type of the case to be tested;
and generating a file path of the use case to be tested according to the type and the first attribute information.
In one embodiment, the processor 101 may be configured to invoke a log storage program of the automated test stored in the memory 102 and perform the following operations:
when the to-be-tested case is a common case, acquiring a case name of the to-be-tested case and a test method name corresponding to the to-be-tested case from the first attribute information;
and generating a file path of the to-be-tested use case according to the use case name and the test method name.
In one embodiment, the processor 101 may be configured to invoke a log storage program of the automated test stored in the memory 102 and perform the following operations:
when the to-be-tested case is a data-driven case, acquiring the calling times of the to-be-tested case from the first attribute information;
and generating a file path of the use case to be tested according to the calling times.
In one embodiment, the processor 101 may be configured to invoke a log storage program of the automated test stored in the memory 102 and perform the following operations:
and deleting the file path corresponding to the last executed test case.
In one embodiment, the processor 101 may be configured to invoke a log storage program of the automated test stored in the memory 102 and perform the following operations:
after the test case with the execution failure is detected, second attribute information of the test case with the execution failure is obtained;
and determining and outputting a log file corresponding to the second attribute information.
According to the scheme, the log storage device of the automatic test determines the to-be-tested case adopted in the automatic test, determines the first attribute information of the to-be-tested case, and generates the file path of the to-be-tested case according to the first attribute information, so that the log generated in the process of executing the to-be-tested case is stored to the file corresponding to the file path to be stored as the log file. The device can generate a corresponding file path for the test case to be tested so as to store the generated logs into the file corresponding to the file path in the execution of the test case to be tested, and also store the logs generated by the execution of each test case into different files, so that the device can be conveniently and accurately positioned to the log file of the test case with failed execution so as to find the reason of the failed execution of the test case.
Based on the hardware architecture of the log storage device for the automatic test, the embodiment of the log storage device method for the automatic test is provided.
Referring to fig. 2, fig. 2 is a first embodiment of a log storage method for an automated test according to the present invention, where the log storage method for an automated test includes the following steps:
step S100, determining a to-be-tested case adopted in an automatic test, and determining first attribute information of the to-be-tested case;
in this embodiment, the execution subject is a log storage device of the automated test. For convenience of description, the device is hereinafter referred to as a log storage device of an automation test. The device stores a logback configuration file, and the logback configuration file is used for setting file separation configuration; the testmethodListener in the device can dynamically set the case name of the test case, and the case name can be used as the attribute information of the test case. The device dynamically loads the logback configuration file through the API of the logback, so that the configuration becomes effective. The logback configuration file is specifically a logback-vtp. It should be noted that, by using TestMethodListener to calculate the case name of the test case, a data-driven scenario needs to be considered, for example, a data-driven manner based on excel, each line of excel represents a log file generated by executing one case, so that the log file is output to different files in lines to represent the log file corresponding to each execution of the test case.
Before the device is tested, a to-be-tested case is determined, namely the to-be-tested case required to be executed in the automatic test process, specifically, sdk of the VTP provides a TestMethodListener class by default, the class is loaded in an SPI manner, and two interfaces of IInvokedMethodListener2 and IConfigurationListener2 of TestNg ng are realized, and the purpose is to intercept a test or configuration method (configuration methods such as befortest, beforethod, BeforeClass, beforeSuite and the like) before the test of the to-be-tested case starts. After determining a case to be tested, the device obtains first attribute information of the case to be tested, where the first attribute information may include a name and a type of the case to be tested, a test method corresponding to the case to be tested, a number of times of calling the test method, and the like.
Step S200, generating a file path of the case to be tested according to the first attribute information;
in a Logback-vtp.xml configuration file, through a SiftingAppender in a Logback log frame, the Appender can output logs generated in the test case execution process to different files according to a strategy specified by sift. And the logKey variable is the file path of the log, and the file path is dynamically set in sdk of vtp. If the logKey variable is not set in sdk of the vtp, the log is transmitted to the default log file by default, that is, the log generated by the non-test case is output to the default log file. In contrast, for each test case to be executed, a file path corresponding to the test case needs to be generated. The device can generate a corresponding file path for the case to be tested according to the first attribute information of the case to be tested. sdk, providing a logback configuration file of logback-vtp.
Step S300, in the process of executing the case to be tested, storing the log generated by executing the case to be tested to the file corresponding to the file strength so as to be stored as a log file.
After the file path is generated, the file path is cached, and the case to be tested is executed to perform automatic testing, so that the log generated by the case to be tested is transmitted to the file corresponding to the file path in the execution process to be stored as a log file. The caching of the file path is cached through a put method of the MDC class provided by the logback. It should be noted that, because the parameters in the logback-vtp. Therefore, before the device determines the test case to be tested, the file path corresponding to the last test case is deleted, that is, the file path of the current test case is cached by one thread, and the file path of the previously executed test case is deleted, so that logs generated by a plurality of test cases are not simultaneously input into one file. Specifically, the logKey can be automatically cleared by adopting an afterinitialization method.
In addition, after the device executes the test case, if the test case fails to be executed, that is, after the device detects the test case that fails to be executed, the second attribute information of the test case that fails to be executed is acquired. The first attribute information and the second attribute information have the same information type, that is, the second attribute information also includes the case name and type of the test case, the test method corresponding to the test case, the number of times of calling the test method, and the like. The device determines the log file corresponding to the second attribute information so as to output the log file, and the output form can be display so that a tester can find the reason of the test case execution failure according to the output log file.
In the technical scheme provided by this embodiment, the log storage device for the automated test determines a to-be-tested case adopted in the automated test, determines first attribute information of the to-be-tested case, and generates a file path of the to-be-tested case according to the first attribute information, so that a log generated in the process of executing the to-be-tested case is stored to a file corresponding to the file path to be stored as a log file. The device can generate a corresponding file path for the test case to be tested so as to store the generated logs into the file corresponding to the file path in the execution of the test case to be tested, and also store the logs generated by the execution of each test case into different files, so that the device can be conveniently and accurately positioned to the log file of the test case with failed execution so as to find the reason of the failed execution of the test case.
Referring to fig. 3, fig. 3 is a second embodiment of the log storage method for the automated testing of the present invention, and based on the second embodiment, the step S200 includes:
step S210, determining the type of the use case to be tested;
step S220, generating a file path of the use case to be tested according to the type and the first attribute information.
In this embodiment, the test cases are divided into a plurality of types, that is, the device stores a plurality of types of test cases, for example, the test cases include common cases and data-driven cases. For different types of test cases, the device sets different file path generation modes, and the different types of test cases can be stored in different storage areas for classified storage.
The device determines the type of the to-be-tested case after acquiring the first attribute information of the to-be-tested case, thereby determining the generation mode of the file path according to the type, and generating the file path of the to-be-tested case according to the first attribute information and the generation mode. The type can be determined according to the testing method of the device, that is, the types of the cases to be tested adopted by different testing methods are different. Of course, the device may directly determine the type of the use case to be tested according to other information such as the use case name of the use case to be tested in the first attribute information.
In the technical scheme provided by this embodiment, the device determines the type of the use case to be tested, and generates a file path of the use case to be tested according to the type and the first attribute information, so that a log generated in the execution process of the use case to be tested is transmitted to a file corresponding to the file path.
Referring to fig. 4, fig. 4 is a third embodiment of the log storage method for the automated testing of the present invention, and based on the second embodiment, the step S220 includes:
step S221, when the case to be tested is a common case, obtaining the case name of the case to be tested and the test method name corresponding to the case to be tested from the first attribute information;
step S222, generating a file path of the to-be-tested case according to the case name and the test method name.
In this embodiment, for a common use case, the device may calculate the logKey, that is, calculate the file path, by using the use case name + the test method name of the test use case. The common use case is relative to the data-driven use case, that is, the non-data-driven use cases are defined as the common use case. The first attribute information comprises a use case name of a use case to be tested and a name of a test method. After the device determines that the case to be tested is a common case, the device generates a file path of the case to be tested according to the case name and the test method name in the first attribute information. For example, the use case to be tested is a common use case, and the use case name is com.vip.test.test1, and the test method name is test1, and the logKey calculated by the device is com.vip.test.test1/test 1.
In the technical scheme provided by this embodiment, after determining that the to-be-tested case is a common case, the device obtains the case name of the to-be-tested case and the test method name of the to-be-tested case from the first attribute information, so as to generate the file path of the to-be-tested case according to the case name and the test method name.
Referring to fig. 5, fig. 5 is a fourth embodiment of the log storage method for the automated testing of the present invention, and based on the fourth embodiment, the step S220 includes:
step S223, when the to-be-tested case is a data-driven case, obtaining the calling times of the test method corresponding to the to-be-tested case from the first attribute information;
and S224, generating a file path of the use case to be tested according to the calling times.
In this embodiment, the use case to be tested may be a data-driven use case. For a data-driven use case, the device generates a file path of the use case to be tested by adopting the calling times of the test method corresponding to the use case to be tested.
Specifically, when the device determines that the case to be tested is a data-driven case, the device obtains the number of calls of the test method corresponding to the case to be tested from the first attribute information, so that a file path of the case to be tested is generated according to the call test. For example, if the test method name during the 1 st call is #1, the file path corresponding to the use case to be tested is com.vip.test.test1/1 #; and the test method name when the 2 nd call is #2, the corresponding file path of the case to be tested is com.
In the technical scheme provided by this embodiment, when the to-be-tested case is a data-driven case, the device obtains the number of calls of the test method corresponding to the to-be-tested case, so as to generate a file path of the to-be-tested case according to the number of calls.
The invention also provides an automatic test log storage device, which comprises a memory, a processor and an automatic test log storage program stored in the memory and capable of running on the processor, wherein when the automatic test log storage program is executed by the processor, the automatic test log storage program realizes the steps of the automatic test log storage method according to the embodiment.
The present invention also provides a computer readable storage medium storing a log storage program for an automated test, which when executed by a processor implements the steps of the log storage method for an automated test according to the above embodiment.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (8)

1. The log storage method for the automatic test is characterized by comprising the following steps of:
determining a to-be-tested case adopted in an automatic test, and determining first attribute information of the to-be-tested case;
generating a file path of the case to be tested according to the first attribute information;
and in the process of executing the case to be tested, storing the log generated by executing the case to be tested to the file corresponding to the file strength so as to be stored as a log file.
2. The log storage method for the automated test according to claim 1, wherein the step of generating the file path of the use case to be tested according to the first attribute information comprises:
determining the type of the case to be tested;
and generating a file path of the use case to be tested according to the type and the first attribute information.
3. The log storage method for the automated test according to claim 2, wherein the step of generating the file path of the use case to be tested according to the type and the first attribute information comprises:
when the to-be-tested case is a common case, acquiring a case name of the to-be-tested case and a test method name corresponding to the to-be-tested case from the first attribute information;
and generating a file path of the to-be-tested use case according to the use case name and the test method name.
4. The log storage method for the automated test according to claim 2, wherein the step of generating the file path of the use case to be tested according to the type and the first attribute information comprises:
when the to-be-tested case is a data-driven case, acquiring the calling times of the to-be-tested case from the first attribute information;
and generating a file path of the use case to be tested according to the calling times.
5. The log storage method for automated testing as claimed in claim 1, wherein the step of determining the cases to be tested used in the automated testing is preceded by the steps of:
and deleting the file path corresponding to the last executed test case.
6. The log storage method for the automated test according to any one of claims 1 to 5, wherein after the step of storing the log generated by executing the use case to be tested to the file corresponding to the file stiffness for saving as the log file, the method further comprises:
after the test case with the execution failure is detected, second attribute information of the test case with the execution failure is obtained;
and determining and outputting a log file corresponding to the second attribute information.
7. An automated test log storage device, comprising a memory, a processor, and an automated test log storage program stored in the memory and executable on the processor, the automated test log storage program, when executed by the processor, implementing the steps of the automated test log storage method of any one of claims 1-6.
8. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a log storage program of an automated test, which when executed by a processor implements the steps of the log storage method of an automated test according to any one of claims 1 to 6.
CN201911307284.8A 2019-12-16 2019-12-16 Log storage method and device for automatic test and computer readable storage medium Active CN111078558B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911307284.8A CN111078558B (en) 2019-12-16 2019-12-16 Log storage method and device for automatic test and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911307284.8A CN111078558B (en) 2019-12-16 2019-12-16 Log storage method and device for automatic test and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN111078558A true CN111078558A (en) 2020-04-28
CN111078558B CN111078558B (en) 2023-04-07

Family

ID=70315497

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911307284.8A Active CN111078558B (en) 2019-12-16 2019-12-16 Log storage method and device for automatic test and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN111078558B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112131101A (en) * 2020-08-27 2020-12-25 新华三大数据技术有限公司 Automatic testing method, testing terminal and storage medium
CN112732587A (en) * 2021-01-21 2021-04-30 腾讯科技（深圳）有限公司 Method and device for acquiring automatic test log, electronic equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107871015A (en) * 2017-11-24 2018-04-03 广东欧珀移动通信有限公司 Daily record data processing method and processing device, terminal and readable storage medium storing program for executing
CN109271316A (en) * 2018-08-28 2019-01-25 惠州Tcl移动通信有限公司 Android device and its automated testing method, memory
CN109885496A (en) * 2019-02-20 2019-06-14 北京百佑科技有限公司 Test log management method and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107871015A (en) * 2017-11-24 2018-04-03 广东欧珀移动通信有限公司 Daily record data processing method and processing device, terminal and readable storage medium storing program for executing
CN109271316A (en) * 2018-08-28 2019-01-25 惠州Tcl移动通信有限公司 Android device and its automated testing method, memory
CN109885496A (en) * 2019-02-20 2019-06-14 北京百佑科技有限公司 Test log management method and system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DAISY: "怎样使用Python脚本日志功能", 《HTTPS://WWW.JB51.NET/ARTICLE/90463.HTM》 *
MIKEMAJARA: "python-更新日志内容时动态更改日志的目录", 《HTTPS://CLOUD.TENCENT.COM/DEVELOPER/ASK/SOF/1495934/ANSWER/2045675》 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112131101A (en) * 2020-08-27 2020-12-25 新华三大数据技术有限公司 Automatic testing method, testing terminal and storage medium
CN112732587A (en) * 2021-01-21 2021-04-30 腾讯科技（深圳）有限公司 Method and device for acquiring automatic test log, electronic equipment and storage medium
CN112732587B (en) * 2021-01-21 2024-04-12 腾讯科技（深圳）有限公司 Automatic test log acquisition method and device, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN111078558B (en) 2023-04-07

Similar Documents

Publication Publication Date Title
US20190324772A1 (en) Method and device for processing smart contracts
CN107145437B (en) Java annotation test method and device
CN109558320B (en) System testing method, device, system, equipment and computer readable storage medium
CN111078558B (en) Log storage method and device for automatic test and computer readable storage medium
CN110673576B (en) Automatic test method and device, vehicle and storage medium
US20050251719A1 (en) Test case inheritance controlled via attributes
CN108255708B (en) Method, device, storage medium and equipment for accessing production file in test environment
CN111984342B (en) Method and related device for loading dynamic link library
CN111008148B (en) Code testing method and device and computer readable storage medium
CN112395202A (en) Interface automation test method and device, computer equipment and storage medium
CN111045941B (en) Positioning method and device for user interface control and storage medium
CN111061637B (en) Interface testing method, interface testing device and storage medium
CN108319551B (en) Software testing method and device, computer equipment and readable storage medium
CN112965912A (en) Interface test case generation method and device and electronic equipment
CN111459492A (en) Method, device, storage medium and equipment for detecting compatibility of Dubbo service interface
CN111104330A (en) Distributed test method, server and distributed test system
CN113342353B (en) Mock data generation method and device
CN111078571B (en) Test method for analog response, terminal equipment and computer readable storage medium
CN111008147B (en) Application program testing method, terminal and computer readable storage medium
US20120167037A1 (en) Software static testing apparatus and method
CN111045706B (en) Method and device for updating execution package of test item and computer readable storage medium
CN112015645A (en) Function test method and device of web system and electronic equipment
CN111209197A (en) Application program continuous integration test method, system, equipment and storage medium
US7082376B1 (en) State full test method executor
CN115545677B (en) Online process specification detection method and system based on automatic case execution condition

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