狠狠色丁香婷婷综合尤物/久久精品综合一区二区三区/中国有色金属学报/国产日韩欧美在线观看 - 国产一区二区三区四区五区tv

Steps for Software Testing Process

Step 1: Asses Development Plan and Status

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 solution.

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 content will vary based on the degree of risk the testers perceive as associated with the software being developed.

Step 3: Test Software Requirements
Incomplete, inaccurate, or inconsistent requirements 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 designated hardware.

Step 5: Program (Build) Phase Testing
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. Experience 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
Acceptance 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 perform.

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 maintenance 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
Testing improvement can best be achieved by evaluating the effectiveness of testing 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.

翻譯：

軟件測試的11個步驟

第一步：評定開發方案和狀態

這第一步是創建W＆T計劃的先決條件，W＆T計劃用于評估執行的軟件解決方案。在這一步，測試員可質疑開發方案的完整性和正確性。并且基于項目計劃的完整和延伸定義，測試員要估計出測試這個執行的軟件解決方案所需要的資源數量。

第二步：形成測試計劃

形成測試計劃應該要符合軟件開發過程的模式，所有計劃的結構應該是一樣的，內容則要基于測試員對開發中的項目的感知程度。

第三步：測試軟件的需求說明

不完整的，不正確的，或不一致的要求都會導致軟件開發失敗。 在需求收集階段，不正確說明軟件需求，會明顯的增加開發費用。 測試員通過查證，一定要保證需求說明的是正確的，完整的，并且不會有沖突。

第四步：測試軟件的設計

這一步測試員首先要能過查證技術測試軟件的外部和內部設計，測試設計是否能完成需求說明的目標和這些設計能否在指定的硬件上起作用。

第五步：軟件開發過程中的測試

根據內部設計文檔選擇的軟件開發方法將會決定測試員測試需要的類型和范圍。因為軟件構建變得更加自動化，所以這一階段要求相對少的測試，不過，如果軟件采用瀑布型的開發模式，容易產生錯誤，這些錯誤應該被發現。經驗表明，在構建階段發現問題會比在動態測試過程發現問題節省很多成本

第六步：執行和記錄錯誤

這個階段包括在動態狀態測試代碼，在測試計劃中指定的步驟，方法，工具會被用于驗證可執行代碼是否符合規定的軟件需求和設計的結構化規范

第七步：可接受性測試

可接受性測試能讓使用者在操作他們的日常工作所需功能時評估軟件的適用性和可用性。這樣能測試出使用者認為軟件應該實現什么功能，與需求文檔的中說明的軟件應該實現什么功能形成對照

第八步：報告測試結果

測試報告是一個持續的過程，可口頭表達也可記錄下來。 缺陷和涉及的問題要向相應的小組報告，并且報告要易于理解，這一點很重要。這樣就能以最低的可能成本修正問題

第十步：測試軟件變化

當進行到第十步，是軟件被安裝使用后的維護過程。相關概念隨著整個執行過程而改變，任何時候需求改變了，測試計劃也要相應改變，并且這些改變對于整個軟件的影響也要測試和評估。

第十一步：評估測試效率