CN109614519B - Data import method and data import device - Google Patents
Data import method and data import device Download PDFInfo
- Publication number
- CN109614519B CN109614519B CN201811496304.6A CN201811496304A CN109614519B CN 109614519 B CN109614519 B CN 109614519B CN 201811496304 A CN201811496304 A CN 201811496304A CN 109614519 B CN109614519 B CN 109614519B
- Authority
- CN
- China
- Prior art keywords
- file
- test
- test case
- target
- xml format
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test 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 invention provides a data import method and a data import device, and relates to the technical field of data import. The data importing method comprises the following steps: selecting one of a plurality of test cases to be imported as a target case, and creating a test file according to a preset test template and the target case; converting the test file into a first target file in an XML format, and converting the first target file into a second target file in an XLS format; importing the plurality of test cases to be imported into the second target file; and converting the second target file into a third target file in an XML format, and importing the third target file into a test case management system. By the method, the test cases can be imported into the test case management system in batches, so that the data import efficiency is improved.
Description
Technical Field
The present invention relates to the field of data import technologies, and in particular, to a data import method and a data import apparatus.
Background
The management of test cases has been shifted from Excel recording to test case management system management. However, the inventors have found that, in the prior art, test cases can only be imported by an operator manually inputting test cases into a test case management system, and there is no method for importing test cases into the test case management system in batch, which results in a problem of low efficiency of data import.
Disclosure of Invention
In view of the above, the present invention provides a data importing method and a data importing apparatus to solve the problems in the prior art.
In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:
a method of data import, the method comprising:
selecting one of a plurality of test cases to be imported as a target case, and creating a test file according to a preset test template and the target case;
converting the test file into a first target file in an XML format, and converting the first target file into a second target file in an XLS format;
importing the plurality of test cases to be imported into the second target file;
and converting the second target file into a third target file in an XML format, and importing the third target file into a test case management system.
In a preferred option of the embodiment of the present invention, the data importing method further includes:
determining at least one test case in the third target file;
executing the at least one test case to obtain a corresponding test result and a bug number;
importing the test result and the bug number into a pre-generated template file in an XLS format to obtain a corresponding test result file;
and converting the test result file into an XML format, and importing the XML format into the test case management system.
In a preferred option of the embodiment of the present invention, the step of determining at least one test case in the third target file includes:
numbering each test case in the third target file based on the test case management system, and generating an XML format file comprising the number;
and selecting at least one test case to be executed in the XML format file comprising the serial number.
In a preferred option of the embodiment of the present invention, the step of importing the test result and the bug number into a pre-generated XLS-formatted template file to obtain a corresponding test result file includes:
generating a file in an XML format based on the test case management system;
and converting the XML format file into an XLS format to obtain the template file.
In a preferred option of the embodiment of the present invention, the step of converting the test result file into an XML format and importing the XML format to the test case management system includes:
converting the test result file into an XML format;
and modifying the date and the executor name in the test result file in the XML format, and importing the modified test result file into the test case management system.
The embodiment of the invention also provides a data importing device, which comprises:
the test file creating module is used for selecting one test case from a plurality of test cases to be imported as a target case and creating a test file according to a preset test template and the target case;
the file conversion module is used for converting the test file into a first target file in an XML format and converting the first target file into a second target file in an XLS format;
the test case importing module is used for importing the plurality of test cases to be imported into the second target file;
and the target file importing module is used for converting the second target file into a third target file in an XML format and importing the third target file into the test case management system.
In a preferred option of the embodiment of the present invention, the data importing apparatus further includes:
the test case determining module is used for determining at least one test case in the third target file;
the test case execution module is used for executing the at least one test case to obtain a corresponding test result and a bug number;
the test result file generation module is used for importing the test result and the bug number into a pre-generated template file in an XLS format to obtain a corresponding test result file;
and the test result file import module is used for converting the test result file into an XML format and importing the test result file into the test case management system.
In a preferred option of the embodiment of the present invention, the test case determining module includes:
the test case numbering unit is used for numbering each test case in the third target file based on the test case management system and generating an XML format file comprising the number;
and the test case selection unit is used for selecting at least one test case to be executed in the XML format file comprising the serial number.
In a preferred option of the embodiment of the present invention, the test result file generating module includes:
the XML format file generating unit is used for generating a file in an XML format based on the test case management system;
and the first file conversion unit is used for converting the XML format file into an XLS format so as to obtain the template file.
In a preferred option of the embodiment of the present invention, the test result file importing module includes:
the second file conversion unit is used for converting the test result file into an XML format;
and the test result file generating unit is used for modifying the date and the executor name in the test result file in the XML format and importing the modified test result file into the test case management system.
According to the data import method and the data import device provided by the embodiment of the invention, a test file can be created according to a preset test template and a target case selected from a plurality of test cases to be imported, the test file generates the target file after format conversion, the plurality of test cases to be imported are imported into the target file, the target file is converted into an XML format and is imported into the test case management system, so that the test cases are imported into the test case management system in batches, and the data import efficiency is improved.
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
Fig. 1 is a block diagram of an electronic device according to an embodiment of the present invention.
Fig. 2 is a schematic flowchart of a data importing method according to an embodiment of the present invention.
Fig. 3 is another schematic flow chart of a data importing method according to an embodiment of the present invention.
Fig. 4 is a flowchart illustrating step S150 in fig. 3.
Fig. 5 is a flowchart illustrating step S170 in fig. 3.
Fig. 6 is a flowchart illustrating step S180 in fig. 3.
Fig. 7 is a block diagram of a data importing apparatus according to an embodiment of the present invention.
Fig. 8 is another block diagram of a data importing apparatus according to an embodiment of the present invention.
Fig. 9 is a block diagram of a test case determining module according to an embodiment of the present invention.
Fig. 10 is a block diagram of a test result file generation module according to an embodiment of the present invention.
Fig. 11 is a block diagram of a structure of a test result file import module according to an embodiment of the present invention.
Icon: 10-an electronic device; 12-a memory; 14-a processor; 100-data import means; 110-a test file creation module; 120-file conversion module; 130-test case import module; 140-target file import module; 150-test case determination module; 151-test case numbering unit; 152-test case selection unit; 160-test case execution module; 170-test result file generation module; 171-XML format file generating unit; 172-a first file conversion unit; 180-test result file import module; 181-second file conversion unit; 182-test result file generation unit.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
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. In the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not intended to be construed as only or implying relative importance.
In the description of the present invention, unless otherwise expressly specified or limited, the terms "disposed," "connected," and "connected" are to be construed broadly, e.g., as meaning fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
As shown in fig. 1, an embodiment of the present invention provides an electronic device 10, which includes a memory 12, a processor 14, and a data importing apparatus 100, where the data importing apparatus 100 includes one or more software functional modules stored in the memory 12 and executed by the processor 14.
Optionally, the specific form of the electronic device 10 is not limited, and may be set according to practical applications. In the present embodiment, a feasible example is provided, and the electronic device 10 may be a computer.
Wherein the memory 12 and the processor 14 are electrically connected directly or indirectly to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The data import apparatus 100 includes at least one software functional module that can be stored in the memory 12 in the form of software or firmware (firmware). The processor 14 is configured to execute executable computer programs stored in the memory 12, such as software functional modules and computer programs included in the data importing apparatus 100, so as to implement a data importing method.
The Memory 12 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. Wherein the memory 12 is used for storing a program, and the processor 14 executes the program after receiving the execution instruction.
The processor 14 may be an integrated circuit chip having signal processing capabilities. The Processor 14 may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but 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, discrete hardware components.
It will be appreciated that the configuration shown in FIG. 1 is merely illustrative and that the electronic device 10 may include more or fewer components than shown in FIG. 1 or may have a different configuration than shown in FIG. 1. The components shown in fig. 1 may be implemented in hardware, software, or a combination thereof.
With reference to fig. 2, an embodiment of the present invention provides a data importing method applicable to the electronic device 10. Wherein the method steps defined by the method related flow may be implemented by the processor 14. The specific process shown in fig. 2 will be described in detail below.
Step S110, selecting one of a plurality of test cases to be imported as a target case, and creating a test file according to a preset test template and the target case.
Optionally, the selection mode of the target use case is not limited, and may be set according to actual application requirements. For example, in this embodiment, a first test case may be selected from the plurality of test cases to be imported as a target case.
In detail, in this embodiment, the preset test template may include a case title, a case level, an execution mode, a keyword, a case abstract, a preset condition, an operation step, an expected result, and a test mode of each test case. The use case titles, the keywords and the use case abstract can distinguish the test cases.
Meanwhile, in this embodiment, a test file is created based on the test case management system according to a preset test template and the target case, where the test file includes information such as a case title, a keyword, and a case abstract of the target case.
Step S120, converting the test file into a first target file in an XML format, and converting the first target file into a second target file in an XLS format.
In detail, based on the test case management system, the test file is converted into a first target file in an XML format, and the first target file can be converted into a second target file in an XLS format by importing the first target file in the XML format into Excel software, so that a test case can be conveniently imported.
The second object file is in an XLS format, that is, the second object file can be opened and edited by Excel software. Also, XLS formats may include, but are not limited to, Excel document formats such as. XLS,. xlsx,. xlw, and the like.
Step S130, importing the plurality of test cases to be imported into the second target file.
In detail, the specific manner of importing the test case is not limited, and may be set according to the actual application requirements. For example, in this embodiment, the test case may be imported in a manner that the plurality of test cases to be imported are copied to the second target file according to a preset test template.
Step S140, converting the second target file into a third target file in an XML format, and importing the third target file into the test case management system.
In detail, in this embodiment, the second object file may be converted into a third object file in an XML format based on Excel software.
Through the arrangement, a test file can be created according to a preset test template and the target cases selected from the multiple test cases to be imported, the test file generates a target file after format conversion is carried out on the test file, the multiple test cases to be imported are imported into the target file, the target file is converted into an XML format and is imported into the test case management system, the test cases are imported into the test case management system in batches, and therefore data import efficiency is improved.
Further, with reference to fig. 3, the data importing method may further include step S150, step S160, step S170, and step S180, so as to import the test results of the test cases into the test case management system in batch.
Step S150, determining at least one test case in the third target file.
Optionally, the manner of executing step S150 to determine at least one test case in the third target file is not limited, and may be set according to actual applications. For example, in this embodiment, with reference to fig. 4, step S150 may include step S151 and step S152, so as to determine at least one test case in the third target file.
Step S151, numbering each test case in the third target file based on the test case management system, and generating an XML format file including the numbering.
In detail, after the third target file including the test cases is imported to a test case management system, the test cases in the third target file are numbered based on the test case management system. In this embodiment, the third target file after numbering the test cases may be converted into an XML format file based on the test case management system.
Step S152, selecting at least one test case to be executed in the XML format file including the number.
The XML format file comprising the numbers comprises the numbers of the test cases, and the case to be executed can be selected by selecting the number of at least one test case to be executed.
And step S160, executing the at least one test case to obtain a corresponding test result and a bug number.
In detail, the test case to be executed selected in step S152 is executed, and a test result corresponding to the test case is generated. And after the test result which does not pass is generated, numbering the corresponding test case to generate a bug number.
Step S170, importing the test result and the bug number into a pre-generated template file in an XLS format to obtain a corresponding test result file.
Optionally, the mode of generating the template file is not limited, and may be set according to actual applications. For example, in the present embodiment, in conjunction with fig. 5, step S170 may include step S171 and step S172 to generate a template file in an XLS format.
Step S171, generating an XML-format file based on the test case management system.
In detail, a file in an XML format is generated based on the test case management system receiving the control signal generated by clicking the ' execute test ' menu to export the export result as the import result '.
Step S172, converting the XML format file into an XLS format to obtain the template file.
The XML-formatted file can be converted into an XLS format in a mode of importing the XML-formatted file into Excel software, so that the template file can be obtained.
And step S180, converting the test result file into an XML format and importing the XML format into the test case management system.
Further, in conjunction with FIG. 6, step S180 may include steps S181 and S182 to modify the date and actor name in the test file.
Step S181, converting the test result file into an XML format.
In detail, in this embodiment, the test result file may be converted into an XML format based on Excel software.
Step S182, modifying the date and the executor name in the test result file in the XML format, and importing the modified test result file into the test case management system.
In detail, the date and the actor name in the XML-formatted test result file may be modified by an editing tool. Optionally, the specific type of the editing tool is not limited, and may be set according to the actual application requirement. For example, in the present embodiment, the editing tool may be Notepad.
With reference to fig. 7, an embodiment of the present invention further provides a data importing apparatus 100 applicable to the electronic device 10, which may include a test file creating module 110, a file converting module 120, a test case importing module 130, and a target file importing module 140.
The test file creating module 110 is configured to select one of the multiple test cases to be imported as a target case, and create a test file according to a preset test template and the target case. In this embodiment, the test file creating module 110 may be configured to execute step S110 shown in fig. 2, and the foregoing description of S110 may be referred to for the detailed description of the test file creating module 110.
The file conversion module 120 is configured to convert the test file into a first target file in an XML format, and convert the first target file into a second target file in an XLS format. In this embodiment, the file conversion module 120 may be configured to perform step S120 shown in fig. 2, and the foregoing description of step S120 may be referred to for specific description of the file conversion module 120.
The test case importing module 130 is configured to import the plurality of test cases to be imported into the second target file. In this embodiment, the test case importing module 130 may be configured to execute step S130 described in fig. 2, and for the specific description of the test case importing module 130, reference may be made to the description of step S130.
The object file importing module 140 is configured to convert the second object file into a third object file in an XML format, and import the third object file into the test case management system. In this embodiment, the object file importing module 140 may be configured to execute step S140 shown in fig. 2, and the foregoing description of step S140 may be referred to for specific description of the object file importing module 140.
With reference to fig. 8, the data importing apparatus 100 may further include a test case determining module 150, a test case executing module 160, a test result file generating module 170, and a test result file importing module 180, so as to import the test results of the test cases into the test case management system in batch.
The test case determining module 150 is configured to determine at least one test case in the third target file. In this embodiment, the test case determining module 150 may be configured to execute step S150 illustrated in fig. 3, and the detailed description about the test case determining module 150 may refer to the description about step S150.
The test case execution module 160 is configured to execute the at least one test case to obtain a corresponding test result and a bug number. In this embodiment, the test case execution module 160 may be configured to execute step S160 shown in fig. 3, and the detailed description about the test case execution module 160 may refer to the description about step S160.
The test result file generating module 170 is configured to import the test result and the bug number into a pre-generated XLS-formatted template file to obtain a corresponding test result file. In this embodiment, the test result file generating module 170 may be configured to execute step S170 described in fig. 3, and for the specific description of the test result file generating module 170, reference may be made to the foregoing description of step S170.
The test result file import module 180 is configured to convert the test result file into an XML format, and import the test result file into the test case management system. In this embodiment, the test result file importing module 180 may be configured to perform step S180 shown in fig. 3, and for the specific description of the test result file importing module 180, reference may be made to the description of step S180 above.
In conjunction with fig. 9, the test case determination module 150 may include a test case numbering unit 151 and a test case selection unit 152.
The test case numbering unit 151 is configured to number each test case in the third target file based on the test case management system, and generate an XML format file including a number. In this embodiment, the test case numbering unit 151 may be configured to execute step S151 described in fig. 4, and the foregoing description of step S151 may be referred to for specific description of the test case numbering unit 151.
The test case selecting unit 152 is configured to select at least one test case to be executed in the XML format file including the number. In this embodiment, the test case selecting unit 152 may be configured to execute step S152 described in fig. 4, and the detailed description about the test case selecting unit 152 may refer to the description about step S152.
Referring to fig. 10, the test result file generating module 170 may include an XML format file generating unit 171 and a first file converting unit 172.
The XML format file generating unit 171 is configured to generate an XML format file based on the test case management system. In this embodiment, the XML-format-file generating unit 171 may be configured to execute step S171 shown in fig. 5, and the detailed description about the XML-format-file generating unit 171 may refer to the foregoing description about step S171.
The first file converting unit 172 is configured to convert the XML-format file into an XLS format to obtain the template file. In this embodiment, the first file converting unit 172 may be configured to execute step S172 shown in fig. 5, and the foregoing description of step S172 may be referred to for the specific description of the first file converting unit 172.
Referring to fig. 11, the test result file import module 180 may include a second file conversion unit 181 and a test result file generation unit 182.
The second file converting unit 181 is configured to convert the test result file into an XML format. In this embodiment, the second file converting unit 181 may be configured to execute step S181 described in fig. 6, and the foregoing description of step S181 may be referred to for the specific description of the second file converting unit 181.
The test result file generating unit 182 is configured to modify the date and the executor name in the test result file in the XML format, and import the modified test result file into the test case management system. In this embodiment, the test result file generating unit 182 may be configured to execute step S182 described in fig. 6, and the foregoing description of step S182 may be referred to for the specific description of the test result file generating unit 182.
In summary, according to the data importing method and the data importing apparatus 100 provided in the embodiments of the present invention, a test file may be created according to a preset test template and a target case selected from a plurality of test cases to be imported, the test file performs format conversion to generate a target file, the plurality of test cases to be imported are imported to the target file, the target file is converted to an XML format and imported to the test case management system, so as to import the test cases to the test case management system in batch, thereby improving the efficiency of data importing.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus and method embodiments described above are illustrative only, as the flowcharts 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 invention. 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, the functional modules in the embodiments of the present invention 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 invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, an electronic device, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. 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 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 identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A method for importing data, the method comprising:
selecting one of a plurality of test cases to be imported as a target case, and creating a test file according to a preset test template and the target case;
converting the test file into a first target file in an XML format, and converting the first target file into a second target file in an XLS format;
importing the plurality of test cases to be imported into the second target file;
converting the second target file into a third target file in an XML format, and importing the third target file into a test case management system;
determining at least one test case in the third target file;
executing the at least one test case to obtain a corresponding test result and a bug number;
importing the test result and the bug number into a pre-generated template file in an XLS format to obtain a corresponding test result file;
and converting the test result file into an XML format, and importing the XML format into the test case management system.
2. The data import method according to claim 1, wherein the step of determining at least one test case in the third target file comprises:
numbering each test case in the third target file based on the test case management system, and generating an XML format file comprising the number;
and selecting at least one test case to be executed in the XML format file comprising the serial number.
3. The data import method according to claim 1, wherein the importing the test result and the bug number into a pre-generated XLS-formatted template file to obtain a corresponding test result file comprises:
generating a file in an XML format based on the test case management system;
and converting the XML format file into an XLS format to obtain the template file.
4. The data import method according to claim 1, wherein the step of converting the test result file into an XML format and importing the test result file into the test case management system includes:
converting the test result file into an XML format;
and modifying the date and the executor name in the test result file in the XML format, and importing the modified test result file into the test case management system.
5. A data importing apparatus, comprising:
the test file creating module is used for selecting one test case from a plurality of test cases to be imported as a target case and creating a test file according to a preset test template and the target case;
the file conversion module is used for converting the test file into a first target file in an XML format and converting the first target file into a second target file in an XLS format;
the test case importing module is used for importing the plurality of test cases to be imported into the second target file;
the target file import module is used for converting the second target file into a third target file in an XML format and importing the third target file into the test case management system;
the test case determining module is used for determining at least one test case in the third target file;
the test case execution module is used for executing the at least one test case to obtain a corresponding test result and a bug number;
the test result file generation module is used for importing the test result and the bug number into a pre-generated template file in an XLS format to obtain a corresponding test result file;
and the test result file import module is used for converting the test result file into an XML format and importing the test result file into the test case management system.
6. The data import apparatus according to claim 5, wherein the test case determination module includes:
the test case numbering unit is used for numbering each test case in the third target file based on the test case management system and generating an XML format file comprising the number;
and the test case selection unit is used for selecting at least one test case to be executed in the XML format file comprising the serial number.
7. The data import apparatus according to claim 5, wherein the test result file generation module comprises:
the XML format file generating unit is used for generating a file in an XML format based on the test case management system;
and the first file conversion unit is used for converting the XML format file into an XLS format so as to obtain the template file.
8. The data import apparatus according to claim 5, wherein the test result file import module comprises:
the second file conversion unit is used for converting the test result file into an XML format;
and the test result file generating unit is used for modifying the date and the executor name in the test result file in the XML format and importing the modified test result file into the test case management system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811496304.6A CN109614519B (en) | 2018-12-07 | 2018-12-07 | Data import method and data import device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811496304.6A CN109614519B (en) | 2018-12-07 | 2018-12-07 | Data import method and data import device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109614519A CN109614519A (en) | 2019-04-12 |
| CN109614519B true CN109614519B (en) | 2021-06-15 |
Family
ID=66008706
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811496304.6A Active CN109614519B (en) | 2018-12-07 | 2018-12-07 | Data import method and data import device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109614519B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111767223B (en) * | 2020-06-29 | 2024-02-23 | 北京奇艺世纪科技有限公司 | File processing method and device, electronic equipment and storage medium |
| CN115080328A (en) * | 2022-08-23 | 2022-09-20 | 江西萤火虫微电子科技有限公司 | Board card testing method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104123227A (en) * | 2014-08-13 | 2014-10-29 | 广东电网公司信息中心 | Method for automatically generating testing cases |
| CN104156342A (en) * | 2014-08-01 | 2014-11-19 | 福建星网视易信息系统有限公司 | Method and device for converting Excel format testing case into XML (extensive markup language) format |
| CN107463603A (en) * | 2017-06-16 | 2017-12-12 | 中国科学院计算机网络信息中心 | It is a kind of that control method and system are customized based on the scientific research project life cycle data management for quantifying DMP |
| CN108021503A (en) * | 2017-11-27 | 2018-05-11 | 万兴科技股份有限公司 | The method, apparatus and computer-readable storage medium of automated function test |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2886792B1 (en) * | 2005-06-07 | 2007-08-10 | Evolium Sas Soc Par Actions Si | COMMUNICATION NETWORK DIAGNOSTIC TOOL, OPERATING RESULTS OF REAL TESTS AND / OR VALIDATION BY CONTROL DISPLAY MODE |
-
2018
- 2018-12-07 CN CN201811496304.6A patent/CN109614519B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104156342A (en) * | 2014-08-01 | 2014-11-19 | 福建星网视易信息系统有限公司 | Method and device for converting Excel format testing case into XML (extensive markup language) format |
| CN104123227A (en) * | 2014-08-13 | 2014-10-29 | 广东电网公司信息中心 | Method for automatically generating testing cases |
| CN107463603A (en) * | 2017-06-16 | 2017-12-12 | 中国科学院计算机网络信息中心 | It is a kind of that control method and system are customized based on the scientific research project life cycle data management for quantifying DMP |
| CN108021503A (en) * | 2017-11-27 | 2018-05-11 | 万兴科技股份有限公司 | The method, apparatus and computer-readable storage medium of automated function test |
Non-Patent Citations (1)
| Title |
|---|
| LED分选系统的软件黑盒测试及用例复用开发;欧阳银;《中国优秀硕士学位论文全文数据库 信息科技辑》;20180115(第 01 期);I138-510 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109614519A (en) | 2019-04-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Drosos et al. | Wrex: A unified programming-by-example interaction for synthesizing readable code for data scientists | |
| Löfberg | Automatic robust convex programming | |
| Tan et al. | The reliability of the Akaike information criterion method in cosmological model selection | |
| Tosadori et al. | Creating, generating and comparing random network models with NetworkRandomizer | |
| CN109801677B (en) | Sequencing data automatic analysis method and device and electronic equipment | |
| CN109614519B (en) | Data import method and data import device | |
| CN109062819B (en) | Method and device for generating software test case | |
| JP6331756B2 (en) | Test case generation program, test case generation method, and test case generation apparatus | |
| US9116931B2 (en) | Integrated, configurable, analytical, temporal, visual electronic plan system | |
| Hakak et al. | Residual-based approach for authenticating pattern of multi-style diacritical Arabic texts | |
| Paramonov et al. | Tacle: Learning constraints in tabular data | |
| CN111722995A (en) | Data processing method and device | |
| CA2734207A1 (en) | Electronic file comparator | |
| JP2018092374A (en) | Test case creating device, and test case creating method | |
| CN113761863A (en) | List page configuration method, device and storage medium | |
| CN118468994A (en) | Method and system for automatically generating knowledge map based on content of generated AI | |
| JP6668271B2 (en) | Business specification analysis support apparatus, business specification analysis support method, and program | |
| Bhullar et al. | Exploration of UML diagrams based code generation methods | |
| CN112445461B (en) | Business rule generation method and device, electronic equipment and readable storage medium | |
| CN115758487A (en) | Household template matching method and device, electronic equipment and storage medium | |
| Scicluna et al. | Toward computing attributions for dimensionality reduction techniques | |
| CN114282501B (en) | Method, device, electronic device and storage medium for creating a table in a document | |
| US20150370819A1 (en) | Computer Implemented System and Method for Comparing At Least Two Visual Programming Language Files | |
| Konopiński | Average weighted nucleotide diversity is more precise than pixy in estimating the true value of π from sequence sets containing missing data | |
| CN104408120A (en) | Source code processing 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 | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 850000 No.2, floor 6, unit 2, building 8, east of Liuwu building, west of East Ring Road, north of 1-4 Road, south of 1-3 Road, east of Liuwu building, Lhasa City, Tibet Autonomous Region Patentee after: Wanxing Technology Group Co.,Ltd. Address before: 850000 No.2, floor 6, unit 2, building 8, east of Liuwu building, west of East Ring Road, north of 1-4 Road, south of 1-3 Road, east of Liuwu building, Lhasa City, Tibet Autonomous Region Patentee before: WONDERSHARE TECHNOLOGY Co.,Ltd. |