Catalog

One 、 demand

Two 、 System architecture

3、 ... and 、 Process management

Four 、 Document management

5、 ... and 、 Risk management

6、 ... and 、 time management

How to do a qualified test ？ What is the post responsibility of software test engineer ？

first , My idea is Execute use cases , Find defects , That's it , Simple and crude ...

later , I saw 《Google The way of software testing 》 This book , Slightly changed , Turned into Actively discover 、 Expose defects , And team work , solve the problem ...

Second half of last year , The company parachuted a director , He made a point ： Improve delivery quality and delivery rate ！ It suddenly opened up , right , The purpose of our work is not to improve the quality of the delivered software system , And improve efficiency ！

After listening to the peer sharing last night , Thinking and summarizing , in the light of How to improve the quality and speed of software applications delivered This problem , I found that I didn't consider some details , Sure enough, I'm still inexperienced , The way of learning and growth , A long way to go ！！！

The following , Reorganized several views shared by the boss , Combine some of your ideas , It can be regarded as a reference ...

One 、 demand

1、 Requirements review

Why Requirement Review ？ The reasons are as follows ：

①、 Familiar with the business , Explain the needs by products or businesses , So as to know well , It will not expose problems caused by unfamiliar business in the development and testing stage ;

②、 multipartite agreement , Before officially entering the development stage , test 、 Development 、 The product confirms the uncertainty of some requirements , To reach an agreement , Avoid subsequent problems ;

③、 Assess workload , Difficulty of realization , And the approximate resource input ;

④、 Define the development test boundary 、 Goals and scope , What to do and what not to do ;

2、 The requirements document

①、 Be as detailed as possible , It is necessary to extract the corresponding function points and test points from the requirements ;

②、 Select appropriate granularity for function points and test points , In this way, it is easy to observe the deviation between test results and requirements ;

③、 Generally speaking , The bigger the system , The more complex the business , It is easier to determine the deviation degree of requirements than small systems ;

Two 、 System architecture

In addition to demand , Understand and be familiar with the technical architecture of the whole system , It is also necessary . For example, the architecture of the whole system , Their characteristics , What communication service framework is used , Database type , Front and rear end frames, etc , This makes it easier to locate defects ,

And choose the appropriate automated testing framework according to the system architecture 、 Performance testing strategy, etc .

features ： Generally speaking , The better the stability of the system , Then its adaptability is worse , The impact is the rising cost of each architecture change and the reconstruction of the development team or the change in the overall direction of the test team .

In recent years, distributed architecture has become popular and widely used 、 Microservices, etc , Both are considered from the availability and scalability of the system , To reduce the cost of changes in all aspects .

3、 ... and 、 Process management

The record of test process results should depend on the record integrity of the process to a certain extent .

If process changes are involved , Also deal with different observation objects （ test / Development ） Record the effects and results , To judge its impact on quality and evaluation criteria .

The test flow is as follows ：

①、 Start-up phase

The development manager determines the test submission time in the development plan , After getting the latest relevant documents, the test director estimates the scale and establishes a test team , complete 《 test plan 》;

②、 design phase

Include test plan 、 Test plan 、 Test cases and other output documents ;

After the requirements analysis document establishes the baseline , The test team needs to write test cases for test requirements , In the actual test , Test cases will be the only implementation standard . In the process of writing use cases , The specific tasks and responsible persons are as follows ：

③、 implementation phase

Executing test cases will take the test team most of the time , These works are based on a lot of planning work in the early stage ;

④、 Reporting stage

On that day （ Or every small stage ） After the test of , The test engineer needs to summarize the test results of the day , Report the test progress ;

⑤、 Summary phase

After the test , The test supervisor prepares the test report , Summarize the test , And submit , Provide important information support for the follow-up work of the product ;

⑥、 Acceptance stage

After the above work is completed , The process of testing , The results are accepted , Announce the end of the testing phase ;

⑦、 The archiving phase

Test archiving is to declare the test valid at the end of test acceptance , After the test , Archive various standard documents involved in the test process ;

Four 、 Document management

Help of documents to work , It is necessary . Although many enterprises advocate agile now , But agile is not without documentation , But light documents . The importance of documents has the following aspects ：

1、 It is very helpful for knowledge transfer in history and current testing process ;

2、 You can compare changes in history and current documents , It is easy to observe the quality of testing in the whole process of requirement change ;

3、 When it comes to personnel changes or defects , Have faster knowledge transfer rate and reference basis ;

5、 ... and 、 Risk management

There are risks in every stage of the project , Common defects are as follows ：

1、 Unclear needs ;

2、 The system design or test design is not perfect ;

3、 Unsafe code writing ;

4、 Insufficient test cases , Low coverage ;

5、 Insufficient test resources , Improper estimation of regression workload ;

7、 The project schedule is inappropriate , The impact of other projects on this project ;

therefore , Risk management and prevention is a necessary and important work , And the responsibilities of the test engineer , Isn't it to provide the quality of delivered software ！！！

6、 ... and 、 time management

Engineers with certain testing experience have basically experienced insufficient resource investment , The problem of insufficient time , Test time is compressed , Resulting in overtime and even production accidents ！ So do a good job of time management , It is so important .

People who can manage time are often one step closer to success , How to reasonably use time to solve urgent project problems 、 The question of conflict 、 Resource arrangement 、 priority 、 Execution sequence of test cases , Good time management is one of the factors to ensure quality . 

For example, it involves new requirements or Requirements change must have corresponding documents （ It can be a requirement specification or an email description ） As the basis of the test ;