[Test] software testing Basics

Testing Basics

 

1. Software Testing Life Cycle

Needs analysis ---> Test Plan ---> test design, test development ---> test execution ---> Test Evaluation

1) Demand Analysis: test requirements range, function points

2) test plan: Specifies the schedule (people, time, what is being done), risk management

3) test design, test development: write test cases

4) test execution: perform testing, defect management

5) Evaluation test: Conclusion (pass or not pass), the defect analysis

1.1 six stages

Requirements phase : Testers understand the needs, the demand decomposition, derived test requirements;

Planning stages : preparation of test plans, test programs on demand;

Design phase : the tester proper understanding of the design, the design is very helpful test, the tester with large detection chamber frame embodiment, the preparation according to the needs and design test portion;

Coding phase : Testers generally does not require coding, but has been encoding module, professional white-box testing personnel can perform unit testing, improvement, refinement and adjustment of test cases to test plans and programs;

Test phase : testing phase is the most important work phases of software testers, test cases and test plan execution, recorded in the process of implementation according to defect management, report writing tests after the test is completed;

Operation and maintenance : tester needs involved in the implementation of the project. Testers and project product business operation is very understanding, coupled with communication skills testers generally stronger than, so testers can participate in training users to use the software to collect problems running the project and timely feedback to the relevant person in charge.

 

2. How to describe a Bug

Look at the bug would not affect the progress of the work, if the impact of words, look for R & D personnel, responsible for the bug, then she saved once you modify, do not repeatedly go to R & D personnel

1) version issues found

2) environmental problems

Step 3) errors

Description 4) the expected behavior

5) description of wrongdoing

6) Other

7) Do not put more into a bug

eg:

Defective title: 163 free e-mail registration submission failed

Found in version: v1.0.1

Environment: win10 + IE11

Severity: High

Steps:

1. Open the 163 website,

2. Click on "Sign up for free email"

3. Enter the relevant information

4. Click Submit

Actual results: page prompts failed to send

Expected results: page prompts sent successfully

Accessories: Upload screenshot

 

3. How to define the level of bug

Each company is different, the following is a sample

1) Blicker (crash) : problems hindering development or testing work; cause system crashes, freezes, infinite loop, resulting in data loss database, the database connection error, major loss of function, lack of basic modules and other issues;

2) Critical (serious) : The main function of the system partial loss, calling database stored error, loss of user data, a function menu can not be used but the test does not affect other functions. Functional design and demand serious discrepancies, the module can not start or call a program restart, automatic withdrawal, call the conflict between the associated procedures, security, stability, etc.

3) Major (General) : function is not fully realized, but does not affect the use, function menu defects but does not affect the stability of the system. Such as: operating for a long time, a long time queries, format error, boundary condition error, there is no confirmation box to delete the database table (there is up to the actual test questions) too many fields, etc.;

. 4) Minor (minor) : the interface, performance deficiencies, recommending kind of problem does not affect the function of performing the operation, the program can optimize performance and the like. Such as: typos, non-standard interface format, the page displays overlap, should not be displayed to hide, description is not clear, prompt loss, irregular arrangement of text, the cursor position is incorrect, the user experience of feeling bad, you can optimize the performance of programs (more testing such problems in the early stages, a low priority; appear in less post-test, should be in time).

 

4.bug life cycle

State of defects: common

New : newly discovered bug without review to decide whether to make changes to the assigned developers;

The Open : confirmed that bug, and that need to be modified, assigned to the respective developers;

Fixed : developers to modify identified as a modified state, pending verification testing regression testing personnel;

Rejected : If you think that is not a bug, it refused to amend

Delay : If you think no need to modify or temporarily can not be modified, delayed modification;

Closed : Modified state bug regression testing by the testers not pass, is closed bug;

Reopen : If verification Bug persists, you need to reopen the Bug, developers re-edit;

无效的bug:open--->closed open--->rejected----->closed

 

Testers work: new -> open fixed verification,

flow chart:

                                      

 

 

 

Testers for each modification must re-take a defective version of a new code changes included in the regression testing to ensure that the same problem no longer occurs, you can close the defect;

For reject changes and modifications delay Bug, need to go through testers and developers on behalf of the representative, the representative part of the user (or a person on behalf of the user perspective) assessment.

5. How to start the first test *****

1) to study the document, understand all documents related to the project

2) possible participation in various project meetings, understand the project background, staff, and business needs to understand as much as possible;

3) Learn to test the appropriate company norms,

4) Learning familiar with test management tools, configuration management tools, access to the corresponding address and login;

5) Read the existing test programs and test cases

6) get the address of the desired product, read the old BUG library, understand the system function;

7) and head of communication

8) core communication

After making the above preparations, testing come, we need to confirm the specific content of the work and test leader:

What 1) is planned to test?

2) What is the test? test case number? Devote several days to perform? There is no free time testing?

3) content developers who want to test me? Who needs staff was?

4) assigned to me to test whether the content requires a special test resources? Whether the resources to meet the needs?

 

6. Test execution and management of BUG

How to find more defects? *****

1. Test there are also 28 principles, 80% of the failures concentrated in 20% of the module, that if a large part of the problem, to strengthen the breadth and depth of testing!

2. The developer also has 28 principles, 80% of the failures concentrated in 20% of developers ,, if the bug Some developers more, he developed modules to strengthen the breadth and depth of testing!

3. Multi-reverse thinking and divergent thinking

4. Do not be limited to the use cases and requirements documents

5. involved in the project as soon as possible, do not wait until then developed almost involved in the project

 

7. a dispute how to do (interpersonal) *****

1. The check itself is not clear whether the bug description

2. From the user point of view the problem

3.BUG rating to well-founded

4. improve their technical and operational level, not only to ask questions, it is best able to propose solutions

5. When developers do not accept, can not quarrel with third-party force, review

 

 

 

Published 62 original articles · won praise 9 · views 10000 +

Guess you like

Origin blog.csdn.net/qq_43669007/article/details/103378496