General Testing Process -- Improved V Model
Talk about this diagram: Unit test, integration and component test is white box. First you test the little pieces in unit test; then put some pieces together: integration test. Unit, integration, component and system test tend to happen in IT. System and acceptance test is black box.
The traditional V model show that the software testing and analysis can play a role throughout the software development lifecycle, but the weakness is obviously, it also show that the testing is started in coding phase, we think the testing should begin at early requirement phase rather than the coding phase.
Do test planning and development of the spec concurrently: boxes to the left, to indicate this. Plan top down: UAT first, etc. Test execution happens later: boxes to the right, and happens bottom-up. The level of detail needed to generate the test cases flushes out holes in the requirements
Our testing model will be the improved V model – Plan top down, Testing starting at the beginning of the lifecycle with each iterations phase; Happen bottom-up, Test execution happens later.
Talk about this diagram: Unit test, integration and component test is white box. First you test the little pieces in unit test; then put some pieces together: integration test. Unit, integration, component and system test tend to happen in IT. System and acceptance test is black box.
The traditional V model show that the software testing and analysis can play a role throughout the software development lifecycle, but the weakness is obviously, it also show that the testing is started in coding phase, we think the testing should begin at early requirement phase rather than the coding phase.
Do test planning and development of the spec concurrently: boxes to the left, to indicate this. Plan top down: UAT first, etc. Test execution happens later: boxes to the right, and happens bottom-up. The level of detail needed to generate the test cases flushes out holes in the requirements
Our testing model will be the improved V model – Plan top down, Testing starting at the beginning of the lifecycle with each iterations phase; Happen bottom-up, Test execution happens later.
No comments:
Post a Comment