Ravi

• Jun 1st, 2005

 

It?s clear that for testing any application, one should be clear about the requirements and specification documents. For testing Web application, the tester should know, what the web application deals with. For Testing Web application, the test cases written should be in two different types, 1) The Test cases related to the Look and Feel of the Web pages and navigation and 2) The test cases related to the functionality of the web application. Make sure, whether the web application is connected to the Database for the inputs. Write Test cases based on the Database and write test cases for the backend testing as well if there is any database. The web application should be tested for the server response time for displaying the web pages, Make sure the web pages under load as well. For load testing, the tools are very much useful for simulating the many users. 
 

garima

• Aug 12th, 2005

 

Ideally to test a web application, the components and functionality on both the client and server side slould be tested.But it is practically impossibly,the best approach to examine the project's requirements,set priorities based on  
risk analysis,and then determine where to focus testing efforts whthin budget and schedule constraints. 
To test a web application we need to perform testing for both GUI and client-server architecture. 
Based on many factors like project requirements,risk analysis,budget and schedule,we can determine that what kind of testing ll be appropriate for ur project.We can perform unit n integration testing,functionality testing,GUI testing,usability testing,compatibility testing,security testing ,perfomance testing,recovery testing,n regression testing.  
 

sireesha

• Dec 18th, 2005

 

the main concept to remember in web testing is testing in Off-line mode,two important coverages in web testing is URL's coverage,static text coverage.

Dhruti Shah

• Jan 7th, 2006

 

Sireesha,Pl. can you make it little more clear for me.My Email is GautamDhruti@yahoo.comalso if some one can answer me what test tools are good for web application testing ?Thanks in advance.Dhruti

rupasenthilkumar

 Profile Answers by rupasenthilkumar 

• Jan 11th, 2006

 

web application can be done by the tools like OPENSTA & QTP

sowmya

• Jan 18th, 2006

 

hi..

 

can u explain of URL's coverage and static text coverage in web testing

 

regards

soumya

ashish

• Sep 27th, 2006

 

Load runner is good tool for performance testing..

Girish

• Feb 6th, 2007

 

Perfect answer.Verymuch useful .Thanks

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 27th, 2009

 

Things to consider when testing a web application:
[not an exhaustive list]

- page layout
- initial focus
- tab order
- text appearance
- headings, titles, and labels
- links
- text boxes and validation
- menus and lists
- navigation
- scrolling and paging
- screen-based controls
- graphics, images, and multimedia
- search
- help
- accessibility
- security
- database
- functionality
- usability
- business logic
- concurrency
- user access and roles
- login and password
- state management
- localization
- internationalization
- compatibility
- performance
- stress
- load

Some typical problems discovered through web testing are:

1) Pages on the website are not properly validated and do not conform to industry standards (CSS, HTML/XHTML)
2) The application's business logic is not proper.
3) Mechandising content on pages are inassessible or incorrect (if applicable).
4) User inputs are not properly validated. 
5) User inputs do not meet technical specification.
6) Error messages are not generated or are incorrect.
7) Web page design (fonts, color scheme, layout) does not meet requirements. 
8) Broken links.
9) Feeds do not work properly.
10) Pages are not assessible for visually impaired.
11) Advertisements are incorrect or don't function as expected.
12) Copyright information is incorrect.
13) End User License Agreement (EULA) is incorrect.
14) Images have not been optimized or do not otherwise meet requirements.
15) Cookies don't work properly (if applicable).
16) Web client can't handle some of the messages returned by server.
17) Pages don't render properly with some operating systems and/or browsers.
18) Submitted data is not captured and/or stored properly in database.
19) It takes too long for some pages to render.
20) Performance lags when there are numerous simultaneous users.
21) Users have inappropriate access to roles or content.
22) User problems with login (password strength, failure to track login attempts, etc).
23) Concurrency issues (session problems) when multiple users are on the same page and/or when a single user is on multiple windows of the same page. 
24) Server log does not properly track transactions.
25) Website does is not properly secured (SSL).