CN112631931A - Version testing method and device, storage medium and electronic equipment - Google Patents

Version testing method and device, storage medium and electronic equipment Download PDF

Info

Publication number
CN112631931A
CN112631931A CN202011611205.5A CN202011611205A CN112631931A CN 112631931 A CN112631931 A CN 112631931A CN 202011611205 A CN202011611205 A CN 202011611205A CN 112631931 A CN112631931 A CN 112631931A
Authority
CN
China
Prior art keywords
test
automatic
equipment
version
case
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
CN202011611205.5A
Other languages
Chinese (zh)
Other versions
CN112631931B (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.)
Beijing Topsec Technology Co Ltd
Beijing Topsec Network Security Technology Co Ltd
Beijing Topsec Software Co Ltd
Original Assignee
Beijing Topsec Technology Co Ltd
Beijing Topsec Network Security Technology Co Ltd
Beijing Topsec 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 Beijing Topsec Technology Co Ltd, Beijing Topsec Network Security Technology Co Ltd, Beijing Topsec Software Co Ltd filed Critical Beijing Topsec Technology Co Ltd
Priority to CN202011611205.5A priority Critical patent/CN112631931B/en
Publication of CN112631931A publication Critical patent/CN112631931A/en
Application granted granted Critical
Publication of CN112631931B publication Critical patent/CN112631931B/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
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • 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
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the application provides a version test method, a version test device, a storage medium and electronic equipment, wherein the version test method comprises the following steps: generating a test task containing a test case, wherein the test case comprises a manual test case and a target automatic test case, the target automatic test case is obtained by selecting all automatic test cases according to the test requirement of the test task, and the test task is a task for testing a customized version; respectively sending the test cases to corresponding test equipment according to the test types of the test cases in the test tasks; receiving test results returned by all the test equipment, wherein the test results comprise manual test results and automatic test results; and backfilling the test results into the test task, so that the test efficiency of the customized version can be provided.

Description

Version testing method and device, storage medium and electronic equipment
Technical Field
The present application relates to the field of software testing technologies, and in particular, to a version testing method and apparatus, a storage medium, and an electronic device.
Background
With the continuous development of computers, automated testing is more and more concerned and favored by testers. Although the existing test method realizes automatic test, the existing test method has the problem of low test efficiency for the test of the customized version.
Disclosure of Invention
An object of the embodiments of the present application is to provide a version testing method, an apparatus, a storage medium, and an electronic device, so as to solve the problem in the prior art that the testing efficiency of a customized version is not high.
In a first aspect, an embodiment of the present application provides a version testing method, where the version testing method includes: generating a test task containing a test case, wherein the test case comprises a manual test case and a target automatic test case, the target automatic test case is obtained by selecting all automatic test cases according to the test requirement of the test task, and the test task is a task for testing a customized version; respectively sending the test cases to corresponding test equipment according to the test types of the test cases in the test tasks, wherein the test equipment comprises manual test equipment and automatic test equipment; receiving test results returned by all the test equipment, wherein the test results comprise manual test results and automatic test results, the manual test results are obtained after the manual test cases are tested by the manual test equipment, and the automatic test results are obtained after the target automatic test cases are tested by the automatic test equipment; and backfilling the test result into the test task.
Therefore, the target automatic test case can be selected from all the automatic test cases according to the test requirements of the test task, and the target automatic test case is subsequently tested. And because the test of the manual test case and the test of the automatic test case are executed in parallel, the test time can be further shortened, the test efficiency can be further improved, and the test requirement of the customized version is further met.
In one possible embodiment, respectively sending the test cases to corresponding test devices according to the test types of the test cases in the test tasks includes: acquiring an identifier of a target automatic test case; and sending the identification of the target automatic test case to automatic test equipment so that the automatic test equipment can search the target automatic test case from all the automatic test cases according to the identification of the target automatic test case.
Therefore, according to the embodiment of the application, the automatic test equipment can quickly acquire the corresponding target automatic test case through the identification of the target automatic test case.
In a possible embodiment, after the test cases are respectively sent to the corresponding test devices according to the test types of the test cases in the test tasks, the version test method further includes: and sending a restart instruction to the automatic test equipment under the condition that an automatic test result sent by the automatic test equipment is not received within the preset time so as to restart the automatic test equipment.
Therefore, in the embodiment of the application, the corresponding automatic test equipment is restarted under the condition that the automatic test result sent by the automatic test equipment is not received within the preset time, so that the problem of low test efficiency caused by abnormality of the automatic test equipment and the like is solved.
In one possible embodiment, the customized version includes a customized portion and a generic portion; the manual test case is a test case related to the customized portion, and the target automatic test case is a test case related to the general portion.
In a second aspect, an embodiment of the present application provides a version testing apparatus, including: the generating module is used for generating a test task containing a test case, the test case comprises a manual test case and a target automatic test case, the target automatic test case is obtained by selecting all automatic test cases according to the test requirement of the test task, and the test task is a task for testing a customized version; the first sending module is used for respectively sending the test cases to corresponding test equipment according to the test types of the test cases in the test tasks, and the test equipment comprises manual test equipment and automatic test equipment; the receiving module is used for receiving test results returned by all the test equipment, wherein the test results comprise manual test results and automatic test results, the manual test results are obtained after the manual test cases are tested by the manual test equipment, and the automatic test results are obtained after the target automatic test cases are tested by the automatic test equipment; and the backfilling module is used for backfilling the test result into the test task.
In a possible embodiment, the first sending module is specifically configured to: acquiring an identifier of a target automatic test case; and sending the identification of the target automatic test case to automatic test equipment so that the automatic test equipment can search the target automatic test case from all the automatic test cases according to the identification of the target automatic test case.
In one possible embodiment, the version testing apparatus further includes: and the second sending module is used for sending a restart instruction to the automatic test equipment under the condition that the automatic test result sent by the automatic test equipment is not received within the preset time so as to facilitate the automatic test equipment to restart.
In one possible embodiment, the customized version includes a customized portion and a generic portion; the manual test case is a test case related to the customized portion, and the target automatic test case is a test case related to the general portion.
In a third aspect, an embodiment of the present application provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is executed by a processor, the computer program performs the method according to the first aspect or any optional implementation manner of the first aspect.
In a fourth aspect, an embodiment of the present application provides an electronic device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the electronic device is running, the machine-readable instructions when executed by the processor performing the method of the first aspect or any of the alternative implementations of the first aspect.
In a fifth aspect, the present application provides a computer program product which, when run on a computer, causes the computer to perform the method of the first aspect or any possible implementation manner of the first aspect.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic diagram illustrating an application scenario provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating a version testing method provided by an embodiment of the present application;
fig. 3 shows a specific flowchart of a version testing method provided in an embodiment of the present application;
fig. 4 shows a block diagram of a version testing apparatus according to an embodiment of the present application;
fig. 5 shows a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
With the continuous development of computers, automated testing is more and more concerned and favored by testers. Although the existing test method utilizes test software to realize automatic test, the existing test method still has the problems of complex operation, difficult sharing of test records and the like, so that the level of the automatic test is lower, and particularly for the test of a customized version, the problem of lower test efficiency caused by the need of testing all test cases also exists.
For example, existing testing methods include: the method comprises the steps of connecting to a Daily constructed (Daily Build) version server through an FTP (File Transfer Protocol) operation module, obtaining a latest successfully compiled Test version, then connecting to a target device through a Secure Shell (SSH) operation module, using the latest Test version to upgrade the device, then creating a Test task (Test Run) through an Application Programming Interface (API) of a Test management tool (testRail), and automatically adding all version Test cases to the Test task. And then, according to the test cases in the test tasks, automatically matching and screening corresponding test scripts, and assembling into an automatic test script set, wherein the test cases in the test script set are sequentially executed (the test target is the upgraded equipment with the latest test version). And after the automatic test is finished, backfilling the test result into the test task through an API of the test management tool, automatically sending an email to inform relevant testers, continuously finishing the part needing to be manually executed in the test task in the deployed environment, and finally automatically generating an overall test report.
However, the above conventional test methods have at least the following disadvantages:
in the existing testing method, after a testing task is created, all version test cases are added to the testing task, so that the testing time is very long (for example, under the condition that thousands of test cases exist, 2-3 days are needed for complete execution). Furthermore, the existing testing method is to perform manual testing after the automatic testing is completed, so that the testing time is long.
However, the test time of the customized version is short because the test of the customized version is often very time-critical, and usually only the modified function of the customized version and the core function of the version are verified, so that the existing test method is not suitable for the test of the customized version.
Based on this, the embodiment of the present application provides a version test scheme, by generating a test task including a test case, where the test case includes a manual test case and a target automatic test case, the target automatic test case is obtained by selecting from all automatic test cases according to a test requirement of the test task, the test task is a task for testing a customized version, and then the test case is respectively sent to corresponding test devices according to a test type of the test case in the test task, where the test devices include a manual test device and an automatic test device, and then receive test results returned by all the test devices, where the test results include a manual test result and an automatic test result, the manual test result is obtained after the manual test case is tested by the manual test device, and the automatic test result is obtained after the target automatic test case is tested by the automatic test device, and finally, backfilling the test result into the test task.
Therefore, the target automatic test case can be selected from all the automatic test cases according to the test requirements of the test task, and the target automatic test case is subsequently tested. And because the test of the manual test case and the test of the automatic test case are executed in parallel, the test time can be further shortened, the test efficiency can be further improved, and the test requirement of the customized version is further met.
To facilitate understanding of the embodiments of the present application, some terms in the embodiments of the present application are first explained below:
"customized version": it is a version obtained by setting some customized functions to the software of a general version.
The customized version comprises a customized part and a general part, the manual test cases are test cases related to the customized part, and the target automatic test cases are test cases related to the general part.
For example, in the case that the generic version is a firewall and the customized version is a customized version for a bidirectional address translation function in the generic version, since the address translation includes a source address translation, a destination address translation and a bidirectional address, in the process of screening test cases, the test cases related to the source address translation and the test cases related to the destination address translation are existing, that is, they may be matched with corresponding target automatic test cases from the storage platform (or matched with corresponding target automatic test cases from the storage platform in a manual manner). However, test cases related to bidirectional address translation are not available, which requires manual configuration.
"test case": it refers to the description of testing tasks performed on a specific software product, embodying test schemes, methods, techniques and strategies.
"manual test equipment": it refers to a device that uses a manual test mode to perform testing.
"automatic test equipment": it refers to a device that utilizes an automatic test mode for testing.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an application scenario provided in an embodiment of the present application. The application scenario shown in fig. 1 includes: management devices, manual test devices, automatic test devices (or automatic test platforms), and storage platforms (e.g., which may be used to store test cases and test tasks, etc.). The management equipment is respectively connected with the manual testing equipment, the automatic testing equipment and the storage platform, and the automatic testing equipment is connected with the storage platform.
It should be understood that the specific device of the management device, the specific device of the manual testing device, the specific device of the automatic testing device, the specific device of the storage platform, and the like may all be set according to actual requirements, and the embodiments of the present application are not limited thereto.
For example, the management device may be a mobile phone, a computer, or the like.
As another example, the automatic test equipment may be an execution engine or the like.
As another example, the storage platform may be a database or the like.
In order to facilitate understanding of the embodiments of the present application, the following description will be given by way of specific examples.
Specifically, in the test of the customized version, the management device may select a target test case from all the automatic test cases stored in the storage platform according to the test requirement of the test task. And because the customized functions of different customized versions are different and the customized parts in the customized versions also need to be tested manually, the manual test case can be input by the user. Subsequently, the management device may generate a test task containing the test case. The test cases comprise manual test cases and automatic test cases.
And then, the management equipment can send the test case to corresponding manual test equipment or automatic test equipment according to the test type of the test case in the test task. Subsequently, the manual test equipment may perform manual testing according to the manual test case, and the automatic test equipment may perform automatic testing according to the automatic test case. And the manual test equipment can feed back the manual test result to the management equipment, and the automatic test equipment can feed back the automatic test result to the management equipment.
Finally, the management equipment can backfill the test result into the test task and can store the test task backfilled with the test result into the storage platform so as to facilitate subsequent query.
It should be noted that the version test method provided in the embodiment of the present application may be further extended to other suitable scenarios, and is not limited to the application scenario shown in fig. 1.
Referring to fig. 2, fig. 2 is a flowchart illustrating a version testing method according to an embodiment of the present application. It should be understood that the version test method shown in fig. 2 may be executed by a version test apparatus, which may correspond to the version test apparatus shown in fig. 4 below, and the version test apparatus may be various devices capable of executing the method, such as a management device, a computer, and the like, for example, and the embodiment of the present application is not limited thereto, and specifically includes the following steps:
step S210, a test task including a test case is generated. The test cases comprise manual test cases and target automatic test cases, the target automatic test cases are obtained by selecting all automatic test cases according to the test requirements of the test tasks, and the test tasks are tasks for testing the customized versions.
It should be appreciated that where the customized version includes a customized portion and a generic portion (or, alternatively, an un-customized portion), the generic portion may be tested in an automated manner since it is consistent with the corresponding portion in the generic version. That is, the test requirements of a test task may refer to the test requirements of a generic part.
It should also be understood that the manual test case may be a test case imported through a peripheral device for testing a customized version, or may be a test case downloaded from another device.
In order to facilitate understanding of the embodiments of the present application, the following description will be given by way of specific examples.
Specifically, the customized version may be obtained, a test task for testing the customized version may be created in the test tool according to the customized version, and the test case may be added to the test task.
For a manual test case in the test cases, the manual test case may be a test case created according to the customized portion or a screened test case, and the manual test cases corresponding to different customized versions may also be different because the requirements of the customized portions of different customized versions are different; for the automatic test cases in the test cases, the target automatic test case may be matched from all the automatic test cases stored in the storage platform according to the test requirements of the common part.
It should be noted here that the target automatic test case may be manually screened by a user, or may be automatically matched, and the embodiment of the present application is not limited to this.
Step S220, respectively sending the test cases to corresponding test equipment according to the test types of the test cases in the test tasks. The test equipment comprises manual test equipment and automatic test equipment.
It should be understood that the test types of the test cases refer to a manual test type and an automatic test type.
In order to facilitate understanding of the embodiments of the present application, the following description will be given by way of specific examples.
Optionally, in a case that the test type of the test case is a manual test type, the manual test case is sent to the corresponding manual test device.
In addition, because the manual test case is newly created and the storage platform may not store the related test case, the manual test case may be issued to the corresponding manual test device. Therefore, after the manual test device receives the manual test case, the tester can perform manual test.
Optionally, the automatic test case is sent to the corresponding automatic test equipment when the test type of the test case is the automatic test type.
In addition, because the automatic test case is screened from all the automatic test cases in the storage platform, the identification of the target automatic test case can be obtained, and the identification of the target automatic test case is sent to the corresponding automatic test equipment through the API. And then, the automatic test equipment can search the target automatic test case from all the automatic test cases in the storage platform according to the identification of the target automatic test case, namely, the identification of the target automatic test case can be matched with the storage platform so as to obtain the target automatic test case through matching. And then, automatically screening test scripts corresponding to the distributed target automatic test cases in the total automatic test scripts according to the automatic test cases, and assembling an automatic test script set by using the target automatic test cases and the corresponding test scripts. Thus, the automatic test equipment can test all target automatic test cases in the automatic test script set.
It should be noted that, in consideration of the fact that the automatic test equipment may possibly be down due to abnormal test, a restart instruction is sent to the automatic test equipment when an automatic test result sent by the automatic test equipment is not received within a preset time (that is, a system of the automatic test equipment may be down or abnormal), so that the automatic test equipment is restarted, and the test progress can be guaranteed.
Step S230, receiving test results returned by all the test devices. The test result comprises a manual test result and an automatic test result, the manual test result is obtained after the manual test case is tested through manual test equipment, and the automatic test result is obtained after the target automatic test case is tested through automatic test equipment.
Specifically, after the manual test device performs the manual test, the manual test device may upload the manual test result. And after the automatic test equipment performs the automatic test, the automatic test equipment can upload the automatic test result.
Step S240, backfilling the test result into the test task.
In addition, after all test cases are tested, a test result report can be generated.
Therefore, in the test of the customized version, a test task can be generated by screening required test cases according to the functional requirements of the customized version, and then the test tasks are respectively assigned to a tester and automatic test equipment according to the test types in the test cases. And the two tests can be performed in parallel, and the test result can be backfilled into the test task at the same time, so that the test time can be saved, and the test efficiency can be improved.
In order to facilitate understanding of the embodiments of the present application, the following description will be given by way of specific examples.
Referring to fig. 3, fig. 3 is a specific flowchart illustrating a version testing method according to an embodiment of the present application. The version test method shown in fig. 3 includes:
in step S310, the tester creates a test task on the test management tool.
The test management tool can be used for creating test cases and case sets, and tracking test execution and test reports. In addition, it integrates many tracing tools and provides an API for Hypertext Transfer Protocol (HTTP) so that test activities can be manipulated and managed externally.
Step S320, screening test cases according to the test requirements of the customized version, and adding the screened test cases to the test task.
Step S330, according to the test types in the screened test cases, assigning the manual test cases to the testers, and assigning the target automatic test cases to the automatic test equipment.
For the target automatic test case assigned to the automatic test equipment, the test management tool can issue the assigned target automatic test case to the corresponding automatic test equipment through the API.
Step S340, after the test case assignment is completed, the tester carries out manual test, and backfills the test result into the test task.
Step S350, after the automatic test equipment receives the target automatic test case, the automatic test equipment automatically filters the test scripts corresponding to the distributed target automatic test case from the total automatic test scripts, and assembles the test scripts into an automatic test script set.
And step S360, the automatic test script sets are sequentially executed, and the result is backfilled into the test task through the API of the test management tool after each target automatic test case is executed.
In step S370, a test result report is automatically generated after all the tests are completed.
Therefore, when the version is customized for testing, the created test task can flexibly screen the required test cases according to the version test requirements, the automatic test equipment automatically screens the corresponding test scripts according to the screened target automatic test cases to assemble an automatic test case set, and then the test cases are executed.
It should be understood that the above version test method is only exemplary, and those skilled in the art can make various modifications according to the above method, and the solution after the modification also falls within the scope of the present application.
Referring to fig. 4, fig. 4 shows a structural block diagram of a version testing apparatus 400 provided in an embodiment of the present application, it should be understood that the version testing apparatus 400 can perform the steps in the above method embodiment, and specific functions of the version testing apparatus 400 may be referred to the above description, and a detailed description is appropriately omitted herein to avoid redundancy. The version test device 400 includes at least one software function module that can be stored in a memory in the form of software or firmware (firmware) or solidified in an Operating System (OS) of the version test device 400. Specifically, the version test apparatus 400 includes:
the generating module 410 is configured to generate a test task including a test case, where the test case includes a manual test case and a target automatic test case, the target automatic test case is obtained by selecting from all automatic test cases according to a test requirement of the test task, and the test task is a task for testing a customized version; the first sending module 420 is configured to send the test cases to corresponding test devices according to the test types of the test cases in the test task, where the test devices include manual test devices and automatic test devices; the receiving module 430 is configured to receive test results returned by all the test devices, where the test results include a manual test result and an automatic test result, the manual test result is obtained after the manual test case is tested by the manual test device, and the automatic test result is obtained after the target automatic test case is tested by the automatic test device; and the backfilling module 440 is used for backfilling the test result into the test task.
In a possible embodiment, the first sending module 420 is specifically configured to: acquiring an identifier of a target automatic test case; and sending the identification of the target automatic test case to automatic test equipment so that the automatic test equipment can search the target automatic test case from all the automatic test cases according to the identification of the target automatic test case.
In one possible embodiment, the version testing apparatus 400 further includes: and a second sending module (not shown) configured to send a restart instruction to the automatic test equipment when the automatic test result sent by the automatic test equipment is not received within a preset time, so that the automatic test equipment is restarted.
In one possible embodiment, the customized version includes a customized portion and a generic portion; the manual test case is a test case related to the customized portion, and the target automatic test case is a test case related to the general portion.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus described above may refer to the corresponding process in the foregoing method, and will not be described in too much detail herein.
Fig. 5 shows a block diagram of an electronic device 500 according to an embodiment of the present application. As shown in fig. 5, electronic device 500 may include a processor 510, a communication interface 520, a memory 530, and at least one communication bus 540. Wherein the communication bus 540 is used for realizing direct connection communication of these components. The communication interface 520 of the device in the embodiment of the present application is used for performing signaling or data communication with other node devices. Processor 510 may be an integrated circuit chip having signal processing capabilities. The Processor 510 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor 510 may be any conventional processor or the like.
The Memory 530 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 530 stores computer readable instructions, which when executed by the processor 510, the electronic device 500 may perform the steps of the above-described method embodiments.
The electronic device 500 may further include a memory controller, an input-output unit, an audio unit, and a display unit.
The memory 530, the memory controller, the processor 510, the peripheral interface, the input/output unit, the audio unit, and the display unit are electrically connected to each other directly or indirectly to realize data transmission or interaction. For example, these elements may be electrically coupled to each other via one or more communication buses 540. The processor 510 is adapted to execute executable modules stored in the memory 530, such as software functional modules or computer programs comprised by the electronic device 500.
The input and output unit is used for providing input data for a user to realize the interaction of the user and the server (or the local terminal). The input/output unit may be, but is not limited to, a mouse, a keyboard, and the like.
The audio unit provides an audio interface to the user, which may include one or more microphones, one or more speakers, and audio circuitry.
The display unit provides an interactive interface (e.g. a user interface) between the electronic device and a user or for displaying image data to a user reference. In this embodiment, the display unit may be a liquid crystal display or a touch display. In the case of a touch display, the display can be a capacitive touch screen or a resistive touch screen, which supports single-point and multi-point touch operations. The support of single-point and multi-point touch operations means that the touch display can sense touch operations simultaneously generated from one or more positions on the touch display, and the sensed touch operations are sent to the processor for calculation and processing.
It will be appreciated that the configuration shown in FIG. 5 is merely illustrative and that the electronic device 500 may include more or fewer components than shown in FIG. 5 or may have a different configuration than shown in FIG. 5. The components shown in fig. 5 may be implemented in hardware, software, or a combination thereof.
A storage medium is provided having stored thereon a computer program which, when executed by a processor, performs the method of an embodiment.
The present application also provides a computer program product which, when run on a computer, causes the computer to perform the method of an embodiment.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the system described above may refer to the corresponding process in the foregoing method, and will not be described in too much detail herein.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the device-like embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or 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 identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A version test method, comprising:
generating a test task containing a test case, wherein the test case comprises a manual test case and a target automatic test case, the target automatic test case is obtained by selecting all automatic test cases according to the test requirement of the test task, and the test task is a task for testing a customized version;
respectively sending the test cases to corresponding test equipment according to the test types of the test cases in the test tasks, wherein the test equipment comprises manual test equipment and automatic test equipment;
receiving test results returned by all the test equipment, wherein the test results comprise manual test results and automatic test results, the manual test results are obtained after the manual test cases are tested by the manual test equipment, and the automatic test results are obtained after the target automatic test cases are tested by the automatic test equipment;
and backfilling the test result into the test task.
2. The version test method according to claim 1, wherein the sending the test cases to the corresponding test devices respectively according to the test types of the test cases in the test tasks comprises:
acquiring the identification of the target automatic test case;
and sending the identification of the target automatic test case to the automatic test equipment so that the automatic test equipment can search the target automatic test case from all automatic test cases according to the identification of the target automatic test case.
3. The version testing method according to claim 1, wherein after the test cases are respectively sent to the corresponding testing devices according to the test types of the test cases in the test tasks, the version testing method further comprises:
and sending a restart instruction to the automatic test equipment under the condition that an automatic test result sent by the automatic test equipment is not received within preset time so as to restart the automatic test equipment.
4. The version testing method of claim 1, wherein the customized version comprises a customized part and a generic part;
the manual test case is a test case related to the customized part, and the target automatic test case is a test case related to the general part.
5. A version test apparatus, comprising:
the system comprises a generating module, a processing module and a processing module, wherein the generating module is used for generating a test task containing a test case, the test case comprises a manual test case and a target automatic test case, the target automatic test case is obtained by selecting all automatic test cases according to the test requirement of the test task, and the test task is used for testing a customized version;
the first sending module is used for respectively sending the test cases to corresponding test equipment according to the test types of the test cases in the test tasks, and the test equipment comprises manual test equipment and automatic test equipment;
the receiving module is used for receiving test results returned by all the test equipment, wherein the test results comprise manual test results and automatic test results, the manual test results are obtained after the manual test cases are tested by the manual test equipment, and the automatic test results are obtained after the target automatic test cases are tested by the automatic test equipment;
and the backfilling module is used for backfilling the test result into the test task.
6. The version test device according to claim 5, wherein the first sending module is specifically configured to: acquiring the identification of the target automatic test case; and sending the identification of the target automatic test case to the automatic test equipment so that the automatic test equipment can search the target automatic test case from all automatic test cases according to the identification of the target automatic test case.
7. The version test device according to claim 5, further comprising:
and the second sending module is used for sending a restarting instruction to the automatic testing equipment under the condition that the automatic testing result sent by the automatic testing equipment is not received within the preset time so as to facilitate the automatic testing equipment to restart.
8. The version test device of claim 5, wherein the customized version comprises a customized portion and a generic portion;
the manual test case is a test case related to the customized part, and the target automatic test case is a test case related to the general part.
9. A storage medium having stored thereon a computer program for executing the version testing method according to any one of claims 1 to 4 when executed by a processor.
10. An electronic device, characterized in that the electronic device comprises: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when the electronic device is operating, the machine-readable instructions when executed by the processor performing the version testing method of any of claims 1 to 4.
CN202011611205.5A 2020-12-29 2020-12-29 Version testing method and device, storage medium and electronic equipment Active CN112631931B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011611205.5A CN112631931B (en) 2020-12-29 2020-12-29 Version testing method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011611205.5A CN112631931B (en) 2020-12-29 2020-12-29 Version testing method and device, storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN112631931A true CN112631931A (en) 2021-04-09
CN112631931B CN112631931B (en) 2023-08-29

Family

ID=75286813

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011611205.5A Active CN112631931B (en) 2020-12-29 2020-12-29 Version testing method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN112631931B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113419955A (en) * 2021-06-25 2021-09-21 展讯通信(上海)有限公司 Software version automatic test system, method, medium and device

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105718366A (en) * 2014-12-05 2016-06-29 中国航空工业集团公司航空动力控制系统研究所 Automatic testing method of model based on Matlab
CN106502888A (en) * 2016-10-13 2017-03-15 杭州迪普科技股份有限公司 The method of testing of software and device
CN108920357A (en) * 2018-06-01 2018-11-30 平安普惠企业管理有限公司 Operation system detection method, device, computer equipment and storage medium
CN110750453A (en) * 2019-09-24 2020-02-04 彩讯科技股份有限公司 HTML 5-based intelligent mobile terminal testing method, system, server and storage medium
CN110941547A (en) * 2019-10-12 2020-03-31 平安普惠企业管理有限公司 Automatic test case library management method, device, medium and electronic equipment
US10678666B1 (en) * 2011-09-07 2020-06-09 Innovative Defense Technologies, LLC Method and system for implementing automated test and retest procedures in a virtual test environment

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10678666B1 (en) * 2011-09-07 2020-06-09 Innovative Defense Technologies, LLC Method and system for implementing automated test and retest procedures in a virtual test environment
CN105718366A (en) * 2014-12-05 2016-06-29 中国航空工业集团公司航空动力控制系统研究所 Automatic testing method of model based on Matlab
CN106502888A (en) * 2016-10-13 2017-03-15 杭州迪普科技股份有限公司 The method of testing of software and device
CN108920357A (en) * 2018-06-01 2018-11-30 平安普惠企业管理有限公司 Operation system detection method, device, computer equipment and storage medium
CN110750453A (en) * 2019-09-24 2020-02-04 彩讯科技股份有限公司 HTML 5-based intelligent mobile terminal testing method, system, server and storage medium
CN110941547A (en) * 2019-10-12 2020-03-31 平安普惠企业管理有限公司 Automatic test case library management method, device, medium and electronic equipment

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113419955A (en) * 2021-06-25 2021-09-21 展讯通信(上海)有限公司 Software version automatic test system, method, medium and device

Also Published As

Publication number Publication date
CN112631931B (en) 2023-08-29

Similar Documents

Publication Publication Date Title
CN107896244B (en) Version file distribution method, client and server
US9639341B2 (en) Network hardware and software upgrade recommender
CN110727575B (en) Information processing method, system, device and storage medium
CN111506318A (en) Circuit board chip burning method, device, terminal and computer readable storage medium
CN112241360A (en) Test case generation method, device, equipment and storage medium
US9582270B2 (en) Effective feature location in large legacy systems
CN113127347A (en) Interface testing method, device, equipment and readable storage medium
CN112015654A (en) Method and apparatus for testing
CN112380145A (en) SDK generation method, device, equipment and readable storage medium
CN109992501A (en) The availability inspection of small routine can use small routine list generation method and device
CN113014445A (en) Operation and maintenance method, device and platform for server and electronic equipment
CN110795332A (en) Automatic testing method and device
CN112631931B (en) Version testing method and device, storage medium and electronic equipment
CN112988600A (en) Service scene testing method and device, electronic equipment and storage medium
CN110187890B (en) Project deployment method, electronic equipment and storage medium
CN104391792A (en) Test environment information processing method, device and system
CN110201397B (en) Game resource allocation method and device and electronic equipment
CN111159028A (en) Webpage testing method and device
CN116594881A (en) Network environment switching method, device, equipment, development system and storage medium
WO2023277802A2 (en) Device and method for identifying errors in a software application
CN113704281A (en) Data format conversion method and device, storage medium and electronic equipment
CN114371866A (en) Version reconfiguration test method, device and equipment of service system
CN115437903A (en) Interface test method, device, apparatus, storage medium, and program
CN112486497A (en) Compiling configuration file generation method and device, electronic equipment and storage medium
CN113011858A (en) Audit project configuration and execution method and device

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