WEB TESTING While testing a web application you need to consider following Cases: Functionality Testing Performance Testing

ng Usability Testing Server Side Interface Client Side Compatibility Security Functionality: In testing the functionality of the web sites the following should be tested: Links i. Internal Links ii. External Links iii. Mail Links iv. Broken Links Forms i. Field validation ii. Error message for wrong input iii. Optional and Mandatory fields Database * Testing will be done on the database integrity. Cookies * Testing will be done on the client system side, on the temporary Internet files. Performance : Performance testing can be applied to understand the web sites scalability, or to benchmark the performan ce in the environment of third party products such as servers and middleware for potential purchase. Connection Speed: Tested over various networks like Dial Up, ISDN etc Load: i. What is the no. of users per time? ii. Check for peak loads and how system behaves iii. Large amount of data accessed by user Stress: i. Continuous Load ii. Performance of memory, CPU, file handling etc.. Usability: Usability testing is the process by which the human-computer interaction characteristics of a system are measured, and weaknesses are identified for correction. Ease of learning Navigation Subjective user satisfaction General appearance

Server Side Interface: In web testing the server side interface should be tested. This is done by verify that communication is done properly. Compatibility of server with software, hardware, network and database should be tested. Client Side Compatibility: The client side compatibility is also tested in various platforms, using various browsers etc.

Here are my thoughts on how a tester can write effective test cases: 1. Self-explanatory and specific test cases should have sufficient details so that even a new tester can execute the same without any help. All the pre-requisite which are required to execute a specific test should be mentioned in the tests itself. Further, it should clearly specify the purpose and scope of their steps. 2. Valid and concise test cases should have all designated steps to test based on expectations of the testing. It should not have unnecessary steps. If there are too many test steps in a single test case to be performed the tester may lose focus and aim. 3. Traceable test cases should cover all the requirements of the software, and every test case should be mapped with Requirement ID." This helps in ensuring that testing is providing 100% coverage to complete requirements and tester is performing testing for all requirements. Further, it also helps in impact analysis. 4. Maintainable with the changes in requirement, tester should be able to easily maintain the test suite of test cases. It should reflect the changes in software and accordingly steps should be modified. 5. Positive and negative coverage test cases should test for boundary values, equivalence classes, normal and abnormal conditions. Apart from testing for expected results, the negative coverage can help in testing failure conditions and error-handling. 6. Coverage for Usability aspect Test cases should include testing for UI interface from the aspect of ease of use. The overall layout and color should be tested against a style guide, if any defined for the software application under testing or should be tested against the signed off mock- up designs. Basic English punctuations, spellings, drop-down list categorizations such as depended pick lists should be covered. 7. Test Data there should be the diversity of the data which should be used in test cases such as Valid data, Legitimate invalid data (to test boundary value), Illegal and abnormal data ( to test error handling and recovery). 8. Non-Functional aspect the test cases should cover scenarios for basic performance testing of the application such as Multi-user operation, capacity test. It should cover security aspects such as user permissions, logging mechanism. Test cases for Browser support in case of web application. To summarize, the test cases should first be able to cover all the functional requirements, and then we should also include the test cases which are related to non- functional requirements as they are equally important for the proper functioning of the software.