工作中的測試員

工作中的測試員

  When testing, you must decide how to exercise the program, then do it. The doing is ever so much more interesting than the deciding. A tester\'s itch to start breaking the program is as strong as a programmer\'s itch to start writing code - and it has the same effect: design work is skimped, and quality suffers. Paying more attention to running tests than to designing them is a classic mistake. A tester who is not systematic, who does not spend time laying out the possibilities in advance, will overlook special cases. They may be the same subtle ones that the programmers overlooked.

  在測試的時候，必須決定如何執行程序，然后完成它們。完成它們比決定它們要有趣的多。測試員渴望的是開始破壞程序，程序員渴望的是開始寫代碼——這導致相同結果：設計工作被忽略了，產品質量受到損害。將更多的注意力集中于運行測試而不是設計它們是一個典型錯誤。

  Concentration on execution also results in unreviewed test designs. Just like programmers, testers can benefit from a second pair of eyes. Reviews of test designs needn\'t be as elaborate as product design reviews, but a short check of the testing approach and the resulting tests can find significant omissions at low cost.

  集中于執行測試也導致未經審核的測試設計。就像程序員一樣，測試員也得益于第二雙眼睛的檢查。測試設計的審核不必像產品審核那樣嚴格，但是對測試方法和結果測試的快速檢查可以低成本地找到重要的疏忽。

  What is a test design?

  什么是測試設計？

  A test design should contain a description of the setup (including machine configuration for a configuration test), inputs given to the product, and a description of expected results. One common mistake is being too specific about test inputs and procedures.

  測試設計應當包含設置描述（包括配置測試的機器配置），對產品的輸入和預期結果的描述。一個常見錯誤是對測試輸入和過程過于注重細節。

  Let\'s assume manual test implementation for the moment. A related argument for automated tests will be discussed in the next section. Suppose you\'re testing a banking application. Here are two possible test designs:

  讓我們先假設一個手工測試實施。相關的自動化測試將在下一節討論。假設你在測試銀行應用程序。這里有兩個可能的測試設計：

  Design 1

  設計1

  Setup: initialize the balance in aclearcase/" target="_blank" >ccount 12 with $100.

  設置：將帳戶12的余額初始化為$100。

  Procedure:

  過程：

  Start the program.

  Type 12 in the Account window.

  Press OK.[Page]

  Click on the \'Withdraw\' toolbar button.

  In the withdraw popup dialog, click on the \'all\' button.

  Press OK.

  Expect to see a confirmation popup that says \"You are about to withdraw all the money from this account. Continue?\"

  Press OK.

  Expect to see a 0 balance in the account window.

  Separately query the database to check that the zero balance has been posted.

  Exit the program with File->Exit.

  啟動程序。

  在帳戶窗口中輸入12。

  按“確定”按鈕。

  點擊“取款”工具條按鈕。

  在彈出的取款對話框中，點擊“所有”按鈕。

  按“確定”按鈕。

  預期會看到一個確認消息：“您將從此帳戶中取出所有的錢，是否繼續？”

  按“確定”按鈕。

  在帳戶窗口中預期會看到余額為0。

  單獨查詢數據庫，檢查余額為0。

  通過“文件->退出” 退出程序。

  Design 2

  設計2

  Setup: initialize the balance with a positive value.

  設置：將帳戶余額初始化為一個正值。

  Procedure:

  過程：

  Start the program on that account.

  Withdraw all the money from the account using the \'all\' button.

  It\'s an error if the transaction happens without a confirmation popup.

  Immediately thereafter:

  - Expect a $0 balance to be displayed.

  - Independently query the database to check that the zero balance has been posted.

  啟動該帳戶的程序。

  用“所有”按鈕從帳戶中取出所有的錢。

  如果在事務發生時沒有彈出確認消息，則是一個錯誤。

  其后立即：

  - 預期余額會顯示$0。

  - 單獨查詢數據庫，檢查余額為0。  The first design style has these advantages:

  第一種設計風格有以下優點：

  · The test will always be run the same way. You are more likely to be able to reproduce the bug. So will the programmer.

  · 測試總是以相同方式運行。重現錯誤的可能性更大。程序員也一樣。

原文轉自：http://www.kjueaiud.com