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.