What is Web Testing?

• Web testing is the name given to software testing that focuses on web applications. 
• Complete testing of a web-based system before going live can help address issues before the system is revealed to the public.
• Issues such as the security of the web application, the basic functionality of the site, its accessibility to handicapped users and fully able users, as well as readiness for expected traffic and number of users and the ability to survive a massive spike in user traffic, both of which are related to load testing.

Web security testing

• Web security testing tells us whether Web based applications requirements are met when they are subjected to malicious input data.

Web Testing Checklist

• Functionality Testing
• Link Testing
• Form Testing
• Cookie Testing
• HTML/CSS Validation
• Database Testing
• Usability testing
• Navigation Checking
• Content Checking
• Interface testing
• Web server and application server interface
• Application server and Database server interface.
• Compatibility testing
• Browser compatibility
• Operating system compatibility
• Mobile browsing
• Printing options
• Performance testing
• Load Testing
• Stress Testing
• Security testing
• URL Manipulation
• Session Testing
• SQL Injection
• Cross Site Scripting
• Vulnerability Testing
• Password Cracking
• Spoofing

For Complete Web Application Checklist, Please visit the below link: http://softwaretestingreference.blogspot.in/p/web-application-testing.html

What is Performance Testing?

• Performance testing is a testing performed to determine how a system performs in terms of responsiveness and stability under a particular workload. 
• It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.
• Performance testing is a means of quality assurance (QA). It involves testing software applications to ensure they will perform well under their expected workload.
• The goal of performance testing is not to find bugs but to eliminate performance bottlenecks
• The focus of Performance testing is checking a software program’s
• Speed – Determines whether the application responds quickly
• Scalability – Determines maximum user load the software application can handle.
• Stability – Determines if the application is stable under varying loads

Types of performance testing.

• Load testing – Load testing is the simplest form of performance testing. A load test is usually conducted to understand the behavior of the system under a specific expected load.
• Stress testing – involves testing an application under extreme workloads to see how it handles high traffic or data processing .The objective is to identify breaking point of an application.
• Endurance testing – is done to make sure the software can handle the expected load over a long period of time.
• Spike testing – Spike testing is done by suddenly increasing the number of, or load generated by, users by a very large amount and observing the behaviour of the system. The goal is to determine whether performance will suffer, the system will fail, or it will be able to handle dramatic changes in load.
• Volume testing – Under Volume Testing large no. of. Data is populated in database and the overall software system’s behavior is monitored. The objective is to check software application’s performance under varying database volumes.
• Scalability testing – The objective of scalability testing is to determine the software application’s effectiveness in “scaling up” to support an increase in user load. It helps plan capacity addition to your software system.
• Configuration testing - Rather than testing for performance from the perspective of load, tests are created to determine the effects of configuration changes to the system's components on the system's performance and behaviour. A common example would be experimenting with different methods of load-balancing.
• Isolation testing - Isolation testing is not unique to performance testing but a term used to describe repeating a test execution that resulted in a system problem. Often used to isolate and confirm the fault domain.