如何測試web網站?

　　web網站本質上帶有web服務器和客戶端瀏覽器的C/S結構的應用程序。主要考慮web頁面、TCP/IP通訊、Internet鏈接、防火墻和運行在web頁面上的一些程序(例如，applet、javascript、應用程序插件)，以及運行在服務器端的應用程序(例如，CGI腳本、數據庫接口、日志程序、動態頁面產生器，asp等)。另外，因為服務器和瀏覽器類型很多，不同版本差別很小，但是表現出現的結果卻不同，連接速度以及日益迅速的技術和多種標準、協議。使得web測試成為一項正在不斷研究的課題。其它要考慮的如下：

　　1、服務器上期望的負載是多少(例如，每單位時間內的點擊量)，在這些負載下應該具有什么樣的性能(例如，服務器反應時間，數據庫查詢時間)。性能測試需要什么樣的測試工具呢(例如，web負載測試工具，其它已經被采用的測試工具，web 自動下載工具，等等)?

　　2、系統用戶是誰?他們使用什么樣的瀏覽器?使用什么類型的連接速度?他們是在公司內部(這樣可能有比較快的連接速度和相似的瀏覽器)或者外部(這可能有使用多種瀏覽器和連接速度)?

　　3、在客戶端希望有什么樣的性能(例如，頁面顯示速度?動畫、applets的速度等?如何引導和運行)?

　　4、允許網站維護或升級嗎?投入多少?

　　5、需要考慮安全方面(防火墻，加密、密碼等)是否需要，如何做?怎么能被測試?需要連接的Internet網站可靠性有多高?對備份系統或冗余鏈接請求如何處理和測試?web網站管理、升級時需要考慮哪些步驟?需求、跟蹤、控制頁面內容、圖形、鏈接等有什么需求?

　　6、需要考慮哪種HTML規范?多么嚴格?允許終端用戶瀏覽器有哪些變化?

　　7、頁面顯示和/或圖片占據整個頁面或頁面一部分有標準或需求嗎?

　　8、內部和外部的鏈接能夠被驗證和升級嗎?多久一次?

　　9、產品系統上能被測試嗎?或者需要一個單獨的測試系統?瀏覽器的緩存、瀏覽器操作設置改變、撥號上網連接以及Internet中產生的“交通堵塞”問題在測試中是否解決，這些考慮了嗎?

　　10、服務器日志和報告內容能定制嗎?它們是否被認為是系統測試的主要部分并需要測試嗎?

　　11、CGI程序、applets、javascripts、ActiveX 組件等能被維護、跟蹤、控制和測試嗎?

　　原文：

　　How can World Wide Web sites be tested?

　　Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort. Other considerations might include:

　　What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required under such loads (such as web server response time, database query response times). What kinds of tools will be needed for performance testing (such as web load testing tools, other tools already in house that can be adapted, web robot downloading tools, etc.)?

　　Who is the target audience? What kind of browsers will they be using? What kind of connection speeds will they by using? Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)?

　　What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations, applets, etc. load and run)?

　　Will down time for server and content maintenance/upgrades be allowed? how much?

　　What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it expected to do? How can it be tested?

　　How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant connection requirements and testing?

　　What processes will be required to manage updates to the web site's content, and what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.?

　　Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers?

　　Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site??

　　How will internal and external links be validated and updated? how often?

　　Can testing be done on the production system, or will a separate test system be required? How are browser caching, variations in browser option settings, dial-up connection variabilities, and real-world internet 'traffic congestion' problems to be accounted for in testing?

　　How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the system and do they require testing?

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