What are different approach required for different types of testing?

Desktop Application testing:

1. User interface testing:

For any testing the first check is GUI. All the controls in the application should be used is proper manner.like size, font, place etc…

2. Functional testing:

• In functional testing more stress should be given to functionality of the application . the product build is right or not.
• Proper error message or warning message should be displayed in case of wrong input or action performed by the user.
• The basic functionality is working or not like print in case of no printer is connected with the system.

• The application is easily installation or not. 
• In case of any changes done in the system like theam change or resolution change application should work properly. Test with multiple account on the desktop.
• Sleep: While the application is running, put the system to sleep (S3). Wake the system up after two minutes. 

          a) Verify the application is still running.
          b) Verify there is no distortion or error

3. Compatibility testing: 

Test the application on different OS to find the compatibility .

4. Performance testing: 

Launch time required to start the application, Memory use

Web based application testing:

Step 1: User interface testing:

• Content, wording , label used on web page should be correct and meaningful.
• Wrap-around should occur properly.
• Instruction given on web page should be correct.
• Images on the web page should be placed properly and does not take long time to load.
• All the controls placed properly.
• View in text browser: Test each web page in text-only browser, or text-browser emulator. It will help you pick up on badly-chosen or missing ALT texts. 

Step 2 - Functional Testing

• Check for broken links 
• Validate the HTML: 
• Disable the cookies from your browser settings. If you are using cookies on your site, your sites major functionality will not work by disabling the cookies. See if appropriate messages are displayed.
• (A cookie is a small piece of information stored as a text file on your computer that a web server uses when you browse certain web sites that you've visited before).
• Switch JavaScript off: It is important to check that your site still functions with Java script disabled or provide proper Java script error message
• Warning messages: Error/warning messages should be flash to user for incorrect inputs.

Step 3 - Interface Testing

• Data display on browser should match with data available on server: To test browser and server interface, run queries on the database to make sure the transaction data is being retrieve and store properly.
• Error Handling: Make sure system can handle application errors.

Step 4 - Compatibility Testing

• Test on different Operating systems: Test your web application on different operating systems like Windows (XP, Vista, Win7 etc), Unix, MAC, Linux, Solaris with different OS flavors.
• Test on different Browsers: Test web application on different browsers like: - Firefox, as that has the best standards compliance and is the second most-used browser. Internet Explorer for Windows – currently the most widely used browser (IE6, IE7, IE8). Opera – growing in popularity due to its speed and pretty good standards compliance. Mobile browsing: This is new technology age. So in future Mobile browsing will rock. Test your web pages on mobile browsers. Compatibility issues may be there on mobile.

Step 5 - Security Testing

• Limit should be defined for the number of tries: Is there a maximum number of failed logins allowed before the server locks out the current user?
• Verify rules for password selection.
• Is there a timeout limit?
• Test by pasting internal url directly into browser address bar without login. Internal pages should not open.
• Test the CAPTCHA for automates scripts logins.
• Test if SSL is used for security measures. If used proper message should get displayed when user switch from non-secure http:// pages to secure https:// pages and vice versa.
• All transactions, error messages, security breach attempts should get logged in log files somewhere on web server.
• Clear your Cache: Be sure to clear the browser cache, including cookies, before each test.
• Session hijacking: If your application has a session identifier number in the URL decrease that number by one and reload the page. The app has a session hijacking vulnerability if the app then "sees" you as a different user. 

Step 6 - Performance testing:

• Can your site handle a large amount of users requesting a certain page.
• Long period of continuous use: Is site able to run for long period, without downtime.