As a software testing engineer, how do you think to ensure software quality?

This question is like asking ：

As a girl , What do you think is the best way to dress up ？

They are open to such questions ！！！ Therefore, it is more important to test the thinking language organization and the overall understanding of job seekers ！！！

For being a girl , What do you think is the best way to dress up ？

1） She has to take a bath

During the bath , Take a bath for a long time , And there should be aromatherapy inside .

I have not bathed for several years , Do you still have to rub your back .

Then choose a beautiful dress , Choose clothes, shoes and bags that match your temperament .

Apply water emulsion , Choose a brand that suits you , Touch a lipstick , Choose your own color number

therefore , Same , Where is the breakthrough to answer the above questions ？

It must be from the perspective of process , Each process node is detailed .

In terms of agile processes

Demand analysis

Read the requirements document provided by the product manager

Record what you don't understand and what you have questions about

Make sure that there is no ambiguity or error in the requirements document

All fields in the requirements document are required to give quantitative standards

Requirements review

The requirement stage is the beginning of software development , The software has not been produced in this process , We are in the process of requirements analysis or requirements , Try to imagine yourself at the user level , Carry out corresponding work from the perspective of users

Key points , Try to combine your past knowledge , Mining hidden needs through explicit needs .

test plan

Test range

Try to divide the business related modules into the scope of my test

Division of labor of testers

Try to distribute the business to the corresponding familiar personnel

Test time

Try to estimate a reasonable time

risk

Try to identify all the risks at the beginning

The test case

When writing test cases , Try to cover all the functions involved in the requirements document

The use case coverage reaches 100%

Try to take all possible situations into account

Use cases should be written succinctly , Not only can I understand and execute , Others are also easy to implement

Use case review

Try to mobilize everyone's enthusiasm to help you find the missing points , Or there are problems

Output smoke test cases

We will also try to filter out all the main functions , Including the important ones , Leave it to development for self-test .

Monitoring self-test , Sometimes even , The development and implementation may not be ideal , I will take the initiative to carry out the formal iteration test

Carefully combine the steps of each use case , And sometimes it is necessary to extend the corresponding use case divergence , encounter bug When , Try to describe clearly and accurately , And can attach screenshots and error reporting logs

Output test report

Combined with test report data , See if there is a follow-up optimization scheme , Improve the development and testing quality of the whole team