Checklist for Desktop Application Testing

Level 1 - User Interface Testing (GUI Testing)
a. Content wording used in the web pages should be correct.

b. Wrap-around should occur properly.

c. Instructions used in the application should be correct (i.e. if you follow each instruction does the expected result occur?)

d. Image spacing – To verify that images are displaying properly with text. 

Level 2 - Functional Testing

a. Check for broken links (Broken link refers to a hyperlink which does not work).

b. Warning messages: User input should get verified at system level according to business rules and error/warning messages should be flash to user for incorrect inputs.

c. Resolution change effect on the application: Ensure that application's functionality and design is compatible with the different resolutions.

d. Print: Following points must be verified

• Test the print functionality of the application when no printer connected - application should behave correctly if printer is not available.
• Test the print functionality of the application when printer is connected
• Ensure that application queues prints in printer if papers are not available in printer.
• To ensure that lengthy description of an event  is not truncating on print layout in selected event printing.

e. Theme change: Ensure the successful launch of application after theme change.

f. Installation Testing (Upgrade/Downgrade): Verify application is included in Programs and Features list after installation. Also Verify application is removed from Programs and Features list after uninstall. Keep in mind that older version of application should not be install on latest version.

g. Testing with multi user accounts: Open Control Panel, User Accounts, and add 2 user accounts (Standard and admin) to the system. With the application running, press Start, the Switch User to the user account just created.

Verify application launches and runs correctly on the newly created user account. Switch back and forth between user accounts and use the application in both. Watch for any performance decreases and check functionality.

h. Sleep: While the application is running, put the system to sleep (S3). Wake the system up after two minutes.

• Verify the application is still running.
• Verify there is no distortion or error.

i. Cache:

- Delete the application's cache, launch the application and verify that application should work properly.

- Delete the application's cache while application is running and verify that application should work properly.

Level 3 - Compatibility Testing

a. Test on different Operating systems: Some functionality in your web application may not be compatible with all operating systems. All new technologies used in web development like graphics designs, interface calls like different API’s may not be available in all Operating Systems. Test your web application on different operating systems like Windows (XP, Vista, Win7 etc), Unix, MAC, Linux, Solaris with different OS flavors.

Level 4 - Performance Testing

a. Long period of continuous use: Is site able to run for long period, without downtime.

b. Memory: Note down the average memory usage in Comments column.

c. Generate "Power Efficiency Diagnostics Report" by running the command powercfg /energy