CN101339532A - An automated testing method and device for a web application system - Google Patents

Abstract

The invention discloses an automatic testing method and device for a Web application system, in order to solve the problems of inflexibility, low reuse rate, large testing workload and low efficiency of existing Web application automatic testing tools. The method includes: decomposing the business process of the Web application system into a combination of atomic processes; creating an automated test component corresponding to each atomic process; reading a pre-configured test case, in which the atomic process sequence is recorded; corresponding to the sequence Each atomic process in calls the corresponding test component to test the Web application system. The component-based automated testing method can flexibly adapt to the automated testing of various complex and changeable business processes, improves the versatility of the test program, greatly improves the efficiency of automated testing, and reduces the workload of testing; moreover, due to the The business process is subdivided into the atomic process, so the atomic process with errors can be tracked and located, the error point can be found in time, and the test effect can be improved.

Description

An automated testing method and device for a web application system

technical field

The invention relates to the field of software testing, in particular to an automatic testing method and device for a Web application system.

Background technique

Software testing is an important part of software development and post-maintenance process. Its testing process runs through all aspects of software engineering. The purpose of testing is to find problems in the program and improve software quality; it is also used for upgrade testing after the software is put into use. For example, after the software is patched, a regression test is required to ensure the correctness of the original function.

Web application systems must be tested before release and after upgrade, including performance testing and functional testing. For functional testing, it is mainly to test various functions of the Web application. Since each function has corresponding one or more business processes, functional testing is to test various business processes of the Web application system. Wherein, the business process refers to a collection sequence of operations with a sequential execution order, and the operation sequences of different business processes are also different.

Existing interface automation testing tools are mainly script-interpreted automated testing software represented by Mercury Winrunner and IBM RationalRobot. process to achieve the purpose of automated testing.

For example, the application document of Chinese Patent No. 200410086041.3 discloses an automated test system based on script interpretation tools. The system solves the problem of test case reuse through the management of test cases. The balanced management of resources has strong flexibility and can meet various business needs. Chinese Patent No. 200410054163.4 discloses an automated test auxiliary system and corresponding software automatic test system. The patent defines structured test cases, adopts dynamic execution of test cases and delay loading technology, and converts test cases into commercial tests. The test script of the software drives the commercial test software to execute the test and records the test results; the system improves the efficiency of test case writing and execution.

The above test method has the following problems:

First, it is difficult to support the ever-changing specific business processes of different web application systems. Because of the different business processes of web applications, test scripts need to be written or recorded separately, so the script writing is inflexible and the reuse rate of scripts is low; moreover, every time Both need to write or record a large number of scripts, and the testing workload is very heavy;

Second, it is difficult to track and locate test error points and analyze the cause of errors, because the existing automated testing technology does not decompose complex business processes. If an error is found in a certain business process during test execution, it can only be located in the business process, which is difficult. Locate specific sub-business processes in a refined manner.

Contents of the invention

The technical problem to be solved by the present invention is to provide an automated testing method and device for a Web application system to solve the problems of inflexibility, low reuse rate, heavy testing workload and low efficiency of existing automated testing tools for Web applications.

In order to solve the above technical problems, according to the specific embodiments provided by the invention, the invention discloses the following technical solutions:

An automated testing method for a web application system, comprising:

Decompose the business process of the Web application system into a combination of atomic processes;

Create automated test components corresponding to each atomic process;

Read pre-configured test cases in which atomic process sequences are recorded;

Corresponding to each atomic process in the sequence, a corresponding test component is invoked to test the Web application system.

Wherein, before calling the test component, it also includes: pre-checking whether the data of the read test case conforms to the specification, and checking whether the called test component exists.

The method also includes: comparing the return value of the test component execution with the expected result, if they are the same, then execute the next test component; if they are not the same, record the error location and related data, and execute the next test case; after recording the above comparison test results.

The method also includes: analyzing the test results and generating a test report.

The method further includes: tracking and recording the execution of each execution step.

The method further includes: combining the test components included in the common business process into a composite component, and calling the composite component directly when invoking.

An automated testing device for a web application system, comprising:

The automated test component library is a collection of automated test components. Each test component corresponds to the creation of atomic processes, and the atomic processes are combined into the business processes of the Web application system;

The case reading module is used to read the pre-configured test case, and the atomic process sequence is recorded in the test case;

The test control module is used to correspond to each atomic process in the sequence, call the corresponding test component, and test the Web application system.

The device also includes: a case parsing module, used for pre-checking whether the data of the read test case conforms to the specification, and checking whether the called test component exists.

Preferably, the test control module includes: a test unit, used to correspond to each atomic process in the sequence, call the corresponding test component, and test the Web application system; a control unit, used to execute the test component to return a value Compared with the expected results, if they are the same, the test unit is triggered to execute the next test component; if not, the next test case is executed; the record unit is used to record the test results after the above comparison, and record the error location and related data.

The device also includes: a test result analysis module for analyzing test results and generating test reports.

The device also includes: a log tracking module, used to track and record the execution of each test step.

An automated testing component comprising:

Component implementation, used to provide corresponding test functions corresponding to the atomic process;

The interface is used to provide a connection between the external module and the component implementation, and the external module calls the component implementation through the interface, or the component implementation calls the external module through the interface.

The component further includes: a component specification, which is used to provide a description of the component.

Preferably, the component includes an atomic component and a composite component, wherein the atomic component corresponds to an atomic process, and the composite component is a combination of multiple atomic components.

According to the specific embodiments provided by the invention, the invention discloses the following technical effects:

First, refine the complex business processes of Web applications to the smallest unit and decompose them into multiple relatively independent atomic processes. Various business processes are combinations of different atomic processes. Create corresponding automated test components for atomic processes. When executing automated test cases, the corresponding automated test components are dynamically invoked according to the sequence of atomic processes configured in the case, so as to realize automated testing of web applications driven by business processes.

The component-based automated testing method can flexibly adapt to the automated testing of various complex and changeable business processes, improves the versatility of the testing program, greatly improves the efficiency of automated testing, and reduces the workload of testing; moreover, due to the The business process is subdivided into the atomic process, so the atomic process with errors can be tracked and located, the error point can be found in time, and the test effect can be improved.

Secondly, based on the standard software component model, this method proposes a unified automation test component interface specification, which makes the automation test components easy to transplant and upgrade, and the components developed by different personnel can be easily transplanted to achieve the aggregation of more automated tests The purpose of component resources is to greatly improve the efficiency and flexibility of the development and maintenance of automated testing tools.

Thirdly, during the test execution process, if the test result of the atomic process is inconsistent with the expected result, the execution of the subsequent atomic process will be terminated, and the test of the entire business process will be directly exited. In this way, the wrong test result data can be prevented from being continuously used in the subsequent test process, causing abnormal operation and errors of the test software, and improving the test efficiency and the robustness of the system.

Description of drawings

Fig. 1 is the flow chart of the steps of the automated testing method provided by the embodiment of the present invention;

Fig. 2 is the flow chart of the automated testing method of the present invention taking the credit adjustment business as an example;

Fig. 3 is a structural diagram of an automated testing device provided by an embodiment of the present invention;

Fig. 4 is a structural diagram of an automated testing component provided by an embodiment of the present invention.

Detailed ways

In order to make the above objects, features and advantages of the present invention more comprehensible, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

An embodiment of the present invention proposes a component-based automated testing method for a Web application business process. The method decomposes the complex business of the Web application into a plurality of relatively independent atomic processes, and designs corresponding automated test components for these atomic business processes. When the automated test tool executes the automated test case, it The sequence dynamically invokes the corresponding automated testing components, so as to realize the automated testing of Web applications driven by business processes.

In the embodiment of the present invention, the concept of components is introduced. A software component is a software architecture-oriented reusable software module, a software module with standardized interfaces and explicit context dependencies, which can be released independently and assembled. Components should be easy to configure in different contexts through parameterization, and can work in different hardware operating platforms and software environments.

The component-based automated testing method is a method for assembling and testing web application business processes using automated test components. After decomposing each business process into atomic processes, you only need to simply call each test component "assembly" when configuring the test case Just get up. For example, a business process includes four sub-business processes A, B, C, and D. In order to fully cover and test the business process, testers may need to test the following three processes: A->B->C->D, A- >B->D, A->C->D. If the test method described in the prior art is adopted, the test tool needs to develop test programs for the three processes respectively. When the needs of the testers change, such as when another process A->D needs to be tested, the previously developed test program cannot "On Demand" too. However, the component-based testing method in the embodiment of the present invention aims at the four sub-business processes, respectively making corresponding automated testing components a, b, c, and d, and the testers can "assemble" the testing components according to the needs of the business during the test. Test different business processes.

In practical applications, web application systems usually target a certain type of business, and many of the same basic operations exist when dealing with the same type of business. Therefore, the atomic process decomposed into the smallest unit is not only applicable to one business process, but also applicable to other business processes of this type. process. Based on the above principles, when designing automated test components, reusable test components are created for the same type of business modules, and different component combinations can test various possible business processes of the business. The design of test components is very important to the testing process, because components that can be reused many times can improve the development and maintenance efficiency and flexibility of automated test tools.

The process of invoking the test component to test the Web application system will be described in detail below. Referring to Fig. 1, it is a flowchart of the steps of the automated testing method.

Step 101, configure a test case. It needs to be configured for each business process, because the test case is completely related to the business process under test. If the business process changes, the test case should be modified accordingly. The main data structure of the test case is shown in Table 1:

Chinese data name data name type length illustrate case number CaseID integer autonumber 4 The unique number of the test case Tested module TestModule number 4 A foreign key is associated to the test module table Atomic Business Process Sequence TestFlow text Unlimited This field indicates the sequence of test business sub-processes, which consists of numbers of atomic business processes separated by separators.

Test pass condition Expectation text Unlimited The sequence of return values of the automated test components corresponding to each atomic business process when the test is successful, that is, the expected value. Test case description Description text Unlimited Description of the case Test input data 1 Datal text Unlimited The data or case parameters that need to be entered on the page ... Test input data n Datal text Unlimited The data or case parameters that need to be entered on the page

Table 1 Data structure table of test cases

In Table 1, "case number" is used to distinguish multiple test cases during test execution, "tested module" indicates the business module in the tested Web application system, and "atomic business process sequence" records the tested business The atomic business process contained in the process and the execution sequence of the atomic business process, the "test pass condition" is used to compare with the test results to find the problems in the Web application system.

Step 102, read the test case.

The preferred step 103 is to pre-check whether the data of the test case conforms to the specification, and return an error message to the tester if it does not meet the specification; if the pre-check is passed, prepare data and apply for resources for the execution of the test case.

During the pre-check, first check whether the filling of the key data items of the test case conforms to the case specification, for example, whether the items in Table 1 are filled in according to the requirements of each field; secondly, it is necessary to convert the number of the atomic business process to the number of the component, and check Whether the automated test component that needs to be called exists, if it exists, it will be loaded into the memory and ready to be executed, otherwise, the detailed information that does not meet the specification will be returned to the tester. This step can prevent wrong test case data from entering the test link in time, causing abnormal operation and errors in the test process.

Step 104: According to the atomic business process sequence configured in the test case, sequentially call the matching automated test components for serial execution, test the specific business process of the Web application system, and record the test results.

Preferably, during the testing process, each time an atomic business process is executed, the execution return value of the corresponding test component is compared with the above-mentioned "test passing condition", and if they are the same, continue to test the next atomic business process; if they are not the same, If there is a problem with the atomic business process, the execution of this test case will be ended immediately. In this way, the error point can be found in time, and the wrong test result data can be prevented from being used continuously in the subsequent test process, resulting in abnormal operation and errors of the test software; it can also find the problem of the web application system in time, and the error location of the specific atomic business process and related data are recorded as part of the test results.

The preferred step 105 is to analyze the test results, count the test pass rate and other data, and organize the analysis and statistics results into a test report according to the specified format, and output it to the testers.

Preferably, during the entire process of the above-mentioned test execution, the execution status of each test step is tracked and recorded, and log files are generated for use by testers for subsequent analysis. For example, according to the error location recorded in the test report, by looking for more contextual information in the log file, analyze the cause of the error.

The component-based automated testing process is described below through a detailed example. The tested Web application system in this embodiment is an internal card error handling platform.

This platform implements error processing (account adjustment) for cash withdrawal and consumption transactions between acquirers (such as POS machines, ATMs) and card issuers (such as card issuers). Platform functions: error services such as confirmation inquiry, credit adjustment, one-time chargeback, etc. The error may be: the cardholder does not dispense cash when withdrawing money at the ATM, but the cardholder's account has been debited, or the cardholder spends at the merchant's POS, and the POS shows that the transaction is unsuccessful, but the cardholder has actually been debited account balance etc. For each transaction, the card issuer retains complete original transaction data, and when making error adjustments, it needs to invoke these original data for processing to balance accounts and clear accounts.

Taking the credit adjustment business as an example, the following describes the specific operation process. When a credit error occurs, first, the operator of the acquiring agency logs in to the error processing platform, and queries the original transaction data (main account number, settlement date) User transaction data, select the transaction with errors, choose to initiate a credit adjustment application, fill in the relevant application information, and submit the application, waiting for review. After the reviewer logs in to the platform, he inquires about the credit application that has not been reviewed. After the review is passed, the erroneous transaction data is entered into the database for liquidation, and the operation process of credit adjustment is completed.

The credit adjustment business, as a module to be tested, is the business process of the Web application, which can be decomposed into the following atomic business processes: the agent of the acquiring institution logs into the error platform sf1, and the agent of the acquiring institution inquires that a loan needs to be made Historical transaction sf2 for debit adjustment, acquiring institution operator initiates credit adjustment transaction sf3 for the queried transaction, acquiring institution operator exits error platform sf4, acquirer reviewer logs in to error platform sf5, acquiring institution The reviewer finds out the credit adjustment and performs the review operation sf6, the reviewer of the acquirer cancels the transaction that passed the review sf7, the reviewer of the acquirer exits the error platform sf8, the operator of the acquirer modifies the transaction that failed the review sf9, The clerk of the acquirer deletes the transaction sf10 that fails the review.

After analysis, sf1 and sf5 can be combined into an automated test component c1 that logs into the error platform, sf4 and sf8 can be combined into an automated test component c4 that exits the error platform, sf2 is designed as component c2, and sf3 is designed as component c3. Design sf6 as component c6, design sf7 as component c7, design sf9 as component c9, and design sf10 as component c10.

For the test of the credit adjustment business, two common test cases are listed, as shown in Table 2.

case name Atomic Business Process Sequence illustrate Case1 sf1->sf2->sf3->sf4->sf5->sf6->sf8 The routine process of test credit adjustment business (initiated by the operator and passed by the reviewer), the component sequence converted to call is c1->c2->c3->c4->c1->c6->c4. Note: The parameters of the two calls to c1 and c4 are different. Case2 sf1-＞sf2-＞sf3-＞sf4-＞sf5-＞sf7-＞sf8-＞sf1-＞sf9-＞sf4 This case is an abnormal case, which is used to test whether the error process of canceling without review can pass. If the process is tested and found that all atomic business processes can be executed, it means that the error platform is wrong. The building block sequence converted to calling is c1->c2->c3->c4->c1->c7->c4->c1->c9->c4.

Table 2 Test case table for credit adjustment business

In Table 2, the atomic business process is the smallest business process unit decomposed according to the specific business, such as sf1, sf3, etc. in this example; the atomic business process sequence is the test execution sequence of the atomic business process, such as sf1-> in this example sf2->sf3->sf4->sf5->sf6->sf8.

Referring to FIG. 2 , it is a flow chart of the automatic testing method of the present invention taking the credit adjustment business as an example.

Step 201, read all the test cases, check the data specification, and check whether the test components that need to be invoked exist. If the check is passed, continue to step 202; otherwise, end the test of this case, and return the error message to the tester.

Step 202, preparing data for the execution of the test case. According to the specific test case, prepare the corresponding test input data.

Step 203, according to the atomic business process sequence, judge whether all atomic business processes have been tested, if not, continue to step 204; if all tests are completed, jump to step 207, and record all test results.

Step 204, preparing the parameters of the test component for the atomic business process to be tested. In this example, component c1 corresponds to two atomic business processes sf1 and sf5, which are called twice in case 1, but the atomic business processes calling component c1 are different, so different parameters need to be passed to component c1 to execute different atomic processes Business Process.

Step 205, calling the corresponding automated test component, passing corresponding parameters to the component, and testing the atomic business process.

Step 206, obtain the execution return value of the automated test component, check whether it matches the expected value, if it matches, return to step 203, and continue the test of the next atomic business process; if not, end the execution of the current test case, and execute the step 207. Record the error location and related data.

In step 207, test results are recorded and a test report is generated, and the execution of a test case ends. Wherein, the test result includes information such as the number of successful tests, the number of failed tests, error locations, and error reason codes.

Step 208, judge whether all the test cases have been executed, if there are other cases, return to step 202, start the execution of the next test case; if all the test cases have been executed, end this run.

For the component-based automated testing method, the embodiment of the present invention also provides an automated testing device for a Web application system. Referring to FIG. 3 , it is a structural diagram of the device, which mainly includes an automated test component library 301 , a case reading module 302 and a test control module 303 .

The automated test component library 301 is a collection of automated test components, which store the description part of the components in a structured manner, so that testers and automated test tool modules can retrieve automated test components according to various conditions. Moreover, the automated test component library 301 also provides testers with the function of maintaining and upgrading the automated test components. Among them, each test component is created corresponding to the atomic business process, and different test component combinations are used to test different business processes. A test component may correspond to one atomic business process, or may correspond to multiple atomic business processes. If it corresponds to more than one, different atomic business processes are tested by receiving different parameter assignments.

The case reading module 302 is used to read pre-configured test cases and send them to the test control module 303 for execution. The test control module 303 is used to schedule the execution of test cases, call the corresponding test components from the automated test component library 301 according to the sequence of atomic business processes in the test cases, serialize the test atomic business processes, and record the test results.

Preferably, the test control module 303 includes a test unit, a control unit and a recording unit. Wherein, the test unit is used to correspond to each atomic business process, call the matching test component from the automated test component library 301, and test the specific business process of the Web application system. The control unit plays a role in scheduling case execution and test component invocation in the whole process. After receiving the component execution return value sent by the test unit, it compares the return value with the expected value recorded in the test case, and if it matches , then trigger the test unit to call the component to continue to execute the next atomic business process; if not, end the execution of the current test case, and trigger the recording unit to record the error location and related data. When all atomic business processes are tested, the control unit schedules the next test case for testing. The recording unit is used to record the test result executed by each component after the test case is executed, and take the comparison result with the expected value as a part of the test result, and the test result also includes error location and related data.

Preferably, the device further includes a test result analysis module 304, configured to analyze and count the test results obtained by the test control module 303, and generate a test report according to a specified format.

Preferably, the device also includes a case analysis module 305, which is used to check whether the data of the test case conforms to the case specification, and converts the number of the atomic business process into a test component number, and checks whether there is a need to call in the automated test component library 301. Test build number. If the check is passed, the test control module 303 is triggered, otherwise an error message is returned to the tester.

Preferably, the device also includes a log tracking module 306, which is used to track and record the execution of the case reading module 302, test control module 303, test result analysis module 304 and case analysis module 305, and generate log files for future use. Testers analyze usage after the fact. For example, according to the error location recorded in the test report, by looking for more contextual information in the log file, analyze the cause of the error.

Preferably, the device further includes a case configuration module, which is used to configure various test cases from all possible business processes executed by the system according to the business characteristics of the Web application system, so as to achieve the purpose of comprehensively testing the Web application system. The main data structure of the test case can be shown in Table 1.

The execution process of the automated testing device is: after receiving the test execution instruction sent by the tester, the case reading module 302 starts to read the test case, and then the case analysis module 305 checks the case data, if the pre-check passes, Prepare data, apply for resources, and other operations for the execution of the test case. After all preparations are completed, the control right is handed over to the test control module 303 for further processing. The test control module 303 executes each test case sequentially according to the order of the test cases. When executing a single test case, according to the sequence of components converted by the case analysis module 305, it sequentially calls the automated test component library 301 for execution. After obtaining the execution return value of the automated test component, check whether it is the same as the expected value in the "test passing condition" field, if it is the same, continue to execute the next automated test component, otherwise directly return the test result, including the error caused by the atomic business process location and cause of error. After all atomic business process tests are completed, the test control module 303 records the test results, and the test result analysis module 304 generates a test report after analyzing the test results, and then enters the test execution link of the next test case.

The embodiment of the present invention also provides an automated testing component with uniform interface specifications, easy to transplant, and easy to upgrade, which is used in the above-mentioned automated testing device and can work in different hardware operating platforms and software environments.

Referring to FIG. 4 , it is a structural diagram of the automated test component, and the component includes an interface 401 , a component implementation 402 and a component specification 403 . The interface 401 provides the connection between the external module and the component implementation 402, the external module calls the component implementation through the interface, or the component implementation calls the external module through the interface. When the test is executed, the test control module 303 calls the component implementation 402 through the interface 401 to perform the test. Component implementation 402 corresponds to the atomic business process and provides corresponding testing functions. It is the test program of the atomic business process implemented by the automated test component and is the core of the automated test component. The component specification 403 specifies the constraints on the structure of the automated test component, and its main function is to specify the structure and description of the component, which is realized by xml technology. Component specification 403 can be understood as a description of components, which is convenient for testers to find and grasp the relevant information of each component.

The following table is the main elements and descriptions of the component description part in the component specification:

element name illustrate id Component number, the unique identification of the component name The name of the component type The type of component, which identifies whether the component is an atomic component or a composite component related-component This element represents the component associated with the current component, and the content of this element is meaningful only when the type is a composite component source The source of the component, i.e. why the component was produced age Component life cycle, indicating the maturity and stability of the component web-application The name of the application system tested by the automated test component module The name of the business module tested by the component flow The name of the atomic business process corresponding to the component function-description A description of the tested functionality of the component version The version of the component history Component history, mainly including version change history author The author or vendor of the component memo Component Remarks

Table 3 Explanation of the component description part in the component specification

Automated test components are divided into atomic automated test components and composite automated test components. The component specification part of the atomic automated test component needs to indicate that the component is an atomic automated test component, and describe the function, version number, etc. of the component; composite automated test components The component specification part of the test component needs to indicate that the component is a composite automated test component and describe the function, version number and other information of the component, and also need to indicate which atomic components the composite component is composed of, and the composition sequence of these atomic components. And the mapping of each atomic component, etc.

In order to illustrate atomic components and composite components, the credit adjustment business is taken as an example. The above-mentioned automated test components c1, c2, c3, c4... are all atomic automated test components, and they correspond to the minimum atomic business process. However, in many cases, for a fixed common business process, such as the operator initiates a credit adjustment to the reviewer to pass this common test process, and the usage rate is very high in practice, the atomic automated test component can be used c1->c2->c3->c4->c1->c6->c4 are combined to form a composite component, and each execution component sequence c1->c2->c3->c4->c1->c6- > c4, just call the corresponding composite component directly. In this way, the shortcoming of calling atomic components many times due to components dispersing business processes into atomic business processes is avoided, thereby improving test efficiency.

The parts not detailed in the apparatus shown in Fig. 3 and Fig. 4 can refer to the relevant parts of the method shown in Fig. 1 and Fig. 2 , and will not be described in detail here for the sake of space.

The above is a detailed introduction to the automated testing method and device of a Web application system provided by the present invention. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The descriptions of the above embodiments are only used to help Understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and application scope. In summary, the contents of this specification should not be construed as limiting the present invention.

Claims (14)

1, a kind of automated testing method of Web application system is characterized in that, comprising:

The operation flow of Web application system is resolved into the combination of atom flow process;

Corresponding each atom flow process is created the automatic test member;

Read pre-configured test cases, write down atomic current program row in the test cases;

Each atom flow process in the corresponding described sequence is called corresponding test member, and the Web application system is tested.

2, method according to claim 1 is characterized in that, also comprises before calling test member: whether the data of the described test cases that reads of preliminary examination compliant, and checks whether the test member of being called exists.

3, method according to claim 1 is characterized in that, also comprises:

Test member is carried out rreturn value and expected results comparison,, then carry out next test member if identical; If inequality, then write down Error Location and related data, and carry out next test cases;

Write down the test result after the above-mentioned comparison.

4, method according to claim 3 is characterized in that, also comprises: analyze described test result, generate test report.

5, method according to claim 1 is characterized in that, also comprises: the implementation status of each execution in step of track record.

6, method according to claim 1 is characterized in that, also comprises: the test member that common operation flow is comprised is combined into composite component, directly calls described composite component when calling.

7, a kind of automatic test device of Web application system is characterized in that, comprising:

The automatic test component base is the set of automatic test member, and the corresponding atom flow process of each test member is created, and the atom flow process is combined into the operation flow of Web application system;

The case read module is used to read pre-configured test cases, has write down atomic current program row in the test cases;

Testing control module is used for each atom flow process of corresponding described sequence, calls corresponding test member, and the Web application system is tested.

8, device according to claim 7 is characterized in that, also comprises: the case parsing module, whether the data that are used for the described test cases that reads of preliminary examination compliant, and checks whether the test member of being called exists.

9, device according to claim 7 is characterized in that, described testing control module comprises:

Test cell is used for each atom flow process of corresponding described sequence, calls corresponding test member, and the Web application system is tested;

Control module is used for that test member is carried out rreturn value and expected results compares, if identical, then trigger described test cell and carries out next test member; If inequality, then carry out next test cases;

Record cell is used to write down the test result after the above-mentioned comparison, and record Error Location and related data.

10, device according to claim 9 is characterized in that, also comprises: the test result analysis module, be used for the analytical test result, and generate test report.

11, device according to claim 7 is characterized in that, also comprises: the log tracks module is used for the implementation status of each testing procedure of track record.

12, a kind of automatic test member is characterized in that, comprising:

Member realizes that being used for corresponding atom flow process provides corresponding test function;

Interface, being connected between being used to external module is provided and member is realized, external module realizes that by described interface interchange member perhaps member is realized by described interface interchange external module.

13, member according to claim 12 is characterized in that, also comprises: component specification is used to provide the explanation to described member.

14, member according to claim 12 is characterized in that: described member comprises atom member and composite component, and wherein the atom member is corresponding with the atom flow process, and composite component is the combination of a plurality of atom members.

Images