CN101739340A - Method and device for verifying script file - Google Patents
Method and device for verifying script file Download PDFInfo
- Publication number
- CN101739340A CN101739340A CN200910260918A CN200910260918A CN101739340A CN 101739340 A CN101739340 A CN 101739340A CN 200910260918 A CN200910260918 A CN 200910260918A CN 200910260918 A CN200910260918 A CN 200910260918A CN 101739340 A CN101739340 A CN 101739340A
- Authority
- CN
- China
- Prior art keywords
- script file
- execution result
- version
- database
- wrong
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a method and a device for verifying a script file. The method comprises the following steps: acquiring edition modification information of a script file in a database to be verified from an edition management tool, and executing the script file of the database to be verified to acquire execution result information of an error script file, wherein the edition modification information at least comprises a modifier account number and a script file path, and the execution result information at least comprises the script file path and an execution result; and matching the edition modification information with the execution result information of the error script file to acquire the modifier account number of the error script file to ensure that a developer denoted by the modifier account number of the error script file modifies the corresponding error script file. The method and the device can improve the working efficiency of the whole verification process when the script file is verified.
Description
Technical field
The present invention relates to database technical field, particularly relate to a kind of verification method and device of script file.
Background technology
In the performance history of Database applications software, need work in coordination with the whole project of finishing by a plurality of developers usually.Wherein, after each developer finishes separately task, submit script file to database respectively.After all script files with a project deposit database in, also need to verify.Wherein, proof procedure is exactly with the actual execution of all script files once, in case there is a script file of carrying out failure, all script files in this database are checking not to be passed through.
In the prior art, if the script file empirical tests in database is obstructed out-of-date, follow-up just need by hand all script files in this database be opened one by one by the dependence test personnel after, find the wrong script file of carrying out failure in the database according to error message, and then whom the developer who removes to search this mistake script file is, so that wrong script file is made amendment by corresponding developer, verify again afterwards, till the script file checking in this database is passed through.For example, a development project is after developer's exploitation, have 100 script files and deposit database in, when the script file empirical tests of this database is not passed through, after need 100 script files all being opened by hand by the dependence test personnel, a file, a file ground contrast are checked, find the script file of carrying out failure in the database according to error message, and then go to search one by one whom all developers that carry out the wrong script file of failure are, wrong script file is returned to corresponding developer place make amendment.The mode of searching to this manual formula the developer of wrong script file and wrong file is carried out and will certainly be expended a large amount of time and efforts of tester, and then make that also checking can not handled fast and effectively by the database script file, especially when the script file number of preserving in the database is huge, expend a large amount of time and efforts of tester more, finally cause the work efficiency of whole verification process low.
Summary of the invention
In order to solve the problems of the technologies described above, the embodiment of the invention provides a kind of verification method and device of script file, to improve when script file is verified the work efficiency of whole verification process.
The embodiment of the invention discloses following technical scheme:
A kind of verification method of script file, comprise: the version modify information of from the version management instrument, obtaining the script file in the database to be verified, and carry out script file in the described database to be verified, obtain the execution result information of wrong script file, described version modify information comprises at least revises people's number of the account and script file path, and described execution result information comprises script file path and execution result at least; The execution result information of described version modify information and described wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.
Preferably, the described version modify information of obtaining script file in the database to be verified from the version management instrument comprises: download the script file in the database to be verified from described version management instrument; According to the journal format in the described version management instrument, resolve the journal file that when downloading script file, is produced, obtain described version modify information.
Preferably, described version management instrument comprises: the CVS of parallel version system, VSS or version control system SVN.
Preferably, the script file in the described execution database to be verified, the execution result information that obtains wrong script file comprises: call third party's instrument and carry out script file in the described database to be verified; According to the journal format in described third party's instrument, resolve the journal file that when carrying out script file, is produced, obtain described execution result information.
Preferably, described third party's instrument comprises: the interconnected JDBC of Java database, the interconnected ODBC of open database or Active X data object ADO.
Preferably, described execution result information with version modify information and wrong script file is mated, and the modification people number of the account that obtains wrong script file comprises: search the identical version modify information in script file path in the execution result information of script file path and described wrong script file; From finding to such an extent that read the version modify information and revise people's number of the account, obtain the modification people number of the account of described wrong script file.
A kind of demo plant of script file, comprise: authentication unit, be used for obtaining the version modify information of the script file the database to be verified from the version management instrument, and carry out script file in the described database to be verified, obtain the execution result information of wrong script file, described version modify information comprises at least revises people's number of the account and script file path, and described execution result information comprises script file path and execution result at least; Matching unit, be used for the execution result information of described version modify information and described wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.
Preferably, described authentication unit comprises: acquiring unit, be used for obtaining the version modify information of the script file the database to be verified from the version management instrument, and described version modify information comprises at least revises people's number of the account and script file path; Performance element is used for carrying out the script file of described database to be verified, obtains the execution result information of wrong script file, and described execution result information comprises script file path and execution result at least.
Preferably, described acquiring unit comprises: download subelement, be used for the script file from described version management instrument download database to be verified; First resolves subelement, is used for the journal format according to described version management instrument, resolves the journal file that is produced when downloading script file, obtains described version modify information.
Preferably, described performance element comprises: call subelement, be used for calling the script file that third party's instrument is carried out described database to be verified; Second resolves subelement, is used for the journal format according to described third party's instrument, resolves the journal file that is produced when carrying out script file, obtains described execution result information.
Preferably, described matching unit comprises: search the unit, be used for searching the script file path version modify information identical with the script file path of the execution result information of described wrong script file; Reading unit is used for obtaining the modification people number of the account of described wrong script file from finding to such an extent that version modify information reads modification people number of the account.
As can be seen from the above-described embodiment, in the proof procedure of script file, obtain the version modify information that comprises the script file path and revise people's number of the account respectively, and the execution result information that includes the wrong script file of script file path and execution result, with the script file path as Correlation Criteria to the execution result information of version modify information and wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.Whole process all is to finish automatically in proof procedure, does not need manual intervention, and then has improved when script file is verified the work efficiency of whole verification process.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art below, apparently, accompanying drawing in describing below only is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the process flow diagram of an embodiment of the verification method of a kind of script file of the present invention;
Fig. 2 is the process flow diagram of another embodiment of the verification method of a kind of script file of the present invention;
Fig. 3 is the structural drawing of an embodiment of the demo plant of a kind of script file among the present invention.
Embodiment
For above-mentioned purpose of the present invention, feature and advantage can be become apparent more, the embodiment of the invention is described in detail below in conjunction with accompanying drawing.
Embodiment one
See also Fig. 1, it is the process flow diagram of an embodiment of the verification method of a kind of script file of the present invention, and this method may further comprise the steps:
Step 101: the version modify information of from the version management instrument, obtaining the script file in the database to be verified, and carry out script file in the described database to be verified, obtain the execution result information of wrong script file, described version modify information comprises at least revises people's number of the account and script file path, and described execution result information comprises script file path and execution result at least;
Wherein, the described version modify information of obtaining script file in the database to be verified from the version management instrument comprises: download the script file in the database to be verified from described version management instrument; According to the journal format in the described version management instrument, resolve the journal file that when downloading script file, is produced, obtain described version modify information.Described version management instrument comprises: CVS of parallel version system or version control system SVN.
For example, script file in the whole project all is maintained in the database usually, and adopt the version management instrument to manage, described version management instrument comprises CVS of parallel version system or version control system SVN, present embodiment during to the Manage Scripts file employed version management instrument do not limit.Usually, in a version management instrument, manage the script file that a plurality of databases are arranged.When the script file in one of them database is verified, from the version management instrument, download all script files in the database to be verified, when the script file in the download database to be verified, each script file all can produce a journal file, according to the journal format in the version management instrument, from the journal file of each script file, parse the modification people number of the account and the script file path of this script file respectively, that is, from journal file, obtain the version modify information of this script file.In the present embodiment, described version modify information comprises modification people's number of the account and script file path at least.
When adopting dissimilar version management instruments, the journal format of the journal file that is produced is different, but for a concrete version management instrument, the journal format of the journal file that it produces is changeless, as long as selected concrete version management instrument, the corresponding journal format of version management instrument that just can obtain and select is resolved journal file according to this journal format then.And the analysis result of journal file is except the script file path and modification people account number that include script file, also has some other information, as, is that example describes with SVN for the version management instrument, the script file path of certain script file on SVN is: http://svn.collab.net/repos/svn/trunk/build/install-sh, and the recorded segment of a journal file is as follows:
r37765|arfrever|2009-05-18?07:39:46CST
*build/install-sh：Update?with?version?from?GNU?Automake?1.11.
In the above in this section journal file recorded piece, " r37765 " field of first row is an amended Item version number; " arfrever " field of first row is revised people's account number exactly, when the developer wants script file in the revision management tool, could revise script file after must logging on the version management instrument with an account number earlier, the number of the account of this version management instrument is revises people's number of the account; " 2009-05-18 07:39:46CST " field of first row is the timestamp of revising; " * build/install-sh:Update with version from GNU Automake 1.11. " field of second row is to revise the illustrative annotation information that the people submits to, and what expression this time revised or why revised.
Need to prove that for our script file proof procedure, version modify information will include script file path and modification people number of the account in the journal file at least.
Wherein, the script file in the described execution database to be verified, the execution result information that obtains wrong script file comprises: call third party's instrument and carry out script file in the described database to be verified; According to the journal format in described third party's instrument, resolve the journal file that when carrying out script file, is produced, obtain described execution result information.Described third party's instrument comprises: the interconnected JDBC of Java database, the interconnected ODBC of open database or Active X data object ADO.
For example, behind the script file that from the version management instrument, obtains in the database to be verified, call third party's instrument and carry out script file in the database to be verified, during script file in carrying out database to be verified, each script file all can produce a journal file.In the above-mentioned script file that executes, include the correct script file that runs succeeded, the wrong script file of the failure carried out is also arranged.Can filter out the wrong script file of carrying out failure earlier, again according to the journal format in third party's instrument, from the journal file of each wrong script file, parse the script file path and the execution result of this mistake script file respectively, promptly obtained the execution result information of wrong script file.In the present embodiment, the execution result information of described wrong script file comprises script file path and execution result at least.
When adopting dissimilar third party's instruments, the journal format of the journal file that is produced is different, but for concrete third party's instrument, the journal format of the journal file that it produces is changeless, as long as selected concrete third party's instrument, the corresponding journal format of third party's instrument that just can obtain and select removes to resolve journal file according to this journal format then.The journal file that third party's instrument is produced when carrying out script file is handled and is included outside script file path and the execution result, also comprises some information that database returns in the implementation, as the out of Memory in database positioning and the implementation etc.A kind of general log file formats of ratio is as follows:
[timestamp] [carrying out the path of script file] [failure runs succeeded/carries out]
[details that produce in the implementation ... ... .]
Above-mentioned form is exactly a more common log file formats, certainly, and when the third party's instrument that adopts other is that other log file formats is also arranged.
Need to prove that for our script file proof procedure, execution result information will include script file path and execution result in the journal file at least.
Also need to prove, present embodiment does not limit the version modify information of obtaining the script file in the database to be verified from the version management instrument and the script file of carrying out in the described database to be verified, obtain the execution sequence of the execution result information of wrong script file, also can carry out simultaneously.
Step 102: the execution result information of described version modify information and described wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.
Wherein, described execution result information with version modify information and wrong script file is mated, and the modification people number of the account that obtains wrong script file comprises: search the identical version modify information in script file path in the execution result information of script file path and described wrong script file; From finding to such an extent that read the version modify information and revise people's number of the account, obtain the modification people number of the account of described wrong script file.
For example, with the script file path in the execution result information of version modify information and wrong script file as a Correlation Criteria, as have 10 script files, respectively corresponding 10 version modify information, after above-mentioned steps 101 execution, there are 3 script files to carry out failure, the execution result information of respectively corresponding 3 wrong script files.In the execution result information of version modify information and wrong script file, all include the script file path, by the script file path in the execution result information of script file path in the version modify information and wrong script file is mated, obtain the version modify information of 3 wrong script files, and from the version modify information of 3 wrong script files, read modification people number of the account D1, D2 and the D3 of wrong script file respectively.So that the follow-up developer that can obtain being correlated with according to the modification people number of the account of wrong script file is made amendment to the corresponding error script file by the indicated developer of the modification people number of the account of wrong script file at last.
As can be seen from the above-described embodiment, in the proof procedure of script file, obtain the version modify information that comprises the script file path and revise people's number of the account respectively, and the execution result information that includes the wrong script file of script file path and execution result, with the script file path as Correlation Criteria to the execution result information of version modify information and wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.Whole process all is to finish automatically in proof procedure, does not need manual intervention, and then has improved when script file is verified the work efficiency of whole verification process.
Embodiment two
Be example with a concrete application scenarios below, describe the proof procedure of script file in detail.See also Fig. 2, it in the present embodiment, selects for use SVN as the version management instrument for the process flow diagram of another embodiment of the verification method of a kind of script file of the present invention, selects for use JDBC as third party's instrument.And, the proof procedure of script file for convenience of description, in the present embodiment, script file number in the project is reduced to 10, these 10 script files are maintained in the database, and manage by SVN, this database is as a database to be verified, and then the process that the script file in this database to be verified is verified may further comprise the steps:
Step 201: from version management instrument SVN, read 10 script files in the database to be verified respectively, obtain the journal file that produces when 10 script files are downloaded simultaneously;
Wherein, download 10 script files from SVN,, produced the journal file of 10 script files respectively when SVN downloads script file, do not have only the script file path of 10 script files in this journal file and revise people's account number, also have out of Memory.
For example, the recorded segment of a journal file is as follows:
r37765|arfrever|2009-05-18?07:39:46CST
*build/install-sh：Update?with?version?from?GNU?Automake?1.11.
In the above in this section journal file recorded piece, " r37765 " field of first row is an amended Item version number; " arfrever " field of first row is revised people's account number exactly, when the developer wants script file in the revision management tool, could revise script file after must logging on the version management instrument with an account number earlier, the number of the account of this version management instrument is revises people's number of the account; " 2009-05-18 07:39:46CST " field of first row is the timestamp of revising; " * build/install-sh:Update with version from GNU Automake 1.11. " field of second row is to revise the illustrative annotation information that the people submits to, and what expression this time revised or why revised.
Step 202: resolve the journal file of 10 script files, resolve from journal file and obtain the script file path and revise people's number of the account, and analysis result is kept in the version modify record in the database;
Wherein, in the present embodiment, SVN is as the version management instrument in utilization, according to the form of SVN journal file, the journal file of SVN is resolved.When other version management instrument of employing, to decide when the version management instrument, the form of the journal file that is adopted is also just decided.Can extract the script file path and revise people's number of the account from analysis result, and be recorded in the version modify record, this record comprises two row: the script file path, revise people's number of the account, respectively to having carried out record with 10 script files.
Step 203: call third party's instrument JDBC and carry out 10 script files, obtain the journal file that produces when the wrong script file of carrying out failure is carried out simultaneously;
Wherein, when carrying out 10 script files, execution result can be recorded in the journal file by JDBC.In the middle of include the journal file of the correct script file that runs succeeded, also include the journal file of the wrong script file of carrying out failure.From all journal files, obtain the journal file of the wrong script file of carrying out failure.As, in 10 script files, there are 3 script files to carry out failure, then obtain the journal file of these 3 wrong script files.
Step 204: resolve the journal file of 3 wrong script files, from journal file, resolve file path and the execution result that obtains wrong script file, and analysis result is kept in the execution result record of the wrong script file in the database;
Wherein, in the present embodiment, JDBC is as third party's instrument in utilization, according to the form of JDBC journal file, the journal file of JDBC is resolved.When adopting third party's instrument of other versions, to decide when third party's instrument, the form of the journal file that is adopted is also just decided.Analysis result not only comprises script file path and the result who whether runs succeeded, and also comprises some information that database returns in the implementation, as database positioning, and the information in the implementation.Can extract script file path and execution result from analysis result, and be recorded in the execution result record, this record comprises two row: the script file path, execution result has carried out record to 3 wrong script files respectively.
Step 205: fit version amendment record and execution result record from database, take out qualified version modify record;
Wherein, with the script file path as matching condition, in the execution result record of version modify record and wrong script file, all include the script file path, by the script file path in the execution result record of script file path in the version modify record and wrong script file is mated, obtain the version modify record of 3 wrong script files, and therefrom obtain the modification people number of the account with wrong script file.
Step 206: the checking report made in qualified version modify record;
Wherein, make the checking report, certainly, in the checking report, can also comprise other additional information, be exemplified below according to modification people number of the account in the version modify record and script file path:
| The script name of makeing mistakes | Repeat | Database | Type | Svn revises people's account number at last | Chinese Name |
| ??.\sql\base\vc\createindex.sql | ??first | ??sqlserver2000 | ??create | ?fengrenfei | Feng Renfei |
| ??.\sql\base\vc\createindex.sql | ??first | ??sqlserver2005 | ??create | ?fengrenfei | Feng Renfei |
See this checking like this, everybody has problem with regard to very clearly knowing whose script, and who needs is revised.Wherein, the make mistakes modification people Chinese name of script file also can obtain by matching process.Promptly, submitter's number of the account and submitter's Chinese Name of 10 script files are kept at before checking in the user record, deposit in the database, after acquisition makes mistakes script file version modify record, modification people number of the account in the version modify record and the submitter's number of the account in the user record are mated, obtain with the Chinese name of pairing modifications of wrong script file people in.
Step 207: report content is organized with the Table label of HTML, reported that verifying the file that is concatenated into a HTML structure sends then.
Wherein, except the form of mail, also can report content be announced with the form of note or BBS webpage.
As can be seen from the above-described embodiment, in the proof procedure of script file, obtain the version modify information that comprises the script file path and revise people's number of the account respectively, and the execution result information that includes the wrong script file of script file path and execution result, with the script file path as Correlation Criteria to the execution result information of version modify information and wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.Whole process all is to finish automatically in proof procedure, does not need manual intervention, and then has improved when script file is verified the work efficiency of whole verification process.
Embodiment three
Corresponding with the verification method of above-mentioned a kind of script file, the embodiment of the invention also provides a kind of demo plant of script file.See also Fig. 3, it is the structural drawing of an embodiment of the demo plant of a kind of script file of the present invention, and this device comprises authentication unit 301 and matching unit 302.Principle of work below in conjunction with this device is further introduced its inner structure and annexation.
Wherein, authentication unit comprises: acquiring unit 3011 and performance element 3012,
Acquiring unit 3011 is used for obtaining from the version management instrument version modify information of the script file the database to be verified, and described version modify information comprises at least revises people's number of the account and script file path;
Performance element 3012 is used for carrying out the script file of described database to be verified, obtains the execution result information of wrong script file, and described execution result information comprises script file path and execution result at least.
Above-mentioned acquiring unit 3011 comprises: download subelement, be used for the script file from described version management instrument download database to be verified; First resolves subelement, is used for the journal format according to described version management instrument, resolves the journal file that is produced when downloading script file, obtains described version modify information.
Above-mentioned performance element 3012 comprises: call subelement, be used for calling the script file that third party's instrument is carried out described database to be verified; Second resolves subelement, is used for the journal format according to described third party's instrument, resolves the journal file that is produced when carrying out script file, obtains described execution result information.
Wherein, matching unit 302 comprises: search unit 3021 and reading unit 3022;
Search unit 3021, be used for searching the script file path version modify information identical with the script file path of the execution result information of described wrong script file;
Reading unit 3022 is used for obtaining the modification people number of the account of described wrong script file from finding to such an extent that version modify information reads modification people number of the account.
As can be seen from the above-described embodiment, in the proof procedure of script file, obtain the version modify information that comprises the script file path and revise people's number of the account respectively, and the execution result information that includes the wrong script file of script file path and execution result, with the script file path as Correlation Criteria to the execution result information of version modify information and wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.Whole process all is to finish automatically in proof procedure, does not need manual intervention, and then has improved when script file is verified the work efficiency of whole verification process.
Need to prove, one of ordinary skill in the art will appreciate that all or part of flow process that realizes in the foregoing description method, be to instruct relevant hardware to finish by computer program, described program can be stored in the computer read/write memory medium, this program can comprise the flow process as the embodiment of above-mentioned each side method when carrying out.Wherein, described storage medium can be magnetic disc, CD, read-only storage memory body (Read-Only Memory, ROM) or at random store memory body (Random AccessMemory, RAM) etc.
More than the verification method and the device of a kind of script file provided by the present invention is described in detail, used specific embodiment herein principle of the present invention and embodiment are set forth, the explanation of above embodiment just is used for helping to understand method of the present invention and core concept thereof; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, the part that all can change in specific embodiments and applications, in sum, this description should not be construed as limitation of the present invention.
Claims (11)
1. the verification method of a script file is characterized in that, comprising:
From the version management instrument, obtain the version modify information of the script file in the database to be verified, and carry out script file in the described database to be verified, obtain the execution result information of wrong script file, described version modify information comprises at least revises people's number of the account and script file path, and described execution result information comprises script file path and execution result at least;
The execution result information of described version modify information and described wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.
2. method according to claim 1 is characterized in that, the described version modify information of obtaining script file in the database to be verified from the version management instrument comprises:
From described version management instrument, download the script file in the database to be verified;
According to the journal format in the described version management instrument, resolve the journal file that when downloading script file, is produced, obtain described version modify information.
3. method according to claim 1 is characterized in that, described version management instrument comprises: the CVS of parallel version system, VSS or version control system SVN.
4. method according to claim 1 is characterized in that, the script file in the described execution database to be verified, and the execution result information that obtains wrong script file comprises:
Call third party's instrument and carry out script file in the described database to be verified;
According to the journal format in described third party's instrument, resolve the journal file that when carrying out script file, is produced, obtain described execution result information.
5. method according to claim 1 is characterized in that, described third party's instrument comprises: the interconnected JDBC of Java database, the interconnected ODBC of open database or Active X data object ADO.
6. method according to claim 1 is characterized in that, described execution result information with version modify information and wrong script file is mated, and the modification people number of the account that obtains wrong script file comprises:
Search the identical version modify information in script file path in the execution result information of script file path and described wrong script file;
From finding to such an extent that read the version modify information and revise people's number of the account, obtain the modification people number of the account of described wrong script file.
7. the demo plant of a script file is characterized in that, comprising:
Authentication unit, be used for obtaining the version modify information of the script file the database to be verified from the version management instrument, and carry out script file in the described database to be verified, obtain the execution result information of wrong script file, described version modify information comprises at least revises people's number of the account and script file path, and described execution result information comprises script file path and execution result at least;
Matching unit, be used for the execution result information of described version modify information and described wrong script file is mated, obtain the modification people number of the account of wrong script file, so that the corresponding error script file is made amendment by the indicated developer of the modification people number of the account of described wrong script file.
8. device according to claim 7 is characterized in that, described authentication unit comprises:
Acquiring unit is used for obtaining from the version management instrument version modify information of the script file the database to be verified, and described version modify information comprises at least revises people's number of the account and script file path;
Performance element is used for carrying out the script file of described database to be verified, obtains the execution result information of wrong script file, and described execution result information comprises script file path and execution result at least.
9. device according to claim 8 is characterized in that, described acquiring unit comprises:
Download subelement, be used for the script file from described version management instrument download database to be verified;
First resolves subelement, is used for the journal format according to described version management instrument, resolves the journal file that is produced when downloading script file, obtains described version modify information.
10. device according to claim 8 is characterized in that, described performance element comprises:
Call subelement, be used for calling the script file that third party's instrument is carried out described database to be verified;
Second resolves subelement, is used for the journal format according to described third party's instrument, resolves the journal file that is produced when carrying out script file, obtains described execution result information.
11. device according to claim 7 is characterized in that, described matching unit comprises:
Search the unit, be used for searching the script file path version modify information identical with the script file path of the execution result information of described wrong script file;
Reading unit is used for obtaining the modification people number of the account of described wrong script file from finding to such an extent that version modify information reads modification people number of the account.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102609189A CN101739340B (en) | 2009-12-17 | 2009-12-17 | Method and device for verifying script file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102609189A CN101739340B (en) | 2009-12-17 | 2009-12-17 | Method and device for verifying script file |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101739340A true CN101739340A (en) | 2010-06-16 |
| CN101739340B CN101739340B (en) | 2012-06-06 |
Family
ID=42462854
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009102609189A Active CN101739340B (en) | 2009-12-17 | 2009-12-17 | Method and device for verifying script file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101739340B (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262555A (en) * | 2011-08-22 | 2011-11-30 | 迈普通信技术股份有限公司 | Method and device for loading different versions of JAVA three-party library |
| CN103885875A (en) * | 2012-12-21 | 2014-06-25 | 中国银联股份有限公司 | Device and method for verifying scripts |
| CN105488170A (en) * | 2015-11-30 | 2016-04-13 | 金蝶软件（中国）有限公司 | Information management method and apparatus for ERP system |
| CN109271199A (en) * | 2018-09-11 | 2019-01-25 | 航天信息软件技术有限公司 | A kind of method and system for database continuous integrating and script file management |
| CN109753289A (en) * | 2019-01-14 | 2019-05-14 | 网易（杭州）网络有限公司 | A kind of fine arts resource merging method, device, electronic equipment and storage medium |
| CN110471665A (en) * | 2019-06-28 | 2019-11-19 | 平安科技（深圳）有限公司 | Script file method of calibration, device, server and storage medium |
| WO2022222437A1 (en) * | 2021-04-23 | 2022-10-27 | 统信软件技术有限公司 | Script verification method, script signing method, and computing device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20070104202A (en) * | 2006-04-21 | 2007-10-25 | 골드피처 주식회사 | Automation test service system for view software of portable telephone and method thereof |
| CN101110020B (en) * | 2006-07-21 | 2011-01-26 | 国际商业机器公司 | Method and system for maintaining originality-related information about elements in an editable object |
-
2009
- 2009-12-17 CN CN2009102609189A patent/CN101739340B/en active Active
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262555A (en) * | 2011-08-22 | 2011-11-30 | 迈普通信技术股份有限公司 | Method and device for loading different versions of JAVA three-party library |
| CN102262555B (en) * | 2011-08-22 | 2013-11-20 | 迈普通信技术股份有限公司 | Method and device for loading different versions of JAVA three-party library |
| CN103885875A (en) * | 2012-12-21 | 2014-06-25 | 中国银联股份有限公司 | Device and method for verifying scripts |
| CN105488170A (en) * | 2015-11-30 | 2016-04-13 | 金蝶软件（中国）有限公司 | Information management method and apparatus for ERP system |
| CN105488170B (en) * | 2015-11-30 | 2019-02-12 | 金蝶软件（中国）有限公司 | A kind of approaches to IM and device of ERP system |
| CN109271199A (en) * | 2018-09-11 | 2019-01-25 | 航天信息软件技术有限公司 | A kind of method and system for database continuous integrating and script file management |
| CN109753289A (en) * | 2019-01-14 | 2019-05-14 | 网易（杭州）网络有限公司 | A kind of fine arts resource merging method, device, electronic equipment and storage medium |
| CN110471665A (en) * | 2019-06-28 | 2019-11-19 | 平安科技（深圳）有限公司 | Script file method of calibration, device, server and storage medium |
| WO2020258674A1 (en) * | 2019-06-28 | 2020-12-30 | 平安科技（深圳）有限公司 | Script file verification method and apparatus, server and storage medium |
| WO2022222437A1 (en) * | 2021-04-23 | 2022-10-27 | 统信软件技术有限公司 | Script verification method, script signing method, and computing device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101739340B (en) | 2012-06-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11023367B1 (en) | Systems and methods for testing a software application | |
| CN101739340B (en) | Method and device for verifying script file | |
| KR101989802B1 (en) | Method for performing test using test case and apparatus for the same | |
| CA2744881C (en) | Mapping instances of a dataset within a data management system | |
| EP2737406B1 (en) | A system and method for identifying fault prone computer code files | |
| US8150674B2 (en) | Automated testing platform for event driven systems | |
| US8386419B2 (en) | Data extraction and testing method and system | |
| US8782609B2 (en) | Test failure bucketing | |
| CN107665171A (en) | Automatic regression test method and device | |
| CN103970659B (en) | Android application software automation testing method based on pile pitching technology | |
| CN106909510A (en) | A kind of method and server for obtaining test case | |
| CN103248524B (en) | Based on test data edition control method, the Apparatus and system of flexible test technology | |
| CN105138461A (en) | Interface testing method and device for application program | |
| Nagy et al. | Where was this SQL query executed? a static concept location approach | |
| US20070100783A1 (en) | Method, system, and program for determining discrepancies between database management systems | |
| EP3547143B1 (en) | System and method for model-based and behaviour-driven testing | |
| CN115203300B (en) | Data verification method and device | |
| US11100131B2 (en) | Simulation of a synchronization of records | |
| CN114238143A (en) | ES data number making method, system and storage medium for interface test | |
| CN113504904A (en) | User-defined function implementation method and device, computer equipment and storage medium | |
| Huang et al. | Generating REST API Specifications through Static Analysis | |
| CN111611209A (en) | Method and system for storing virtual test data in task-divided manner | |
| Aalmink et al. | Enterprise tomography: An efficient approach for Semi-Automatic localization of integration concepts in VLBAs | |
| CN109446091B (en) | Business entity object testing method and device | |
| Wittler | Derivation of Change Sequences from State-Based File Differences for Delta-Based Model Consistency |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210312 Address after: 266000 201a, 2nd floor, international ocean Sensor Research Institute, Qingdao Blue Valley technology road, aoshanwei street, Jimo District, Qingdao City, Shandong Province Patentee after: Qingdao Kingdee Software Technology Co.,Ltd. Address before: 518057 High-tech Industrial Village W1-B4, Shennan Avenue, Nanshan District, Shenzhen City, Guangdong Province Patentee before: Kingdee software (China) Co.,Ltd. |
|
| TR01 | Transfer of patent right |