Checklist - GUI Testing Test Scenarios/Testcases

Generic level of testcases for testing windows GUI applications:

Listed below checklist of GUI testing scenarios:

TC_ID	Test Scenarios	Headline	Testcase Description	Expected Result
GUI_001	Application.exe file	Check on application.exe and tool tip	1. Application.exe name should be in proper naming convention 2. Move on mouse over the application.exe file and check if application.exe is providing correct tool tip information to the user 3. Application.exe should  display meaningful representation of icon to the user. Note: Same application caption should reflect on everywhere like task manager, program manager...	Application.exe file must be displayed clearly and correctly.
GUI_002	Launching the application	Check on application icon and launching the application	1. Double click on application.exe icon 2. Check application should launch and displaying main screen UI to the user without any errors.	Application must be launched successfully
GUI_003	Application Termination	Closing the application	1. Launch the application 2. Close the application (by click on close button or File->Exit) 3. Ensure Conformation pop up message is displayed to the user.	Application should terminate gracefully
GUI_004	Multiple Instance support	Check on launching the application multiple times	1. Double click on the application.exe icon and launch the Instance 1 2. Again try to launch the 2nd instance of the application 3. Ensure Instance2 is not getting launched and Instance1's currently active windows remains the same	Instance1's active screen should displayed to the user and also only instance1 should be in task manager.
GUI_005	Title Bar	Check on Title Bar	1. Lanuch the application 2. Ensure title bar is displaying the application icon and followed by application name and it's version 3. Navigate to other window/screen and ensure on all navigation windows title bar remains the same	Application icon followed by the application name must be displayed in the title bar on the launch of the application.
GUI_006	Menu Bar	Check on Menu Bar	1. Launch the application 2. Menu bar should display at the top and bottom of the title bar. 3. Ensure Help, About button in all the screens for access	All screens should have a Help button, F1 should work doing the same. About should display on all the screen and it should display version informations
GUI_007	Status Bar	Check on Status Bar	1. Launch the application 2. Status bar should display progress of test execution and status information like disk info, testcases running or not, cursor pointing position and so on. 3. Ensure status bar is getting updated with dynamic changes	Status bar must get updated with the dynamic changes of the application.
GUI_008	Tool tip	Check the tool tip information on mouse over	1. Launch the application 2. Move the mouse on the widgets/icons 3. Ensure tool tip os shown to the user, whenever user mouse over on the widgets/icons	Tool tip must be clearly and correctly displayed to the user.
GUI_009	Shortcut keys	Check on Shortcut key	1. Launch the application 2. Ensure Shortcut key is supported to trigger the functionality without mouse click on the UI screens. Note: Ensure standard shortcut keys are followed. For Say: Ctrl+S is for Saving, Ctrl+Q for Quit and So on Note: Check the behavior of the TAB, ESC, Space bar, Enter keypress as well	Shortcut key should be supported on the application
GUI_010	Multiple selection on Hold keys (Control/Shift)	Multiple selection	Incase of selecting multiple choices, Ensure Application is supporting On Hold keys (Control and Shift key) to allow the user to select the multiple selections	Application should allow the user to select any multiple choices
GUI_011	Popup message box	Check on Popup message box	Ensure application is popuping appropriate message to the user in standard format. Note: For Ex: Error popup message should display Error icon on the popup box	All popup message should get display in standard format
GUI_012	Resize	Check on Resizing the dialog boxes	1. Launch the application 2. Resize the dialog boxes and/or screen frames if any 3. Ensure resizing of the box/frames should not affect the application viewability and functionality	Resizing of the box/frames should not affect the application viewability and functionality
GUI_013	Minimize, Maximize, Restore	Test to check the Minimize, Maximize, Restore properties	1. Launch the application 2. Check if user is able to minimize, maximize and restore to previous screen size display by pressing Minimize, Maximize and Restore buttons correspondingly.	Application should allow the user to minimize, maximize and restore.
GUI_014	Widget, frames alignments	Test to check for alignment of frames, text boxes and other Widgets	1. Launch the application 2. Check if application is displaying all the widgets in uniform and it’s alignments like text box, frames, radio/check options, text alignments, etc., 3. Ensure on resizing of the screen should not affect the aligments of text/widgets	All Widgets, text should displayed properly
GUI_015	Navigations	Test to check all screen navigation links	1. Launch the application 2. Navigate one screen to another screen 3. Check if user is able to navigate the screens without any ambiguous display or in delay in display	Application should display the screen without delay in loading and should not display any ambiguously.
GUI_016	Spell Check	Test to check for spell check	1. Launch the application 2. Ensure there is no spell mistake and verbal mistakes on the text display.	Application should display meaning ful words and without any spell check
GUI_017	Uniform Font Size and Style	Test to check for font display - like Color, Size, Style and Background color	1. Launch the application 2. Ensure application is displaying uniform text style, color and size. 3. Ensure display of text should be eye-catching and should not as eye-hitting one to the user.	Display of text should be eye-catching and should not as eye-hitting one to the user
GUI_018	Set Focus	Test to check for set focus on widgets	1. Launch the application 2. Ensure after filling/entering/tab any input fields, cursor should set focus on next widgets.	GUI should provide usablity of the end user on set focus.
GUI_019	Screen Resolution	Check under different screen resolution of 1280*1024, 1280*960, 1280*720, 1152*864, 1024*768, 800*60	1. Set different monitor screen resolution (1280*1024, 1280*960, 1280*720, 1152*864,1024*768,800*600) 2. Launch the application and ensure display of GUI is not changed	GUI should not display any ambiguous display and should not disturb on change in screen resolution
GUI_020	Input field validation	Check on input field validation - boundary value testing, maximum digits, special chars, maximum values	1. Fill the input field box with boundary values and check the exception handling 2. Fill the input field box with alpha numberic, special character including white space and check if application is handling the error exceptions 3. Fill the input field box with maximum values or maximum digits and check if application is handling the exception	Application should catch all kinds of exception and throw appropriate error message to the user

when i surf on net, i got one more useful GUI testing checklist link. Might be this link also helpful for you, here it is http://bazman.tripod.com/checklist.html

Checklist - Log File Module Test Scenarios/Testcases

Generic level of testcases for testing Log file module of the Application and it’s content testing scenario’s.

Listed below checklist of log file testing testcases:

TC_ID	Headline	Testcase Description	Expected Result
Log_001	Log file generation	1. Log file shall be generated after successful execution of the feature. 2. In default case, log file shall get generated in applications' installation directory else on a user defined path at runtime based on user preferance	Log file should get generated.
Log_002	Log file generation at user defined path	1. Launch the application and set the user defined path at the run time and close the application 2. Again re-launch the application and check if log file is getting generated on the user defined path	Application should generate log file under user defined path
Log_003	Log file extension	Check if log file extension is as per specification.	Log file extension should be as per specification
Log_004	Log file naming convention check	Check if log filename is with proper naming convention	Log filename should follow proper naming convention
Log_005	Log file size check	1. Launch the application and execute the testcases for couple days. 2. Check the log file content are getting updated in a single file or maintained in multiple files once log file size exceeding as per specification	As per log file policy and project requirements, it need to be takencare of log file size at maximum, limit of log files generation and all
Log_006	Log file content check	1. Launch the application and execute the set of testcases 2. Check if log file content are getting updated with proper timestamp, Device serial number, application version and messages Note: Sometimes there will be differenece on log file timestamp and local system timestamp	Log file content should be updated with proper timestamp and content
Log_007	Formatting and Fonts of log file	Ensure Formatting and Fonts used in log file are consistent and correct with neat alignment	Formatting and Fonts used in log file shall be consistent and correct
Log_008	incase of Single log file generation - Check on appending of file content	1. Launch the application and execute set of testcases 2. Ensure log file is captured all the content 3. Close the application and re-launch the application 4. Execute the set of testcases and check if log file content is getting appended and not overwritten on the same single log file	Log content should be get appended and should not overwrite the existing content.
Log_009	Incase of Single log file doesn't exists	1. Launch the application and execute set of testcases 2. Ensure log file is captured all the content 3. Close the application and delete the generated log file 4. Re-launch the application and execute the set of testcases 5. Check if log file is created newly and contents are captures on it.	Log file should get generated and all content should be updated.
Log_010	incase of single log file generation - check on multiple instance	1. Launch multiple instance of the application 2. Check the behavior of the application and log file generation/updation	incase application supports multiple instance, log file should be maintained with proper timestamp or convention instead of appending on a single log file
Log_011	Uninstallation of the application	1. Install and invoke the application 2. Execute any feature of the product that supports logging 3. Exit application execution 4. Explore log storage directory, validate recently generated log file is retained. 5. Un-install the application 6. Explore log storage directory, validate recently generated log file is retained.	Generated log file's should be retained.

Checklist - Installation Module Test Scenarios/Testcases

This is my first blog posting on testing. I’m started my career as mobile application tester and later on my testing career moved to testing applications and device drivers. I thought to start testing blog to post and share all of my work experiences on testing. Here in this post I would like to share generic level of testcases for testing Installation module of Application and not the installation wizard means test scenarios of application installation module.

TC_ID	Test Scenarios	Headline	Testcase Description	Expected Result
INS_001	Installation setup	Check on Installation Setup - extension file and icon respresentation	1. Ensure Installer setup file is in .exe or .bat or .inf or .msi file extension type. 2. Ensure Installer setup file represented in standard icon and/or company standard icon	Installer setup should be in standard file extension and icon.
INS_002	Installation setup	Check on Installation Setup - Tooltip on mouse over	1. Move the mouse over the installation setup file and/or select the setup file. 2. Check if tool tip box is showing Application name, Company name, Version, File size and Date created	Tool tip should display correct and accurate information about the application informations like version, company name, date created or modified date and file size.
INS_003	Installation setup	Check on installation wizard dialogbox steps	1. Double click on the installer 2. Check the installation wizard dialogbox is displaying the correct information about the application information like name, version number.	Installer wizard should display correct application information everywhere and should not differ from the tool tip and actual application information.
INS_004	Installation setup	Check on installation wizard navigation and input fields values	1. Double click on the installer 2. Ensure user is able to click on Next and then back button to view the previous screen and all for modification and input fields values are remains same 3. Ensure user is able to alter the filled values and proceeding the installation	Installation wizard should allow the user for navigation and filled input values should remains the same.
INS_005	Installation setup	Check on multiple instance of installation wizard	1. Double click on the installer and ensure installer wizard is getting displayed to the user 2. Before completion of the installation again click on the installer 3. Check if installer wizard remains the same of the instance1 and also set focus on it 4. Ensure only one application progress running under task manager	Installation wizard should not allow multiple instance of installation on the same time
INS_006	Installation setup	Check the termination of installation wizard	1. Double click on the installer 2. Before completion of the installation, try to exit/terminate the installation 3. Ensure user is able to terminate the installation wizard after the conformation popup message to the user. Note: Cancellation of installation - if user press 'Esc', exit, Abort, cancel	Installation wizard should display the termination conformation popup message to the user and should terminate the wizard.
INS_007	Installation setup	Check the installation under not recommended platforms	1. Try to install the application under non-recommended system configurations (Note: Installing the application under windowXP, eventhough application only support windows7 platform) 2. Check if installer is throwing appropriate error message to the user.	Installation setup should fail to install the application and should throw appropriate error message to the user.
INS_008	Installation setup	Installation under recommended system configuration	1. Install application under recommended system configuration and according to user manual installation guidelines. 2. Check if user is able to install the application without any error or warnings messages. Note: Default Path - C:\Program Files\App_name\	Application should install successfully without any warnings and/or errors.
INS_009	Installation setup	Installation of supported packages/patches, if any	1. Install application under recommended system configuration and according to user manual installation guidelines. 2. Check if installer setup is installing the supported packages and/or patches which are mandatory for the application, if any	Installer setup should install the supported packages/patches which are mandatory for the application.
INS_010	Installation setup	Installing the setup after termination of the installation	1. Double click on the installer and ensure installer wizard is getting displayed to the user 2. Before completion of the installation, terminate the installation 3. Again double click on the installer and check user is able to install the application successfully Note: In some cases, second time installation failed due to effect of first installation termination.	Installer setup should install the application.
INS_011	Installation setup	Re-installation of the application	1. Double click on the installer and install the application 2. After the successful installation, again double click on the installer to re-install the application 3. check the behavior of the application.	Installer setup should display conformation popup message of overwrite and proceed with user inputs.
INS_012	Installation setup	Try to install the application, when application is in running state	1. Double click on the installer and install the application 2. After the successful installation, launch the application 3. Try to install the application again and check the behavior of the application.	Application should display appropriate error message to the user saying "Please close the application before proceeding Re-installation".
INS_013	Installation setup	Try to uninstall the application, when application is in running state	1. Double click on the installer and install the application 2. After the successful installation, launch the application 3. Try to uninstall the application and check the behavior of the application.	Application should display appropriate error message to the user saying "Please close the application before proceeding uninstallation".
INS_014	Userdefined installation path	Try to set user defined path for the installation	1. Double click on the installer 2. On the installation wizard, try to alter/set user defined path instead of default path 3. Check if installer is allowing the user to setting the path 4. Ensure application is installed on the user defined installation path	Installer should allow user to set the installation path and should install the application on defined path as well
INS_015	User manual, Help file	Check on user manual and help files	1. Install the application 2. Ensure user manual guide and help files as part of installation.	Installer should install user manual in pdf file format and helper/supported files.
INS_016	Sample scripts	Check on sample scripts	1. Install the application 2. Ensure application is providing sample scripts for the user Note: Sample script availability is depends upon the project/application requirements.	Application should provide sample scripts in the installer package.
INS_017	Uninstallation	To check the Uninstallation functionality	1. After successful installation of the application, click on uninstall option to uninstall application 2. Check the Uninstaller removed the application and it's dependency files. Note: Uninstall should happen irrespective of the installation path	Applicaiton should be uninstalled successfully and during uninstallation process, all necessary dependency files should be completely removed from the PC along with short cut icons Note: Log file should be retained.
INS_018	Re-installation	To check Re-installation of application after uninstallation	1. Install the application 2. Ensure application is working normally 3. Uninstall the application and restart the system. 4. Install the application once again 5. Check if application is working fine after re-installation.	Application should work fine normally
INS_019	Booting	To verify OS booting after successful installation	1. Install the application 2. Restart the pc. 3. Check if PC is restarted successfully without any booting failures and ensure installed drivers on place.	PC should restart successfully after installation and application should work as expected.
INS_020	Registry	To check the application version in the registry after installation	1. Install the application 2. Go to windows registry settings	Application name,version and installation path should be seen correctly in the windows registry
INS_021	Registry	To check the application version in the registry after uninstallation	1. Install the application 2. Ensure application is registered under Registry 3. Uninstall the application 4. Check if registry of the application is removed from the windows registry settings.	Registry of the application should be removed from the windows registry settings.
INS_022	Installation on Fresh PC/Non MS-Visual studio	To verify the installer setup under non-availability of MS visual studio	1. Precondition: MS Visual Studio tool should not be installed on the test PC. 2. Double click on the installer setup and try to install the application. 3. Check if user is able to install the application successfully or not. Note: There should not be any dependency.	Application should install successfully and ready for usage.
INS_023	Installer requires ADMIN privileges	Check for the user privileges before starting installation	1. Ensure installer is installed under ADMIN privileges	In most of the cases, installer requires ADMIN privileges
INS_024	Installing the application under different language OS	Check the installation of the application under different OS language (Korean OS)	1. Install the application and ensure user is able to launch the application under different language OS	Application should support different language OS
INS_025	Installing the application under full disk space drive	Check the installation of the application under disk full drive	1. Try to install the application under disk full drive 2. Check if installer is displaying error message to the user saying Disk is full and failed to install the application	Installer should display appropriate error message to the user.