CN103064780A - Software testing method and device thereof - Google Patents

Software testing method and device thereof Download PDF

Info

Publication number
CN103064780A
CN103064780A CN201110316922XA CN201110316922A CN103064780A CN 103064780 A CN103064780 A CN 103064780A CN 201110316922X A CN201110316922X A CN 201110316922XA CN 201110316922 A CN201110316922 A CN 201110316922A CN 103064780 A CN103064780 A CN 103064780A
Authority
CN
China
Prior art keywords
test
testing process
branch
priority
testing
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
Application number
CN201110316922XA
Other languages
Chinese (zh)
Other versions
CN103064780B (en
Inventor
郑兴杰
江进朋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201110316922.XA priority Critical patent/CN103064780B/en
Publication of CN103064780A publication Critical patent/CN103064780A/en
Priority to HK13107124.9A priority patent/HK1180067A1/en
Application granted granted Critical
Publication of CN103064780B publication Critical patent/CN103064780B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Debugging And Monitoring (AREA)

Abstract

The invention provides a software testing method and a device of the software testing method. The software testing method includes the flowing steps: obtaining use ratio of all the testing processes in the preset period of time, and arranging priority level of all the testing processes according to the use ratio of the testing processes in the preset period of time; obtaining use ratio of all the testing branches of the testing processes in the preset period of time, and arranging the priority level of all the testing branches according to the use ratio of all the testing branches in the preset period of time; testing all the testing processes according to the priority level of all the testing processes, and testing all the testing branches of the testing processes according to the priority level of the testing branches.

Description

A kind of method of software test and device
Technical field
The application relates to the technical field of measurement and test of computer software, particularly relates to the method for software test, and, a kind of device of software test.
Background technology
Large-scale software includes a plurality of flow processs usually, and each flow process includes a plurality of branches, and flow process or the branch of part are in different systems.For this type of complicated project, industry generally adopts matrix method to carry out test analysis, and test process is as follows:
At first each flow process is assembled in the matrix and carries out test analysis; Then each matrix service based analysis is tested respectively each branch of single flow process; At last, tester and developer analyze and link up test result according to project demands and design documentation.
The problem that above prior art exists is:
1, the test emphasis is unclear, and priority is unclear, if important flow process or branch have been placed at last tests, and after pinpointing the problems, needs the more time of cost to revise, and can cause so the whole testing progress time to lengthen, and testing efficiency is lower.
2, because the large test object includes a plurality of flow processs, each flow process includes a plurality of branches, and relate to a plurality of systems, improper arrangement when using matrix method to test one by one, cause easily in the test process occurring situation that a flow process or branch's repeated test or test are omitted, thereby break down after causing project to be reached the standard grade.
3, owing to the complicacy of tested object, the cost that tester and developer link up can be very high, is difficult to the testing progress of the project of holding in the test process.
Therefore, need at present the urgent technical matters that solves of those skilled in the art to be exactly: a kind of method and device of software test are provided, so that whole test process orderliness is clear, emphasis is clearly demarcated, and is easy to link up and management.
Summary of the invention
The application's technical matters to be solved provides a kind of method of software test, so that whole test process orderliness is clear, emphasis is clearly demarcated, and is easy to link up and management.
Accordingly, the application also provides a kind of device of software test, in order to guarantee said method implementation and application in practice.
In order to address the above problem, the application discloses a kind of method for testing software, comprising:
Obtain each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked;
Obtain in the described testing process each test branch in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked;
Priority according to described testing process is tested each testing process, and tests according to the priority of described test branch for each test branch in the described testing process.
Preferably, described priority according to testing process is tested each testing process, and the step of testing according to the priority of test branch for each test branch in the testing process comprises:
According to the priority of each testing process, create the test catalogue, comprise the information of the testing process that sorts by priority in the described test catalogue, and, the information of the test branch that sorts by priority in the testing process;
Successively each testing process is tested according to the ordering in the described test catalogue;
Successively each test branch in the testing process is tested according to the ordering in the described test catalogue.
Preferably, before described step of successively each testing process being tested according to the ordering in the test catalogue, described method also comprises:
Described test catalogue and corresponding test case are uploaded to SVN, VSS or CVS server;
After described step of successively each test branch in the testing process being tested according to the ordering in the test catalogue, described method also comprises:
Record test data, and described test data is uploaded to SVN, VSS or CVS server.
Preferably, described each testing process that obtains is in the utilization factor of Preset Time section, and according to the utilization factor of testing process in the Preset Time section, the step of the priority of each testing process that is ranked comprises:
From test database, extract described testing process invoked number of times in the Preset Time section;
Sort from high to low according to each testing process invoked number of times in the Preset Time section, form corresponding priority.
Preferably, described each test branch of obtaining in the testing process is in the utilization factor of Preset Time section, and according to the utilization factor of each test branch in the Preset Time section, the step of the priority of each test branch that is ranked comprises:
From test database, extract each test branch invoked number of times in the Preset Time section in the described testing process;
Sort from high to low according to each test branch invoked number of times in the Preset Time section, form corresponding priority.
Preferably, described test catalogue also comprises: the performance of each testing process, test role, test account, test access and test result; Described test catalogue is with form, and the form of text or sectional drawing is showed.
Preferably, described method also comprises:
Whether the test branch of not surveying is arranged according to described test data inspection;
If have, then the described test branch of not surveying is tested.
The application also provides a kind of software testing device, comprising:
Testing process prioritization module is used for obtaining each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked;
Test branch prioritization module is used for obtaining each test branch of described testing process in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked;
Test module is used for according to the priority of described testing process each testing process being tested, and tests according to the priority of described test branch for each test branch in the described testing process.
Preferably, described test module comprises:
Test directory creating submodule is used for the priority according to each testing process, creates the test catalogue, comprises the information of the testing process that sorts by priority in the described test catalogue, and, the information of the test branch that sorts by priority in the testing process;
The flow testing submodule is used for successively each testing process being tested according to the ordering of described test catalogue;
The branch testing submodule is used for successively each test branch in the testing process being tested according to the ordering of described test catalogue.
Preferably, before the flow testing submodule, described device also comprises:
The test catalogue is uploaded submodule, is used for described test catalogue and corresponding test case are uploaded to SVN, VSS or CVS server;
After the branch testing submodule, described device also comprises:
Test data is uploaded submodule, is used for record test data, and described test data is uploaded to SVN, VSS or CVS server.
Compared with prior art, the application comprises following advantage:
The application is according to each testing process and the utilization factor of each test branch in the Preset Time section, the priority of be ranked corresponding flow process or branch, and the test emphasis is clear, is beneficial to the raising testing efficiency.According to the test catalogue each testing process and each test branch are tested, whole test analysis process orderliness is clear, will test catalogue with form, and the form of text or sectional drawing is showed, so that the tester is very clear to current progress.
In addition, will utilize SVN, VSS or CVS server to carry out the management of test case and test data in test process, the tester has reduced the communication cost between the tester in test process can upgrade in time test case or test data; Be completed rear test catalogue and can directly be used as service profile, reduced tester's document maintenance cost.
Description of drawings
Fig. 1 is the process flow diagram of a kind of method for testing software embodiment 1 of the application;
Fig. 2 is the process flow diagram of a kind of method for testing software embodiment 2 of the application;
Fig. 3 is the structured flowchart of a kind of software testing device embodiment 1 of the application;
Fig. 4 is the structured flowchart of a kind of software testing device embodiment 2 of the application.
Embodiment
For above-mentioned purpose, the feature and advantage that make the application can become apparent more, below in conjunction with the drawings and specific embodiments the application is described in further detail.
Large software includes a plurality of flow processs more, and each flow process has comprised a plurality of branches, and the flow process among the application refers to workflow, and workflow refers to that the active flow of work item to order, comprises working link, step and program in the practical work process.Such as the flow process of asking for leave in the work, it is exactly a workflow.Branch refers to branches different in workflow, as, in all flow processs of asking for leave, please the leave of absence may need manager to examine in the above, calling in sick only needs supervisor to examine, although all be to walk to ask for leave flow process, the branch of walking is different.
What in the prior art software is tested employing is matrix method, indefinite for some demands, the large software of multiple-limb, multipaths and cross-system can exist test improper arrangement when utilizing matrix method to test, the test emphasis is unclear, links up the large problem of cost.
The embodiment of the present application is, by obtaining each testing process and the utilization factor of each test branch in the Preset Time section, and according to the be ranked priority of corresponding flow process or branch of this utilization factor, then according to priority each testing process and each test branch are tested, thereby so that whole test process orderliness is clear, emphasis is clearly demarcated, and is easy to link up and management.
With reference to figure 1, show the process flow diagram of a kind of method for testing software embodiment 1 of the application, specifically can may further comprise the steps:
Step 101, obtain each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked.
In a preferred embodiment of the present application, described step 101 can comprise:
Substep S11, from test database, extract described testing process invoked number of times in the Preset Time section.
In the present embodiment, the testing process utilization factor can be presented as invoked number of times in the Preset Time section, invoked number of times can extract in the corresponding database of software, for example, can extract the SQL statement of Oracle client call testing process, SQL statement has comprised the invoked information of this testing process, and the number of the SQL statement that statistics is extracted is the invoked number of times of this testing process.
Certainly, only as example, in concrete realization, those skilled in the art can take any method that can realize to remove to obtain the number of times that is called to said method, and the application does not limit this.
Substep S 12, sort from high to low according to each testing process invoked number of times in the Preset Time section, form corresponding priority.
After more than having extracted the invoked number of times of testing process, can from high to low each testing process be sorted according to the number of times that is called, sorting forward namely is that priority ratio is higher, the priority ratio of rank after is lower, for the lower testing process of priority ratio, can decide according to actual conditions and want to test, thus can be in situation it is pressed for time, preferentially finish the test of important testing process, avoid the important flow process of test leakage to affect whole test result.
Step 102, obtain in the described testing process each test branch in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked.
In a preferred embodiment of the present application, described step 102 can comprise:
Substep S21, from test database, extract each test branch invoked number of times in the Preset Time section in the described testing process;
Substep S22, sort from high to low according to each test branch invoked number of times in the Preset Time section, form corresponding priority.
Obtain test branch be called the method for number of times can be the same with the method for testing process, after the number of times that is called sorted, can obtain the priority of test branch, the forward first survey of sorting, the rear survey after ordering is leaned on.
Step 103, according to the priority of described testing process each testing process is tested, and tested according to the priority of described test branch for each test branch in the described testing process.
In a preferred embodiment of the present application, described step 103 can comprise:
Substep S31, according to the priority of each testing process, create the test catalogue, comprise the information of the testing process that sorts by priority in the described test catalogue, and, the information of the test branch that sorts by priority in the testing process.
Substep S32, successively each testing process is tested according to the ordering in the described test catalogue;
Substep S33, successively each test branch in the testing process is tested according to the ordering in the described test catalogue.
More than obtained after the priority of each testing process and test branch, can be according to the information of the testing process that sorts by priority, and the information of the test branch that sorts by priority in the testing process is set up the test catalogue, at first can set up according to testing process priority the test catalogue of testing process, the priority of the test branch that then can comprise according to each testing process is set up the test catalogue of corresponding each testing process.
In a kind of preferred embodiment of the application, described test catalogue can also comprise: the performance of each testing process, test role, test account, test access and test result.After according to the test catalogue testing process and test branch being tested, the above information in the test catalogue just can improve.
In concrete realization, described test catalogue is with form, the form of text or sectional drawing is showed, corresponding can use tabulation software Excle, word processor Word or grab screen instrument FsCapture, and tester or developer can directly be known the test details from the page of showing.
In the following example, can set up following Excle formal testing catalogue according to the priority of testing process:
Figure BDA0000099628440000071
Figure BDA0000099628440000081
In concrete realization, the technique of expression of priority has multiple, can represent obvious color, can with priority high come front etc., upper table is the result after according to priority sorting from high to low.
Then can set up according to the priority of test branch the test catalogue of corresponding certain testing process, in the following example:
Figure BDA0000099628440000082
This catalogue page can be related with corresponding testing process foundation, thereby make things convenient for searching of branch and flow process, can arrange to return catalogue page corresponding to testing process after the Home link is convenient to test branch in above-mentioned table, and orderliness is more clear.
After having set up the test catalogue, successively each testing process is tested according to the ordering in the described test catalogue, and the process of successively each test branch in the testing process being tested according to the ordering in the described test catalogue, that is:
According to the ordering of testing process in the test catalogue, extract successively testing process as tested object.
Testing process for current extraction, ordering according to the test branch of correspondence, successively test branch is tested, after each branch tested, whether the test branch of judging described extraction is last of the test branch that comprises of corresponding testing process, if not last, then extracting next test branch according to the ordering of test branch tests, if last, then finish the test to current testing process, and according to the ordering of testing process, extract next testing process and test.For next testing process, equally also be to test one by one according to the ordering of the test branch of correspondence.
When the test of each testing process finishes, need to judge that current testing process is last during corresponding testing process sorts, if last, then finish test, if not last then extracts next testing process according to the ordering of testing process and tests.
In concrete realization, before described step of successively each testing process being tested according to the ordering in the test catalogue, can also comprise:
Substep, described test catalogue and corresponding test case are uploaded to SVN, VSS or CVS server.
After described step of successively each test branch in the testing process being tested according to the ordering in the test catalogue, can also comprise:
Substep, record test data, and described test data is uploaded to SVN, VSS or CVS server.
SVN, VSS and CVS server are the code release management softwares, in this server, file can be returned to any version in the past, and can know which modification is data made by checking history, and the operator who revises.The test case of the correspondence that needs in test catalogue and the test process to use is uploaded to SVN, VSS or CVS server, can make things convenient for the tester that test case is managed.In test process, test data is uploaded onto the server, can realize data sharing, intersect between the tester when convenient test is finished and check.In practice, if when having a plurality of testers to test in the project, different testers can be recorded in the own test data of using in the test case in test process, the 2nd takes turns, the 3rd takes turns the test data validation test result that test can directly be recorded according to the first round, if the problem of tested flow process just notifies the developer to revise, if the problem of test case is just directly revised use-case.
With reference to figure 2, show the process flow diagram of a kind of method for testing software embodiment 2 of the application, specifically can may further comprise the steps:
Step 201, obtain each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked;
Step 202, obtain in the described testing process each test branch in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked;
Step 203, according to the priority of described testing process each testing process is tested, and tested according to the priority of described test branch for each test branch in the described testing process.
Whether step 204, the described test data inspection of foundation have the test branch of not surveying;
If step 205 has, then the described test branch of not surveying is tested.
When testing process and test branch are tested, test catalogue and test case can be uploaded onto the server, if the situation of test errors is not surveyed or occurred to certain test branch, so just there is not corresponding test data, therefore, can whether there be test data to judge whether after tested according to test branch.
In concrete realization, testing process that can this test branch is corresponding carries out mark, for example is labeled as redness and highlights.When checking, test case that can first checkout flow process if find markd testing process, represents namely that this flow process exists not survey branch.Then the test data of each branch of this flow process being checked, namely is test leakage branch without the branch of test data, can mend survey to it after checking out the test leakage branch.
After test was finished, tester and developer can check according to the test data of putting down in writing in the test catalogue together, determine whether the branch that test is omitted, if having, then the branch that does not survey are tested.
In sum, the application provides a kind of method for testing software, and according to each testing process and the utilization factor of each test branch in the Preset Time section, the priority of be ranked corresponding flow process or branch is so that the test emphasis is clear.According to the test catalogue each testing process and each test branch are tested, whole test analysis process orderliness is clear, will test catalogue with form, and the form of text or sectional drawing is showed, so that the tester is very clear to current progress.
In addition, will utilize SVN, VSS or CVS server to carry out the management of test case and test data in test process, the tester has reduced the communication cost between the tester in test process upgrade in time test case or test data; Be completed rear test catalogue and can directly be used as service profile, reduced tester's document maintenance cost.
For embodiment of the method, for simple description, so it all is expressed as a series of combination of actions, but those skilled in the art should know, the application is not subjected to the restriction of described sequence of movement, because according to the application, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in the instructions all belongs to preferred embodiment, and related action and module might not be that the application is necessary.
With reference to figure 3, show the structured flowchart of a kind of software testing device embodiment 1 of the application, specifically can comprise with lower module:
Testing process prioritization module 301 is used for obtaining each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked;
Test branch prioritization module 302 is used for obtaining each test branch of described testing process in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked;
Test module 303 is used for according to the priority of described testing process each testing process being tested, and tests according to the priority of described test branch for each test branch in the described testing process.
In a preferred embodiment of the present application, described test module can comprise:
Test directory creating submodule is used for the priority according to each testing process, creates the test catalogue, comprises the information of the testing process that sorts by priority in the described test catalogue, and, the information of the test branch that sorts by priority in the testing process;
The flow testing submodule is used for successively each testing process being tested according to the ordering of described test catalogue;
The branch testing submodule is used for successively each test branch in the testing process being tested according to the ordering of described test catalogue.
In a preferred embodiment of the present application, before the flow testing submodule, can also comprise:
The test catalogue is uploaded submodule, is used for described test catalogue and corresponding test case are uploaded to SVN, VSS or CVS server;
After the branch testing submodule, can also comprise:
Test data is uploaded submodule, is used for record test data, and described test data is uploaded to SVN, VSS or CVS server.
In a preferred embodiment of the present application, described testing process prioritization module can comprise:
The process invocation number of times extracts submodule, is used for extracting described testing process invoked number of times in the Preset Time section from test database;
Flow process priority forms submodule, is used for sorting from high to low according to each testing process invoked number of times in the Preset Time section, forms corresponding priority.
In a preferred embodiment of the present application, described test branch prioritization module can comprise:
Branch's call number is extracted submodule, is used for extracting each test branch invoked number of times in the Preset Time section the described testing process from test database;
Branch's priority forms submodule, is used for sorting from high to low according to each test branch invoked number of times in the Preset Time section, forms corresponding priority.
In a preferred embodiment of the present application, described test catalogue can also comprise: the performance of each testing process, test role, test account, test access and test result; Described test catalogue can be with form, and the form of text or sectional drawing is showed.
With reference to figure 4, show the structured flowchart of a kind of software testing device embodiment 2 of the application, specifically can comprise with lower module:
Testing process prioritization module 401 is used for obtaining each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked;
Test branch prioritization module 402 is used for obtaining each test branch of described testing process in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked;
Test module 403 is used for according to the priority of described testing process each testing process being tested, and tests according to the priority of described test branch for each test branch in the described testing process.
Test branch checking module 404 is used for according to described test data inspection whether the test branch of not surveying being arranged;
Test branch is mended and is surveyed module 405, if be used for having, then the described test branch of not surveying is tested.
Because described device embodiment is substantially corresponding to aforementioned embodiment of the method illustrated in figures 1 and 2, so not detailed part in the description of present embodiment can referring to the related description in the previous embodiment, just not given unnecessary details at this.
The application can be used in numerous general or special purpose computingasystem environment or the configuration.For example: personal computer, server computer, handheld device or portable set, plate equipment, multicomputer system, the system based on microprocessor, set top box, programmable consumer-elcetronics devices, network PC, small-size computer, mainframe computer, comprise distributed computing environment of above any system or equipment etc.
The application can describe in the general context of the computer executable instructions of being carried out by computing machine, for example program module.Usually, program module comprises the routine carrying out particular task or realize particular abstract data type, program, object, assembly, data structure etc.Also can in distributed computing environment, put into practice the application, in these distributed computing environment, be executed the task by the teleprocessing equipment that is connected by communication network.In distributed computing environment, program module can be arranged in the local and remote computer-readable storage medium that comprises memory device.
At last, also need to prove, in this article, relational terms such as the first and second grades only is used for an entity or operation are made a distinction with another entity or operation, and not necessarily requires or hint and have the relation of any this reality or sequentially between these entities or the operation.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby not only comprise those key elements so that comprise process, method, article or the equipment of a series of key elements, but also comprise other key elements of clearly not listing, or also be included as the intrinsic key element of this process, method, article or equipment.Do not having in the situation of more restrictions, the key element that is limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.
More than a kind of method for testing software that the application is provided, and, a kind of software testing device is described in detail, used specific case herein the application's principle and embodiment are set forth, the explanation of above embodiment just is used for helping to understand the application's method and core concept thereof; Simultaneously, for one of ordinary skill in the art, the thought according to the application all will change in specific embodiments and applications, and in sum, this description should not be construed as the restriction to the application.

Claims (10)

1. a method for testing software is characterized in that, comprising:
Obtain each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked;
Obtain in the described testing process each test branch in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked;
Priority according to described testing process is tested each testing process, and tests according to the priority of described test branch for each test branch in the described testing process.
2. method according to claim 1 is characterized in that, described priority according to testing process is tested each testing process, and the step of testing according to the priority of test branch for each test branch in the testing process comprises:
According to the priority of each testing process, create the test catalogue, comprise the information of the testing process that sorts by priority in the described test catalogue, and, the information of the test branch that sorts by priority in the testing process;
Successively each testing process is tested according to the ordering in the described test catalogue;
Successively each test branch in the testing process is tested according to the ordering in the described test catalogue.
3. method according to claim 1 and 2 is characterized in that, before described step of successively each testing process being tested according to the ordering in the test catalogue, also comprises:
Described test catalogue and corresponding test case are uploaded to SVN, VSS or CVS server;
After described step of successively each test branch in the testing process being tested according to the ordering in the test catalogue, also comprise:
Record test data, and described test data is uploaded to SVN, VSS or CVS server.
4. method according to claim 1 is characterized in that, described each testing process that obtains is in the utilization factor of Preset Time section, and according to the utilization factor of testing process in the Preset Time section, the step of the priority of each testing process that is ranked comprises:
From test database, extract described testing process invoked number of times in the Preset Time section;
Sort from high to low according to each testing process invoked number of times in the Preset Time section, form corresponding priority.
5. method according to claim 4 is characterized in that, described each test branch of obtaining in the testing process is in the utilization factor of Preset Time section, and according to the utilization factor of each test branch in the Preset Time section, the step of the priority of each test branch that is ranked comprises:
From test database, extract each test branch invoked number of times in the Preset Time section in the described testing process;
Sort from high to low according to each test branch invoked number of times in the Preset Time section, form corresponding priority.
6. method according to claim 5 is characterized in that, described test catalogue also comprises: the performance of each testing process, test role, test account, test access and test result; Described test catalogue is with form, and the form of text or sectional drawing is showed.
7. according to claim 3 or 6 described methods, it is characterized in that, also comprise:
Whether the test branch of not surveying is arranged according to described test data inspection;
If have, then the described test branch of not surveying is tested.
8. a software testing device is characterized in that, comprising:
Testing process prioritization module is used for obtaining each testing process in the utilization factor of Preset Time section, and according to the utilization factor of described testing process in the Preset Time section, the priority of each testing process that is ranked;
Test branch prioritization module is used for obtaining each test branch of described testing process in the utilization factor of Preset Time section, and according to the utilization factor of described each test branch in the Preset Time section, the priority of each test branch that is ranked;
Test module is used for according to the priority of described testing process each testing process being tested, and tests according to the priority of described test branch for each test branch in the described testing process.
9. device according to claim 8 is characterized in that, described test module comprises:
Test directory creating submodule is used for the priority according to each testing process, creates the test catalogue, comprises the information of the testing process that sorts by priority in the described test catalogue, and, the information of the test branch that sorts by priority in the testing process;
The flow testing submodule is used for successively each testing process being tested according to the ordering of described test catalogue;
The branch testing submodule is used for successively each test branch in the testing process being tested according to the ordering of described test catalogue.
10. according to claim 8 or 9 described devices, it is characterized in that, before the flow testing submodule, also comprise:
The test catalogue is uploaded submodule, is used for described test catalogue and corresponding test case are uploaded to SVN, VSS or CVS server;
After the branch testing submodule, also comprise:
Test data is uploaded submodule, is used for record test data, and described test data is uploaded to SVN, VSS or CVS server.
CN201110316922.XA 2011-10-18 2011-10-18 A kind of method of software test and device Active CN103064780B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201110316922.XA CN103064780B (en) 2011-10-18 2011-10-18 A kind of method of software test and device
HK13107124.9A HK1180067A1 (en) 2011-10-18 2013-06-19 Method and device for testing software

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110316922.XA CN103064780B (en) 2011-10-18 2011-10-18 A kind of method of software test and device

Publications (2)

Publication Number Publication Date
CN103064780A true CN103064780A (en) 2013-04-24
CN103064780B CN103064780B (en) 2016-06-01

Family

ID=48107413

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201110316922.XA Active CN103064780B (en) 2011-10-18 2011-10-18 A kind of method of software test and device

Country Status (2)

Country Link
CN (1) CN103064780B (en)
HK (1) HK1180067A1 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104778179A (en) * 2014-01-14 2015-07-15 阿里巴巴集团控股有限公司 Data migration test method and system
CN105487970A (en) * 2014-10-13 2016-04-13 中国移动通信集团公司 Interface display method and apparatus
CN105610878A (en) * 2014-10-30 2016-05-25 腾讯科技(深圳)有限公司 Directory uploading method, data releasing method, terminal and server
CN106033386A (en) * 2015-03-10 2016-10-19 联想(北京)有限公司 A software testing method and an electronic apparatus
CN108616410A (en) * 2016-12-09 2018-10-02 北京京东尚科信息技术有限公司 Information calibration method and device
CN110262933A (en) * 2015-09-10 2019-09-20 阿里巴巴集团控股有限公司 Test method, test device and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080184206A1 (en) * 2007-01-31 2008-07-31 Oracle International Corporation Computer-implemented methods and systems for generating software testing documentation and test results management system using same
CN101847120A (en) * 2010-03-31 2010-09-29 中兴通讯股份有限公司 Design method and system of test case
CN102063376A (en) * 2011-02-16 2011-05-18 哈尔滨工程大学 Test case selection method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080184206A1 (en) * 2007-01-31 2008-07-31 Oracle International Corporation Computer-implemented methods and systems for generating software testing documentation and test results management system using same
CN101847120A (en) * 2010-03-31 2010-09-29 中兴通讯股份有限公司 Design method and system of test case
CN102063376A (en) * 2011-02-16 2011-05-18 哈尔滨工程大学 Test case selection method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
李朝辉等: "业务流程测试方法的研究", 《仪器仪表用户》, vol. 16, no. 5, 31 May 2009 (2009-05-31), pages 61 - 62 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104778179A (en) * 2014-01-14 2015-07-15 阿里巴巴集团控股有限公司 Data migration test method and system
CN104778179B (en) * 2014-01-14 2019-05-28 阿里巴巴集团控股有限公司 A kind of Data Migration test method and system
CN105487970A (en) * 2014-10-13 2016-04-13 中国移动通信集团公司 Interface display method and apparatus
CN105487970B (en) * 2014-10-13 2019-01-08 中国移动通信集团公司 A kind of method for showing interface and device
CN105610878A (en) * 2014-10-30 2016-05-25 腾讯科技(深圳)有限公司 Directory uploading method, data releasing method, terminal and server
CN106033386A (en) * 2015-03-10 2016-10-19 联想(北京)有限公司 A software testing method and an electronic apparatus
CN110262933A (en) * 2015-09-10 2019-09-20 阿里巴巴集团控股有限公司 Test method, test device and storage medium
CN110262933B (en) * 2015-09-10 2023-05-02 阿里巴巴集团控股有限公司 Test method, test device, and storage medium
CN108616410A (en) * 2016-12-09 2018-10-02 北京京东尚科信息技术有限公司 Information calibration method and device

Also Published As

Publication number Publication date
CN103064780B (en) 2016-06-01
HK1180067A1 (en) 2013-10-11

Similar Documents

Publication Publication Date Title
US11379348B2 (en) System and method for performing automated API tests
WO2020233330A1 (en) Batch testing method, apparatus, and computer-readable storage medium
CN110321113B (en) Integrated assembly line system taking project batches as standards and working method thereof
US20230393846A1 (en) System and Method For Automated Cross-Application Dependency Mapping
CN106951369B (en) Management method and device for joint debugging test
CN108763091B (en) Method, device and system for regression testing
CN103064780A (en) Software testing method and device thereof
CN110389896A (en) Code automated analysis and test method, device and computer readable storage medium
CN102236672A (en) Method and device for importing data
CN108959067B (en) Method and device for testing search engine and computer readable storage medium
CN102135938A (en) Software product testing method and system
CN202339542U (en) Software product test system
CN110297760A (en) Building method, device, equipment and the computer readable storage medium of test data
CN104679500B (en) Method and device for realizing automatic generation of entity class
CN102760096A (en) Test data generation method, unit testing method and unit testing system
CN105912461A (en) Test method and system for software agility
CN103186463B (en) Determine the method and system of the test specification of software
CN115016321A (en) Hardware-in-loop automatic testing method, device and system
CN108694108A (en) A kind of method and apparatus of iOS crash datas classification and statistics
CN110795332A (en) Automatic testing method and device
CN111240981A (en) Interface testing method, system and platform
CN113448869B (en) Method and device for generating test case, electronic equipment and computer readable medium
CN113032256A (en) Automatic test method, device, computer system and readable storage medium
CN107273293B (en) Big data system performance test method and device and electronic equipment
CN102279798B (en) Software testing method and system based on point function driving

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1180067

Country of ref document: HK

C14 Grant of patent or utility model
GR01 Patent grant
REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1180067

Country of ref document: HK