配置測試和場景測試都測試產品的全面的、跨功能的方面。另一類測試是跨越產品以檢查在壓力(大量事務、很大的事務、大量并發事務)下的表現。將壓力測試和負載測試推遲到最后一刻才進行是一種常見的情況,但是這樣做的結果是,當你發現你的產品不能支持12個以上的用戶時,你已經沒有多少時間來采用實際的措施。
Two related mistakes are not testing the documentation and not testing installation procedures. Testing the documentation means checking that all the procedures and examples in the documentation work. Testing installation procedures is a good way to avoid making a bad first impression.
一個相關錯誤是不測試文檔,也不測試安裝過程。測試文檔意味著檢查文檔中所有過程和示例都能工作。測試安裝過程是避免給別人留下糟糕的第一印象的好方法。
How about avoiding testing altogether?
不做測試會怎么樣?
At a conference last year, I met (separately) two depressed testers who told me their management was of the opinion that the World Wide Web could reduce testing costs. "Look at [wildly successful internet company]. They distribute betas over the network and get their customers to do the testing for free!" The Windows 95 beta program is also cited in similar ways.
在去年的一個會議上,我(分別)遇到兩個沮喪的測試員,他們告訴我他們的管理是基于這樣一種意見:萬維網(World Wide Web)可以減少測試成本。“看看非常成功的網絡公司”。他們在網絡上分發β版,讓客戶免費給他們做測試!”。Windows 95的β程序也是這樣的。
Beware of an overreliance on beta testing. Beta testing seems to give you test cases representative of customer use - because the test cases are customer use. Also, bugs reported by customers are by definition those important to customers. However, there are several problems:
要當心對β測試的過分依賴。因為測試用例是客戶使用的,所以β測試似乎是給了你客戶使用的代表用例。另外,客戶報告的錯誤也是對客戶重要的。但是,有幾個問題:
1. The customers probably aren't that representative. In the common high-tech marketing model, beta users, especially those of the "put it on your web site and they will download" sort, are the early adopters, those who like to tinker with new technologies. They are not the pragmatists, those who want to wait until the technology is proven and safe to adopt. The usage patterns of these two groups are different, as are the kinds of bugs they consider important. In particular, early adopters have a high tolerance for bugs with workarounds and for bugs that "just go away" when they reload the program. Pragmatists, who are much less tolerant, make up the large majority of the market.
客戶可能不是代表。在一個普通的高科技市場營銷模型中,β用戶,特別是那種“將產品放到網站上讓他們下載”的情況,是早期的采用者。他們喜歡擺弄新技術。他們不是實用主義者,不是那種愿意等到新技術被證明是安全可靠后才采用的人。這兩種類別的使用方式是不同的,就像他們認為 bug 的重要程度是不同的一樣。特別地,早期的采用者對于能夠用變通方法解決的 bug和重新加載程序就能消失的 bug有較強的容忍性。但容忍性較差的實用主義者占據了市場的大部分。
2. Even of those beta users who actually use the product, most will not use it seriously. They will give it the equivalent of a quick test drive, rather than taking the whole family for a two week vacation. As any car buyer knows, the test drive often leaves unpleasant features undiscovered.
即使是那些實際使用產品的β用戶,大多數也不會認真地使用。他們會給一個類似于試駕車的快速測試,而不是帶著整個家庭休假兩周。很多購買汽車的人都知道,試駕車經常會遺漏一些令人不愉快的特性。
3. Beta users - just like customers in general - don't report usability problems unless prompted. They simply silently decide they won't buy the final version.
β用戶象客戶一樣,除非特別要求,一般不會報告可用性錯誤。他們只是暗自決定不去購買最終產品。
4. Beta users - just like customers in general - often won't report a bug, especially if they're not sure what they did to cause it, or if they think it is obvious enough that someone else must have already reported it.
β用戶象客戶一樣,常常不會報告 bug ,尤其是當他們不能確定是什么操作導致了錯誤,或者是他們認為這個錯誤很明顯,其他人肯定已經報告了。
原文轉自:http://www.uml.org.cn/Test/200709289.asp