CN103761188B - A kind of automated testing method of electronic document management system - Google Patents
A kind of automated testing method of electronic document management system Download PDFInfo
- Publication number
- CN103761188B CN103761188B CN201410045487.5A CN201410045487A CN103761188B CN 103761188 B CN103761188 B CN 103761188B CN 201410045487 A CN201410045487 A CN 201410045487A CN 103761188 B CN103761188 B CN 103761188B
- Authority
- CN
- China
- Prior art keywords
- management system
- electronic document
- document management
- variable
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The present invention relates to a kind of automated testing method of electronic document management system, step is: Define defects code, defect type and the defect information table of comparisons; On a data layer modeling is carried out to electronic document management system and test activity thereof, generate test data model; 3) relevant regulations in electronic document management system functional requirement is described as some Rule of judgment, and by all Rule of judgment stored in rule base; 4) adopt mode map and matching process, set up between test data set and target data set and dynamically associate; 5) travel through in electronic document management system each test data stored, and call corresponding Rule of judgment test data set is tested, find defect; 6) attempt to revise the data to be tested in electronic document management system, judge whether 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, judge whether e-file attended operation meets the requirements in data hierarchy; 8) gather the defect with test data in statistical study electronic document management system, generate test report.
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 country is to the attention of the management of electronic documents (ElectronicRecordsManagement), electronic document management system (ElectronicRecordsManagementSystem, ERMS) one of research and development new problem becoming field of software engineering, 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 ERMS general utility functions requirement, such as European Union Moreq2010 standard (ModelRequirementsfortheManagementofElectronicRecords, Moreq2010) U.S. DOD5015.2(ElectronicRecordsManagementSoftwareApplication sDesignCriteriaStandard, DOD5015.2) international archives association ICA standard (PrinciplesandFunctionalRequirementsforRecordsinElectroni cOfficeEnvironments), Australia VERS standard (VERSStandard99/007:ManagementofElectronicRecords), ISO15489 standard (InformationandDocumentation-RecordsManagement) 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 European Union Moreq2010, U.S. DOD5015.2 and China GB/T29194-2012, and provides corresponding test and authentication service.
At present, the method for testing that the Standard conformance test of European Union Moreq2010, U.S. DOD5015.2 and China GB/T29194-2012 adopts has following general character: 1) based on manual test, lack the robotization of test process; 2) based on the test of functional hierarchy, the test to data hierarchy is lacked; 3) based on test function point, the test of interface to function point and logical relation is lacked; 4) based on the universal method of software test, the professional test for electronic document management system technical characteristic is lacked.
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) test of functional hierarchy is not only difficult to the design defect finding data hierarchy, and is easily misled by the surface phenomena that system realizes, the test result that must make mistake; 3) function point test cannot find the function point interface in electronic document management system and the defect in logical relation; 4) with general Software System unlike, electronic document management system has particular provisions to data model and operator scheme.Therefore, the test of electronic document management system directly can not continue to use the conventional method of software test, needs to carry out certain adjustment and optimisation.
Summary of the invention
For the problems referred to above, the object of this invention is to provide a kind of method of data hierarchy being tested electronic document management system, change the electronic document management system test present situation based on manual test, improve 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) Define defects code, defect type and the defect information table of comparisons; 2) require standard according to the general utility functions of electronic document management system, the data processing involved by analytic function requires needs, and carries out modeling to electronic document management system and test activity thereof on a data layer, generates test data model; 3) mode changed in the form the relevant regulations of various test data in electronic document management system functional requirement is described as some Rule of judgment, and by all Rule of judgment stored in rule base; 4) adopt mode map and matching process, from the data base management system (DBMS) and file system of electronic document management system, obtain test data set, and set up between target data set in test data set and electronic document management system and dynamically associate; 5) each test data stored in electronic document management system is traveled through, and corresponding Rule of judgment is tested test data set in calling rule storehouse, find the defect that each test data that test data is concentrated exists, and the defect each test data existed carries 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, judge whether e-file attended operation meets the requirements in data hierarchy; 8) gather the defect with test data in statistical study electronic document management system, generate test report.
Described step 2) in the test data model of electronic document management system be made up of 12 patterns, i.e. electronic file types, 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, propose a kind of method of data hierarchy being tested electronic document management system, by defining test data defect type and defect content at data Layer, and judged by the defect of some Rule of judgment to test data in rule base, finally automatically generate test report, therefore change the electronic document management system test present situation based on manual test, improve 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, compared with existing electronic document management system method of testing, the present invention can meet in electronic document management system the needs of barrier of trying hard to keep to the control of e-file, probative value and service better.The present invention can in the test of widespread use and electronic document management system.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, detailed description is carried out to the present invention.But should be appreciated that being provided only of accompanying drawing understands the present invention better, 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 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, Define defects code, defect type and the defect information table of comparisons.According to the practical work experience of electronic document management system test and the singularity of automatic test work of data hierarchy, the present invention defines 6 large class, totally 30 defects, defines the defect type of test data and as shown in table 1 to corresponding defect content:
Table 1 defect type and defect content
2, require standard according to the general utility functions of electronic document management system, the data processing involved by analytic function requires needs, and carries out modeling to electronic document management system and test activity thereof on a data layer, generates test data model.
As shown in Figure 2, the test data of electronic document management system of the present invention is made up of 12 kinds of relation schemas, i.e. electronic file types, 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, electronic file types 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; Whether whether e-file comprises file unique identifier, file name, type unique identifier, deposit position, check code, retention period unique identifier, whether double-set system, whether mixed file, physics deposit position, be copy and 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, the mode changed in the form the relevant regulations of various test data in electronic document management system functional requirement is described as some Rule of judgment, and by all Rule of judgment stored in rule base.
In rule base, Rule of judgment can set according to concrete test data, in rule base of the present invention, Rule of judgment is divided into four classes, comprise the Rule of judgment centered by e-file, Rule of judgment centered by Web log mining, 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 be described below:
Rule of judgment centered by e-file comprises two kinds, and wherein, the process of establishing of the Rule of judgment one centered by e-file is:
1) a pointer variable P is defined, and first of points relationship e-file tuple, 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 ', then performing and performs step 3) ~ 9 one by one), otherwise directly enter step 10);
3) judge that whether the currency of the field ' unique identifier of retention period ' in connection-related electricity use son file is empty, if ' being ', then reported defects, and defect code ' 410 ' is put among defect queue;
4) judge that whether the currency of the field ' unique identifier of file type ' in connection-related electricity use son file is empty, if ' being ', then reported defects, and defect code ' 411 ' is put among defect queue;
5) whether the currency judging field in the connection-related electricity use son file mark of mixed file ' whether be ' is empty, if ' being ', then reported defects, and puts among defect queue by defect code ' 412 ';
6) whether the currency judging field in the connection-related electricity use son file mark of double-set system file ' whether be ' is empty, if ' being ', then reported defects, and puts among defect queue by defect code ' 413 ';
7) whether the currency judging field in connection-related electricity use son file ' whether being the mark taken passages ' is empty, if ' being ', then reported defects, and puts among defect queue by defect code ' 415 ';
8) whether the currency judging field in the connection-related electricity use son file mark of copy ' whether be ' is empty, if ' being ', then reported defects, and defect code ' 416 ' is put among defect queue;
9) judge the field ' file unique identifier ' in connection-related electricity use son file is whether be non-NULL, and whether the currency of field in the connection-related electricity use son file mark of double-set system file ' whether be ' be the currency of field in value of true or the connection-related electricity use son file mark of mixed file ' whether be ' is value of true, ' if being ', whether the currency then continuing the field ' physics deposit position ' judged in connection-related electricity use son file is empty, ' if being ', then reported defects, and defect code ' 414 ' is put among defect queue;
10) judge last tuple of pointer variable P whether points relationship e-file, if ' being ', then terminating this and judge; If not last tuple, then move current pointer to next record in connection-related electricity use son file, continue to perform once execution step 2) ~ 10).
The process of establishing of the Rule of judgment two centered by e-file is:
1) a pointer variable P is defined, and first of points relationship e-file tuple, 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 ' destroys mark ' is ' being ', if ' being ', so performs step 3), otherwise skip this circulation.
3) judge whether the value of the field ' deposit position ' in connection-related electricity use son file be whether field ' physics deposit position ' in non-NULL or connection-related electricity use son file is non-NULL, ' if being ', so reported defects, and defect code ' 407 ' is put among defect queue;
4) judge last tuple of pointer variable P whether points relationship e-file, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in connection-related electricity use son file, continue to perform once execution step 2) ~ 4).
Rule of judgment centered by Web log mining comprises 16 kinds, and wherein, the process of establishing of the Rule of judgment one centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) defining variable ' operation reason ', and its initial value is set to ' sky ';
3) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
4) judge whether the field ' action type ' in relation track daily record is ' amendment e-file title ', if ' being ', so performs step 5) ~ 6), otherwise, skip step 5) ~ 6);
5) value of status indication variable is set 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 last tuple of pointer variable P whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in relation track daily record, continue execution and once perform step 4) ~ 7).
8) judge the currency of status indication variable be whether ' 1 ' or the currency of variable ' operation reason ' be ' sky ', if ' being ', perform step 9), otherwise end this rule;
9) reported defects, and defect code ' 401 ' is put among defect queue.
The process of establishing of the Rule of judgment two centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) defining variable ' operation reason ', and its initial value is set to ' sky ';
3) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
4) judge that field ' action type ' in relation track daily record is as ' create and take passages ', if ' being ', so performs step 5) ~ 6), otherwise skip step 5) ~ 6);
5) currency of status indication variable is changed into ' 0 ';
6) currency of variable ' operation reason ' changes the field ' operation reason ' in relation track daily record into;
7) judge last tuple of pointer variable P whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in relation track daily record, continue to perform once execution step 4) ~ 7).
8) judge the currency of status indication variable be whether ' 1 ' or relation track daily record in the currency of field ' operation reason ' whether be ' sky ', if ' being ', so reported defects, and defect code ' 601 ' is put among defect queue.
The process of establishing of the Rule of judgment three centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) defining variable ' operation reason ', and its initial value is set to ' sky ';
3) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
4) judge that field ' action type ' in relation track daily record is as ' reclassifying of e-file ', if ' being ', is so set to ' 0 ' by the currency of status indication variable;
5) variable ' operation reason ' is changed into the value of the field ' operation reason ' in relation track daily record;
6) judge last tuple of pointer variable P whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in relation track daily record, continue to perform once execution step 4) ~ 6).
7) judge the currency of status indication variable be whether ' 1 ' or the currency of variable ' operation reason ' whether be empty, if ' being ', so reported defects, and defect code ' 402 ' is put among defect queue.
The process of establishing of the Rule of judgment four centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that field ' action type ' in relation track daily record is as ' establishment classification schemes ', if ' being ', so performs 4), otherwise skip 4);
4) currency of status indication variable is changed into ' 0 ';
5) judge last tuple of pointer variable P whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in relation track daily record, continue to perform once execution step 3) ~ 5).
6) whether the currency judging status indication variable is ' 1 ', if ' being ', so reported defects, and defect code ' 101 ' is put among defect queue.
The process of establishing of the Rule of judgment five centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 '
2) defining variable ' operation reason ', and its initial value is set to ' sky '
3) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
4) whether the value judging the field ' action type ' in relation track daily record is ' amendment of metadata proposal ', if ' being ', so performs 5th ~ 6), otherwise skip step 5 ~ 6);
5) currency of status indication variable is changed 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 last tuple of pointer variable P whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in relation track daily record, continue execution and once perform step 4) ~ 7);
8) judge the currency of status indication variable be whether ' 1 ' or the currency of variable ' operation reason ' for empty, if ' being ', so reported defects, and defect code ' 302 ' is put among defect queue.
The process of establishing of the Rule of judgment six centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge whether the currency of the field ' action type ' in relation track daily record be whether the currency of field ' action type ' in ' copying classification ' or relation track daily record is ' mobile classification ', ' if being ', so perform step 4), otherwise skip step 4);
4) currency of status indication variable changes ' 0 ' into;
5) judge last tuple of pointer variable P whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in relation track daily record, continue execution and once perform step 3) ~ 5);
6) whether the currency judging status indication variable is ' 1 ', if ' being ', so reported defects, and defect code ' 103 ' is put among defect queue.
The process of establishing of the Rule of judgment seven centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) a pointer variable P is defined, and first of points relationship trace log tuple, 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 ', so performs step 4) ~ 9), otherwise skip step 4) ~ 9);
4) defining variable ' inserts the 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 the value its currency being changed into the field ' operand ' in relation track daily record;
6) defining variable ' classification unique identifier ', and its initial value is set to the classification unique identifier at file place;
7) a pointer variable Q is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
8) variable ' last shut-in time ' of ' the classification unique identifier ' that ' to insert the time ' with variable nearest is found;
9) whether judgment variable ' last shut-in time ' and variable open this type of object daily record between ' inserting the time ', if there is no this classification opened, then the currency of status indication variable is changed into=0;
10) judge last tuple of pointer variable Q whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable Q to next record in relation track daily record, continue execution and once perform step 8) ~ 10);
11) whether the currency judging status indication variable is ' 0 ', if ' being ', so reported defects, and puts among defect queue by defect code ' 403 ';
12) judge last tuple of pointer variable P whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable P to next record in relation track daily record, continue execution and once perform step 3) ~ 12).
The process of establishing of the Rule of judgment eight centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 0 ';
2) a pointer variable P is defined, and first of points relationship trace log tuple, 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 field in connection-related electricity use son file ' whether being the mark taken passages ' is ' being ', and the currency of the field ' operation reason ' in relation track daily record is blank, ' if being ', so perform 4), otherwise skip 4);
4) currency of status indication variable is changed into ' 1 ';
5) judge last tuple of pointer variable P whether points relationship trace log, if not last tuple, then move pointer variable P to next record in relation track daily record, continue to perform and once perform step 3-5.
6) judge whether the currency of status indication variable equals 0, if ' being ', so reported defects, and defect code ' 601 ' is put among defect queue.
7) a pointer variable Q is defined, and first of points relationship trace log tuple, 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 ', so performs step 9) ~ 11), otherwise skip step 9) ~ 11);
9) currency of this status indication variable is changed into ' 0 ';
10) defining variable ' e-file unique identifier ', and its initial value is set to the field ' operand ' in relation track daily record;
11) defining variable ' operation reason ', and its value is set to the field ' operation reason ' in relation track daily record;
12) a pointer variable R is defined, and first of points relationship e-file tuple, 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 ', so changes the currency of status indication variable into ' 0 ';
14) judge last tuple of pointer variable R whether points relationship e-file, if ' being ', then terminate this rule; If not last tuple, then move pointer variable R to next record in connection-related electricity use son file, continue execution and once perform step 13) ~ 14);
15) judge that the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, 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 ', so reported defects, and puts among defect queue by defect code ' 408 ';
16) judge last tuple of pointer variable Q whether points relationship trace log, if ' being ', then terminate this rule; If not last tuple, then move pointer variable Q to next record in relation track daily record, continue execution and once perform step 13) ~ 14).
The process of establishing of the Rule of judgment nine centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that field ' action type ' in relation track daily record is as newly-built son volume, if ' being ', so performs step 4) ~ 9), otherwise skip step 4) ~ 9);
4) defining variable ' operand ', and the value its value being set to the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and its value is set to the field ' running time ' in relation track daily record;
6) defining variable ' parent files ', and its value is set to the files at ' operand ' place;
7) a pointer variable Q is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
8) whether judgment variable ' parent files ' nearest daily record before variable ' running time ' is ' closedown ' type, if ' being ', so changes the currency of this status indication variable into ' 0 ';
9) judge last tuple of pointer variable Q whether points relationship trace log, if not last tuple, then move pointer variable Q to next record in relation track daily record, continue to perform and once perform step 8-9;
10) judge whether the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 501 ' is put among defect queue;
11) judge last tuple of pointer variable P whether points relationship trace log, if not last tuple, then move pointer variable P to next record in relation track daily record, continue to perform once perform step 3) ~ 11); If be 'No', then terminate current rule.
The process of establishing of the Rule of judgment ten centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) a pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that field ' action type ' in relation track daily record is as ' opening files ' temporarily, if ' being ', Na Me Kayak 4) ~ 8), otherwise skip step 4) ~ 8);
4) defining variable ' operand ', and the value its initial value being set to the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and the value its initial value being set to the field ' running time ' in relation track daily record;
6) a pointer variable Q is defined, and first of points relationship trace log tuple, 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 ' action type ' in relation track daily record is ' Temporarily Closed files, and the value of variable ' running time ' is early than the value of the field ' running time ' in relation track daily record, ' if being ', so change the currency of this status indication variable into ' 0 ', and skip 8), directly perform 9);
8) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 7) ~ 8);
9) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 9);
10) judge that the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 502 ' is put among defect queue.
The process of establishing of the Rule of judgment 11 centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that field ' action type ' in relation track daily record is as ' authorized user off-line ', if ' being ', so performs step 4) ~ 9), otherwise skip step 4) ~ 9);
4) pointer variable Q is defined, and first of points relationship trace log tuple, 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, perform step 6) ~ 9), otherwise skip step 6) ~ 9);
6) defining variable ' operand ', and the value its value being set to the field ' operand ' in relation track daily record;
7) defining variable ' running time ', and the value its value being set to the field ' running time ' in relation track daily record;
8) pointer variable R is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
9) whether the value judging 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 the field ' running time ' in relation track daily record, ' if being ', so change the currency of this status indication variable into ' 0 ';
10) judge that whether pointer R is last tuple of relation track daily record, if not last tuple, then move pointer R to next record in relation track daily record, continue to perform once perform step 9) ~ 10);
11) judge that the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 503 ' is put among defect queue;
12) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 3) ~ 12);
13) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 2) ~ 13).
The process of establishing of the Rule of judgment 12 centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) defining variable ' operation reason ', and its initial value is set to ' sky ';
3) pointer variable P is defined, and first of points relationship trace log tuple, 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 ', so performs step 5) ~ 6), otherwise, skip step 5) ~ 6);
5) currency of this status indication variable is changed into ' 0 ';
6) value of variable ' operation reason ' is changed into the value of the field ' operation reason ' in relation track daily record;
7) judge the currency of status indication variable whether equal ' 1 ' or the currency of variable ' operation reason ' for empty, if ' being ', so reported defects, and defect code ' 504 ' is put among defect queue;
8) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 4) ~ 8).
The process of establishing of the Rule of judgment 13 centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) defining variable ' operation reason ', and its initial value is set to sky;
3) pointer variable P is defined, and first of points relationship trace log tuple, 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 ', so perform step 5) ~ 6), otherwise skip step 5) ~ 6);
5) currency of this status indication variable is changed 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 last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 4) ~ 7);
8) judge the currency of status indication variable whether equal ' 0 ' or the currency of variable ' operation reason ' be whether empty, if ' being ', so reported defects, and defect code ' 104 ' is put among defect queue.
The process of establishing of the Rule of judgment 14 centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that whether the currency of the field ' operation reason ' in relation track daily record is empty, whether the value of the field ' action type ' in relation track daily record equals ' copying classification ', whether the field ' operand ' in relation track daily record equals the field ' file unique identifier ' in connection-related electricity use son file, whether the field ' file unique identifier ' in connection-related electricity use son file equals the field ' unique identifier of file type ' in connection-related electricity use son file, and whether the field ' node type ' in relation classification schemes equals ' classification ', if be ' being ', so reported defects, and defect code ' 105 ' is put among defect queue,
4) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 4).
The process of establishing of the Rule of judgment 15 centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) defining variable ' operation reason ', and its value is set to ' sky ';
3) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
4) judge whether the field ' action type ' in relation track daily record equals ' amendment of retention period or disposal method ', if ' being ', so performing step 5-6, otherwise skip step 5) ~ 6);
5) currency of this status indication variable is changed into ' 0 ';
6) currency of variable ' operation reason ' changes the value of the field ' operation reason ' in relation track daily record into;
7) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 4) ~ 7);
8) judge the currency of status indication variable whether equal ' 1 ' and also the currency of variable ' operation reason ' be whether empty, if ' being ', so reported defects, and defect code ' 202 ' is put among defect queue.
The process of establishing of the Rule of judgment 16 centered by Web log mining is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that the field ' action type ' in relation track daily record can be no as ' merging classification ', if ' being ', so perform step 4) ~ 8), otherwise skip step 4) ~ 8);
4) defining variable ' merges the time ', and its value is set to the field ' running time ' in relation track daily record;
5) pointer variable Q is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
6) the classification shut-in time variable ' last shut-in time ' that ' to merge the time ' with variable nearest is found;
7) check whether variable ' last shut-in time ' and variable open this type of object daily record between ' merging the time ', if open this type of object daily record, so, change the currency of this status indication variable into ' 0 ';
8) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 6) ~ 8);
9) judge whether the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 103 ' is put among defect queue;
10) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform 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) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, 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 ', so performs step 4) ~ 5), otherwise skip step 4) ~ 5);
4) pointer variable Q is defined, and first of points relationship e-file tuple, and start to travel through connection-related electricity use son file;
5) whether the field ' operand ' judging in relation track daily record equals the field ' file unique identifier ' in connection-related electricity use son file, if ' being ', so changes the currency of this status indication variable into ' 0 ';
6) judge last tuple of pointer Q whether points relationship e-file, if not last tuple, then move pointer Q to next record in connection-related electricity use son file, continue to perform once perform step 5) ~ 6);
7) judge that the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 406 ' is put among defect queue;
8) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 8).
The method for building up of the Rule of judgment two of audit-trail daily record/metadata category is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge whether field ' action type ' in the relation track daily record field ' action type ' that whether be whether field ' action type ' in ' renewing e-file ' or relation track daily record be in ' destruction e-file ', relation track daily record is ' transfer e-file ', as long as if there is an establishment in above-mentioned condition, so perform step 4) ~ 5), otherwise skip step 4) ~ 5);
4) defining variable ' e-file unique identifier ', and its initial value is set to the value of the field ' operand ' in relation track daily record;
5) pointer variable Q is defined, and first of points relationship e-file tuple, 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 ', so the currency of this status indication variable is changed into ' 0 ';
7) judge last tuple of pointer Q whether points relationship e-file, if not last tuple, then move pointer Q to next record in connection-related electricity use son file, continue to perform once perform step 6) ~ 7);
8) judge whether the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 404 ' is put among defect queue;
9) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 9).
The method for building up of audit-trail daily record/metadata category Rule of judgment three is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, 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 ', so performs step 4) ~ 8), otherwise skip step 4) ~ 8);
4) defining variable ' operand unique identifier ', and its value is set to the value of the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and the value its initial value being set to the field ' running time ' in relation track daily record;
6) pointer variable Q is defined, and first of points relationship trace log tuple, 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 ' action type ' in relation track daily record is ' destruction e-file ', ' if being ', so change the currency of this status indication variable into ' 0 ';
8) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 7) ~ 8);
9) judge whether the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 405 ' is put among defect queue;
10) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform 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) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, 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 ', so performs step 4) ~ 9), otherwise skip step 4) ~ 9);
4) defining variable ' operand unique identifier ', and its initial value is set to the field ' operand ' in relation track daily record;
5) defining variable ' running time ', and its initial value is set to the field ' running time ' in relation track daily record;
6) pointer variable Q is defined, and first of points relationship trace log tuple, 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 ', so change the currency of this status indication variable into ' 0 ';
8) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 7) ~ 8);
9) judge whether the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 405 ' is put among defect queue;
10) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 10).
The process of establishing of audit-trail daily record/right assignment/metadata category rule judgment condition two is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that field ' action type ' in relation track daily record is as ' maintenance of retention period or disposal method ', if ' being ', so performs step 4) ~ 9), otherwise skip step 4) ~ 9);
4) defining variable ' user's unique identifier ', and its initial value is set to the field ' operator ' in relation track daily record;
5) defining variable ' running time ', and its initial value is set to the field ' running time ' in relation track daily record;
6) pointer variable Q is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
7) judge that whether field ' operator ' in relation track daily record is the currency of variable ' user's unique identifier ', and the field ' action type ' in relation track daily record 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 ', so change the currency of this status indication variable into ' 0 ';
8) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform and once perform step 7-8;
9) judge that the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 201 ' is put among defect queue;
10) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 10).
The process of establishing of audit-trail daily record/right assignment/metadata category rule judgment condition three is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that field ' action type ' in relation track daily record is as ' maintenance of classification schemes ', if ' being ', so performs step 4) ~ 9), otherwise skip step 4) ~ 9);
4) defining variable ' user's unique identifier ', and its initial value is set to the field ' operator ' in relation track daily record;
5) currency of variable ' running time ' is set to the field ' running time ' in relation track daily record;
6) pointer variable Q is defined, and first of points relationship trace log tuple, 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 ' action type ' in relation track daily record 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 ', so change the currency of this status indication variable into ' 0 ';
8) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 7) ~ 8);
9) judge that the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 105 ' is put among defect queue;
10) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 10).
The process of establishing of audit-trail daily record/right assignment/metadata category rule judgment condition four is:
1) define a status indication variable, and its initial value is set to ' 1 ';
2) pointer variable P is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
3) judge that field ' action type ' in relation track daily record is as ' maintenance of metadata proposal ', if ' being ', so can manage it step 4) ~ 8), otherwise skip step 4) ~ 8);
4) defining variable ' user's unique identifier ', and its initial value is set to the field ' operator ' in relation track daily record;
5) defining variable ' running time ', and its currency is changed into the field ' running time ' in relation track daily record;
6) pointer variable Q is defined, and first of points relationship trace log tuple, and start to travel through relation track daily record;
7) judge that whether field ' operator ' in relation track daily record is the currency of variable ' user's unique identifier ', and whether the field ' action type ' in relation track daily record 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 ', so change the currency of this status indication variable into ' 0 ';
8) judge last tuple of pointer Q whether points relationship trace log, if not last tuple, then move pointer Q to next record in relation track daily record, continue to perform once perform step 7) ~ 8);
9) judge that the currency of status indication variable equals ' 1 ', if ' being ', so reported defects, and defect code ' 301 ' is put among defect queue;
10) judge last tuple of pointer P whether points relationship trace log, if not last tuple, then move pointer P to next record in relation track daily record, continue to perform once perform step 3) ~ 10).
4, adopt mode map and matching process, from the data base management system (DBMS) and file system of electronic document management system, obtain test data set, and set up between target data set in test data set and electronic document management system and dynamically associate.
Associate to set up dynamic realtime between test data set and the target data set in 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, pattern is defined as follows: file type (file type unique identifier, typonym);
2) file template view, pattern is defined as follows: file template (template unique identifier, type unique identifier, element, binding character, repeatability, call format, ways of presentation);
3) e-file view, pattern is defined as follows: e-file (file unique identifier, file name, type unique identifier, electronics deposit position, retention period unique identifier, check code, whether double-set system, whether mixed file, whether be copy, non-electronic deposit position, whether destroy, whether be extracts);
4) just/copy relationship view, pattern is defined as follows: reserved copy and duplicate relation (relation unique identifier, original unique identifier, copy unique identification accord with);
5) trace log view, pattern is defined 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, pattern is defined as follows: classification schemes (node unique identifier, nodename, father node unique identifier, node state, node type), and wherein the value of ' node state ' is " closedown " or " opening "; ' node type ' is " classification " or " files ";
7) metadata proposal view, pattern is defined 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, pattern is defined 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, pattern is defined as follows: user's (user's unique identifier, user's name, user cipher, user role unique identifier, User Status), and wherein the value of ' User Status ' is ' opening ' or ' closedown ';
10) role-view, pattern is defined as follows: role's (role's unique identifier, role's title);
11) authority view, pattern is defined as follows: authority (authority unique identifier, authority name);
12) right assignment view, pattern is defined as follows: role/authority (role's unique identifier, authority unique identifier, object unique identifier, start time, end time, whether authorize).
5, each test data stored in electronic document management system is traveled through, and corresponding Rule of judgment is tested test data set in calling rule storehouse, find the defect that each test data that test data is concentrated exists, and the defect each test data existed carries out record;
The each test data stored in traversal electronic document management system, and corresponding Rule of judgment is tested test data set in calling rule storehouse, find the defect that each test data that test data is concentrated exists, and the defect each test data existed carries out record, the test data that wherein the present invention adopts is e-file and trace log, but be not limited thereto, can select according to actual conditions, respectively these two kinds of test datas are described respectively below:
(1) e-file view is traveled through, and the Rule of judgment centered by e-file in calling rule storehouse, find existing defects in e-file and metadata thereof, concrete steps are as follows:
1) dynamic array Arr1 is defined;
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 is from 1 to 10, according to performing Rule of judgment Rule (i) successively, and the code of error message is put into dynamic array Arr1;
5) judge whether counter variable value is greater than 10, if be 'No', increment operator carried out to counter variable, be+1 from amplification degree, and repeat the 4th) ~ 5);
6) file pointer points to next record;
7) judge that whether current pointer is last tuple of connection-related electricity use son file, if not last tuple, then move current pointer to next record in connection-related electricity use son file, continue to perform once perform step 4) ~ 7).
(2) trace log view is traveled through, and the Rule of judgment centered by Web log mining in calling rule storehouse, find the defect existed in trace log, concrete steps are:
1) dynamic array Arr2 is defined;
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 is from 1 to 10, according to Rule of judgment Rule (i) performed successively centered by Web log mining, and the code of error message is put into dynamic array Arr2;
5) judge whether counter variable value is greater than 10, if be 'No', increment operator carried out to counter variable, be+1 from amplification degree, and repeat the 4th) ~ 5);
6) file pointer points to next record;
7) judge that whether current pointer is last tuple of relation track daily record, if not last tuple, then move current pointer to next record in relation track daily record, continue to perform once perform step 4) ~ 7).
6, attempt to revise the data to be tested in (copy/deletes/replaces) electronic document management system, judge whether electronic document management system has failure and protect the ability of data to be tested, and its detailed process is:
1) directly open the catalogue at e-file place, and when attempting the operation carrying out copying some e-files, whether system refuses user operation, and carry out record in audit-trail daily record;
2) directly open the catalogue at e-file place, and when attempting the operation carrying out deleting some e-files, whether system refuses user operation, and carry out record in audit-trail daily record;
3) directly open the catalogue at e-file place, and when attempting the operation carrying out replacing some e-files, whether system refuses user operation, and carry out record in audit-trail daily record;
4) directly open the data base management system (DBMS) depositing metadata or file management system, and when attempting the operation carrying out copying some metadata items, whether system refuses user operation, and carry out record in audit-trail daily record;
5) directly open the data base management system (DBMS) depositing metadata or file management system, and when attempting the operation carrying out the some metadata items of replacement operation, whether system refuses user operation, and carry out record in audit-trail daily record;
6) directly open the data base management system (DBMS) depositing metadata or file management system, and when attempting the operation carrying out deleting some metadata items, whether system refuses user operation, and carry out record in audit-trail daily record.
7, the test of the updating maintenance of e-file and electronic document management system is synchronously carried out, judge whether e-file attended operation meets the requirements in data hierarchy.E-file and trace log are described by the present invention, and judge whether e-file attended operation meets the requirements in data hierarchy, detailed process is:
1) in test process, when often increasing an e-file, to the inspection carrying out the Rule of judgment centered by e-file under newly-increased file;
2) in test process, often during a newly-increased daily record, current log is carried out to the inspection of the Rule of judgment centered by Web log mining.
8, gather the defect with test data in statistical study electronic document management system, generate test report (as shown in Figure 3), detailed process is:
1) array Arr1 and Arr2 is merged into new array Arr;
2) the new array Arr after traversal merging;
3) define counter variable i, and be 1 by its Initial Value definition;
4) carry out display test in accordance with the following methods to comprise: if Arr(i) be more than or equal to 100 and also Arr(i) be less than 200, be so presented 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 so presented 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 so presented 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 so presented 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 so presented in " files class " defect hurdle; If Arr(i) be more than or equal to 600 and also be less than Arr(i) be so presented in " extracts class " defect hurdle.
5) judge whether the currency of counter variable is greater than 10, if ' being ', stop performing; If be 'No', then carrying out increment operator to counter variable, is+1 from amplification degree, is back to step 4) and repeats step 4) ~ 5).
The various embodiments described above are only for illustration of the present invention, and wherein each implementation step etc. of method 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 (1)
1. an automated testing method for electronic document management system, it comprises the following steps:
1) Define defects code, defect type and the defect information table of comparisons;
2) standard is required according to the general utility functions of electronic document management system, data processing involved by analytic function requires needs, and on a data layer modeling is carried out to electronic document management system and test activity thereof, generate test data model, test data model is made up of 12 patterns, i.e. electronic file types, e-file template, e-file, metadata proposal, classification schemes, files, retention period and disposal plan, trace log, role, user, authority and right assignment;
3) mode changed in the form the relevant regulations of various test data in electronic document management system functional requirement is described as some Rule of judgment, and by all Rule of judgment stored in rule base;
4) adopt mode map and matching process, from the data base management system (DBMS) and file system of electronic document management system, obtain test data set, and set up between target data set in test data set and electronic document management system and dynamically associate;
5) each test data stored in electronic document management system is traveled through, and corresponding Rule of judgment is tested test data set in calling rule storehouse, find the defect that each test data that test data is concentrated exists, and the defect each test data existed carries 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, judge whether e-file attended operation meets the requirements in data hierarchy;
8) gather the defect with test data in statistical study electronic document management system, generate test report.
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 CN103761188A (en) | 2014-04-30 |
| CN103761188B true 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) |
Families Citing this family (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 |
| CN110275862B (en) * | 2019-06-26 | 2021-07-30 | 北京字节跳动网络技术有限公司 | Method and device for counting number of created documents |
| CN111506513B (en) * | 2020-06-04 | 2021-06-22 | 南京大学 | File system testing method based on hierarchical model |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8595559B2 (en) * | 2007-08-23 | 2013-11-26 | International Business Machines Corporation | Method and apparatus for model-based testing of a graphical user interface |
| CN102650966B (en) * | 2011-02-24 | 2016-01-27 | 王轶辰 | A kind of embedded software test method of Reuse-Oriented and test macro thereof |
| CN102331970B (en) * | 2011-07-28 | 2013-11-27 | 北京航空航天大学 | Safety critical system-oriented automatic testing resource management method and platform |
| CN102411540B (en) * | 2012-01-12 | 2014-01-15 | 王轶辰 | Automatic management system of workflow-based common software testing process |
-
2014
- 2014-02-08 CN CN201410045487.5A patent/CN103761188B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN103761188A (en) | 2014-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108376376B (en) | BIM model-based construction engineering quality management standardization method | |
| CN106815326B (en) | System and method for detecting consistency of data table without main key | |
| CN109948134A (en) | A kind of report automatic generation method, system and electronic equipment and storage medium | |
| CN101221530B (en) | Method for automatically leading in test cases | |
| CN108062484A (en) | A kind of classification stage division based on data sensitive feature and database metadata | |
| CN104598376A (en) | Data driving layered automation test system and method | |
| CN109542967A (en) | Smart city data-sharing systems and method based on XBRL standard | |
| CN107609188A (en) | Data syn-chronization method of calibration based on GoldenGate | |
| CN104298595A (en) | Automatic testing method and testing system | |
| CN102708213A (en) | Method for realizing BOM (Bill of Material) information transmission between PDM (Product Data Management) system and ERP (Enterprise Resource Planning) system | |
| CN102043719A (en) | Method for testing IEC61850 configuration description file | |
| CN106528828A (en) | Multi-dimensional checking rule-based data quality detection method | |
| CN106503158A (en) | Method of data synchronization and device | |
| CN103761188B (en) | A kind of automated testing method of electronic document management system | |
| CN104298726A (en) | BMS data storage system and method based on database | |
| CN102254029A (en) | View-based data access system and method | |
| CN110866024B (en) | Vector database increment updating method and system | |
| CN104252519A (en) | Increment updating method of topographic database | |
| CN104899143A (en) | Software peer review system realizing device for providing DM (Data Mining) | |
| CN103593449A (en) | Method and system for recycling database resources | |
| CN115617776A (en) | Data management system and method | |
| CN103577550A (en) | Grid equipment data verification method | |
| CN111984796A (en) | Automatic compliance checking method based on standard knowledge graph IFC model | |
| CN115576950A (en) | Report generation method based on JSON configuration file | |
| CN105183966A (en) | Database-based method for fast drawing instrument plane arrangement diagram |
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 |