Shulou(Shulou.com)06/02 Report--

1. Definition:

All tests are carried out at a later stage of development.

Second, the period of occurrence

A test project with a certain complexity of planning and detailed documentation

The project schedule is complex and the time is long enough to delay the test.

Third, trap performance

In the overall schedule of the project, the test is scheduled to be executed in the later stage of development.

Testing is involved only after requirements engineering, architecture engineering, design, and coding implementation, when all defects have been created. (found when it fails to prevent or occur)

In the early and middle stages of the development cycle, there are no plans to perform unit or integration tests.

During the current incremental and iterative build, there is not enough time to test, so that some or all of the tests of the current build are deferred to the subsequent build process.

IV. Negative consequences

There is not enough time in the schedule to correct the major defects found.

It is difficult to achieve and demonstrate the required test coverage.

Because many of the systems are integrated before testing, it is difficult to find and locate the Bug that is still hidden inside the system.

Testing is postponed from one build to another, creating a growing test shock wave that can never be executed unless the schedule is fundamentally changed and work other than testing is postponed until the test catches up (necessary).

Fifth, reasons

The project uses a traditional, continuous waterfall model, without requirements, architecture, and design testing (that is, using a single-v model instead of a double-v model).

Management does not have test team personnel in the early stages of the development cycle.

Management does not recognize the need for low-level (unit, integration) testing.

Not enough time is allocated within incremental, iterative builds to develop iterative increments and fully test.

VI. Suggestions

Preparation phase:

From early in the development process, plan and schedule the test schedule in an iterative, incremental, and parallel manner.

Provide incremental and iterative testing training.

Incorporate iterative and incremental testing into the system engineering process of the project.

Enable phase:

Provide adequate test resources (people, tools, budget, schedule) early in the development process

Execution phase:

From the early days of development, tests are executed iteratively, incrementally, and in parallel.

Testing works closely with developers to conduct unit and integration testing as soon as new or updated components are available.

Verification phase:

Determine whether testing is carried out iteratively and incrementally and in parallel with design, implementation, and integration in an ongoing manner (major project milestones).

Use test metrics to determine test status and continuous progress.

VII. Related Bug

The testing and engineering processes are not integrated, and testing, as a stage, is not involved in the early stage.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.