How software testers get to know the business

The business process of the software being tested is an important preparatory activity for testing , and it plays a very important role in the reference and analysis in the process of testing.

The question is simple but difficult. Simple is because the software business process can be the clues, difficult because I do not know where to start.

"Tested software" sounds a bit large, the industry background of the software tested, the general role of software, the overall framework of these "big" aspects of information is relatively easy to access and understanding. In fact, the software is composed of many functions, in the actual work, the functional module of the business process to test the direct guidance and reference role (such as test case writing, test results analysis, etc.), do not grasp the business process is not enough to good test.

Testers want to know the business process of the SOFTWARE function module, it is necessary to involve the developer, that is, to involve the development and testing of the interface.

The problem is to be solved, and to a great extent depends on the cooperation of testing and development. The development of test system is normative and sound very influence this joint point and even affect the entire test process.

Please be sure to find this software function module involved in the developer, it is best to find a "head" (can also be found by your head to their head), OK, the following is a live PK, just beginning this is very torture, you do not know anything, but you have to ask, Be sure to make a point to understand (for example, a function module in a program is what, this function module is who who is responsible for, this function module involves the interface, database ), find this point can be a follow-up, all involved in the developer asked a time (conditional words, You can sit down and explore with all the people involved, for testers are good for developers, knowing that developers who are responsible for different functions are likely to be clueless about the rest of the project's developers, and muddle through the business as a whole. Communication at the same time to remember the mutual benefit, you know, but also to tell the people do not know, in your future communication and exchange career, to form a benign reciprocal activities, rather than blindly ask for answers.

Through a virtuous cycle, the testers change from "Unknown" to "late knowledge".

Of course, "late to know" compared to "early know" the cost of energy and much more expensive, but this is precisely the situation that many people encounter, have to face.

For a team with a good development test process system, you have to be happy, you can "know".

But do not relax yourself, because "knowing" does not mean that you "know" (understand correctly).

In the test process, with the coverage and depth of the test, will inevitably cause a variety of problems and questions, need to judge and analysis. This time still requires testers and developers to work together to facilitate a deeper understanding of business processes, functional details, raw requirements, etc.

How can you master business processes? The following points are more important:

First, understand the main business framework, do not have to pursue branch details. First to the overall business has an impression, know some conceptual things, mixed familiar;

Second, understand why to have this business, the most original demand from where. Can jump out of the current business process thinking, consider the most source of business-driven, the original business is to solve one or a kind of problem. This is a definite target.

Third, the user or business needs themselves to understand the branch of the details of the point of view. This time can give full play to our imagination to understand these things, you can also find a familiar with this business or similar business colleagues to chat, there may be a lot of unexpected harvest.

Four, the branch and the backbone are all strung together, thinking about the whole business process integration. Re-comb your understanding of the entire business process, and if there is a place to go, you can check again. At this point you may no longer just understand the business, perhaps you can also find that the unreasonable place, everything is possible.

In addition, do not limit yourself to the role of testers, in the knowledge and understanding of the business, need to think from a number of dimensions, such as: from the perspective of the demand side to consider the value of the business itself, from the perspective of development to infer the logical framework of the business, from the perspective of testing to analyze the business's rationality and integrity , from the user's point of view to experience the ease of business.

1, in the requirements of documents, design documents and other specifications of the case, of course, the first to get the document familiar with the business process, generally in the business process more understanding of the case, the company will have to develop products and technology introduction, so that you can more in-depth understanding of the development of the background, as well as some technical characteristics, You can also learn the focus of testing and so on ...

2, in the absence of detailed requirements of the document, there are generally 2 of the situation, a design document, look at the first look at the design documents, familiar with the business flow chart, so that the testers to spend more time in the process, I hope in the development of the introduction of products and technology, can be made up without the need for documents to bring business unfamiliar ...

The 2nd situation is that there is no need for documentation and design of detailed documents, that personal advice and development communication, do not understand, not clear only to find the development of oral demand, so that the efficiency is not called low.

3, the demand has been changed? The best way to do this is to develop and communicate with the designers, and communication is most effective when there is no detailed documentation.

4, Development bad communication ... It's not going to work!

How software testers get to know the business