CN103761188A - Automated testing method for electronic file management system - Google Patents
Automated testing method for electronic file management system Download PDFInfo
- Publication number
- CN103761188A CN103761188A CN201410045487.5A CN201410045487A CN103761188A CN 103761188 A CN103761188 A CN 103761188A CN 201410045487 A CN201410045487 A CN 201410045487A CN 103761188 A CN103761188 A CN 103761188A
- Authority
- CN
- China
- Prior art keywords
- management system
- variable
- daily record
- file
- defect
- 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
- Debugging And Monitoring (AREA)
Abstract
The invention relates to an automated testing method for an electronic file management system. The automated testing method comprises the steps that (1) a comparison table of flaw codes, flaw types and flaw information is defined; (2) modeling is conducted on the electronic file management system and the testing activities of the electronic file management system on a data layer, so that a test data model is generated; (3) relevant regulations in functional requirements of the electronic file management system are described into a plurality of judgment conditions, and all the judgment conditions are stored in a rule base; (4) a model mapping and matching method is adopted, and dynamic correlation is established between a test data set and a target data set; (5) all test data stored in the electronic file management system are traversed, and the corresponding judgment conditions are called to test the test data set, so that flaws are found; (6) the test data to be tested in the electronic file management system are modified, and whether the possibility of a failure and the ability to protect the test data to be tested exist is judged; (7) updating maintenance of electronic files and testing of the electronic file management system are conducted simultaneously, and whether the updating maintenance operation of the electronic files meets requirements on the data layer is judged; (8) the flaws of the test data in the electronic file management system are collected and analyzed through statistics, and then a test report is formed.
Description
Technical field
The present invention relates to electronic document management system field tests, particularly about a kind of automated testing method of electronic document management system.
Background technology
In recent years, along with the attention of country to the management of electronic documents (Electronic Records Management), electronic document management system (Electronic Records Management System, ERMS) research and development become one of new problem of field of software engineering, and a lot of software companys take to the R&D work of ERMS.For this reason, the supervision of association area and research department's successively issue the requirement of ERMS general utility functions, the Moreq2010 of European Union standard (Model Requirements for the Management of Electronic Records for example, Moreq2010) U.S. DOD5015.2(Electronic Records Management Software Applications Design Criteria Standard, DOD5015.2) the international archives ICA of association standard (Principles and Functional Requirements for Records in Electronic Office Environments), Australia's VERS standard (VERS Standard99/007:Management of Electronic Records), ISO15489 standard (Information and Documentation-Records Management) and China GB/T29194-2012 (requirement of electronic document management system general utility functions).Meanwhile, the Standard conformance test work of ERMS also starts, has successively set up the mechanism for testing for the Moreq2010 of European Union, U.S. DOD5015.2 and China GB/T29194-2012, and corresponding test and authentication service are provided.
At present, the method for testing that the Standard conformance test of the Moreq2010 of European Union, U.S. DOD5015.2 and China GB/T29194-2012 adopts has following general character: 1) take manual test as main, lack the robotization of test process; 2) take the test of functional hierarchy as main, lack the test to data hierarchy; 3) take test function point as main, lack the test to interface between function point and logical relation; 4) take the universal method of software test as main, lack the professional test for electronic document management system technical characterictic.
Existing method of testing cannot meet the Validity Test needs of electronic document management system: 1) due to manual testing to tester require high, efficiency is low, subjectivity is high; 2) design defect of data hierarchy be not only difficult to is found in the test of functional hierarchy, and the surface phenomena easily being realized by system misleads, the test result that must make mistake; 3) function point test cannot be found function point interface in electronic document management system and the defect in logical relation; 4) different from general Software System, electronic document management system has particular provisions to data model and operator scheme.Therefore, the conventional method of software test can not be directly continued to use in the test of electronic document management system, need to carry out certain adjustment and optimization.
Summary of the invention
For the problems referred to above, the object of this invention is to provide a kind of method of testing electronic document management system in data hierarchy, changed and take manual test as main electronic document management system test present situation, improved test validity and reliability.
For achieving the above object, the present invention takes following technical scheme: a kind of automated testing method of electronic document management system, and it comprises the following steps: 1) definition defect code, defect type and the defect information table of comparisons; 2) according to the general utility functions of electronic document management system, require standard, analytic function requires related data processing needs, and on data Layer, electronic document management system and test activity thereof is carried out to modeling, generates test data model; 3) will in electronic document management system functional requirement, the relevant regulations of various test datas be described as to some Rule of judgment in formal mode, and all Rule of judgment are deposited in rule base; 4) adopt mode map and matching process, from the data base management system (DBMS) of electronic document management system and file system, obtain test data set, and set up and dynamically associate between the target data set in test data set and electronic document management system; 5) each test data of storing in traversal electronic document management system, and in calling rule storehouse, corresponding Rule of judgment is tested test data set, find the defect of each test data existence that test data is concentrated, and the defect that each test data is existed is carried out record; 6) attempt to revise the data to be tested in electronic document management system, judge whether electronic document management system has the ability of failure and protection data to be tested; 7) test of the updating maintenance of e-file and electronic document management system is synchronously carried out, judged whether e-file attended operation meets the requirements in data hierarchy; 8) gather with statistical study electronic document management system in the defect of test data, generate test report.
The test data model of the electronic document management system described step 2) is comprised of 12 patterns, i.e. e-file type, e-file template, e-file, metadata proposal, classification schemes, files, retention period and disposal plan, trace log, role, user, authority and right assignment.
The present invention is owing to taking above technical scheme, it has the following advantages: 1, the present invention breaks through the limitation of the functional test of electronic document management system, proposed to test in a kind of data hierarchy the method for electronic document management system, by test data defect type and defect content being defined at data Layer, and by the some Rule of judgment in rule base, the defect of test data is judged, the last test report that automatically generates, therefore changed and take manual test as main electronic document management system test present situation, improved test validity and reliability.2, the present invention proposes the method for testing of the function collection of electronic document management system, overcome the limitation of function point method of testing to functional sequence and logic testing.Therefore, compare with existing electronic document management system method of testing, the present invention can meet the needs of in electronic document management system, the control of e-file, probative value and service being tried hard to keep and being hindered better.The present invention can widespread use and the test of electronic document management system in.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is carried out to detailed describing.Yet only providing in order to understand better the present invention of accompanying drawing is provided, they not should be understood to limitation of the present invention.
Fig. 1 is the testing process schematic diagram of electronic document management system of the present invention;
Fig. 2 is electronic document management system test data model schematic diagram of the present invention;
Fig. 3 is electronic document management system test report effect schematic diagram of the present invention.
Embodiment
Below in conjunction with drawings and Examples, the present invention is described in detail.
As shown in Figure 1, the automated testing method of electronic document management system of the present invention, comprises the following steps:
1, definition defect code, defect type and the defect information table of comparisons.According to the singularity of the automatic test work of the practical work experience of electronic document management system test and data hierarchy, the present invention defines 6 large classes, and totally 30 defects define the defect type of test data and as shown in table 1 to corresponding defect content:
Table 1 defect type and defect content
2, according to the general utility functions of electronic document management system, require standard, analytic function requires related data processing needs, and on data Layer, electronic document management system and test activity thereof is carried out to modeling, generates test data model.
As shown in Figure 2, the test data of electronic document management system of the present invention is comprised of 12 kinds of relation schemas, i.e. e-file type, e-file template, e-file, metadata proposal, classification schemes, files, retention period and disposal plan, trace log, role, user, authority and right assignment.Wherein, e-file is the core of this test model.As shown in Figure 2, e-file type comprises type unique identifier and typonym; E-file template comprises template unique identifier, type unique identifier, element, binding character, repeatability, call format and exhibition method; E-file comprise file unique identifier, file name, type unique identifier, deposit position, check code, retention period unique identifier, whether two cover system, whether mixed file, physics deposit position, whether be copy and whether destroy; Metadata proposal comprises metadata unique identifier, title, binding character, repeatability, element type, coding scheme, codomain, default value and remarks; Metadata proposal comprises metadata unique identifier, title, binding character, repeatability, element type, coding scheme, codomain, default value and remarks; Classification schemes comprises node unique identifier, nodename, father node unique identifier, node state and node type; Retention period and disposal plan comprise retention period unique identifier, retention period title, the keeping time limit, method of disposal and triggering mode; Trace log comprises daily record unique identifier, operator, running time, operand, content of operation, operating result and operation reason; User comprises user's unique identifier, user's name, user role and User Status; Role comprises role's unique identifier and role's title; Authority comprises unique identifier and title.
3, will in electronic document management system functional requirement, the relevant regulations of various test datas be described as to some Rule of judgment in formal mode, and all Rule of judgment are deposited in rule base.
In rule base, Rule of judgment can be set according to concrete test data, in rule base of the present invention, Rule of judgment is divided into four classes, comprise Rule of judgment centered by e-file, the Rule of judgment centered by daily record is excavated, with audit-trail daily record/metadata category Rule of judgment and audit-trail daily record/right assignment/metadata category Rule of judgment, respectively the process of establishing of four class Rule of judgment is described below:
Rule of judgment centered by e-file comprises two kinds, wherein, take the Rule of judgment one centered by e-file process of establishing as:
1) a pointer variable P of definition, and first tuple of points relationship e-file, and start to travel through connection-related electricity use son file;
2) judge whether the field ' file unique identifier ' in connection-related electricity use son file is non-NULL, if ' being ' carried out and performed step one by one 3)～9), otherwise directly enter step 10);
3) whether the currency that judges the field ' unique identifier of retention period ' in connection-related electricity use son file is empty, if ' being ' reports defect, and defect code ' 410 ' is put among defect queue;
4) whether the currency that judges the field ' unique identifier of file type ' in connection-related electricity use son file is empty, if ' being ' reports defect, and defect code ' 411 ' is put among defect queue;
5) whether the currency that judges the field ' whether being the sign of mixed file ' in connection-related electricity use son file is empty, if ' being ' reports defect, and defect code ' 412 ' is put among defect queue;
6) whether the currency that judges field in connection-related electricity use son file ' whether being the signs of two cover file processed ' is sky, if ' being ' reports defect, and defect code ' 413 ' is put among defect queue;
7) whether the currency that judges field in connection-related electricity use son file ' whether being the mark of taking passages ' is empty, if ' being ' reports defect, and defect code ' 415 ' is put among defect queue;
8) whether the currency that judges the field ' whether being the sign of copy ' in connection-related electricity use son file is empty, if ' being ',, report defect, and defect code ' 416 ' is put among defect queue;
9) judge whether field ' file unique identifier ' in connection-related electricity use son file is for being non-NULL, and the currency of the field in connection-related electricity use son file ' being whether the signs of two cover file processed ' is whether the currency of the field ' whether being the sign of mixed file ' in value of true or connection-related electricity use son file is value of true, ' if being ', continue to judge whether the currency of the field ' physics deposit position ' in connection-related electricity use son file is empty, ' if being ', report defect, and defect code ' 414 ' is put among defect queue;
10) judge whether last tuple of points relationship e-file of pointer variable P, if ' being ' finishes this judgement; If not last tuple, mobile current pointer, to next record in connection-related electricity use son file, continues to carry out once performing step 2)～10).
Take the Rule of judgment two centered by e-file process of establishing as:
1) a pointer variable P of definition, and first tuple of points relationship e-file, and start to travel through connection-related electricity use son file;
2) judge whether the value whether field in connection-related electricity use son file ' has destroyed sign ' is ' being ', if ' being ' performs step 3 so), otherwise skip this circulation.
3) whether the value that judges the field ' deposit position ' in connection-related electricity use son file is whether the field ' physics deposit position ' in non-NULL or connection-related electricity use son file is non-NULL, ' if being ', report so defect, and defect code ' 407 ' is put among defect queue;
4) judge whether last tuple of points relationship e-file of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in connection-related electricity use son file, continues to carry out once performing step 2)～4).
Rule of judgment centered by daily record is excavated comprises 16 kinds, wherein, the process of establishing of the Rule of judgment one of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) defining variable ' operation reason ', and its initial value is made as to ' sky ';
3) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
4) judge whether the field ' action type ' in relation track daily record is ' revising e-file title ', if ' being ' performs step 5 so)～6), otherwise, skips steps 5)～6);
5) value of status indication variable is made as to ' 0 ';
6) value of variable ' operation reason ' is changed into the value of the field ' operation reason ' in relation track daily record;
7) judge whether last tuple of points relationship trace log of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 4)～7).
8) currency that judges status indication variable be whether ' 1 ' or the currency of variable ' operation reason ' be ' sky ', if ' being ', execution step 9), otherwise finish this rule;
9) report defect, and defect code ' 401 ' is put among defect queue.
The process of establishing of the Rule of judgment two of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) defining variable ' operation reason ', and its initial value is made as to ' sky ';
3) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
4) field ' action type ' in the daily record of judgement relation track is ' create and take passages ', if ' being ' performs step 5 so)～6), otherwise skips steps 5)～6);
5) change the currency of status indication variable into ' 0 ';
6) currency of variable ' operation reason ' changes the field ' operation reason ' in relation track daily record into;
7) judge whether last tuple of points relationship trace log of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 4)～7).
8) currency that judges status indication variable be whether ' 1 ' or relation track daily record in the currency of field ' operation reason ' whether be ' sky ', if ' being ' reports defect so, and defect code ' 601 ' is put among defect queue.
The process of establishing of the Rule of judgment three of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) defining variable ' operation reason ', and its initial value is made as to ' sky ';
3) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
4) field ' action type ' in the daily record of judgement relation track is ' reclassifying of e-file ', if ' being ' is made as ' 0 ' by the currency of status indication variable so;
5) variable ' operation reason ' is changed into the value of the field ' operation reason ' in relation track daily record;
6) judge whether last tuple of points relationship trace log of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 4)～6).
7) currency that judges status indication variable be whether ' 1 ' or the currency of variable ' operation reason ' whether be empty, if ' being ' reports defect so, and defect code ' 402 ' is put among defect queue.
The process of establishing of the Rule of judgment four of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' in the daily record of judgement relation track is ' establishment classification schemes ', if ' being ' carries out 4 so), otherwise skip 4);
4) change the currency of status indication variable into ' 0 ';
5) judge whether last tuple of points relationship trace log of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 3)～5).
6) whether the currency that judges status indication variable is ' 1 ', if ' being ' reports defect so, and defect code ' 101 ' is put among defect queue.
The process of establishing of the Rule of judgment five of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 '
2) defining variable ' operation reason ', and its initial value is made as to ' sky '
3) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
4) whether the value that judges the field ' action type ' in relation track daily record is ' modification of metadata proposal ', if ' being ' carries out 5th～6 so), otherwise skips steps 5～6);
5) change the currency of status indication variable into ' 0 ';
6) currency of variable ' operation reason ' is changed into the value of the field ' operation reason ' in relation track daily record;
7) judge whether last tuple of points relationship trace log of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 4)～7);
8) currency that judges status indication variable be whether ' 1 ' or the currency of variable ' operation reason ' for empty, if ' being ' reports defect so, and defect code ' 302 ' is put among defect queue.
The process of establishing of the Rule of judgment six of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) whether the currency that judges the field ' action type ' in relation track daily record is whether the currency of the field ' action type ' in ' copying classification ' or relation track daily record is ' mobile classification ', ' if being ', perform step so 4), otherwise skips steps 4);
4) currency of status indication variable changes ' 0 ' into;
5) judge whether last tuple of points relationship trace log of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 3)～5);
6) whether the currency that judges status indication variable is ' 1 ', if ' being ' reports defect so, and defect code ' 103 ' is put among defect queue.
The process of establishing of the Rule of judgment seven of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) judge whether the field ' action type ' in relation track daily record is ' newly-increased file ', if ' being ' performs step 4 so)～9), otherwise skips steps 4)～9);
4) defining variable ' insertion time ', and its currency is changed into the value of the field ' running time ' in relation track daily record;
5) defining variable ' file unique identifier ', and its currency is changed into the value of the field ' operand ' in relation track daily record;
6) defining variable ' classification unique identifier ', and its initial value is made as to the classification unique identifier at file place;
7) a pointer variable Q of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
8) find the variable ' last shut-in time ' of ' classification unique identifier ' nearest with variable ' insertion time ';
9) between judgment variable ' last shut-in time ' and variable ' insertion time ', whether open this type of object daily record,, if do not open this classification, the currency of status indication variable is changed into=0;
10) judge whether last tuple of points relationship trace log of pointer variable Q, if ' being ' finishes this rule; If not last tuple, moving hand variable Q, to next record in relation track daily record, continues to carry out once performing step 8)～10);
11) whether the currency that judges status indication variable is ' 0 ', if ' being ' reports defect so, and defect code ' 403 ' is put among defect queue;
12) judge whether last tuple of points relationship trace log of pointer variable P, if ' being ' finishes this rule; If not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 3)～12).
The process of establishing of the Rule of judgment eight of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 0 ';
2) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) judge whether the field ' operand ' in relation track daily record equals the value of the field ' e-file unique identifier ' in connection-related electricity use son file, and the value of the field in connection-related electricity use son file ' whether being the mark of taking passages ' is ' being ', and the currency of the field in relation track daily record ' operation reason ' is blank, ' if being ', carry out so 4), otherwise skip 4);
4) change the currency of status indication variable into ' 1 ';
5) judge whether last tuple of points relationship trace log of pointer variable P, if not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 3-5.
6) whether the currency that judges status indication variable equals 0, if ' being ' reports defect so, and defect code ' 601 ' is put among defect queue.
7) a pointer variable Q of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
8) judge whether the field ' action type ' in relation track daily record is ' destruction ', if ' being ' performs step 9 so)～11), otherwise skips steps 9)～11);
9) change the currency of this status indication variable into ' 0 ';
10) defining variable ' e-file unique identifier ', and its initial value is made as to the field ' operand ' in relation track daily record;
11) defining variable ' operation reason ', and its value is made as to the field ' operation reason ' in relation track daily record;
12) a pointer variable R of definition, and first tuple of points relationship e-file, and start to travel through connection-related electricity use son file;
13) whether the currency of judgment variable ' e-file unique identifier ' equals the field ' e-file unique identifier ' in connection-related electricity use son file, if ' being ' changes the currency of status indication variable into ' 0 ' so;
14) judge whether last tuple of points relationship e-file of pointer variable R, if ' being ' finishes this rule; If not last tuple, moving hand variable R, to next record in connection-related electricity use son file, continues to carry out once performing step 13)～14);
15) currency of judgement status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 409 ' is put among defect queue; If 'No', so then whether the currency of judgment variable ' operation reason ' is empty, if ' being ' reports defect so, and defect code ' 408 ' is put among defect queue;
16) judge whether last tuple of points relationship trace log of pointer variable Q, if ' being ' finishes this rule; If not last tuple, moving hand variable Q, to next record in relation track daily record, continues to carry out once performing step 13)～14).
The process of establishing of the Rule of judgment nine of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' in the daily record of judgement relation track is newly-built son volume, if ' being ' performs step 4 so)～9), otherwise skips steps 4)～9);
4) defining variable ' operand ', and its value is made as to the value of the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and its value is made as to the field ' running time ' in relation track daily record;
6) defining variable ' parent files ', and its value is made as to the files at ' operand ' place;
7) a pointer variable Q of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
8) whether judgment variable ' parent files ' is ' closing ' type in variable ' running time ' nearest daily record before, if ' being ' changes the currency of this status indication variable into ' 0 ' so;
9) judge whether last tuple of points relationship trace log of pointer variable Q, if not last tuple, moving hand variable Q, to next record in relation track daily record, continues to carry out once performing step 8-9;
10) whether the currency that judges status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 501 ' is put among defect queue;
11) judge whether last tuple of points relationship trace log of pointer variable P, if not last tuple, moving hand variable P, to next record in relation track daily record, continues to carry out once performing step 3)～11); 'No', finishes current rule if.
The process of establishing of the Rule of judgment ten of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) a pointer variable P of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' in the daily record of judgement relation track is ' opening files ' temporarily, if ' being ', Na Me Kayak 4)～8), otherwise skips steps 4)～8);
4) defining variable ' operand ', and its initial value is made as to the value of the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and its initial value is made as to the value of the field ' running time ' in relation track daily record;
6) a pointer variable Q of definition, and first tuple of points relationship trace log, and start to travel through relation track daily record;
7) whether the value of judgment variable ' operand ' equals the value of the field ' operand ' in relation track daily record, and whether the field in relation track daily record ' action type ' is ' Temporarily Closed files, and the value of variable ' running time ' is early than the value of ' running time ' of the field in relation track daily record, ' if being ', change the currency of this status indication variable into ' 0 ' so, and skip 8), directly carry out 9);
8) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 7)～8);
9) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～9);
10) currency of judgement status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 502 ' is put among defect queue.
The process of establishing of the Rule of judgment ten one of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' in the daily record of judgement relation track is ' authorized user off-line ', if ' being ' performs step 4 so)～9), otherwise skips steps 4)～9);
4) definition pointer variable Q, and first tuple of points relationship trace log, and start to travel through relation track daily record;
5) judge whether the field ' action type ' in relation track daily record is ' opening files ' temporarily, if ' being ', so, execution step 6)～9), otherwise skips steps 6)～9);
6) defining variable ' operand ', and its value is made as to the value of the field ' operand ' in relation track daily record;
7) defining variable ' running time ', and its value is made as to the value of the field ' running time ' in relation track daily record;
8) definition pointer variable R, and first tuple of points relationship trace log, and start to travel through relation track daily record;
9) whether the value that judges the field ' action type ' in relation track daily record is ' automatically closing files ', and the value of variable ' operand ' equals the value of the field ' operand ' in relation track daily record, and variable ' running time ' is early than the value of ' running time ' of the field in relation track daily record, if ' being ', changes the currency of this status indication variable into ' 0 ' so;
10) judge whether pointer R is last tuple of relation track daily record, if not last tuple, moving hand R, to next record in relation track daily record, continues to carry out once performing step 9)～10);
11) currency of judgement status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 503 ' is put among defect queue;
12) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 3)～12);
13) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 2)～13).
The process of establishing of the Rule of judgment ten two of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) defining variable ' operation reason ', and its initial value is made as to ' sky ';
3) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
4) judge whether the field ' action type ' in relation track daily record is ' files operation ', if ' being ' performs step 5 so)～6), otherwise, skips steps 5)～6);
5) change the currency of this status indication variable into ' 0 ';
6) value of variable ' operation reason ' is changed into the value of the field ' operation reason ' in relation track daily record;
7) currency that judges status indication variable whether equal ' 1 ' or the currency of variable ' operation reason ' for empty, if ' being ' reports defect so, and defect code ' 504 ' is put among defect queue;
8) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 4)～8).
The process of establishing of the Rule of judgment ten three of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) defining variable ' operation reason ', and its initial value is made as to sky;
3) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
4) judge that whether field ' action type ' in relation track daily record is ' mobile classification ' or be ' copying classification ', if ' being ' performs step 5 so)～6), otherwise skips steps 5)～6);
5) change the currency of this status indication variable into ' 0 ';
6) currency of variable ' operation reason ' is changed into the value of the field ' operation reason ' in relation track daily record;
7) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 4)～7);
8) currency that judges status indication variable whether equal ' 0 ' or the currency of variable ' operation reason ' whether be empty, if ' being ' reports defect so, and defect code ' 104 ' is put among defect queue.
The process of establishing of the Rule of judgment ten four of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) whether the currency that judges the field ' operation reason ' in relation track daily record is empty, whether the value of the field in relation track daily record ' action type ' equals ' copying classification ', whether the field in relation track daily record ' operand ' equals the field ' file unique identifier ' in connection-related electricity use son file, whether the field in connection-related electricity use son file ' file unique identifier ' equals the field ' unique identifier of file type ' in connection-related electricity use son file, and be related to whether the field ' node type ' in classification schemes equals ' classification ', if be ' being ', report so defect, and defect code ' 105 ' is put among defect queue,
4) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～4).
The process of establishing of the Rule of judgment ten five of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) defining variable ' operation reason ', and its value is made as to ' sky ';
3) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
4) judge whether the field ' action type ' in relation track daily record equals ' modification of retention period or disposal method ', if ' being ' performs step 5-6 so, otherwise skips steps 5)～6);
5) change the currency of this status indication variable into ' 0 ';
6) currency of variable ' operation reason ' changes the value of the field ' operation reason ' in relation track daily record into;
7) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 4)～7);
8) currency that judges status indication variable whether equal ' 1 ' and also the currency of variable ' operation reason ' whether be empty, if ' being ' reports defect so, and defect code ' 202 ' is put among defect queue.
The process of establishing of the Rule of judgment ten six of the daily record of take centered by excavating as:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' meeting in the daily record of judgement relation track is no is ' merging classification ', if ' being ' performs step 4 so)～8), otherwise skips steps 4)～8);
4) defining variable ' merging time ', and its value is made as to the field ' running time ' in relation track daily record;
5) definition pointer variable Q, and first tuple of points relationship trace log, and start to travel through relation track daily record;
6) find the classification shut-in time variable nearest with variable ' merging time ' ' last shut-in time ';
7) check between variable ' last shut-in time ' and variable ' merging time ' whether open this type of object daily record, if open this type of object daily record, so, change the currency of this status indication variable into ' 0 ';
8) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 6)～8);
9) whether the currency that judges status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 103 ' is put among defect queue;
10) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～10).
The Rule of judgment of audit-trail daily record/metadata category comprises three kinds, and wherein, the method for building up of the Rule of judgment one of audit-trail daily record/metadata category is:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) judge whether the field ' action type ' in relation track daily record is ' transfer e-file ', if ' being ' performs step 4 so)～5), otherwise skips steps 4)～5);
4) definition pointer variable Q, and first tuple of points relationship e-file, and start to travel through connection-related electricity use son file;
5) judge whether the field ' operand ' in relation track daily record equals the field ' file unique identifier ' in connection-related electricity use son file, if ' being ' changes the currency of this status indication variable into ' 0 ' so;
6) judge whether last tuple of points relationship e-file of pointer Q, if not last tuple, moving hand Q, to next record in connection-related electricity use son file, continues to carry out once performing step 5)～6);
7) currency of judgement status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 406 ' is put among defect queue;
8) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～8).
The method for building up of the Rule of judgment two of audit-trail daily record/metadata category is:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) judge whether field ' action type ' in relation track daily record is whether field ' action type ' in ' renewing e-file ' or relation track daily record is whether field ' action type ' in ' destruction e-file ', relation track daily record is ' transfer e-file ', as long as if there is an establishment in above-mentioned condition, perform step so 4)～5), otherwise skips steps 4)～5);
4) defining variable ' e-file unique identifier ', and its initial value is made as to the value of the field ' operand ' in relation track daily record;
5) definition pointer variable Q, and first tuple of points relationship e-file, and start to travel through connection-related electricity use son file;
6) if whether the currency of variable ' e-file unique identifier ' equals the field ' file unique identifier ' in connection-related electricity use son file, if ' being ' changes the currency of this status indication variable into ' 0 ' so;
7) judge whether last tuple of points relationship e-file of pointer Q, if not last tuple, moving hand Q, to next record in connection-related electricity use son file, continues to carry out once performing step 6)～7);
8) whether the currency that judges status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 404 ' is put among defect queue;
9) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～9).
The method for building up of audit-trail daily record/metadata category Rule of judgment three is:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) judge whether the field ' action type ' in relation track daily record is ' transfer e-file ', if ' being ' performs step 4 so)～8), otherwise skips steps 4)～8);
4) defining variable ' operand unique identifier ', and its value is made as to the value of the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and its initial value is made as to the value of the field ' running time ' in relation track daily record;
6) definition pointer variable Q, and first tuple of points relationship trace log, and start to travel through relation track daily record;
7) whether judgment variable ' operand unique identifier ' equals the value of the field ' operand ' in relation track daily record, and field ' running time ' is later than the field ' running time ' in relation track daily record, and the field in relation track daily record ' action type ' is ' destruction e-file ', if ' being ', changes the currency of this status indication variable into ' 0 ' so;
8) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 7)～8);
9) whether the currency that judges status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 405 ' is put among defect queue;
10) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～10).
Audit-trail daily record/right assignment/metadata category rule judgment condition comprises five kinds, and wherein, the process of establishing of audit-trail daily record/right assignment/metadata category rule judgment condition one is:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) judge whether the field ' action type ' in relation track daily record is ' management of classification schemes ', if ' being ' performs step 4 so)～9), otherwise skips steps 4)～9);
4) defining variable ' operand unique identifier ', and its initial value is made as to the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and its initial value is made as to the field ' running time ' in relation track daily record;
6) definition pointer variable Q, and first tuple of points relationship trace log, and start to travel through relation track daily record;
7) whether the currency of judgment variable ' operand unique identifier ' equals the field ' operand ' in relation track daily record, and the value of variable ' running time ' is later than the field ' running time ' in relation track daily record, if ' being ', changes the currency of this status indication variable into ' 0 ' so;
8) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 7)～8);
9) whether the currency that judges status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 405 ' is put among defect queue;
10) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～10).
The process of establishing of audit-trail daily record/right assignment/metadata category rule judgment condition two is:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' in the daily record of judgement relation track is ' maintenance of retention period or disposal method ', if ' being ' performs step 4 so)～9), otherwise skips steps 4)～9);
4) defining variable ' user's unique identifier ', and its initial value is made as to the field ' operator ' in relation track daily record;
5) defining variable ' running time ', and its initial value is made as to the field ' running time ' in relation track daily record;
6) definition pointer variable Q, and first tuple of points relationship trace log, and start to travel through relation track daily record;
7) judge whether the field ' operator ' in relation track daily record is the currency of variable ' user's unique identifier ', and the field in relation track daily record ' action type ' is ' retention period or disposal method authority are safeguarded in distribution ', and the currency of variable ' running time ' is later than the field ' running time ' in relation track daily record, if ' being ', changes the currency of this status indication variable into ' 0 ' so;
8) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 7-8;
9) currency of judgement status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 201 ' is put among defect queue;
10) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～10).
The process of establishing of audit-trail daily record/right assignment/metadata category rule judgment condition three is:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' in the daily record of judgement relation track is ' maintenance of classification schemes ', if ' being ' performs step 4 so)～9), otherwise skips steps 4)～9);
4) defining variable ' user's unique identifier ', and its initial value is made as to the field ' operator ' in relation track daily record;
5) currency of variable ' running time ' is made as the field ' running time ' in relation track daily record;
6) definition pointer variable Q, and first tuple of points relationship trace log, and start to travel through relation track daily record;
7) judge whether the field ' operator ' in relation track daily record equals variable ' user's unique identifier ', and whether the field in relation track daily record ' action type ' is ' authority that classification schemes is safeguarded in distribution ', and whether the currency of variable ' running time ' is later than the field ' running time ' in relation track daily record, if ' being ', changes the currency of this status indication variable into ' 0 ' so;
8) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 7)～8);
9) currency of judgement status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 105 ' is put among defect queue;
10) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～10).
The process of establishing of audit-trail daily record/right assignment/metadata category rule judgment condition four is:
1) a status indication variable of definition, and its initial value is made as to ' 1 ';
2) definition pointer variable P, and first tuple of points relationship trace log, and start to travel through relation track daily record;
3) field ' action type ' in judgement relation track daily record is ' maintenance of metadata proposal ', if ' being ' can manage it step 4)～8 so), otherwise skips steps 4)～8);
4) defining variable ' user's unique identifier ', and its initial value is made as to the field ' operator ' in relation track daily record;
5) defining variable ' running time ', and change its currency into field ' running time ' in relation track daily record;
6) definition pointer variable Q, and first tuple of points relationship trace log, and start to travel through relation track daily record;
7) judge whether the field ' operator ' in relation track daily record is the currency of variable ' user's unique identifier ', and whether the field in relation track daily record ' action type ' is ' authority of distributing dimension metadata proposal ', and the currency of variable ' running time ' is later than the field ' running time ' in relation track daily record, if ' being ', changes the currency of this status indication variable into ' 0 ' so;
8) judge whether last tuple of points relationship trace log of pointer Q, if not last tuple, moving hand Q, to next record in relation track daily record, continues to carry out once performing step 7)～8);
9) currency of judgement status indication variable equals ' 1 ', if ' being ' reports defect so, and defect code ' 301 ' is put among defect queue;
10) judge whether last tuple of points relationship trace log of pointer P, if not last tuple, moving hand P, to next record in relation track daily record, continues to carry out once performing step 3)～10).
4, adopt mode map and matching process, from the data base management system (DBMS) of electronic document management system and file system, obtain test data set, and set up and dynamically associate between the target data set in test data set and electronic document management system.
In order to set up dynamic real time correlation between the target data set in test data set and electronic document management system, the present invention adopts view techniques to create following 12 views, and viewdata comes from the target data set of electronic document management system.
1) file type view, mode-definition is as follows: file type (file type unique identifier, typonym);
2) file template view, mode-definition is as follows: file template (template unique identifier, type unique identifier, element, binding character, repeatability, call format, ways of presentation);
3) e-file view, mode-definition is as follows: e-file (file unique identifier, file name, type unique identifier, electronics deposit position, retention period unique identifier, check code, whether two cover system, whether mixed file, whether be copy, non-electronic deposit position, whether destroy, whether be extracts);
4) just/copy relationship view, mode-definition is as follows: reserved copy and duplicate relation (being related to unique identifier, original unique identifier, copy unique identifier);
5) trace log view, mode-definition is as follows: trace log (daily record unique identifier, operator's unique identifier, running time, operand, action type, operating result, operation reason), wherein the value of ' operating result ' is ' success ' or ' failure ';
6) classification schemes view, mode-definition is as follows: classification schemes (node unique identifier, nodename, father node unique identifier, node state, node type), wherein the value of ' node state ' is " closing " or " opening "; ' node type ' is " classification " or " files ";
7) metadata proposal view, mode-definition is as follows: metadata proposal (metadata unique identifier, title, binding character, repeatability, element type, coding scheme, codomain, default value and remarks), wherein ' binding character ' refers to the whether essential or optional metadata of this metadata, and ' element type ' is simple types and compound type;
8) retention period and circular economy view, mode-definition is as follows: retention period and circular economy (retention period unique identifier, retention period title, the keeping time limit, method of disposal, triggering method);
9) User, mode-definition is as follows: user's (user's unique identifier, user's name, user cipher, user role unique identifier, User Status), wherein the value of ' User Status ' is ' opening ' or ' closing ';
10) role-view, mode-definition is as follows: role's (role's unique identifier, role's title);
11) authority view, mode-definition is as follows: authority (authority unique identifier, authority name);
12) right assignment view, mode-definition is as follows: role/authority (role's unique identifier, authority unique identifier, object unique identifier, start time, end time, whether authorize).
Each test data of 5, storing in traversal electronic document management system, and in calling rule storehouse, corresponding Rule of judgment is tested test data set, find the defect of each test data existence that test data is concentrated, and the defect that each test data is existed is carried out record;
Each test data of storing in traversal electronic document management system, and in calling rule storehouse, corresponding Rule of judgment is tested test data set, find the defect of each test data existence that test data is concentrated, and the defect that each test data is existed is carried out record, the test data that wherein the present invention adopts is e-file and trace log, but be not limited to this, can select according to actual conditions, respectively these two kinds of test datas are described respectively below:
(1) traversal e-file view, and the Rule of judgment centered by e-file in calling rule storehouse, finds to have defect in e-file and metadata thereof, and concrete steps are as follows:
1) define dynamic array Arr1;
2) defined file pointer, and define a counter variable i;
3) first tuple of current pointer points relationship e-file, and start to travel through connection-related electricity use son file;
4) counter variable from 1 to 10, according to carrying out successively Rule of judgment Rule (i), and the code of error message put into dynamic array Arr1;
5) judge whether counter variable value is greater than 10, 'No', carries out increment operator to counter variable if, from amplification degree, is+1, and repeats the 4th)～5);
6) file pointer points to next record;
7) judge whether current pointer is last tuple of connection-related electricity use son file, if not last tuple, mobile current pointer, to next record in connection-related electricity use son file, continues to carry out once performing step 4)～7).
(2) traversal trace log view, and the Rule of judgment centered by daily record is excavated in calling rule storehouse, the defect existing in discovery trace log, concrete steps are:
1) define dynamic array Arr2;
2) defined file pointer, and define a counter variable i;
3) first tuple of current pointer points relationship trace log, and start to travel through relation track daily record;
4) counter variable from 1 to 10, according to the Rule of judgment Rule (i) carrying out successively centered by daily record is excavated, and the code of error message put into dynamic array Arr2;
5) judge whether counter variable value is greater than 10, 'No', carries out increment operator to counter variable if, from amplification degree, is+1, and repeats the 4th)～5);
6) file pointer points to next record;
7) judge whether current pointer is last tuple of relation track daily record, if not last tuple, mobile current pointer, to next record in relation track daily record, continues to carry out once performing step 4)～7).
6, attempt to revise the data to be tested in (copy/delete/replace) electronic document management system, judge whether electronic document management system has the ability of failure and protection data to be tested, and its detailed process is:
1) directly open the catalogue at e-file place, and while attempting to copy the operation of some e-files, whether system refuses user's operation, and in audit-trail daily record, carries out record;
2) directly open the catalogue at e-file place, and while attempting to delete the operation of some e-files, whether system refuses user's operation, and in audit-trail daily record, carries out record;
3) directly open the catalogue at e-file place, and while attempting to replace the operation of some e-files, whether system refuses user's operation, and in audit-trail daily record, carries out record;
4) directly open data base management system (DBMS) or the file management system of depositing metadata, and while attempting to copy the operation of some metadata items, whether system refuses user's operation, and in audit-trail daily record, carries out record;
5) directly open data base management system (DBMS) or the file management system of depositing metadata, and while attempting to carry out the operation of the some metadata items of replacement operation, whether system refuses user's operation, and in audit-trail daily record, carries out record;
6) directly open data base management system (DBMS) or the file management system of depositing metadata, and while attempting to delete the operation of some metadata items, whether system refuses user's operation, and in audit-trail daily record, carries out record.
7, the test of the updating maintenance of e-file and electronic document management system is synchronously carried out, judged whether e-file attended operation meets the requirements in data hierarchy.The present invention describes e-file and trace log, judges whether e-file attended operation meets the requirements in data hierarchy, and detailed process is:
1) in test process, during an e-file of every increase, to carrying out the inspection of the Rule of judgment centered by e-file under newly-increased file;
2), in test process, often during a newly-increased daily record, current daily record is carried out to the inspection of the Rule of judgment centered by daily record excavation.
8, gather with statistical study electronic document management system in the defect of test data, generate test report (as shown in Figure 3), detailed process is:
1) array Arr1 and Arr2 are merged into new array Arr;
2) the new array Arr after traversal merging;
3) definition counter variable i, and its initial value is defined as to 1;
4) show in accordance with the following methods test comprise: if Arr(i) be more than or equal to 100 and also Arr(i) be less than 200, be presented at so in " classification schemes class " defect hurdle; If Arr(i) be more than or equal to 200 and also Arr(i) be less than 300, be presented at so in " retention period and disposal method class " defect hurdle; If Arr(i) be more than or equal to 300 and also Arr(i) be less than 400, be presented at so in " metadata proposal class " defect hurdle; If Arr(i) be more than or equal to 400 and also Arr(i) be less than 500, be presented at so in " e-file class of operation " defect hurdle; If Arr(i) be more than or equal to 500 and also Arr(i) be less than 600, be presented at so in " files class " defect hurdle; If Arr(i) be more than or equal to 600 and also be less than Arr(i) be presented at so in " extracts class " defect hurdle.
5) whether the currency that judges counter variable is greater than 10, if ' being ' stops carrying out; 'No', carries out increment operator to counter variable if, from amplification degree, is+1, is back to step 4) and repeats step 4)～5).
The various embodiments described above are only for illustrating the present invention, and wherein each implementation step of method etc. all can change to some extent, and every equivalents of carrying out on the basis of technical solution of the present invention and improvement, all should not get rid of outside protection scope of the present invention.
Claims (2)
1. an automated testing method for electronic document management system, it comprises the following steps:
1) definition defect code, defect type and the defect information table of comparisons;
2) according to the general utility functions of electronic document management system, require standard, analytic function requires related data processing needs, and on data Layer, electronic document management system and test activity thereof is carried out to modeling, generates test data model;
3) will in electronic document management system functional requirement, the relevant regulations of various test datas be described as to some Rule of judgment in formal mode, and all Rule of judgment are deposited in rule base;
4) adopt mode map and matching process, from the data base management system (DBMS) of electronic document management system and file system, obtain test data set, and set up and dynamically associate between the target data set in test data set and electronic document management system;
5) each test data of storing in traversal electronic document management system, and in calling rule storehouse, corresponding Rule of judgment is tested test data set, find the defect of each test data existence that test data is concentrated, and the defect that each test data is existed is carried out record;
6) attempt to revise the data to be tested in electronic document management system, judge whether electronic document management system has the ability of failure and protection data to be tested;
7) test of the updating maintenance of e-file and electronic document management system is synchronously carried out, judged whether e-file attended operation meets the requirements in data hierarchy;
8) gather with statistical study electronic document management system in the defect of test data, generate test report.
2. the automated testing method of a kind of electronic document management system as claimed in claim 1, it is characterized in that: the test data model of the electronic document management system described step 2) is comprised of 12 patterns, i.e. e-file type, e-file template, e-file, metadata proposal, classification schemes, files, retention period and disposal plan, trace log, role, user, authority and right assignment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410045487.5A CN103761188B (en) | 2014-02-08 | 2014-02-08 | A kind of automated testing method of electronic document management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410045487.5A CN103761188B (en) | 2014-02-08 | 2014-02-08 | A kind of automated testing method of electronic document management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103761188A true CN103761188A (en) | 2014-04-30 |
| CN103761188B CN103761188B (en) | 2016-03-16 |
Family
ID=50528430
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410045487.5A Expired - Fee Related CN103761188B (en) | 2014-02-08 | 2014-02-08 | A kind of automated testing method of electronic document management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103761188B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110245075A (en) * | 2019-05-21 | 2019-09-17 | 深圳壹账通智能科技有限公司 | Test data configuration method, device, computer equipment and storage medium |
| CN110275862A (en) * | 2019-06-26 | 2019-09-24 | 北京字节跳动网络技术有限公司 | Count the method and apparatus for having created number of files |
| CN111506513A (en) * | 2020-06-04 | 2020-08-07 | 南京大学 | File system testing method based on hierarchical model |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090055331A1 (en) * | 2007-08-23 | 2009-02-26 | International Business Machines Corporation | Method and apparatus for model-based testing of a graphical user interface |
| CN102331970A (en) * | 2011-07-28 | 2012-01-25 | 北京航空航天大学 | Safety critical system-oriented automatic testing resource management method and platform |
| CN102411540A (en) * | 2012-01-12 | 2012-04-11 | 王轶辰 | Workflow-based automatic management system for general software testing process |
| CN102650966A (en) * | 2011-02-24 | 2012-08-29 | 王轶辰 | Multiplexing-oriented embedded software testing method and system |
-
2014
- 2014-02-08 CN CN201410045487.5A patent/CN103761188B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090055331A1 (en) * | 2007-08-23 | 2009-02-26 | International Business Machines Corporation | Method and apparatus for model-based testing of a graphical user interface |
| CN102650966A (en) * | 2011-02-24 | 2012-08-29 | 王轶辰 | Multiplexing-oriented embedded software testing method and system |
| CN102331970A (en) * | 2011-07-28 | 2012-01-25 | 北京航空航天大学 | Safety critical system-oriented automatic testing resource management method and platform |
| CN102411540A (en) * | 2012-01-12 | 2012-04-11 | 王轶辰 | Workflow-based automatic management system for general software testing process |
Non-Patent Citations (2)
| Title |
|---|
| 朝乐门: "电子文件管理系统的技术特征", 《现代图书情报技术 》 * |
| 朝乐门: "电子文件管理系统研发的重点与难点分析", 《档案学通讯 》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110245075A (en) * | 2019-05-21 | 2019-09-17 | 深圳壹账通智能科技有限公司 | Test data configuration method, device, computer equipment and storage medium |
| CN110275862A (en) * | 2019-06-26 | 2019-09-24 | 北京字节跳动网络技术有限公司 | Count the method and apparatus for having created number of files |
| CN110275862B (en) * | 2019-06-26 | 2021-07-30 | 北京字节跳动网络技术有限公司 | Method and device for counting number of created documents |
| CN111506513A (en) * | 2020-06-04 | 2020-08-07 | 南京大学 | File system testing method based on hierarchical model |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103761188B (en) | 2016-03-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108376376B (en) | BIM model-based construction engineering quality management standardization method | |
| CN102831052B (en) | Test exemple automation generating apparatus and method | |
| CN108600148B (en) | Transaction message processing method and device | |
| US20110161132A1 (en) | Method and system for extracting process sequences | |
| CN101221530B (en) | Method for automatically leading in test cases | |
| CN104598376A (en) | Data driving layered automation test system and method | |
| CN104966172A (en) | Large data visualization analysis and processing system for enterprise operation data analysis | |
| CN102445941B (en) | Method for automatically determining and analyzing interoperability test results of on-board equipment of train control system | |
| CN106503158A (en) | Method of data synchronization and device | |
| CN102254029A (en) | View-based data access system and method | |
| CN104899143A (en) | Software peer review system realizing device for providing DM (Data Mining) | |
| CN104298726A (en) | BMS data storage system and method based on database | |
| CN110866024B (en) | Vector database increment updating method and system | |
| CN112579563B (en) | Power grid big data-based warehouse visualization modeling system and method | |
| CN113642299A (en) | One-key generation method based on power grid statistical form | |
| CN104252519A (en) | Increment updating method of topographic database | |
| CN103761188B (en) | A kind of automated testing method of electronic document management system | |
| CN108647147A (en) | It is a kind of to execute automatic test machine people and its application method using atlas analysis | |
| CN115617776A (en) | Data management system and method | |
| CN103810094B (en) | Execution method, device and the testing tool of a kind of test cases | |
| CN113657854A (en) | Man-machine cooperation intelligent audit analysis method for incomplete data | |
| CN111126946B (en) | Modeling method and device for data tracing of informatization system | |
| CN114971547B (en) | Component product level borrowing analysis method and system | |
| CN111191086A (en) | Test data identification method | |
| CN115587692A (en) | Building construction technical scheme management system and method based on informatization management platform |
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 | ||
| 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: 20160316 Termination date: 20190208 |