1. What is software testing:

Two basis (requirements, test cases), two methods (manual, automatic), one comparison (comparison of expected and actual results)

2. The purpose and meaning of software testing: (how to do software testing well)

In the beginning: find as many defects as possible to generate relevant specifications

Mid-term: find defects as early as possible

Later: try to prevent problems: accumulate through past experience

Control costs (throughout) and find more defects with as little time and effort as possible

3. Software life cycle:

Waterfall Model:

Test Intervention Point: After coding

Test coverage: Entire product

The waterfall model has the following advantages

(1) Provides checkpoints for the project by stages.

(2) After the previous stage is completed, you only need to focus on the subsequent stage.

(3) The waterfall model can be applied in the iterative model.

Incremental iterations are applied to the waterfall model.Iteration 1 solves the biggest problem.Each iteration produces a runnable version while adding more functionality.Each iteration must go through quality and integration testing.

(4) It provides a template under which methods of analysis, design, coding, testing and support can have a common guide.

The waterfall model has the following disadvantages

(1) The division of each stage is completely fixed, and a large number of documents are generated between stages, which greatly increases the workload.

(2) Since the development model is linear, users can only see the development results at the end of the whole process, thus increasing the development risk.

(3) Track various project phases with a plethora of mandatory completion dates and milestones.

(4) The outstanding disadvantage of the waterfall model is that it does not adapt to changes in user needs.

Spiral Model:

​Test intervention point: When a function is completed (unit test), when a module is completed, "integrated visual test) the whole system is completed (formal moral test"

When the system is used by users (acceptance testing by the user organization) and user confirmation is required during the development process (organization experts conduct identification testing)

Test coverage:

Unit rolling test:Code integration test: The interface between functional blocks and functional modules is tested for the combination of functional modules of each segment

Official Trial:Entire Product

All-in-stream trial:Users use the product intertextually

Benefits

1. Delicate

2 Early intervention time

3 Good risk control.Put forward Fang Dong's response to the wind meeting

4. Control Law Network for Changes

Cons:

High cost and high technical ability

Scope of application:Major projects involving personal and property safety

RUP (Rational Unified Process), unified development process model

Test Intervention Points:After each stage is coded

Scope of testing: Scope of work earlier in this phase, scope of work in earlier phases

Benefits:

1. Improve test coverage

2. Simplify the testing process and reduce the cost of testing (only test this stage and those affected before)

3. Semi-finished products are submitted at each stage, and the project success rate is high

Cons:

1. Repeated work is important

2. High technology content

Scope of application: relatively scattered functions

IPD model

Test intervention point:After software and hardware development

Scope of testing:Software and hardware

Advantages: All departments are involved in the entire project process, which can better integrate the opinions of all departments to make a decision

Disadvantages:High cost and difficult to manage

Scope of application: Large scale, many affected departments, need multiple departments and software and hardware support.

In terms of personal value, one is to give us a career development direction

4. How to find as many defects as possible?

Communication

Communicate with development in the early stage of testing to confirm the focus of the test and confirm the priority of the test

Understand the developer's technical and business background, business level, technical level, code quality, staff mobility

After the test

Statistics on discovered bugs to know that bugs with high probability should be tested in new projects

For code code complexity

Version management

Extensive testing of the base version for basic testing

The last version before acceptance must be fully retested

Test method

Black-box approach Functional issues Cannot guarantee that all code logic is executed Supplement black-box testing with white-box testing ideas

Static testing method, document review, code walkthrough

Testing process

The previous stage provides key guidance for the next stage

The user participated in the test or the user reported the error and problem as the necessary content for the next test or test