How to be a professional software testing engineer? Listen to the byte five year old test

As a software test engineer , During the interview , How to express your core competitiveness ? How to reflect your professionalism ? This is a question worth thinking about .

1、 The life cycle of defects

summary ： Whether the life cycle of defects can be accurately and clearly described , And what you should do in each flow process ? How do you do it? ?( On the blackboard , reflection !!!)

2、 Definition of defect status

newly build (New)： Newly reported software defects during testing ;

open (Open)： Identified and assigned to relevant developers for processing ;

correct (Fixed)： The developer has completed the correction , Wait for the tester to verify ;

Refuse (Declined): Refuse to modify defects ;

delay (Deferred): Errors not fixed in the current version , Next version fix ;

close (Closed)： The error has been fixed ;
summary ： The responsibility of software test engineer is to actively find and expose software defects , And assist the development engineer to ensure that the defects are repaired , Improve the quality and speed of software delivery , Each different software defect state , As a test engineer , What should you do ?

3、 Different permissions of personnel roles

new—tester： Test Engineer

declined-not bug–Test Supervisor： Test Supervisor / Test Engineer

declined-duplicated–Test Supervisor： Test Supervisor / Test Engineer

open–Project Manager/Technical Manager： Test Engineer / project manager / Technical director

fixed—programer： Development Engineer

closed—tester： Test Engineer

deferred-next build–Test Supervisor： Test Supervisor / Test Engineer

deferred-next main release–Test Supervisor： Test Supervisor / Test Engineer

summary ： It should be clear that in a project or department , Your authority and responsibility , The authority and responsibility of different colleagues , And the need for negotiation and communication in case of problems , Who should I call , How to solve !

4、 Key points of defect management process

To ensure the correctness of the error , Testers with rich testing experience are required to verify whether the errors found are real errors , Whether the written test steps are accurate , Is it possible to repeat ;

Keep the processing information every time you deal with the error , Including processing names , Time , processing method , Handling opinions ,Bug state ;

Rejection or delay errors cannot be decided unilaterally by the programmer , It should be the project manager , The test manager and product manager jointly decide ;

After the error is fixed, it must be verified by the tester who reported the error , Confirm that it has been repaired , To close the error ;

Strengthen the communication between testers and programmers , For some unrepeatable errors , You can ask the tester to supplement the detailed test steps and methods , And the necessary test cases ;
summary ： The above points , In fact, the main idea is around the first part – In the flow of the whole life state of defects , How to manage , What state requires what corresponding management method , Flexible application !

5、 Use case design specification

When creating a new test case, it is required to select the corresponding product module 、 Use case types 、 Applicable stages and related requirements , The type of use case is generally functional test , System test is generally selected in the applicable stage ;

The use case Title requires that the function of the description object is clear , And try to be concise ;

Fill in the appropriate preconditions as needed , It is required that the first operation can be connected after the preconditions in the business process ;

The operation steps shall be clearly stated, and the specific steps, check points and their positions shall be clearly stated ,UI Elements and controls need to be clearly identified ;

The expected results need to be clear , In principle, there should be no operation steps with unexpected results ;

summary ： When it comes to use case design , Have the most basic “ Eight elements ”, And the design of use cases 2 A train of thought ( By module or by business flow ), Dependence on business 、 How to think and deal with exceptions ? How to improve coverage ? These can be found from the specification of design use cases !

6、 Submit specification defects

When submitting defects, it is required to select the corresponding product module 、 Project 、 Affects version 、 priority 、 Severity and related needs ;

The defect title is required to accurately describe the defect , Including the location and performance of defects , Be careful to avoid lengthy ;

Steps must be included in the reproduction step , Results and expectations , If circumstances permit, test data need to be provided for developers to quickly reproduce the problem ( Log screenshot , Error reporting method ); in addition , More complex UI Ask for screenshots ;

summary ： Submit the defect , Four elements must be kept in mind ：when、how、what、why!

That is to express the four conditions that a problem must meet ： When and what actions were performed , What happened , Why does it happen ( Or can be understood as how to solve )!

7、 Defect priority definition

Dependent on many other functions or checkpoints , Or cause blocking issue A defect is defined as P1, Developers are required to give the highest priority to solving ;

A defect to which a function or checkpoint is dependent by another function or checkpoint is defined as P2, Ask developers to give second priority to ;

The defect to which an independent function or checkpoint belongs is defined as P3, Require developers to P1 and P2 After the level defect treatment is completed, it can be solved ;

Minor functional defects or page style problems are defined as P4, Require developers to P1、P2 and P3 After the level defect treatment is completed, it can be solved ;

Some suggestions on functions and styles can also be registered into the system and marked with priority P4, Generally, it can be solved in subsequent versions ;

summary ： Defect priority has a lot to do with severity , And comprehensively consider the online release , Impact on users !

The test results are the minimum standard for quality evaluation ： The test results meet the requirements at least and can run normally !

8、 Definition of defect severity

A particularly serious problem , For example, serious style problems , Data error , The main process is stuck, etc , It is required to mark the severity level as S1;

More serious problems , For example, more serious style problems , Main functional defects, etc , It is required to mark the severity level as S2;

Style or function problems of general severity , It is required to mark the severity level as S3;

Minor style or function problems , It is required to mark the severity level as S4;

Some improvements and optimizations found by testers during the testing process , It should also be recorded and submitted to the defect management tool , The severity level can be marked as S4, Generally, it can be put into subsequent versions to follow up ;

summary ： About the severity of the defect , Learn to choose , What to do and what not to do ? If you do , How do you do it? ? If you don't do it now , When to do ?
　　
Finally, I also sorted out some software testing learning materials , It should be very helpful for small partners learning software testing . Friends who need information can pay attention to the official account. ： Software testing tips dao, Free access ！ Include , Software learning Roadmap ,50 Video of class for many days 、16 It's a real assault project ,80 More than one software for testing ,37 A test document ,70 A software testing related problem ,40 Test experience level article , Thousands of test questions to share , also 2021 Software testing interview Dictionary , There's also a selection of resumes for software testing jobs , I hope that's helpful ……

Learn not to fight alone , It's best to keep warm , Achieve each other and grow together , The effect of mass effect is very powerful , Let's learn together , Punch in together , Will be more motivated to learn , And you can stick to it .

Typing is not easy , If this article is helpful to you , I like it, I like it , Give the author an encouragement . It's also convenient for you to find it quickly next time .