A solution for testers to improve their business mastery

This article is from the "Willow" blog, please be sure to keep this source http://eilfei2000.blog.51cto.com/2956473/1040396

In addition to mastering test-related techniques, such as test procedures, test case authoring ideas, and the writing and maintenance of automated scripts, testers need to learn and master the specific business they are testing.

Only in this way can we deal with gray box, white box test, in the test execution process, improve their ability to analyze and locate problems.

For testers to improve the level of business mastery, adhering to the consistent training, guidance ideas, the preliminary proposed the following plan.

The scenario is divided into three steps: first, the Business module mapping inventory ii. Building business model diagrams and examples Third, the examination stageDetailed Description: first, the Business module mapping inventoryResponsible person: first-line testers with personnel: first-line developers, CMO (Configuration Manager) for each group of modules are combed, convenient for testers to understand the defects of the various business module names, as well as the general role of each module, the owner of the module. Therefore, each project team is required to re-comb the module of this project.    By the testers as the responsible person, oneself attempts to understand this project each module detail, the function of each module, itself is to the business one kind of thorough study and grasps.    Depending on the experience, the CMO (Configuration Manager) may be required to pull the module, and the specific module will consult the developer for general functionality. At the same time, thorough grooming, may find a lot of no maintenance of the module, is an accident of joy. ii. business model diagrams and examplesResponsible Person: Test supervisor co-workers: Project manager or SE (requirement analyst) test supervisor, reconstruct the business model diagram of the project from hardware to driver, protocol, business, application, etc. Based on the completed business model diagram, training and learning within the group.     List some typical bugs, analyze the business logic relationships, and the dependencies between the modules. It may be that the test supervisor does not understand the system deeply and needs to be informed about the system, such as the project manager or the requirement analysis. Third, the examination stageResponsible Person: Test Management Team Participant: so the testers. After the above two steps are completed, each group is evaluated by the test management team. Each group gives a set of papers covering the understanding of the business module, troubleshooting the problem, drawing and explaining the business structure, and so on.    Then use the project more relaxed time, batch test examination.      will be in advance to declare that the assessment of performance as one of the criteria to improve seriousness.    As above, hope that through the above methods, to achieve a few results: 1, to improve the testing personnel of the project business Understanding;    2. Improve the test supervisor's understanding of the overall architectural model of the project.    3, comb refresh business module, found sluggish, unmanned maintenance module.    4, let the developers themselves also have a certain overall concept.     5, follow-up as basic training courseware use, so that the team new staff to quickly understand the business. As a competency enhancement, managers must confirm the authenticity and accessibility of various training documents and resources, and also need to inspire individual initiative in order to achieve better results.

A solution for testers to improve their business mastery