Software testing technology-Zhang Yaixia teacher

Zhang Yaixia Teacher

Life is not black, white, and gray.

Don't speak too straight, not too blunt.

Software Testing:

Purpose of the test:

The software is consistent and easy to integrate between members.

Stages are reviewed at each stage. Judging is not too modest. Being too humble is not self-confidence.

Before the review team to do internal testing, to ensure that there is no error between the review.

White box test:

Testing needs to understand the internal structure and process of the program

Black box test:

Also known as functional testing, data-driven testing, or specification-based testing, can be called user testing

Black Box test Method:

Equivalence class Partitioning method

Boundary value analysis Method (maximum number, minimum number)

Notice the difference between:< and <=

Boundary of data type

The bounds of the array

Error-guessing, also known as destructive testing

Grey Box test

Functional Testing

Performance test load test, stress test, capacity test

Development Life cycle:

Requirements Analysis-design definition-programming-maintenance/modification

Test life cycle:

Test plan--Test design--Test development--Test Execution/Evaluation (summary)

Defect Tracking

Unit Test

Integration testing ensures that each unit is grouped together to run in accordance with established intentions and to ensure that the increment behaves correctly.

System test a series of overall, validity test for the whole system

Acceptance Testing

Formal acceptance test for project amended

Informal testing for products

Regression test

Maintenance period Test

Software defects

1, not meet the specifications specified by the scope

2. Error occurred at runtime

3, beyond the scope specified in the specification

4. Failure to meet the target

Why software defects are present

The biggest cause of software defects is the requirement specification

The workload of the test process can basically reach 40% of the project process.

Costs can be 20%~30% to the cost of the project

Defect level

1. Other

2, Cosmetic

3, Minir

4, Major

5, Critical

Resolving priority levels

1, Low

2, Medium

3, High

4, Very Hign

5, Urgent

Defect status

1. New

2, Open/reopen

3. Fixed

4, rejected refused

5, Deferred delayed repair

6, Closed closed

7, rejected

Principles for reporting defects:

1. Report software defects as soon as possible (but at least three times to reproduce)

2. Effectively describe software defects

Short language, a report only for a software defect, obvious and generic, against the facts, can not be any evaluation of the programmer, the defects found do not lose (perfect report)

Cmd.exe Run as Administrator

Bcdedit set {Current}nx AlwaysOff

Install files--right-click Properties--Compatibility mode--at least XP

Software testing technology-Zhang Yaixia teacher