In the analysis of business processes, we should get the following information:
What are the main flow 1) system is
2) alternative process is what conditions
3) What is the data flow
4) What is the key to determine the conditions
Process testing testers to link up the various modules of the system is running, to simulate real users actually work processes to meet the needs of the user-defined function to perform the testing process.
Business Process Testing is the most important content system testing, and the test is based on user-defined test design requirements and testers, so following on from the focus on demand, test design, test execution and other point of view to illustrate how well the business process testing .
First, the concerns and needs of users
1, user's perspective
Excellent demand should be from the user's point of view to consider the issue, the user is able to take advantage of what the complete system, not the system yourself. So to be more and end-user demand in the software's understanding and learn about their demands for targeted testing.
2, emphasis on global, rather than details
Emphasis should be placed on demand comprehensive collection points as possible, understand the overall business process, analyze the main business processes and key business processes work. After obtaining a complete picture of the system, we will find that the original understanding of the preparation of functional test cases in the system is not sufficient, then the process to write test cases need to be rearranged according to new ideas.
3, on-site customer
On-site to provide customers with guidance on the detailed requirements at any time. If there are no conditions, regularly invite users to participate in the project or arrange regular meetings and exchange user. Also in understanding the needs assessment and test design review will try to invite user participation.
Second, the use cases designed flow
1, the flow points prepared by Example
● have basic data for system testing multiple use, and easy automation tools to intervene.
● other processes to rely on this data, so that each process can be more targeted execution.
● built data to try to have specific meaning, it is prohibited by a, b, c; 1,2,3, etc.
● process to meet the user's business operations common habit, try to consider the actual operation of the user to write.
● process can be very flexible, but each process should be a typical business operations.
● flow need not cover all functions of points, because the process is a use case example of a supplementary function.
● not be limited by the specific process module, each module may intersect. Users actual business operations are no boundaries.
2, the process practiced with the preparation of Example
● total system flow chart
The purpose of this list is to sort out the system first developed by context, ideas and writers; followed into the project to the tester, a general understanding of the system, the relationship between the functions of the system and the individual modules have a macro understanding .
● Role Menu
Because our system does now mostly multi-user multi privileges, corresponding to different roles have different permissions. Including menu level and operational level. For example, E-Sales system, there are eight kinds of role 50 kinds of permissions, so there is a clear list for users to understand and test systems are of great help in different functions or operating different test page corresponding to the role by the table two-dimensional correspondence.
● Test Data List
A flow of the test depends on and can be reused as much as possible in line with the actual operation data of the user. Test case contains the data carefully prepared, in the implementation will be targeted, closer to the user's operation.
● flow test table
This is the most important part is our starting point and testing process according to functional test cases, and the difference is,
Our concern here is the flow of business operations, referring to the time of writing "process use cases written in point."
Test test case writing process flow template and reference cases.
Third, test execution
● holding round test is complete a test database initial system test data, achieved by exp / imp;
● processes through automated tools to record test scripts in the data stability, stability of the interface; now recommend MI sector companies WinRunner and LoadRunner.
● WinRunner using the reference WinRunner7.6 Guide vss finishing in the test group
LoadRunner test group using the reference vss finishing LoadRunner Stress Test Example
First, the business process consolidation
1 fully grasp the business knowledge, business process and data flow services.
From the user's perspective, rather than just consider how business processes in the system; clear roles and processes in detail all aspects involved in each of the business, a relatively complex business processes which often are more detailed, and only a thorough grasp of the business, in order to present a full range of business areas tested.
2, demand from customers or staff learned importance and frequency of use of each business process. (This is very important to grasp the focus of the test)
3 for the business process corresponding to the function in the system. (Establish business mapping system, to prepare for the writing test cases)
Second, the preparation of test cases (after demand documents and UI prototype review)
1, a flowchart of drawing operations (for a relatively simple process, can also be described in the form of words, but the flowchart is relatively straightforward, but also allow for analysis path).
2. The importance of business processes, frequency of use for the process set priorities.
3, using the method scene, path or other methods (methods are actually not fixed, and sometimes can be integrated using a variety of methods) to tease out the business process corresponding to operation of each step in the system, the test case is formed of a business process.
note:
* This step is not necessary as the operation of the step function so detailed test point, this procedure may be a set of business operations, can be decomposed into a plurality of steps, the set of operations services, may also correspond to a particular functional test point, so that do the test case reuse. It can be said here is a business process as a combination of test test a plurality of functions into a set of points, forming a traffic flow.
* In each step the user needs to identify the role performed operation, because in a business process, it may relate to different roles.
* The need to balance the project schedule, cost, does not necessarily need to cover all of the paths.
Third, the design of the test data
1, the input data:
Test test business processes and functional point of focus is not the same, so the design of test data needed more time to consider the following factors (in order of importance to a secondary arrangement):
1) The key determination condition
2) data with business sense
3) boundary data
4) abnormal data
In addition, no data have any impact on the process, I think we can not consider this, put it in a more appropriate function point test, which can reduce unnecessary interference. However, some features are dependent on a strong point of the process, or business process is very simple, functional testing and business process testing point may be combined. (I think the actual functional testing and business process testing points separate data bit better, because after all, the focus is not the same; but sometimes forced to schedule pressure, will combine these data)
2, the output data:
Results report and the data obtained in the system, need reflected, when necessary, also need to provide output data according to the format of the report to be checked during the test.
Note: You need balance project schedule, cost, as found more problems with less test data.
Fourth, test execution
The main test execution of business processes in the following stages:
1, the most important is the system testing phase (a high priority as a major business process test smoke test).
2, in the late integration testing, the test part of the business process already been tested may be tested in the business process integration test system according to the order of integration. Integration testing phase focused on the test function point, there is a serious problem function point test, it is unable to carry out business process tests, and so it is generally more stable business processes of time before the test.
3, acceptance testing.
4, personal point of view: to ensure the quality of the most effective means of prevention or, if the business process can be used to test the pre-test, for example: for the developers to the FBI, or send a test before the test, which may improve the quality of songce reduce the test rounds, improve coding quality.
Further, with specific steps, and the test data, may be combined with automated testing tools to test the business process.