原文：
11 Steps for Software Testing Process
Step 1: Asses Development Plan and Status
documented翻译This first step is a prerequisite to building the VV&T Plan used to evaluate the implemented software solution. During this step, testers challenge the completeness and correctness of the development plan. Based on the extensiveness and completeness of the Project Plan the testers can estimate the amount of resources they will need to test the implemented software solutio n.
Step 2: Develop the Test Plan
Forming the plan for testing will follow the same pattern as any software planning process. The structure of all plans should be the same, but the con tent will vary based on the degree of risk the testers perceive as associated with the software being developed.
Step 3: Test Software Requirements
In complete, in accurate, or incon siste nt requireme nts lead to most software failures. The inability to get requirement right during the requirements gathering phase can also increase the cost of implementation significantly. Testers, through verification, must determine that the requirements are accurate, complete, and they do not conflict with another.
Step 4: Test Software Design
This step tests both external and internal design primarily through verification techniques. The testers are concerned that the design will achieve the objectives of the requirements, as well as the design being effective and efficient on the designmted hardware・
Step 5: Program (Build) Phase Testi ng
The method chosen to build the software from the internal design document will determine the type and extensiveness of the testers needed・ As the construction becomes more automated, less testing will be required during this phase・ However, if software is constructed using the waterfall process, it is subject to error and should be verified・ Exper
ience has shown that it is significantly cheaper to identify defects during the construction phase, than through dynamic testing during the test execution step.
Step 6: Execute and Record Result
This involves the testing of code in a dynamic state. The approach, methods, and tools specified in the test plan will be used to validate that the executable code in fact meets the stated software requirements, and the structural specifications of the design.
Step 7: Acceptance Test
Acceptanee testing enables users to evaluate the applicability and usability of the software in performing their day-to-day job functions. This tests what the user believes the software should perform, as opposed to what the documented requirements state the software should perfor m.
Step 8: Report Test Results
Test reporting is a continuous process. It may be both oral and written. It is important that defects and concerns be reported to the appropriate parties as early as possible, so that corrections can be made at the lowest possible cost.
Step 9: The Software Installation
Once the test team has confirmed that the software is ready for production use, the ability to execute that software in a production environment should be tested. This tests the interface to operating software, related software, and operating procedures・
Step 10: Test Software Changes
While this is shown as Step 10, in the context of performing maintenanee after the software is implemented, the concept is also applicable to changes throughout the implementation process・ Whenever requirements changes, the test plan must change, and the impact of that change on software systems must be tested and evaluate・
Step 11: Evaluate Test Effectiveness
Testi ng improvement can best be achieved by evaluati ng the effective ness of testi ng at the end of each software test assignment. While this assessment is primarily performed by the testers, it should involve the developers, users of the software, and quality assurance professionals if the function exists in the IT organization.

版权声明：本站内容均来自互联网，仅供演示用，请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系QQ:729038198，我们将在24小时内删除。