CN101174240B - Software testing management method and system thereof - Google Patents
Software testing management method and system thereof Download PDFInfo
- Publication number
- CN101174240B CN101174240B CN200610138061XA CN200610138061A CN101174240B CN 101174240 B CN101174240 B CN 101174240B CN 200610138061X A CN200610138061X A CN 200610138061XA CN 200610138061 A CN200610138061 A CN 200610138061A CN 101174240 B CN101174240 B CN 101174240B
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- file
- case
- project information
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a software testing management method, comprising the following steps: A generating a configuration file according to input extraction test case configuration items, acquiring a test procedure file according to the configuration file; B acquiring test cases from the acquired test procedure file according to the configuration file. Furthermore the acquired test cases can be stored in a test cases library. The software testing management method can choose the needed test cases according to the requirement of users from existing test procedure files and then store them into the test case library, thereby realizing convenient management of the test cases and improving the work efficiency of testing personnel. The invention also provides a software testing management system which can realize convenient and flexible management of the test cases, and improve the work efficiency of testing personnel.
Description
Technical field
The present invention relates to the software testing technology field, be specifically related to a kind of software testing management method and system thereof.
Background technology
Software test is after software development is finished, to the correctness of software, the link that reliability and stability are verified.In existing other testing process of api function level, Test Design personnel at first will understand the function of api function to the programmer that api function is write in design, write the test case scheme according to the function of api function again, the test execution personnel write corresponding test procedure according to this test case scheme in such as translation and compiling environments such as compilation, C, C++, VC, JAVA afterwards, judge according to the execution result of test procedure whether tested api function exists defective at last.As seen, existing test process is one and carries out the test case design for scheme earlier, writes the process of corresponding test procedure again according to the test case scheme.At different test case schemes, require the test execution personnel to write corresponding test procedure again.If test execution personnel increase in test process or have revised test procedure, then need the modification of Test Design personnel according to test procedure, increase in the place of test case scheme correspondence or revise corresponding test case and describe.Corresponding process is more consuming time, can not extract test case from test procedure, as the test case scheme, has influenced test execution efficient.In some cases, some test case can also be reused, and wishes that therefore the test case that will write extracts and preserves, can obtain and use when needs, in order to the efficient of raising testing software.
The DOXYGEN instrument provides a kind of function that extracts corresponding document from the source file note, can generate document formats such as XML, HTML, RTF, PDF.And can go out data structure and corresponding graph of a relation in the source file according to configuration extraction.The document that extracts can be used as the test case scheme.But this instrument can not provide the function of extracting test case according to user's flexible configuration, does not also possess the function of test case management.
In order to realize management to test case, application number is that the Chinese patent application of CN200410086041.3 discloses a kind of automation software testing system based on script explanatory tool, be used for test cases is effectively managed, solve test cases and reuse problem.The test cases of this patented claim is similar to above-mentioned test case.This patented claim adopts the test Master Control Unit to receive user's operation instruction information by man-machine interface, and the primary data of control test cases processing unit read test case from the test cases storehouse, after user's editing operation, form with text is preserved the test cases script, and its path is kept in the test cases storehouse.This patented claim can be extracted test cases according to user instruction automatically from the test cases storehouse, and generates the test cases script.But its shortcoming is, this system can not directly extract test cases from test procedure document, the test cases that is extracted is that the user writes in advance and finishes and leave in the test cases storehouse, therefore need be when test cases be added in the test cases storehouse, need the user to write test cases earlier, the test cases storehouse of restoring, this new test cases can be used.Therefore, when the software testing management system was managed, work efficiency was not high, and can not directly extract test case from test procedure.
As seen, how test case both being extracted flexibly, and managed easily again, is a problem demanding prompt solution.
Summary of the invention
In view of this, first fundamental purpose of the present invention is to provide a kind of software testing management method, can make things convenient for, obtain flexibly test case, realizes the management to test case, improves the work efficiency of tester testing software.
Second fundamental purpose of the present invention is to provide a kind of software testing management system, can make things convenient for, obtain flexibly test case, realizes the management to test case, improves the work efficiency of tester testing software.
First aspect to achieve the above object of the invention the invention provides a kind of software testing management method, and this method comprises:
A, according to the extraction test case configuration item of input, generate configuration file; And obtain test procedure document according to this configuration file;
B, according to described configuration file from the test procedure document that obtains, obtain test case;
C, according to the input generation test frame configuration item, generate second configuration file;
D, according to described generation test frame configuration item, obtain and meet test case and the project information thereof that generates the requirement of test frame configuration item;
Test case and project information thereof that E, basis are obtained form test case file;
F, according to described second configuration file and described test case file, generate the test procedure framework.
The method of obtaining described test case and project information thereof among the step D comprises:
D1, the test case that described step B is obtained import database;
The project information of D2, the described test case that will obtain according to described configuration file imports described database;
D3, according to described generation test frame configuration item, from described database, obtain and meet test case and the project information thereof that generates the requirement of test frame configuration item.
The method of obtaining described test case and project information thereof among the step D comprises:
D1, obtain according to described generation test frame configuration item and to meet the existing text use-case that generates the requirement of test frame configuration item;
D2, according to described generation test frame configuration item, from described existing text use-case, obtain test case and project information thereof.
Preferable, software testing management method of the present invention further comprises: the management information according to input manages the test case in the described database.
Second aspect for achieving the above object the invention provides a kind of software testing management system, and this system comprises:
Be used for generating configuration file, and obtain the module of test procedure document according to this configuration file according to the extraction test case configuration item of input; And
Be used for obtaining from the test procedure document that obtains the module of test case according to described configuration file;
This system further comprises the module that is used for generating according to the generation test frame configuration item of user's input second configuration file; Obtain test case and project information thereof according to described generation test frame configuration item, and form the module of test case file; And
Be used for module according to described second configuration file and described test case file generation test procedure framework.
Preferable, this system further comprises the database that is used to store test case.
This system further comprises and is used for obtaining project information according to described configuration file, the module that the described test case obtained and described project information are imported to database.
This system further comprises the management information that is used for according to user input, the module that the information in the described database is managed.
This system further comprises and is used for the module that test case that described administration module is obtained according to described configuration file and described existing text use-case and project information thereof import described database.
Describedly obtain test case and project information thereof, and the module that forms test case file is obtained test case and project information from database according to generating the test frame configuration item.
Describedly obtain test case and project information thereof, and the module that forms test case file is obtained test case and project information from existing text use-case according to generating the test frame configuration item.
Compared with prior art, software testing management method provided by the present invention and system thereof can extract required test case according to the extraction test case configuration item of user's input from existing test procedure document or existing text use-case.At this moment, test case can be deposited in the test case data storehouse, thereby realize the interpolation of test case easily, improve tester's work efficiency; Secondly, the user can also operate by GUI, and the test case in the test case data storehouse is made amendment, and deletion such as searches at operation, thereby has realized the management to test case, is convenient to the more efficiently test case of utilizing in the test case data storehouse.In addition, the present invention is according to the generation test frame configuration item of user's input, from test case data storehouse or existing text use-case, obtain required test case, generate test case and trial function test procedure framework one to one, the tester only needs to fill in trial function in the test procedure document of test procedure framework can finish writing of test procedure, and the test procedure document that generates stores classifiedly under different directories, makes things convenient for the tester to search with coding and uses.
Description of drawings
Fig. 1 is the block diagram of system of software testing management of the present invention system.
Fig. 2 extracts the test case method flow diagram for the present invention.
Fig. 3 writes the test case in the file set for Fig. 2 step 207 method flow diagram of XML file.
Fig. 4 reads the method flow diagram of configuration file for the present invention.
Fig. 5 generates the method flow diagram of the embodiment one of test procedure framework for the present invention.
This invention of Fig. 6 generates the method flow diagram of the embodiment two of test procedure framework.
Fig. 7 writes the method flow diagram of source file for test procedure framework of the present invention
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, below in conjunction with embodiment and accompanying drawing, the present invention is described in more detail.
Core concept of the present invention is the configuration item of software testing management system according to input, obtains test procedure document or existing text use-case; And, obtain test case according to this configuration item content and the test procedure document or the existing text use-case that obtain.
Fig. 1 is the block diagram of system of software testing management of the present invention system.As shown in Figure 1, this software testing management system comprises that file imports module 110, graphic user interface (GUI) 120, administration module 130, test case data storehouse 140 and file generating module 150.
Wherein, file imports module 110, is used for importing test procedure document to be extracted or existing text use-case to GUI120.Wherein, test procedure document to be extracted is the test procedure document that has write, and this test procedure document to be extracted is according to entry name, and category of test is stored in respectively under the different catalogues.The content of test procedure document comprises the test case contents such as test I D, test purpose, test description, expected results and test duration that exist with the note form, and corresponding to the trial function of this test case.A test procedure document may comprise one or more test case; Wherein, existing text use-case is the test case of textual form.
GUI120 is used for providing operation interface to the user.This GUI comprises inputting interface 121 and output interface 122.The software testing management system obtains file by inputting interface 121 and imports test procedure document to be extracted or existing text use-case in the module 110; The user extracts the test case configuration item by these inputting interface 121 inputs and gives administration module 130.This extraction test case configuration item is the term restriction to the test case that will extract.The user generates the test frame configuration item by output interface 122 inputs and gives administration module 130.This generation test frame configuration item is to generating the term restriction of test frame content.
File generating module 150 is used for generating the test frame configuration item according to configuration file that obtains from administration module 130 and test case, or according to the test case of obtaining from administration module 130, generates new text use-case.
Administration module 130 comprises and extracts test case module 131, is used for according to the extraction test case configuration item of above-mentioned user's input test procedure document to be extracted being extracted test case, and the test case of extracting is imported in the test case data storehouse 140.
Administration module 130 also comprises database management module 132, is used for the existing text use-case that inputting interface 121 receives is imported to test case data storehouse 140; The bookkeeping that this database management module 132 can increase, delete, revises and search the test case in the test case data storehouse 140; In addition, this module is obtained test case according to the generation text use-case configuration item of user in output interface 122 inputs from test case data storehouse 140, and generates new text use-case in file generating module 150, and browses printing.
Administration module 130 also comprises generation test frame module 133, be used for obtaining test case at the generation test frame configuration item of output interface 122 inputs from test case data storehouse 140, and export to file generating module 150 by output interface 122 the configuration file that generates according to this generation test frame configuration item with according to the test case that this generation test frame configuration item obtains according to the user.
Test case data storehouse 140 is used to store test case.If directly adopt the test case in the existing text use-case that administration module 130 obtains to generate the test procedure framework, then this software testing management system also can not comprise test case data storehouse 140.
In this software testing management system, GUI120 is for administration module 130 and file import between the module 110, provide an information transmission interface between administration module 130 and the file generating module 150.Administration module 130 also can directly import module 110 with file and link to each other with file generating module 150, directly import module 110 and obtain test procedure document to be extracted or existing text use-case from file, and the test case from the test procedure framework to file generating module output and the relevant information thereof that directly are used to generate.
Software testing management of the present invention system will be stored in from the test case that test procedure document extracts the test case data storehouse 140.Search for convenience and management of test cases, also store the project information relevant in the test case data storehouse 140 with test case.This project information is from the extraction test case configuration item of user's input.Below extract among the test case method embodiment, the test case that not only has of extracting and deposit in the test case data storehouse also has its project information.
Fig. 2 extracts the test case method flow diagram for the present invention.The concrete steps of this method are as follows:
In this step, the extraction test case configuration item that the user need import comprises following several contents:
Entry name and program member: these two contents are imported by the user, in order to when test case is write the test case data storehouse, as the information that writes.
PROJECT TIME: represent that this extracts the time of test case.2006.10.24 for example.
Item description: expression is extracted the description of test case purpose to this.For example: this project is used for demonstration (This project is used for demo).
Testing classification: represent that this need extract the test case of which kind of testing classification.This category of test comprises functional test, performance test, testing classifications such as pressure test, compatibility test, uniformity test.The test procedure document of every kind of classification all is stored in the corresponding file folder.Present embodiment adopts filename to distinguish the test-types of test procedure document to be extracted.For example the filename of functional test with F as prefix, the filename of performance test with P as prefix, the filename of pressure test with S as prefix, the filename of compatibility test with C as prefix.This configuration item can be selected one or more classification, has selected all testing classifications if do not select then be defaulted as.
File type to be extracted: expression need be extracted test case from the test procedure document to be extracted of which kind of file type.The type of test procedure document is different and different according to the translation and compiling environment that adopts, and can comprise the file of types such as compilation, C, C++, VC, JAVA.Can adopt the extension name of file to distinguish file type, the extension name of file can be .c .asm .java etc.This configuration item can be selected one or more type, has selected all file types if do not select then be defaulted as.
File path to be extracted: represent the path at test procedure document to be extracted place, extract test case module 131 and can find test procedure document to be extracted according to this path.
The note sign: expression needs the annotation symbol that test case adopted of extraction.Can select "/* @...@*/", when then extracting test case, can extract the content in "/* @...@*/" symbol.This note sign can be selected other tag mark for use, for example "/* § ... § */" etc.
Show Styles: which kind of Show Styles is the test case that expression extracts adopt.Present embodiment specifies expansion identifiable language (XML) form as specifying Show Styles, and therefore the test case of extracting from test procedure document writes the XML file earlier, utilizes the perl wscript.exe that the content in the XML file is imported the test case data storehouse again.In the present embodiment, the interpretative tool of script adopts the perl wscript.exe, and the perl wscript.exe is used for the file content of certain form is read variable, so that use this variable to carry out some operation, perhaps this variable is write some file.Present embodiment reads configuration file content, reads the test case file information of XML form, generates the test case file of XML form, and this document is imported in the test case data storehouse, all adopts the perl wscript.exe.Adopting the perl wscript.exe is for the present invention is better illustrated, but is not limited to this, can use the other Languages that can articulate with database.
Connect database information: the nominative testing use-case database that the test case that expression extracts will be preserved, this connection database information comprises the database-name that will connect the test case data storehouse, database address, database port, account, encrypted message.
More than in each configuration item, file path to be extracted, file type to be extracted, note are designated essential information; Entry name, program member, PROJECT TIME, item description, testing classification are project information; The connection database information is a database information.
In the present embodiment, user's cuit is called G2000, the program member is alen, PROJECT TIME is 2006.10.24, item description is This project is used for demo, testing classification is functional test and performance test (Function Performance), file path to be extracted is ./G2000, and file type to be extracted is .c, note is designated/and * @...@*/, Show Styles is XML, the database name that connects database information is called MySQL, and database address is 10.1.1.1, and the database port is 1021, account is test, and password is test.
In this step, form configuration file according to extracting the test case configuration item, be to extract the process that the test case configuration item writes configuration file, concrete grammar is: the content stores that will extract each field of test case configuration item is written to the variable name and the variate-value thereof of those variablees in the configuration file in the variable of correspondence line by line.This moment, configuration file comprised: essential information, project information, database information etc.The content of this configuration file is that the mode with joint writes down, in the present embodiment, joint with " [] " as a token of, after connect this joint interior variable name and variate-value thereof.
Wherein, essential information is represented with the joint of [General], being comprised: file path to be extracted (Path), file type/file extension to be extracted (File Extension), note sign variable name and variate-values thereof such as (CommentMark); Project information is represented with the joint of [Project], being comprised: entry name (ProjectName), program member (ProjectMember), key word (Keyword), category of test variable name and variate-values thereof such as (Type); Database information is represented with the joint of [DB], being comprised: database-name (DBName), database address (DBAddress), database port (DBPort), account (DBAccount), password variable name and variate-values thereof such as (DBCode).Above-mentioned every information is to write configuration file respectively line by line.Wherein, key word can have more than one, has two in the present embodiment, difference corresponding PROJECT TIME (Keyword1) and item description (Keyword2), and this key word can add as required; According to the configuration item of user's input, file extension and category of test can have more than one, and file extension has one in the present embodiment, i.e. .c; Because the user selected two category of tests, so category of test has two in configuration file, i.e. Type1 and Type2.
In the present embodiment, the configuration file of formation is as follows
[General]
Path＝./G2000
File?Extension＝.c
CommentMark＝/*@...@*/
[Project]
ProjectName＝G2000
ProjectMember＝″alen″
Keyword1＝2006.10.24
Keyword2＝This?project?is?used?for?demo
Type1＝Function
Type2＝Performance
[DB]
DBName＝MySQL
DBAddress＝10.1.1.1
DBPort＝1021
DBAccount＝test
DBCode＝test
Step 203 adopts the perl script to read configuration file.
In this step, extract test case module 131 and adopt the perl wscript.exe to read in the configuration file that forms in the step 202 line by line, the profile data that reads out is deposited in the configuration information variable of perl wscript.exe, wait is called.The operation according to the information and executing in the configuration file of the following stated is actually and carries out according to corresponding configuration information variable.
In this step, the modularity function that adopts the perl script to provide, specified catalogue of file path to be extracted and the test procedure document to be extracted under the catalogue thereof in the query configuration file.Query directory is a test procedure document under the ./G2000 in the present embodiment, because test procedure document is deposited under the classification sub-directory according to testing classification, therefore the perl wscript.exe is according to the Type information that provides in the configuration file, and all test procedure documents under catalogue and the performance test catalogue are tested in the query function test.
Step 205 judges whether to inquire qualified file.If inquire, then execution in step 206; Otherwise, execution in step 209, process ends.
In this step, qualified file is meant and meets File Extension requirement, and meets the test case file to be extracted that Type requires.In the present embodiment, in 131 arbitration functions test of extraction test case module and the performance test sub-directory whether File Extension being arranged is the test procedure document of .c.
Step 206 is preserved the file set that inquires.
In this step, path, qualified test procedure document place and the filename that inquires is saved in a file set, that is, preserves the path and the filename of these test procedure documents with a data structure.
Step 207 according to configuration file, extracts qualified test case in the file set, and writes the XML file.
In this step, qualified test case is meant that the note sign of test case identifies the test case that is complementary with user configured note.These test cases can import test case data storehouse 140, with the management of realization to test case, and can derive use when needed.Qualified test case in the file set is imported database 140, need earlier test case to be extracted from test procedure document, and write the XML file.The XML file that generates is the test case file of XML form, comprises project information and the test case that extracts from test procedure document.Wherein, project information is the project information in the configuration file.Each test case all identifies to start with filename (file name) in the XML file, and the back writes the test I D of test case successively, test purpose, test description, expected results and test duration; The test case of same testing classification is write together, identifies to start with specific name (typename).Have a plurality of testing classifications in this XML file, have a plurality of test cases in each testing classification.In the present embodiment, shown in the theing contents are as follows of the XML file of formation:
<？xml?version＝″1.0″encoding＝″gb2312″？>
<project?projectname＝″G2000″projectmember＝″alem，joe，mark″
keyword1＝″2006.10.24″keyword2＝″This?project?is?used?for?demo″>
<type?name＝″Function″>
<file?name＝″./G2000/Function/F_A.c″line＝”001”>
＜test I D 〉
F_A
＜/test I D 〉
＜test purpose 〉
Checking C can compile
＜/test purpose 〉
＜test description 〉
On screen, print Hello world
＜/test description 〉
＜expected results 〉
Hello world appears on the screen
＜/expected results 〉
＜the test duration 〉
2006.10.24
＜/the test duration 〉
</file>
</type>
<type?name＝″Performance″>
<file?name＝″./G2000/Performance/P_A.c″line＝”012”>
＜test I D 〉
P_A
＜/test I D 〉
＜test purpose 〉
Verify that once more C can compile
＜/test purpose 〉
＜test description 〉
On screen, print Hello world-again
＜/test description 〉
＜expected results 〉
Hello world-again appears on the screen
＜/expected results 〉
＜the test duration 〉
2006.10.24
＜/the test duration 〉
</file>
</type>
</project>
In the above XML file, the version information that first behavior is relevant.The end of each message segment of XML file all with＜/expression, according to different message segments＜/insert different contents.Extracted test case among the file F_A.c under path/G2000/Function/ (suppose to have only in this document one and meet note sign test case) in the above-mentioned XML file, the row of the initial row of this use-case in test procedure document F_A.c to be extracted number be that line=" 001 " represents.If write the XML file a plurality of test cases are arranged, also extracted test case among the file P_A.c under path/G2000/Performance/ (supposing that this document has only and meets note sign test case) in the above-mentioned for another example XML file, the row of the initial row of this use-case in test procedure document P_A.c to be extracted number be that line=" 012 " represents.
Step 208 imports the test case data storehouse with the XML file.
In this step, the test case data storehouse is by database information appointment in the configuration file, and creates test case data storehouse according to this database information and connect.This test case data storehouse comprises test case table and Project Information Table.The process that the XML file is imported the test case data storehouse is, the perl wscript.exe reads the XML file content, entry name in the XML file, program member, PROJECT TIME, item description are write in the respective field of Project Information Table, and each test case in the XML file all write in the respective field of test case table, the field of test case table comprises entry name, testing classification, test I D, test purpose, test description, expected results, test duration.Use this test case table that test case is managed in order to further facilitate the user, make test case library reaction more information can also comprise filename (Filename) and test case row number (line) field in this test case table.Filename and test case row number also all obtain from above-mentioned XML file.In the present embodiment, the test case table that forms behind the XML file importing test case data storehouse is as shown in table 1, and Project Information Table is as shown in table 2:
| Entry name | Testing classification | Test I D | Filename | Capable number | Test purpose | Test description | Expected results | Test duration |
| G2000 | Function | F_A | ./G2000/ Function/ F_A.c | 001 | Checking C can compile | On screen, print Hello world | On screen, print Hello world | 2006.10.24 |
| G2000 | Performance | P_A | ./G2000/ Performance/ P_A.c | 012 | Verify that once more C can compile | On screen, print Hello world-ag ain | On screen, print Hello world-agai n | 2006.10.24 |
Table 1
| Entry name | The program member | PROJECT TIME (Keyword1) | Item description (Keyword2) | ?other |
| G2000 | alen | 2006.10.24 | This?project?is?used?for?demo |
Table 2
When needing the test case of use test use-case database storing, can utilize the test I D field accurately to inquire about test case by inputting interface 121, perhaps utilize in " test description " field in the test case table or the Project Information Table " item description " field, " program member " field to carry out fuzzy query.The user can also operate by GUI, realizes each field information in the test case data storehouse is increased, deletes or revises by the management to content in test case table and the Project Information Table.
In extracting the test case process, step 207 is the processes that qualified test case write one by one the XML file.As shown in Figure 3, the step of formation XML file is as follows:
In this step, entry name, program member, PROJECT TIME, the item description of project information in the configuration file are write in the XML file, these information are that the user imports when extracting the test case configuration item and imports, and are used for inserting when the XML file is imported the test case data storehouse Project Information Table.
In this step, adopt the data structure of traversal whole storage file path and filename to judge whether the file in the file set all disposes.When traversal, travel through according to testing classification.In the present embodiment, according to Type1, the order of Type2 travels through the file in the file set.The Type1 presentation function is tested, and therefore at first handles the test procedure document of functional test in the file set, and the prefix of the filename of test procedure document has identified the type of this test procedure document.
In this step, traverse a test procedure document after, this test procedure document is opened, adopt the perl wscript.exe to read and search the annotation symbol that is complementary with the note sign line by line, as "/* @...@*/".
In this step, utilize the regular expression that the perl wscript.exe provides to extract the qualified notes content that finds, i.e. test case, and put into temporary variable, then the test case in this temporary variable is write in the XML file.The form that the test case that extracts in this step writes file can also be formatted files such as HTML, RFT, TXT.The form of file is to determine according to the Show Styles that the user imports.In the present embodiment, the test case content that writes the XML file comprises test I D, test purpose, test description, expected results and test duration etc.
In extracting the test case process, step 203 adopts the perl script to get and reads configuration file line by line.Referring to Fig. 4, the concrete steps that read the configuration file method are as follows:
Step 300 is opened configuration file.
Step 302 judges whether the content that reads is the beginning of " joint " sign.Present embodiment is to be feast-brand mark will with " [] ", but also is not limited thereto, and can be the tag mark of other type, for example " { } " etc.Begin if this row content is a feast-brand mark will, then execution in step 306, claim the content in i.e. " [] " to read in the configuration information variable section name; Begin if not feast-brand mark will, then execution in step 303 further judges whether this content that reads is variable name; If not then returning step 301, variable name reads in delegation's content again; Otherwise execution in step 304,305 is read in variable name, and to this variable name assignment.
Step 307 judges whether configuration file finishes.If do not finish, return step 301 and read in delegation again; Otherwise execution in step 308 is closed configuration file.
Step 310 reads configuration file and finishes.
More than extracting the embodiment of test case method, is that test procedure document to be extracted is extracted test case.Can also from existing text use-case, extract test case.The file of existing text use-case comprises test case and project information thereof.Its content class is similar to the above-mentioned content of extracting test case XML file from test procedure document.Therefore in the step 201 of Fig. 2, file can be imported existing text use-case in the module 110, import administration module 130 by inputting interface 121.Database management module 132 in the administration module 130 will have the text use-case and join in the test case data storehouse 140, and in the test case table, set up field according to test case in the existing text use-case, in Project Information Table, set up field according to project information in the existing text use-case.Database management module 132 also by GUI to visual data base administration interface that the user provides, the user can pass through the interface operation importing management information, increase field and data thereof in the mode of adding, perhaps update Database field, for example entry name in the test case library and testing classification field.
Extraction test case method of the present invention can extract test case, and be kept in the test case data storehouse according to the extraction test case configuration item of user's input from test procedure document.When needing, the user only needs to import the configuration item of required test case from the data base administration interface, can browse and print required test case.Just can obtain all test cases of this project, i.e. test case scheme if only imported entry name.Simplify the tester and carried out the test case conceptual design earlier, carried out the process that test case is write again.But can carry out writing of test procedure document earlier, from test procedure document, extract test case by the method for extracting test case again, and form the test case scheme.The extraction test case configuration item of user input comprises the note sign, so the present invention can extract the test case of different note styles from dissimilar files, has increased the dirigibility of extracting test case.The user can also obtain test case by the operation of GUI from the test case data storehouse, and to test case add, bookkeeping such as modification or deletion.
Software testing management of the present invention system also provides and generates the test procedure frame method.Generating the test procedure framework is to extract qualified test case by the generation test frame configuration item that the user imports from existing test case, and write test procedure document, in each test case back, write the trial function framework of this test case correspondence simultaneously.The test procedure framework that the generates preservation of classifying automatically, the test procedure of different category of tests is kept under the different catalogues, makes things convenient for the tester to search and writes test procedure.
The test case that is adopted that generates the test procedure framework can be from the test case data storehouse, also can be from existing text use-case.When test case during,, be directly used in generation test procedure framework according to generating the test case chassis configuration to the existing text use-case that will import from the outside from existing text use-case.The generation of test procedure framework is mainly finished by generation test frame module 133 and file generating module 150 in the administration module, and generation test frame module 133 is mainly finished according to generating the test frame configuration item and obtained corresponding test case file and configuration file; File generating module 150 is mainly finished according to test case file and configuration file and is generated the test procedure framework.Below just illustrate that the present invention generates the method for test procedure framework for two example two.At first the method that generates the test procedure framework with the test case of obtaining in the test case data storehouse is as embodiment one, and referring to Fig. 5, the concrete steps that this embodiment generates the test procedure framework are as follows:
Step 400 generates the test frame configuration item in the output interface input.
In this step, the generation test frame configuration item of user's input comprises Basic Configuration Items and expanded configuration item.Basic Configuration Items comprises project information, test case content, TPL, note style again, connects the generation test file path of database information and appointment.The expanded configuration item comprises: function information such as function name, function return value, function parameter.
Wherein, project information comprises other project information such as entry name, program member, testing classification, PROJECT TIME, item description, and those project information can be obtained from Project Information Table, and the user can choose by output interface when input.The test case content comprises contents such as test I D, test purpose, test description, expected results, and those test case contents can be obtained from the test case table, and the user can choose by output interface when input.The field of project information and test case content all can be used as the field of matching test use-case.
TPL, expression generates the programming language of test procedure framework, c for example, c++ etc.
The note sign, which kind of note style is test case adopt in the test procedure framework that expression generates.
Connect database information, expression will be obtained the relevant information in the test case data storehouse of test case.
The generation test file path of appointment, the path that the test procedure framework that expression generates will be preserved.
The expanded configuration item, the frame content of the pairing trial function of expression test case.
The configuration item that the unnecessary input of user is all when for example wanting to obtain the test procedure document of certain all testing classification of project, then can not be provided with the testing classification item.If do not want to limit the concrete function of test case, the test case content can be set.
In the present embodiment, if user's cuit is called G2000, testing classification is Function, and note is denoted as "/*/", and the database name that connects database information is called MySQL, database address is 10.1.1.1, the database port is 1021, and account is test, and password is test, TPL is the c language, and the generation test file path of appointment is ./G.Function name is not imported, and promptly is defaulted as the test I D of corresponding test case, and function return value (Return Value) is void, and function parameter (Parameter) is void.Other configuration item is not filled out.Therefore utilize the test case of functional test in the G2000 project to generate the test procedure framework.And the language of having determined to generate the test procedure framework is the c language, and the test procedure framework of generation is kept under the ./G path.
Step 401 forms configuration file according to generating the test frame configuration item.
In this step, generate entry name, the TPL of test frame module 130 with Basic Configuration Items, testing classification, the note sign, and the function return value of expanded configuration item, function parameter write configuration file.The information of configuration file is used for setting up engineering catalogue and testing classification sub-directory when generating the test procedure framework, and the note style of definite TPL and test case.
Step 402 generates test frame module 130 usefulness perl wscript.exes and reads configuration file.The process that reads configuration file is with shown in Figure 4 to read the configuration file process identical.Information in the configuration file is read in the configuration information variable at this moment, and wait is called.The operation according to the information and executing in the configuration file of the following stated is actually and carries out according to corresponding configuration information variable.
Step 411,412 is obtained the test case in test case data storehouse according to generating the test frame configuration item, and is derived from the test case data storehouse.
In this step, generate test frame module 130 and set up the connection of test case data storehouse according to the database information that generates in the test frame configuration item, according to the test case that generates in other content match test case data storehouse of test frame configuration item, obtain qualified test case, and from the test case data storehouse, derive.
In the present embodiment, qualified test case is that in the MySQL database, testing classification is the test case of functional test under the project G2000.Suppose to generate test frame module 133 and find a qualified test case from the test case data storehouse, test I D as shown in table 1 is the test case of F_A.
Step 413 forms test case file with the test case that derives.The form of this test case file is the XML form, and this form is imported configuration item according to the user and selected the XML Show Styles to determine.The form of test case file can also be file layouts such as HTML, RTF, TXT.After adopting the XML form to form test case file, need read this document, adopt the perl wscript.exe here with the wscript.exe of correspondence.
In the present embodiment, the test I D that finds out according to step 412 is the test case generation XML file of F A, and this XML file is as follows:
<？xml?version＝″1.0″encoding＝″gb2312″？>
<project?projectname＝″G2000″projectmember＝″alen″keyword1＝″2006.10.24″
keyword2＝″This?project?is?used?for?demo″>
<type?name＝″Function″>
<pattern?line＝″1″>
＜test I D 〉
F_A
＜/test I D 〉
＜test purpose 〉
Checking C can compile
＜/test purpose 〉
＜test description 〉
On screen, print Hello world
＜/test description 〉
＜expected results 〉
Hello world appears on the screen
＜/expected results 〉
＜the test duration 〉
2006.10.24
＜/the test duration 〉
</pattern>
</type>
</project>
Wherein, in forming XML file process, write project information earlier, again test case is write in the different sections according to testing classification.For beginning sign, each test case identifies with use-case numbering (pattern line) section of testing classification to start with specific name (type name).The end of each section all with＜/as finishing sign, different sections＜/the content difference.
Step 420 according to configuration file and XML file, generates the test procedure framework, and writes source file.
In this step, adopt the perl wscript.exe that the content in the XML file is read in the test case variable, so as with the content match of configuration information variable, generate the test procedure framework.When writing the test procedure framework, earlier under specified path, set up engineering catalogue and testing classification sub-directory according to the content of configuration file, and in the testing classification sub-directory, set up test procedure document, the file type of foundation determines that by the TPL that the user selects filename is determined by test I D.Subsequently, open test procedure document, the test case that will extract from the test case data storehouse according to the note style writes this test procedure document with the note form, and the function framework of this test case correspondence is inserted each test case back.So just formed the source file of test procedure.After the test case that derives from test case all is written to corresponding test procedure document, constipation Shu Shengcheng test procedure framework.
Step 430 is with the source file output of test procedure framework.The tester can carry out programming and testing according to the test case in the test frame that generates like this.
To obtain method that external data generates the test procedure framework as embodiment two, referring to Fig. 6, the concrete steps that this embodiment generates the test procedure framework are as follows below:
Step 501 forms configuration file according to generating the test frame configuration item.
Step 502 adopts the perl wscript.exe to read this configuration file.Read process and shown in Figure 4 to read the configuration file process identical.
Step 511 imports module 110 by file and obtains existing text use-case, forms external data.
In this step, obtain satisfactory existing text use-case according to generating the test frame configuration.Should test case and project information thereof have been comprised in the existing text use-case.The qualification to the use-case content extracts test case and project information thereof from the existing text use-case that obtains in the test frame configuration according to generating, and forms external data.If to the qualification of use-case content, then the test case and the project information thereof of the existing text use-case of all that will obtain do not extract, form external data.Then this external data being imported generation test frame module 133 handles.That is, to this external data inquire about, increase, operation such as deletion or modification.At this moment, the existing text use-case that obtains can exist with file layouts such as XML, HTML, RTF or TXT.
Step 512 forms external file, i.e. test case file with the external data after the above-mentioned processing.This external file can exist with file layouts such as XML, HTML, RTF or TXT.Simultaneously, this external file can also directly import in the test case data storehouse 140 and manage.Present embodiment, external file exists with the XML form, and its form is identical with the form that forms the XML file according to the test case in test case data storehouse.
Step 520 according to the external file of configuration file and XML form, generates the test procedure framework, and writes source file.
Step 530 is exported source file.The tester can carry out programming and testing according to the test case in the test frame that generates like this.
After generating test frame module 133 generation test procedure frameworks, write source file, the tester could adopt this source file programming and test.Fig. 7 is the method flow diagram that test procedure framework of the present invention writes source file, and this method may further comprise the steps:
Step 600 is read in data.These data comprise, the configuration file content of obtaining according to generation test frame configuration item in the step 614, test case and the project information thereof obtained from the test case data storehouse in the step 615, perhaps step 616 is from having test case and the project information thereof that the text use-case obtains.
Step 601 according to the specified path and the entry name of Basic Configuration Items in the configuration file, is set up the engineering catalogue with entry name under this path.
Step 602 is set up the testing classification sub-directory according to testing classification under the engineering catalogue.This testing classification sub-directory is divided into functional test file, performance test file, pressure test file, compatibility test file etc. with test procedure document.
Step 603 is set up test procedure document according to test case under each testing classification sub-directory.The test I D of file this test case by name.
Step 604 is opened the testing classification sub-directory that step 602 is set up.
Step 605 is opened the test procedure document that step 603 is set up.
Step 606 is inserted test case with the note form in test procedure.In the present embodiment "/* @...@*/".
Function entrance is inserted, function body begins and the function body end mark in order in step 607～609.Wherein the form that begins of function body is as " Retumvalue functionname (parameter) ".
Step 610 judges whether the test case content that writes current test procedure document finishes.If do not finish, then return step 606 execution in step 606～610 once more, write a test case again; Otherwise execution in step 611 judges whether the test procedure document under this testing classification sub-directory travels through.If no, then execution in step 605～611, open another test procedure document under the current testing classification sub-directory, write test case and trial function framework; Otherwise execution in step 612, judge whether the testing classification sub-directory under this project catalogue travels through, if do not have, then execution in step 604～612, under current engineering catalogue, open another testing classification sub-directory, each test procedure document under this catalogue is write corresponding test case and test procedure framework; Otherwise execution in step 613, process ends.
In the present embodiment, owing to have only one from the test case data library inquiry to qualified test case, when generating the test procedure framework, under specified path ./G, set up engineering catalogue/G2000, under this project sub-directory, set up functional test classification sub-directory/Function, under this functional test sub-directory, set up the test procedure document of file F_A.c by name, the content of this test procedure, as follows:
/*@
Test I D F_A
Test purpose checking C can compile
Test description on screen, print Hello world
Hello world appears on the expected results screen
Test duration 2006.10.24
@*/
void?F_A(void)
{
}
As seen, when generating the test procedure framework, test procedure is corresponding one by one with test case.In use, the user only need insert program coding and get final product in the F_A function, helps testing the coding personnel and increases work efficiency.
By the above as can be seen, program test management system provided by the present invention can be extracted required form test case scheme according to user's needs from existing test procedure document, improve tester's work efficiency; Secondly, the user can also operate by GUI, and the test case in the test case data storehouse is managed.In addition, the present invention can generate the test procedure framework according to user's needs, the test procedure document of generation store classifiedly with different directories under, and test case is corresponding one by one with test procedure in the test procedure document, makes things convenient for the use of tester's coding.
In sum, more than be preferred embodiment of the present invention only, be not to be used to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (18)
1. a software testing management method is characterized in that, this method comprises:
A, generate configuration file, and obtain test procedure document according to this configuration file according to the extraction test case configuration item of input;
B, according to described configuration file from the test procedure document that obtains, obtain test case;
C, according to the input generation test frame configuration item, generate second configuration file;
D, according to described generation test frame configuration item, obtain and meet test case and the project information thereof that generates the requirement of test frame configuration item;
Test case and project information thereof that E, basis are obtained form test case file;
F, according to described second configuration file and described test case file, generate the test procedure framework.
2. method according to claim 1 is characterized in that, the method for obtaining described test case and project information thereof among the step D comprises:
D1, the test case that described step B is obtained import database;
The project information of D2, the described test case that will obtain according to described configuration file imports described database;
D3, according to described generation test frame configuration item, from described database, obtain and meet test case and the project information thereof that generates the requirement of test frame configuration item.
3. method according to claim 2 is characterized in that,
Steps A is described to be obtained test procedure document according to this configuration file and is: according to the file path to be extracted in the described configuration file, file type to be extracted and testing classification, obtain the test procedure document that meets described file type to be extracted and described testing classification from described file path to be extracted;
Steps A is described to be obtained after the test procedure document according to this configuration file, further comprises: the file path and the filename of the test procedure document that obtains are kept in the file set;
The described test case of obtaining of step B is: travel through all test procedure documents in the described file set, according to the sign of the note in the described configuration file, extract test case from described test procedure document.
4. method according to claim 3 is characterized in that, described testing classification represents that the test case in the described test procedure document is used for the test of which kind of type, this testing classification is performance test, or functional test, or pressure test, or compatibility test, or uniformity test.
5. method according to claim 2 is characterized in that described database comprises test case table and Project Information Table;
Among the described step D, the test case obtained and project information are imported database be: described test case is write described test case table, the project information of described test case is write described Project Information Table.
6. method according to claim 1 is characterized in that, the method for obtaining described test case and project information thereof among the step D comprises:
D1, obtain according to described generation test frame configuration item and to meet the existing text use-case that generates the requirement of test frame configuration item;
D2, according to described generation test frame configuration item, from described existing text use-case, obtain test case and project information thereof.
7. method according to claim 6 is characterized in that,
Describedly further comprise after obtaining test case and project information thereof: described test case is added, deleted or revises processing.
8. according to claim 2 or 6 described methods, it is characterized in that, described according to described second configuration file and described test case file, generate the test procedure framework and comprise:
According to specified path and the entry name in described second configuration file, under described specified path, set up the engineering catalogue with described entry name;
According to the testing classification in described second configuration file, under described engineering sub-directory, set up the testing classification sub-directory;
Under each testing classification sub-directory, set up test procedure document according to described test case file;
Insert test case and trial function framework according to described second configuration file and described test case file to the test procedure document of described foundation.
9. method according to claim 8 is characterized in that, inserts test case and the trial function framework comprises to the test procedure document of described foundation:
According to the sign of the note in described second configuration file, in the test procedure document of described foundation, insert test case with the note form;
According to function return value and the function parameter in described second configuration file, in described test procedure document, insert the do-nothing function corresponding with described test case.
10. method according to claim 2 is characterized in that, this method further comprises:
Management information according to input manages the test case in the described database.
11. a software testing management system is characterized in that, this system comprises:
Be used for generating configuration file, and obtain the module of test procedure document according to this configuration file according to the extraction test case configuration item of input; And
Be used for obtaining from the test procedure document that obtains the module of test case according to described configuration file;
This system further comprises the module that is used for generating according to the generation test frame configuration item of user's input second configuration file; Obtain test case and project information thereof according to described generation test frame configuration item, and form the module of test case file; And
Be used for module according to described second configuration file and described test case file generation test procedure framework.
12. system according to claim 11 is characterized in that, this system further comprises the database that is used to store test case.
13. system according to claim 12 is characterized in that, this system further comprises and is used for obtaining project information according to described configuration file, the module that the described test case obtained and described project information are imported to database.
14. system according to claim 13 is characterized in that, this system further comprises the management information that is used for according to user input, the module that the information in the described database is managed.
15. system according to claim 14 is characterized in that, this system further comprises and is used for the module that the test case that will obtain according to configuration file and existing text use-case and project information thereof import described database.
16. system according to claim 13 is characterized in that, describedly obtains test case and project information thereof according to generating the test frame configuration item, and the module that forms test case file is obtained test case and project information from database.
17. system according to claim 11 is characterized in that, describedly obtains test case and project information thereof according to generating the test frame configuration item, and the module that forms test case file is obtained test case and project information from existing text use-case.
18. system according to claim 13 is characterized in that, described database comprises test case table and Project Information Table;
Described test case table is used to store the described test case of obtaining from administration module;
Described Project Information Table is used to store the described project information of obtaining from administration module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610138061XA CN101174240B (en) | 2006-11-03 | 2006-11-03 | Software testing management method and system thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610138061XA CN101174240B (en) | 2006-11-03 | 2006-11-03 | Software testing management method and system thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101174240A CN101174240A (en) | 2008-05-07 |
| CN101174240B true CN101174240B (en) | 2011-04-06 |
Family
ID=39422762
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610138061XA Expired - Fee Related CN101174240B (en) | 2006-11-03 | 2006-11-03 | Software testing management method and system thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101174240B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103164312A (en) * | 2011-12-09 | 2013-06-19 | 阿里巴巴集团控股有限公司 | Method and system for preparing interface testing data |
Families Citing this family (43)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102855174B (en) * | 2011-06-28 | 2016-06-01 | 北京奇虎科技有限公司 | The target program progress control method that can automatically recover in automatic test and device |
| CN102981947B (en) * | 2011-09-07 | 2015-07-08 | 阿里巴巴集团控股有限公司 | Data preparation method in test and system provided with the same |
| CN102340687A (en) * | 2011-10-17 | 2012-02-01 | 四川长虹电器股份有限公司 | Set-top box testing system and method |
| CN102426520A (en) * | 2011-10-21 | 2012-04-25 | 浪潮电子信息产业股份有限公司 | Method for acquiring network equipment information of Linux system |
| CN103377101A (en) * | 2012-04-18 | 2013-10-30 | 百度在线网络技术（北京）有限公司 | Testing system and testing method |
| CN103699478A (en) * | 2012-09-27 | 2014-04-02 | 中国银联股份有限公司 | Test case generation system and test case generation method |
| CN103902439B (en) * | 2012-12-25 | 2016-08-24 | 北大方正集团有限公司 | The management method of a kind of test case, Apparatus and system |
| CN103079086A (en) * | 2012-12-30 | 2013-05-01 | 广东九联科技股份有限公司 | Automatic testing system for set-top box |
| CN104182333B (en) * | 2013-05-23 | 2018-03-09 | 阿里巴巴集团控股有限公司 | A kind of performance test methods and equipment |
| CN103336741A (en) * | 2013-06-28 | 2013-10-02 | 广东电网公司电力科学研究院 | Method and device for testing stability of operation system of power secondary system |
| CN103324572B (en) * | 2013-06-28 | 2016-12-28 | 广东电网公司电力科学研究院 | The operating system performance method of testing of electric power secondary system and device |
| CN103336740B (en) * | 2013-06-28 | 2016-12-28 | 广东电网公司电力科学研究院 | The operating system integrated test facility of electric power secondary system and device |
| CN103345444A (en) * | 2013-06-28 | 2013-10-09 | 中国南方电网有限责任公司 | Method and device for testing operating system function of power secondary system |
| CN103473045A (en) * | 2013-08-27 | 2013-12-25 | 广州华多网络科技有限公司 | Method and device for generating interface documents |
| CN103473175A (en) * | 2013-09-11 | 2013-12-25 | 江苏中科梦兰电子科技有限公司 | Extraction method for software testing case set |
| US20150082286A1 (en) * | 2013-09-18 | 2015-03-19 | Microsoft Corporation | Real-time code instrumentation |
| CN104731697A (en) * | 2013-12-19 | 2015-06-24 | 青岛海尔空调器有限总公司 | Running control method, control system and sound monitor of test case |
| CN104794049B (en) * | 2014-01-20 | 2019-05-24 | 腾讯科技（深圳）有限公司 | Applied program testing method and device |
| CN103823754A (en) * | 2014-02-11 | 2014-05-28 | 深圳市同洲电子股份有限公司 | Method and device for realizing automatic testing |
| CN104216830B (en) * | 2014-09-01 | 2017-05-10 | 广州供电局有限公司 | Method and system for detecting consistency of equipment software |
| CN105487966B (en) * | 2014-09-17 | 2023-07-25 | 深圳市雅阅科技有限公司 | Program testing method, device and system |
| CN104331295B (en) * | 2014-11-05 | 2018-06-26 | 北京中科辅龙信息技术有限公司 | Page generation method and system |
| CN104391796B (en) * | 2014-12-05 | 2018-01-02 | 上海斐讯数据通信技术有限公司 | A kind of test case analytic method |
| CN104461895B (en) * | 2014-12-17 | 2017-11-24 | 广东欧珀移动通信有限公司 | The edit methods and system and automatization test system of cycle tests |
| CN105487979A (en) * | 2015-12-02 | 2016-04-13 | 广州华多网络科技有限公司 | Test tool management method and user terminal |
| CN106656650B (en) * | 2016-10-08 | 2020-01-14 | 腾讯科技（深圳）有限公司 | Method and system for generating service test environment, and method, device and system for service test |
| CN108241576B (en) * | 2016-12-26 | 2021-07-20 | 航天信息股份有限公司 | Interface testing method and system |
| CN107766250A (en) * | 2017-11-02 | 2018-03-06 | 百度在线网络技术（北京）有限公司 | Method of testing, device, server and the storage medium of advertisement pattern |
| CN107908563A (en) * | 2017-11-23 | 2018-04-13 | 中国航空无线电电子研究所 | The test system of test flight task scheduling software human-computer interaction interface |
| CN108829590B (en) * | 2018-05-31 | 2021-11-16 | 网易（杭州）网络有限公司 | Software testing method, device and system |
| CN109101420A (en) * | 2018-07-20 | 2018-12-28 | 中国邮政储蓄银行股份有限公司 | Determine the method, apparatus and system, terminal of Test Strategy |
| CN109101431A (en) * | 2018-09-26 | 2018-12-28 | 深圳壹账通智能科技有限公司 | A kind of testing case management, computer readable storage medium and terminal device |
| CN109240933B (en) * | 2018-09-28 | 2022-07-26 | 四川虹微技术有限公司 | Data table operation result assertion method |
| CN109815123A (en) * | 2018-12-15 | 2019-05-28 | 中国平安人寿保险股份有限公司 | Interface testing case script classification method, device, electronic equipment and medium |
| CN109697167B (en) * | 2018-12-27 | 2022-03-25 | 江苏满运软件科技有限公司 | Method and system for managing test variables, electronic device and storage medium |
| CN109901999B (en) * | 2019-01-31 | 2021-01-29 | 国核自仪系统工程有限公司 | Simulation method and system of programmable logic based on UVM |
| CN110377566B (en) * | 2019-06-29 | 2022-02-18 | 苏州浪潮智能科技有限公司 | Method and system for sorting S parameter test files of PCB |
| CN110380939B (en) * | 2019-08-08 | 2022-03-29 | 重庆邮电大学 | Consistency test method and system for local communication protocol in electricity consumption information acquisition system |
| CN110445690A (en) * | 2019-08-16 | 2019-11-12 | 北京智芯微电子科技有限公司 | The design method of electric power wireless public network communication unit interchangeability test software |
| CN112445694A (en) * | 2019-08-29 | 2021-03-05 | 杭州广立微电子股份有限公司 | Tool for formulating test configuration file and application thereof |
| CN112416746A (en) * | 2020-01-21 | 2021-02-26 | 上海哔哩哔哩科技有限公司 | Test case generation method, device, equipment and medium |
| CN114116453B (en) * | 2021-10-31 | 2024-01-09 | 苏州浪潮智能科技有限公司 | Method, device, equipment and readable medium for testing case association configuration information |
| CN116820811B (en) * | 2023-08-29 | 2023-11-28 | 杭州实在智能科技有限公司 | RPA component variable rapid deriving and assigning method and system based on shear plate |
-
2006
- 2006-11-03 CN CN200610138061XA patent/CN101174240B/en not_active Expired - Fee Related
Non-Patent Citations (2)
| Title |
|---|
| 尚冬娟.软件测试中的测试用例及复用研究.《计算机技术与发展》.2006,第16卷(第1期),71,72. * |
| 尚冬娟.软件测试中的测试用例及复用研究.<<计算机技术与发展>>.2006,第16卷(第1期),71,72. |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103164312A (en) * | 2011-12-09 | 2013-06-19 | 阿里巴巴集团控股有限公司 | Method and system for preparing interface testing data |
| CN103164312B (en) * | 2011-12-09 | 2015-07-01 | 阿里巴巴集团控股有限公司 | Method and system for preparing interface testing data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101174240A (en) | 2008-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101174240B (en) | Software testing management method and system thereof | |
| US6651240B1 (en) | Object-oriented software development support apparatus and development support method | |
| CA2289347C (en) | Method and apparatus for round-trip software engineering | |
| US5301318A (en) | Hierarchical netlist extraction tool | |
| Küster et al. | Detecting and resolving process model differences in the absence of a change log | |
| CN104881275B (en) | A kind of electronic report forms generation method and device | |
| US8826225B2 (en) | Model transformation unit | |
| US20020059327A1 (en) | Method and apparatus for generating web pages from templates | |
| US20060015839A1 (en) | Development of software systems | |
| JP2002024211A (en) | Method and system for document management and storage medium having processing program stored thereon | |
| US7831614B2 (en) | System and method for generating SQL using templates | |
| CN101866315B (en) | Test method and system of software development tool | |
| CN101641678B (en) | Source program review program, source program review method and source program review device | |
| CN101499063A (en) | Tracing-based database schema evolution method and system | |
| CN106991100A (en) | Data lead-in method and device | |
| JP2007534036A (en) | Field development of XML schema in database | |
| EP1586014A2 (en) | Contextual data representation and retrieval method | |
| CN115756634A (en) | Database object relational mapping model establishing method, device, equipment and medium | |
| US20050183097A1 (en) | Schema-based machine generated programming models | |
| US8001503B2 (en) | Method and system for automatically accessing internal signals or ports in a design hierarchy | |
| Mou et al. | Visual orchestration and autonomous execution of distributed and heterogeneous computational biology pipelines | |
| Falkenstine et al. | Natural Language Processing for Autonomous Identification of Impactful Changes to Specification Documents | |
| JPH1027178A (en) | Document data base managing device | |
| Körtgen | New Strategies to Resolve Inconsistencies between Models of Decoupled Tools. | |
| CN116303759A (en) | Entity object information synchronization method, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: BEIJING SUNPLUS EHUE TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: BEIJING BEIYANG ELECTRONIC TECHNOLOGY CO., LTD. Effective date: 20140303 |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20140303 Address after: Science and Industry Park, Taiwan, Hsinchu, China, No. 19-1 Patentee after: Lingyang Science and Technology Co., Ltd. Patentee after: BEIJING SUNPLUS-EHUE TECHNOLOGY CO., LTD. Address before: Science and Industry Park, Taiwan, Hsinchu, China, No. 19 Patentee before: Lingyang Science and Technology Co., Ltd. Patentee before: Beijing Beiyang Electronic Technology Co., Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110406 Termination date: 20161103 |