寫一個 bug 報告，記錄一個可用性問題，希望能夠分配一個合理的高優先級（因為這個修復很明顯對每個人都很用，對有部分用戶來說還非常重要，并且也容易修改）？
2. file a bug report with the expectation that it will be assigned "enhancement request" priority and disappear forever into the bug database?
寫一個 bug 報告，希望它被分配為“功能提升請求”優先級并永遠從 bug 數據庫中消失？
3. file a bug report that yields a "works as designed" resolution code, perhaps with an email "nastygram" from a programmer or the development manager?
寫一個 bug 報告，產生一個“按設計工作”解決碼，可能還加上一個來自程序員或開發經理的“不同意”電子郵件?
4. not bother with a bug report because it would end up in cases (2) or (3)?
不打算費事去寫 bug 報告，因為它將以情況(2)或(3)結束？
If usability problems are not considered valid bugs, your project defines the testing task too narrowly. Testers are restricted to checking whether the product does what was intended, not whether what was intended is useful. Customers do not care about the distinction, and testers shouldn't either.
如果可用性問題不認為是有效的 bug，那么你們的項目將測試任務定義得太狹窄了。測試員嚴格限制為檢查產品是否按預期工作，而不管這種預期是否有效�？蛻舨魂P心這個區別，測試員也不應該關心。
Testers are often the only people in the organization who use the system as heavily as an expert. They notice usability problems that experts will see. (Formal usability testing almost invariably concentrates on novice users.) Expert customers often don't report usability problems, because they've been trained to know it's not worth their time. Instead, they wait (in vain, perhaps) for a more usable product and switch to it. Testers can prevent that lost revenue.
測試員經常是組織中唯一像專家一樣大量使用系統的人。他們會注意到專家會看到的可用性問題。（形式上的可用性測試幾乎不可避免地集中于沒有經驗的用戶。）專家客戶常常不會報告可用性問題，因為他們已經被訓練的知道不值得花時間去這樣做。相反，他們（也許是徒勞地）等待下一個可用的產品然后切換過去。測試員可以避免這個損失。
While defining the purpose of testing as "finding bugs important to customers" is a step forward, it's more restrictive than I like. It means that there is no focus on an estimate of quality (and on the quality of that estimate). Consider these two situations for a product with five subsystems.
將測試的目的定義為“找到對用戶重要的 bug ”是向前進了一步，但與我所喜歡定義相比仍有限制。這意味著沒有集中于質量評估（以及這種評估的質量）�？紤]一下測試含有五個子系統的產品的兩種情況。
1. 100 bugs are found in subsystem 1 before release. (For simplicity, assume that all bugs are of the highest priority.) No bugs are found in the other subsystems. After release, no bugs are reported in subsystem 1, but 12 bugs are found in each of the other subsystems.
在發布前，在子系統1中找到了100個bug 。（為了簡單起見，假設所有的 bug 都是最高級別的。）在其他子系統中沒有發現 bug 。在發布后，在子系統1中沒有報告 bug ，但在其他每個子系統中都報告了12個 bug 。
延伸閱讀
文章來源于領測軟件測試網 http://www.kjueaiud.com/
