180+ Sample Test Cases for Testing Web and Desktop Applications – Comprehensive Testing Checklist

This is a testing checklist for web and desktop applications.

Note – This article is little long (over 2700 words). My goal is to share one of the most comprehensive testing checklist ever written and this is not yet done. I’ll keep updating this post in future with more scenarios. If you don’t have time to read it now, please feel free to share with your friends and bookmark it for later.

Make testing checklist as an integral part of test cases writing process. Using this checklist you can easily create hundreds of test cases for testing web or desktop applications. These are all general test cases and should be applicable for almost all kind of applications. Refer these tests while writing test cases for your project and I’m sure you will cover most testing types except the application specific business rules provided in your SRS documents.

Software Testing Checklist

Though this is a common checklist, I recommend preparing a standard testing checklist tailored to your specific needs using below test cases in addition with application specific tests.

Importance of Using Checklist for Testing:
- Maintaining a standard repository of reusable test cases for your application will ensure the most common bugs will be caught more quickly.
– Checklist helps to quickly complete writing test cases for new versions of the application.
– Reusing test cases help to save money on resources to write repetitive tests.
– Important test cases will be covered always making it almost impossible to forget.
– Testing checklist can be referred by developers to ensure most common issues are fixed in development phase itself.

Few notes to remember:
1) Execute these scenarios with different user roles e.g. admin user, guest user etc.
2) For web applications these scenarios should be tested on multiple browsers like IE, FF, Chrome, and Safari with versions approved by client.
3) Test with different screen resolutions like 1024 x 768, 1280 x 1024, etc.
4) Application should be tested on variety of displays like LCD, CRT, Notebooks, Tablets, and Mobile phones.
4) Test application on different platforms like Windows, Mac, Linux operating systems.

Comprehensive Testing Checklist for Testing Web and Desktop Applications:

Assumptions: Assuming that your application supports following functionality
– Forms with various fields
– Child windows
– Application interacts with database
– Various search filter criteria and display results
– Image upload
– Send email functionality
– Data export functionality

General Test Scenarios

1. All mandatory fields should be validated and indicated by asterisk (*) symbol
2. Validation error messages should be displayed properly at correct position
3. All error messages should be displayed in same CSS style (e.g. using red color)
4. General confirmation messages should be displayed using CSS style other than error messages style (e.g. using green color)
5. Tool tips text should be meaningful
6. Dropdown fields should have first entry as blank or text like ‘Select’
7. Delete functionality for any record on page should ask for confirmation
8. Select/deselect all records options should be provided if page supports record add/delete/update functionality
9. Amount values should be displayed with correct currency symbols
10. Default page sorting should be provided
11. Reset button functionality should set default values for all fields
12. All numeric values should be formatted properly
13. Input fields should be checked for max field value. Input values greater than specified max limit should not be accepted or stored in database
14. Check all input fields for special characters
15. Field labels should be standard e.g. field accepting user’s first name should be labeled properly as ‘First Name’
16. Check page sorting functionality after add/edit/delete operations on any record
17. Check for timeout functionality. Timeout values should be configurable. Check application behavior after operation timeout
18. Check cookies used in an application
19. Check if downloadable files are pointing to correct file paths
20. All resource keys should be configurable in config files or database instead of hard coding
21. Standard conventions should be followed throughout for naming resource keys
22. Validate markup for all web pages (validate HTML and CSS for syntax errors) to make sure it is compliant with the standards
23. Application crash or unavailable pages should be redirected to error page
24. Check text on all pages for spelling and grammatical errors
25. Check numeric input fields with character input values. Proper validation message should appear
26. Check for negative numbers if allowed for numeric fields
27. Check amount fields with decimal number values
28. Check functionality of buttons available on all pages
29. User should not be able to submit page twice by pressing submit button in quick succession.
30. Divide by zero errors should be handled for any calculations
31. Input data with first and last position blank should be handled correctly

GUI and Usability Test Scenarios

1. All fields on page (e.g. text box, radio options, dropdown lists) should be aligned properly
2. Numeric values should be right justified unless specified otherwise
3. Enough space should be provided between field labels, columns, rows, error messages etc.
4. Scroll bar should be enabled only when necessary
5. Font size, style and color for headline, description text, labels, infield data, and grid info should be standard as specified in SRS
6. Description text box should be multi-line
7. Disabled fields should be grayed out and user should not be able to set focus on these fields
8. Upon click of any input text field, mouse arrow pointer should get changed to cursor
9. User should not be able to type in drop down select lists
10. Information filled by users should remain intact when there is error message on page submit. User should be able to submit the form again by correcting the errors
11. Check if proper field labels are used in error messages
12. Dropdown field values should be displayed in defined sort order
13. Tab and Shift+Tab order should work properly
14. Default radio options should be pre-selected on page load
15. Field specific and page level help messages should be available
16. Check if correct fields are highlighted in case of errors
17. Check if dropdown list options are readable and not truncated due to field size limit
18. All buttons on page should be accessible by keyboard shortcuts and user should be able to perform all operations using keyboard
19. Check all pages for broken images
20. Check all pages for broken links
21. All pages should have title
22. Confirmation messages should be displayed before performing any update or delete operation
23. Hour glass should be displayed when application is busy
24. Page text should be left justified
25. User should be able to select only one radio option and any combination for check boxes.

Test Scenarios for Filter Criteria

1. User should be able to filter results using all parameters on the page
2. Refine search functionality should load search page with all user selected search parameters
3. When there is at least one filter criteria is required to perform search operation, make sure proper error message is displayed when user submits the page without selecting any filter criteria.
4. When at least one filter criteria selection is not compulsory user should be able to submit page and default search criteria should get used to query results
5. Proper validation messages should be displayed for invalid values for filter criteria

Test Scenarios for Result Grid

1. Page loading symbol should be displayed when it’s taking more than default time to load the result page
2. Check if all search parameters are used to fetch data shown on result grid
3. Total number of results should be displayed on result grid
4. Search criteria used for searching should be displayed on result grid
5. Result grid values should be sorted by default column.
6. Sorted columns should be displayed with sorting icon
7. Result grids should include all specified columns with correct values
8. Ascending and descending sorting functionality should work for columns supported with data sorting
9. Result grids should be displayed with proper column and row spacing
10. Pagination should be enabled when there are more results than the default result count per page
11. Check for Next, Previous, First and Last page pagination functionality
12. Duplicate records should not be displayed in result grid
13. Check if all columns are visible and horizontal scroll bar is enabled if necessary
14. Check data for dynamic columns (columns whose values are calculated dynamically based on the other column values)
15. For result grids showing reports check ‘Totals’ row and verify total for every column
16. For result grids showing reports check ‘Totals’ row data when pagination is enabled and user navigates to next page
17. Check if proper symbols are used for displaying column values e.g. % symbol should be displayed for percentage calculation
18. Check result grid data if date range is enabled

Test Scenarios for a Window

1. Check if default window size is correct
2. Check if child window size is correct
3. Check if there is any field on page with default focus (in general, the focus should be set on first input field of the screen)
4. Check if child windows are getting closed on closing parent/opener window
5. If child window is opened, user should not be able to use or update any field on background or parent window
6. Check window minimize, maximize and close functionality
7. Check if window is re-sizable
8. Check scroll bar functionality for parent and child windows
9. Check cancel button functionality for child window

------------

Database Testing Test Scenarios

1. Check if correct data is getting saved in database upon successful page submit
2. Check values for columns which are not accepting null values
3. Check for data integrity. Data should be stored in single or multiple tables based on design
4. Index names should be given as per the standards e.g. IND_<Tablename>_<ColumnName>
5. Tables should have primary key column
6. Table columns should have description information available (except for audit columns like created date, created by etc.)
7. For every database add/update operation log should be added
8. Required table indexes should be created
9. Check if data is committed to database only when the operation is successfully completed
10. Data should be rolled back in case of failed transactions
11. Database name should be given as per the application type i.e. test, UAT, sandbox, live (though this is not a standard it is helpful for database maintenance)
12. Database logical names should be given according to database name (again this is not standard but helpful for DB maintenance)
13. Stored procedures should not be named with prefix “sp_”
14. Check is values for table audit columns (like createddate, createdby, updatedate, updatedby, isdeleted, deleteddate, deletedby etc.) are populated properly
15. Check if input data is not truncated while saving. Field length shown to user on page and in database schema should be same
16. Check numeric fields with minimum, maximum, and float values
17. Check numeric fields with negative values (for both acceptance and non-acceptance)
18. Check if radio button and dropdown list options are saved correctly in database
19. Check if database fields are designed with correct data type and data length
20. Check if all table constraints like Primary key, Foreign key etc. are implemented correctly
21. Test stored procedures and triggers with sample input data
22. Input field leading and trailing spaces should be truncated before committing data to database
23. Null values should not be allowed for Primary key column

Test Scenarios for Image Upload Functionality

(Also applicable for other file upload functionality)
1. Check for uploaded image path
2. Check image upload and change functionality
3. Check image upload functionality with image files of different extensions (e.g. JPEG, PNG, BMP etc.)
4. Check image upload functionality with images having space or any other allowed special character in file name
5. Check duplicate name image upload
6. Check image upload with image size greater than the max allowed size. Proper error message should be displayed.
7. Check image upload functionality with file types other than images (e.g. txt, doc, pdf, exe etc.). Proper error message should be displayed
8. Check if images of specified height and width (if defined) are accepted otherwise rejected
9. Image upload progress bar should appear for large size images
10. Check if cancel button functionality is working in between upload process
11. Check if file selection dialog shows only supported files listed
12. Check multiple images upload functionality
13. Check image quality after upload. Image quality should not be changed after upload
14. Check if user is able to use/view the uploaded images

Test Scenarios for Sending Emails

(Test cases for composing or validating emails are not included)
(Make sure to use dummy email addresses before executing email related tests)
1. Email template should use standard CSS for all emails
2. Email addresses should be validated before sending emails
3. Special characters in email body template should be handled properly
4. Language specific characters (e.g. Russian, Chinese or German language characters) should be handled properly in email body template
5. Email subject should not be blank
6. Placeholder fields used in email template should be replaced with actual values e.g. {Firstname} {Lastname} should be replaced with individuals first and last name properly for all recipients
7. If reports with dynamic values are included in email body, report data should be calculated correctly
8. Email sender name should not be blank
9. Emails should be checked in different email clients like Outlook, Gmail, Hotmail, Yahoo! mail etc.
10. Check send email functionality using TO, CC and BCC fields
11. Check plain text emails
12. Check HTML format emails
13. Check email header and footer for company logo, privacy policy and other links
14. Check emails with attachments
15. Check send email functionality to single, multiple or distribution list recipients
16. Check if reply to email address is correct
17. Check sending high volume of emails

Test Scenarios for Excel Export Functionality

1. File should get exported in proper file extension
2. File name for the exported Excel file should be as per the standards e.g. if file name is using timestamp, it should get replaced properly with actual timestamp at the time of exporting the file
3. Check for date format if exported Excel file contains date columns
4. Check number formatting for numeric or currency values. Formatting should be same as shown on page
5. Exported file should have columns with proper column names
6. Default page sorting should be carried in exported file as well
7. Excel file data should be formatted properly with header and footer text, date, page numbers etc. values for all pages
8. Check if data displayed on page and exported Excel file is same
9. Check export functionality when pagination is enabled
10. Check if export button is showing proper icon according to exported file type e.g. Excel file icon for xls files
11. Check export functionality for files with very large size
12. Check export functionality for pages containing special characters. Check if these special characters are exported properly in Excel file

Performance Testing Test Scenarios

1. Check if page load time is within acceptable range
2. Check page load on slow connections
3. Check response time for any action under light, normal, moderate and heavy load conditions
4. Check performance of database stored procedures and triggers
5. Check database query execution time
6. Check for load testing of application
7. Check for stress testing of application
8. Check CPU and memory usage under peak load condition

Security Testing Test Scenarios

1. Check for SQL injection attacks
2. Secure pages should use HTTPS protocol
3. Page crash should not reveal application or server info. Error page should be displayed for this
4. Escape special characters in input
5. Error messages should not reveal any sensitive information
6. All credentials should be transferred over an encrypted channel
7. Test password security and password policy enforcement
8. Check application logout functionality
9. Check for Brute Force Attacks
10. Cookie information should be stored in encrypted format only
11. Check session cookie duration and session termination after timeout or logout
11. Session tokens should be transmitted over secured channel
13. Password should not be stored in cookies
14. Test for Denial of Service attacks
15. Test for memory leakage
16. Test unauthorized application access by manipulating variable values in browser address bar
17. Test file extension handing so that exe files are not uploaded and executed on server
18. Sensitive fields like passwords and credit card information should not have auto complete enabled
19. File upload functionality should use file type restrictions and also anti-virus for scanning uploaded files
20. Check if directory listing is prohibited
21. Password and other sensitive fields should be masked while typing
22. Check if forgot password functionality is secured with features like temporary password expiry after specified hours and security question is asked before changing or requesting new password
23. Verify CAPTCHA functionality
24. Check if important events are logged in log files
25. Check if access privileges are implemented correctly
Penetration testing test cases – I’ve listed around 41 test cases for penetration testing on this page.

I ‘d really like to thank Devanshu Lavaniya (Sr. QA Engineer working for I-link Infosoft) for helping me to prepare this comprehensive testing checklist.

I’ve tried to cover all standard test scenarios for web and desktop application functionality. But still I know this is not a compete checklist. Testers on different projects have their own testing checklist based on their experience.

Please feel free to make this as a complete checklist by adding more test scenarios or negative test cases in below comments.

Also I’d appreciate if you’d share this with your friends!



The Best Software Testing Training You'll Ever Get!

software testing QA training

188 comments ↓

#1 Boris Ivanov on 01.03.13 at 8:55 pm

Great list of scenarios, however I believe they wont work for all applications. But this can be a good basis for everybody to create their own check lists

#2 Vijay on 01.03.13 at 9:24 pm

@Boris – General, security, performance, GUI, DB tests should be applicable for almost all applications.
As mentioned in the assumptions, other tests are applicable for applications containing forms to save data in DB, file upload functionality, having popup windows, search and result pages, data export functionality etc.

#3 Kirankumar Reddy on 01.03.13 at 9:26 pm

Vijay, this is by far the most comprehensive test cases list I ever seen in any other online articles.
Thanks for compiling and sharing with us.

#4 Sanjay Kumar on 01.04.13 at 3:37 am

Thanks for such a effort, Very comphrensive

#5 aslam sharif on 01.04.13 at 4:33 am

Very Very useful , looking forward for the next articles from u :)

#6 Kanif F on 01.04.13 at 4:59 am

Great work Vijay, definately this will help a lot for all.

#7 gurpreet on 01.04.13 at 5:08 am

very useful.. and helpful… a ery good effort done by u…
thanks…
kindly post a article on negative testing test case….

#8 Bhushan on 01.04.13 at 5:34 am

This is very good article post by you sir.

Please post the same on negative testing test case also.

#9 pardeep sharma on 01.04.13 at 6:17 am

thanks for such useful post for every tester…..

#10 Jitender Singh on 01.04.13 at 6:25 am

Very helpful and nicely prepared article for testers…..

#11 Nico on 01.04.13 at 8:02 am

Very comprehensive list, I’ll send it to my testers and developers.
Thanks,

#12 Deepa on 01.04.13 at 9:37 am

Very nice article, and very useful.

#13 Sugnesh on 01.04.13 at 9:38 am

Very valid point, to make the checklist, i am too early for them now, seems to be very important

#14 dolly agarwal on 01.04.13 at 10:38 am

This 1 superb , really its applicable on each and evry application . Thanks for making this type of comprehensive scenarios. Keep updating us by this new -new ideas , realy i like this website …

#15 masala on 01.04.13 at 1:07 pm

Very helpful and ready to use for testers. GREAT WORK.

#16 Chris on 01.04.13 at 1:43 pm

Vijay- Nice work.
You have compiled a thorough testing checklist.
Thanks for sharing!

#17 SACHIN R.V on 01.04.13 at 2:46 pm

VERY USEFUL INFORMATION FOR FRESHERS TO FACE INTERVIEW QUESTIONS ON TEST CASES..
GOOD WORK…
THANKS ALOT..

#18 Amol Kanthe on 01.04.13 at 3:43 pm

Good information. Everyone should read this, mainly freshers.

#19 Hieenf on 01.05.13 at 2:45 am

Very helpful. Thank you so so much

#20 Manu Vasisht on 01.05.13 at 3:39 am

Thank u…

#21 Rikash Singh on 01.05.13 at 5:48 am

Thanks for the test cases. I will definately be using them.

#22 pallav on 01.05.13 at 7:40 am

Very effective materiel for testing professionals…

#23 Satish on 01.05.13 at 8:57 am

Thanks a lot and awaiting for your next post on negative test cases

#24 karthikeyan on 01.05.13 at 10:24 am

Awesome tips….

#25 Vijay on 01.05.13 at 12:09 pm

thank you everyone for your help!

it takes anywhere between 10 and 20 hours to complete these kind of articles. but this wouldn’t have been possible without your support, which inspires me to put in these efforts.

#26 Vijay on 01.05.13 at 12:20 pm

For those who are looking for more test scenarios specific to web applications please refer this article:
http://www.softwaretestinghelp.com/web-application-testing/

#27 Geeta on 01.05.13 at 5:11 pm

Thank you Vijay for giving such a comprehensive checklist.

#28 Ahmed AbdElmaksod on 01.06.13 at 12:32 am

Good Article, and Very Helpful
These are Good Abstracts (Head Lines

#29 Salma Abdel Jawad on 01.06.13 at 7:24 am

Very useful article, thank you!

#30 geoffery on 01.06.13 at 1:44 pm

its very helpful thank u…..

#31 Durgesh Chaudhary on 01.07.13 at 5:32 am

Simply awesome list. I would certainly recommend it to my testing team.

Nice list.

#32 rads on 01.07.13 at 6:53 am

Hi,
These articles are very informative & useul. Thanks a lot. Can you please give more idea how to test live chat application.

Thanks

#33 Liji on 01.07.13 at 7:09 am

Very good Article :)

#34 annie on 01.08.13 at 4:28 am

. All resource keys should be configurable in config files or database instead of hard coding..please explain??

#35 Maheedhar on 01.08.13 at 6:05 am

Really a very good job done by you.. I had never seen such a extensive list

Thanks
Maheedhar

#36 Tushar on 01.08.13 at 6:47 am

Awesome Document For Testers both for freshers and experienced, Thanks a lot.

#37 Lakshmi on 01.08.13 at 7:20 am

Hi…
These articles are very informative & useful. and awaiting for your next post on negative test cases

Thanks
Lakshmi

#38 sunil on 01.08.13 at 9:48 am

Thanks for sharing such a comprehensive list of test cases, this will be really helpfull for all the testers.

#39 Miro on 01.11.13 at 1:15 am

Thank You so much for sharing , Do you have nay list for negative Tastings. This is Awesome.

#40 saravanan v.i on 01.11.13 at 7:59 am

Awesome this list more useful for all common Web and Window application

#41 Mujahid on 01.11.13 at 12:01 pm

Very good work which will be helpful.

#42 Esperanza on 01.11.13 at 2:57 pm

Hi there, this is very helpful. Are you able to provide some sample of test cases based on healthcare IT. Thank you.

#43 Yogesh Salunke on 01.15.13 at 5:56 am

Very good article…. Thanks.

Can anyone pls forward me sample test case document of any application.

#44 Yogesh Salunke on 01.15.13 at 5:58 am

yog2day@yahoo.co.in my mail id

#45 Sopan on 01.15.13 at 7:49 am

Thanks a lot Vijayji, These scenarios are very useful while Testing application for software testing professional as well as a fresher while facing testing interview questions..

#46 Testingwalk on 01.18.13 at 5:35 am

Thanks for sharing this article…
I am big fan of softwaretestinghelp.com

Thanks again…

#47 neha on 01.18.13 at 6:01 am

Its really helpful.

#48 LK on 01.18.13 at 2:56 pm

Excellent article!!

#49 LK on 01.18.13 at 2:56 pm

Excellent article!!

#50 Fernando on 01.23.13 at 6:03 pm

Thanks for the checklist. Great work! A good starting point.

#51 ElizaF on 01.25.13 at 5:07 pm

This is a good basic checklist but no where do you mention testing the functional purpose of the page. For example in Amazon, it could be to search for, select and buy a product, in people soft, it would be to import a contact from email, edit their details and save the entry. Checking the layout and the uniform behaviour of text fields is all very well and good but of you cannot carry out the functional purpose of the web page / app then it is of no use to no-one.

#52 Himaz Ahamed on 02.01.13 at 10:55 am

Great Work!!! very useful …

#53 Mohamed ezzat on 02.02.13 at 8:53 am

thank u..

#54 anji on 02.03.13 at 12:28 am

great work , you posted a nice article for all the people who wants enter into the testing field thank you allot for sharing this information with us waiting for the upcoming articals…….

#55 mahalaxmi on 02.04.13 at 6:08 pm

very good information.

simply ‘GREAT’.

#56 Akash soni on 02.05.13 at 5:48 am

Thank you !! I just want to notify that I have more than 2 years of experience in Software testing and all of these because of you Software Testing help!! Great work and nice article !!!

#57 Raveendra on 02.05.13 at 12:33 pm

Thanks Vijay……..Can you provide information of QTP tool, at least trial version

#58 Nhung on 02.07.13 at 6:46 am

good job. very helpful

#59 Dipti on 02.07.13 at 8:12 pm

This is excellent Vijay. You have made work a bit easier for us. I dont know, how much and when it will be possible, but would be excellent to have such detailed explanation for other areas like QTP, QC, etc.

Thanks again!!

#60 Lalitha on 02.08.13 at 6:56 am

Hi Vijay,

Am really thankful for providing detailed info.. as i joined small s/w company.. and am being so confused, what to do first, and how to test…

Thank u once again

#61 GiveMeMore123 on 02.09.13 at 8:43 pm

very good sample test case template. Anyone wanting to take Software Testing to another level can buy exam papers @ ISEB-sofwaretesting.weebly.com

#62 Nitha on 02.12.13 at 7:29 am

Very Useful Information Thanks…..

#63 Anuj on 02.12.13 at 8:11 am

Sincere thanks to you guys !!
This is the Core of Manual Testing..Extremely helpful for every Tester/ QA guy !

#64 althaf on 02.18.13 at 11:17 am

if u have any test case templates then mail me and pls let me know what r the tools available in market as track versions i need to be install for automation testing
thank u **********

#65 vasu on 02.19.13 at 5:52 am

Hello Vijay ,
thank you for Great article , i have learned some new points from check list.

#66 nadia hussain on 02.20.13 at 6:15 am

thnks for such articles, informative

#67 Sangram Kumar Das on 02.22.13 at 8:51 am

Thanks for Sharing such a wonderful article. The contains are very good and scenarios are good described. Keep posting such articles. This is really helpful for the people related to Software Testing industry.

#68 jim sebastian on 02.25.13 at 2:16 pm

very useful topic for me..thanks boss…

#69 Kalyan R on 02.26.13 at 4:18 am

impressive test cases. Thanks for sharing

#70 Altamash Heroli on 02.27.13 at 9:57 am

Thankyou for this wonderful documentation.

#71 Muhammad taahaa on 02.28.13 at 5:14 am

Good one, every tester should learn this..

#72 arshed mohammed on 02.28.13 at 5:17 am

really it is a good work..

#73 follan on 02.28.13 at 8:42 am

need complete tutorial on MonkeyTalk testing tool plz or give an link

#74 Rani on 03.18.13 at 12:33 pm

Really a useful one.. looking for more post about s/w testing.

#75 Rani on 03.18.13 at 12:36 pm

hi, Can anyone tell me, is there any tool available to test word applications.

#76 ASHISH KUMAR CHANDRA on 03.26.13 at 7:04 pm

sir, it is very knowlegable with easy language, it is so easy to understand all the test cases functionalities.it will definetly help me in making my project with gud n effective test cases..thanku so much sir..keep going ..all d best.

#77 kavi on 04.04.13 at 9:32 am

This is really helpful article for every tester. It reminds me the mistakes I made in the past. Thanks to the authors of the article.
I will keep this checklist handy while working on each project hereafter.

#78 kannaki.k on 04.11.13 at 9:57 am

Thank a lot,i get lot of knowledge from this article,can you able to post web service test scenarios

#79 Noufal on 04.15.13 at 7:37 am

Great work. Do you have sample test cases word document for testing

#80 Jamsheed on 04.24.13 at 1:25 pm

Really Amazing…. Awesome Checklist
i appreciate your work..

#81 SJM on 04.30.13 at 1:50 pm

Thank you.. I’ve been writing test cases for new web site development for a few years.. started searching today for new, more comprehensive information on cases. This will be helpful.

#82 rain on 05.08.13 at 1:58 am

thank you so much, very useful to us.

#83 Sweet on 05.09.13 at 7:21 am

i cant able to understand this line..? could you help me plz to understand..?

“All resource keys should be configurable in config files or database instead of hard coding”

#84 jaya on 05.09.13 at 10:04 am

its good, tnks for sharing

#85 nmtle on 05.09.13 at 2:39 pm

Great article, well done. But someting I just wonder:
1) How to test memory leaks
2) Please tell me how I create a file with virus to test file attachment without spreading virus to my PC
3) Tester can not tell developer that they have to create audit tables in the databse. Audit requires in audit_log.
4) Tester can not require that table indexes are created.

#86 Amazingzone on 05.14.13 at 11:19 am

Its amazing

#87 Pranav on 05.16.13 at 5:44 pm

everybody already typed so many things abt this article… no more words needed :) it’s simply great work.

#88 Srinivasulu on 05.19.13 at 12:40 pm

thank u so much, very useful to us…..!

#89 Karthik on 05.20.13 at 9:33 am

Excellent job! Really an amazing research on test scenarios..Please continue your service. -Karthik,Bangalore

#90 eshwar on 05.23.13 at 5:54 am

hello can any one help me how to write negative secnarios for a tab

#91 Stuart on 05.23.13 at 11:24 am

Thanks, this is a very useful list, especially for projects that dont have a dedicated test team. I found a few I have missed so very useful.

many thanks

#92 anandhk7 on 05.27.13 at 7:11 am

Thanks, this is a very useful list, especially for projects that dont have a dedicated test team. I found a few I have missed so very useful.

#93 Satkar Bodhe on 05.27.13 at 7:33 am

Very useful data to stable software…

#94 Tu.VU on 06.10.13 at 6:30 am

Many thanks for your list, it helps us a lot

#95 mannava on 06.11.13 at 5:47 am

Very usefull thanks very much it helped me a lot for writting the test cases.

If you have any document related to it can you please send mail.

Thanks.

#96 gnaneswari on 06.13.13 at 3:03 pm

awesome ./…..is really useful to me 100%

#97 ramya on 06.19.13 at 9:59 am

good one

#98 Ashok on 06.25.13 at 12:00 pm

Excellent tips on Testing. Very helpful for all beginners

#99 Jignesh Patel on 06.26.13 at 8:54 am

I appreciate your work and thank you for sharing article.

I give 7* for this article.

#100 David Wang on 06.27.13 at 9:11 pm

Does anyone have an idea of what a resource key is? I’ve looked all over and can’t seem to find a clear definition of it. Trying to understand this statement: “All resource keys should be configurable in config files or database instead of hard coding.”

#101 antony on 07.05.13 at 4:33 am

nice and useful

#102 jaya on 07.09.13 at 1:06 pm

its good article,i need information about load testing and performance testing tools information.what is bug density?

#103 Virendra Ambekar on 07.10.13 at 11:13 am

Good Article really helpful for new testers and experienced as well

#104 swathi on 07.15.13 at 10:43 am

very nice article sir..many thanks

#105 Saravanan on 07.18.13 at 9:30 am

This could be much useful for all QA’s

#106 Ajay on 07.23.13 at 9:26 pm

Hi Vijay your work is Much appreciated , the amount of knowledge you are spreading through these Posts is really Terrific , Accept our sincere & Heartful Thanks .

#107 Tom Mantsch on 07.25.13 at 9:23 am

Great Stuff – It’s a pretty good overview although not everything will work for every project. Nevertheless it’s a good start and a brilliant checklist.

#108 Max on 07.25.13 at 11:01 am

Excellent and helpful.

#109 Dandy on 07.26.13 at 5:41 am

Thank u so much boss,….it helped me alot to write scenarios for my application,..n i vl b looking forward for ur next articles.

#110 Vineet Pandey on 07.26.13 at 11:24 am

Really Very Good Artical Very helpful and ready to use for testers. GREAT WORK.

#111 Shabda on 07.30.13 at 12:24 pm

Very useful and great effort by you..

#112 Minakata on 07.30.13 at 5:56 pm

Great! This help me a lot for quick refresh, I will share with my friends.

#113 Shubhangi on 08.02.13 at 6:17 am

Very usefull
Thank you

#114 mayank on 08.02.13 at 6:24 am

brilliant stuff

#115 Prachujya Saikia on 08.06.13 at 11:08 am

lots of thanks….

#116 saraswathy on 08.09.13 at 7:25 am

very useful and clear to the pont..thanks..:)

#117 gayathri venkatraman on 08.14.13 at 2:35 am

very useful… lots of thanks

#118 mahi on 08.14.13 at 7:17 am

Excellent tips on Testing…nice

#119 Santosh on 08.20.13 at 3:55 am

Hi Techies, Please anyone share or send me the system test cases for any of the web application.. Please even share any testing related documents.. I am new to testing .. Please..

#120 Sravan Kumar on 08.21.13 at 4:24 am

1. Check if correct data is getting saved in database upon successful page submit
2. Check values for columns which are not accepting null values
3. Check for data integrity. Data should be stored in single or multiple tables based on design
4. Index names should be given as per the standards e.g. IND__
5. Tables should have primary key column
6. Table columns should have description information available (except for audit columns like created date, created by etc.)
7. For every database add/update operation log should be added
8. Required table indexes should be created
9. Check if data is committed to database only when the operation is successfully completed
10. Data should be rolled back in case of failed transactions
11. Database name should be given as per the application type i.e. test, UAT, sandbox, live (though this is not a standard it is helpful for database maintenance)
12. Database logical names should be given according to database name (again this is not standard but helpful for DB maintenance)
13. Stored procedures should not be named with prefix “sp_”
14. Check is values for table audit columns (like createddate, createdby, updatedate, updatedby, isdeleted, deleteddate, deletedby etc.) are populated properly
15. Check if input data is not truncated while saving. Field length shown to user on page and in database schema should be same
16. Check numeric fields with minimum, maximum, and float values
17. Check numeric fields with negative values (for both acceptance and non-acceptance)
18. Check if radio button and dropdown list options are saved correctly in database
19. Check if database fields are designed with correct data type and data length
20. Check if all table constraints like Primary key, Foreign key etc. are implemented correctly
21. Test stored procedures and triggers with sample input data
22. Input field leading and trailing spaces should be truncated before committing data to database
23. Null values should not be allowed for Primary key column

Test Scenarios for Image Upload Functionality

(Also applicable for other file upload functionality)
1. Check for uploaded image path
2. Check image upload and change functionality
3. Check image upload functionality with image files of different extensions (e.g. JPEG, PNG, BMP etc.)
4. Check image upload functionality with images having space or any other allowed special character in file name
5. Check duplicate name image upload
6. Check image upload with image size greater than the max allowed size. Proper error message should be displayed.
7. Check image upload functionality with file types other than images (e.g. txt, doc, pdf, exe etc.). Proper error message should be displayed
8. Check if images of specified height and width (if defined) are accepted otherwise rejected
9. Image upload progress bar should appear for large size images
10. Check if cancel button functionality is working in between upload process
11. Check if file selection dialog shows only supported files listed
12. Check multiple images upload functionality
13. Check image quality after upload. Image quality should not be changed after upload
14. Check if user is able to use/view the uploaded images

Test Scenarios for Sending Emails

(Test cases for composing or validating emails are not included)
(Make sure to use dummy email addresses before executing email related tests)
1. Email template should use standard CSS for all emails
2. Email addresses should be validated before sending emails
3. Special characters in email body template should be handled properly
4. Language specific characters (e.g. Russian, Chinese or German language characters) should be handled properly in email body template
5. Email subject should not be blank
6. Placeholder fields used in email template should be replaced with actual values e.g. {Firstname} {Lastname} should be replaced with individuals first and last name properly for all recipients
7. If reports with dynamic values are included in email body, report data should be calculated correctly
8. Email sender name should not be blank
9. Emails should be checked in different email clients like Outlook, Gmail, Hotmail, Yahoo! mail etc.
10. Check send email functionality using TO, CC and BCC fields
11. Check plain text emails
12. Check HTML format emails
13. Check email header and footer for company logo, privacy policy and other links
14. Check emails with attachments
15. Check send email functionality to single, multiple or distribution list recipients
16. Check if reply to email address is correct
17. Check sending high volume of emails

Test Scenarios for Excel Export Functionality

1. File should get exported in proper file extension
2. File name for the exported Excel file should be as per the standards e.g. if file name is using timestamp, it should get replaced properly with actual timestamp at the time of exporting the file
3. Check for date format if exported Excel file contains date columns
4. Check number formatting for numeric or currency values. Formatting should be same as shown on page
5. Exported file should have columns with proper column names
6. Default page sorting should be carried in exported file as well
7. Excel file data should be formatted properly with header and footer text, date, page numbers etc. values for all pages
8. Check if data displayed on page and exported Excel file is same
9. Check export functionality when pagination is enabled
10. Check if export button is showing proper icon according to exported file type e.g. Excel file icon for xls files
11. Check export functionality for files with very large size
12. Check export functionality for pages containing special characters. Check if these special characters are exported properly in Excel file

Performance Testing Test Scenarios

1. Check if page load time is within acceptable range
2. Check page load on slow connections
3. Check response time for any action under light, normal, moderate and heavy load conditions
4. Check performance of database stored procedures and triggers
5. Check database query execution time
6. Check for load testing of application
7. Check for stress testing of application
8. Check CPU and memory usage under peak load condition

Security Testing Test Scenarios

1. Check for SQL injection attacks
2. Secure pages should use HTTPS protocol
3. Page crash should not reveal application or server info. Error page should be displayed for this
4. Escape special characters in input
5. Error messages should not reveal any sensitive information
6. All credentials should be transferred over an encrypted channel
7. Test password security and password policy enforcement
8. Check application logout functionality
9. Check for Brute Force Attacks
10. Cookie information should be stored in encrypted format only
11. Check session cookie duration and session termination after timeout or logout
11. Session tokens should be transmitted over secured channel
13. Password should not be stored in cookies
14. Test for Denial of Service attacks
15. Test for memory leakage
16. Test unauthorized application access by manipulating variable values in browser address bar
17. Test file extension handing so that exe files are not uploaded and executed on server
18. Sensitive fields like passwords and credit card information should not have auto complete enabled
19. File upload functionality should use file type restrictions and also anti-virus for scanning uploaded files
20. Check if directory listing is prohibited
21. Password and other sensitive fields should be masked while typing
22. Check if forgot password functionality is secured with features like temporary password expiry after specified hours and security question is asked before changing or requesting new password
23. Verify CAPTCHA functionality
24. Check if important events are logged in log files
25. Check if access privileges are implemented correctly
Penetration testing test cases – I’ve listed around 41 test cases for penetration testing on this page.

I ‘d really like to thank Devanshu Lavaniya (Sr. QA Engineer working for I-link Infosoft) for helping me to prepare this comprehensive testing checklist.

I’ve tried to cover all standard test scenarios for web and desktop application functionality. But still I know this is not a compete checklist. Testers on different projects have their own testing checklist based on their experience.
fgfgfgrgfgftrvfgrt

#121 raju on 08.21.13 at 9:50 am

good to learn.

#122 venky on 08.21.13 at 9:58 am

send me sir test cases for billing a product and irctc for check availbality

#123 Tushar on 08.23.13 at 11:58 am

its very Knowledgeful material for Fresher as well as experianced

#124 Richard on 08.29.13 at 1:41 pm

Great checklist. We have developed a website testing tool and are now in the process of adding support for testing checklists. Ill make sure your checklists can be used within our Webseam tool.

#125 bibhishan on 09.02.13 at 9:31 am

hello sir,
I want scenario on bike..

#126 swati on 09.02.13 at 3:52 pm

Hi, am a fresher can u plz tell me do v prepare test cases on bases of this checklist.

#127 sushma on 09.03.13 at 4:50 am

how should we write test case in a template while we r clicking on menus the image at the top should not be change

#128 shailaja on 09.04.13 at 7:12 am

Really good job

#129 Arunchanu on 09.04.13 at 3:26 pm

Hello,
i’m in testing team now, i konw about testing and why its needs but i don’t know how to write and differences to understand. so it very new for me but after reading it’s really helpful for me. Thank you for everthing.

#130 Satish.SP on 09.06.13 at 9:25 am

Execellent stuff…this is the one stop shop for freshers especially. Amazing Stuff….

#131 RAvi kant on 09.06.13 at 11:48 am

Excellent article!!

#132 nitish choudhary on 09.12.13 at 5:49 am

Hi
really this is very helpfull for me. I have some query about the security testing. Can you describe alittle bit about
a) Deniel of service attack
b) Brute Force Attacks
c) Memory Leakage

#133 Ramesh on 09.12.13 at 9:19 am

Very useful article. keep posting more..

#134 Sumit on 09.12.13 at 9:48 am

What kind of testing is there which can be done for Desktop applications but not for web based applications?please give me in details

#135 Mayank Rathore on 09.12.13 at 11:48 am

Dear Vijay ji,

your artical is very helpful for the beginners, but you know what i didn’t do any course of testing but still i utilize all the test cases which is mention by you in the manual or performance testing by my own.

But my company never ever appreciate my efforts of testing his software. they are telling that the testers are the useless fellow of the company.

Actually i make a standard product for him, but still they give less value to a experience tester in comparison to the fresher programmer.

sorry for writing this but it release my anger & frustration on that kind of fellows.

thanks

#136 aparna on 09.12.13 at 4:15 pm

very useful and thanks for helping….

#137 Mutaz Nassar on 09.15.13 at 12:07 pm

lots of appreciation and gratefulness

#138 Ram on 09.20.13 at 7:21 am

Checklist is very useful, Thank you

#139 Neha on 09.23.13 at 12:02 pm

Very helpful. Thanks a lot..Keep posting!!!

#140 sanjib Rout on 09.26.13 at 5:33 am

It’s really very very nice one.

#141 Ritesh Joshi on 10.01.13 at 10:14 am

This Information is Very useful for QA or Non-QA Professional.they can easily understand all these points.Developer’s can also Read these Point and aware regarding such kind of issues.

#142 NB on 10.08.13 at 8:55 am

Awesome help..i am fresher and was asked to prepare the test cases…yours came handy..dont know if it would be approved but still my personal opinion ..its real good.

#143 purna on 10.10.13 at 8:16 am

good one

#144 Amrath on 10.15.13 at 12:39 pm

thanks for sharing knowledge

#145 TonyL on 10.19.13 at 7:32 pm

Can you point me to any test plan for web content filtering solutions. We are trying to decide between a couple off shelf web content filters and I wish to avoid skipping a common Use-Case. We are a K12 school but corp test plans would be good too?

#146 satheesh on 10.24.13 at 6:37 am

very useful check list…thank you…

#147 satheesh on 10.24.13 at 6:41 am

This Check list is very useful these is one of the test case sample models. i would like to extra check list our added.
………really very nice……….

#148 Savita on 10.26.13 at 5:00 pm

In General Test Scenarios:
While testing filed for special character also test for reserved keywords like:
‘Create’, ‘Update’… etc

#149 Mr. NILESH N. Parakh on 10.30.13 at 12:33 pm

R/s VIJAY sir,
The site and post is very very very nice. I would like to praise your parents for keeping your name VIJAY because your knowledge and this site is acting as visa for getting VIJAY or success in the software testing industry

Your friend,
NILESH

#150 Mr. NILESH N. Parakh on 10.30.13 at 12:34 pm

Vijay,
I would like to read the methodology of doing software testing

#151 samra on 11.05.13 at 9:49 am

its really good work

#152 sameer on 11.25.13 at 1:11 pm

thank u very much…
very useful

#153 tedy on 12.04.13 at 7:35 am

nice work

#154 mamatha on 12.10.13 at 12:29 pm

Very nice article and very useful

#155 Noel Divekar on 12.11.13 at 1:42 am

Thank you Vijay,

Ur Awesome….Its really Helpful….

#156 Rajaselvan on 12.13.13 at 7:42 am

Hi,

We can consider the below point as well in the section of “Test Scenarios for Excel Export Functionality”

Check whether there is any sheet has been hidden in the exported excel sheet

#157 Rajaselvan on 12.13.13 at 7:44 am

Hi,

We can consider the below point as well in the section of “Test Scenarios for Excel Export Functionality”

Check whether there is any sheet has been hidden in the exported excel sheet

#158 aruna on 12.15.13 at 4:29 pm

Thanks for the article
helped me to project real time scenarios in my interview

#159 madhuri on 12.20.13 at 6:42 am

Hi a very good article helped me alot.Can u also kindly tell us with an example how do we write test cases based on document

#160 vibhuti on 12.26.13 at 1:28 pm

Thanks for your efforts. Its very useful for me. :)

#161 Renuka on 12.27.13 at 4:45 am

Hi these checklists are very informative in real time.could u plz upload the checklist for crop a image.iam in need of it

#162 its very useful..thanks on 01.02.14 at 12:40 pm

anithanayak11@gmail.com

#163 ravi on 01.09.14 at 8:32 am

very useful checklist great thanks……

#164 kiran on 01.28.14 at 10:57 am

It’s nice explanation to learn more about test cases preparation and more helpful for software testing freshers like me . thank you so much.

#165 jd on 02.01.14 at 10:23 am

thanx for all these material its helpfull whose they start work in testing…. on itself…… ……

#166 Mallikarjun on 02.04.14 at 10:04 am

Great checklist. Very helpful article.

#167 Maqsood Syed on 02.12.14 at 5:45 pm

Vijay your’re really Excellent !!

#168 jamuna on 02.13.14 at 6:01 am

its an excellent checklist for beginners.i have recently joined as tester wanted some tips to create efficient test cases for desktop application its an financial software. looking for help pls revert back :-)

jamuna.avera@gmail.com

#169 kumanan on 02.19.14 at 11:42 am

very useful one thank you……

#170 Ankita on 02.23.14 at 6:23 pm

So many scenarios for so many topics ate one place. It is really very helpful. Wonderful work !! :)

#171 Rahul Jaiswal on 02.27.14 at 5:12 am

itz amaze me to see thz answer thanx……..

#172 Anjul on 03.11.14 at 6:00 pm

Thanks for helping me a brief understanding of Test Scenario with Example! Really nice

#173 ivan on 03.11.14 at 11:22 pm

Thx vijay.. really helpful

#174 sharad bagul on 03.14.14 at 6:09 am

really good for fresher as well as experienced testers

#175 kiran kumar on 03.15.14 at 4:53 am

Thank u Vijay for giving such a good senarios on desktop and web app testing which usefull more for who are working under these testings.

#176 Yatin on 03.18.14 at 7:09 am

Nice work sir,

Helped me a lot.

#177 Bhavin on 03.19.14 at 9:36 am

Greate and helpful article

Thank you vijay for post this article for testing desktop application. Thanks for your efforts. Its very useful for me.

#178 jagtar on 03.21.14 at 11:28 am

many functionality are covered

#179 Rakesh Hansalia on 03.22.14 at 7:10 pm

Very helpful. Thank you so so much

#180 Taru on 03.27.14 at 4:29 pm

Vijay, this is by far the most comprehensive test cases list I ever seen in any other online articles.
Thanks for compiling and sharing with us.

#181 TesterfromPH on 04.01.14 at 11:56 pm

Thank you so much for sharing this with us. This has been my go-to checklist ever since.

#182 Monika Shah on 04.03.14 at 9:11 am

This is very very informative and knowledgable…
Thanks for sharing this with us…
This is a nobel task for many testers… you will get blessings from those testres…

I had few doubts that, can you please send the same kind of list for ETL and Database testing???
rest is fine…

thanks once again…

#183 Sripadma on 10.31.14 at 11:58 am

Hi,
All the test cases that you posted are very helpful. Could you please post test cases for Clinical Trials in Pharmaceutical domain. I need it please.

Thanks,
Sripadma

#184 Neenu on 11.03.14 at 11:46 am

Very helpful document.Thanks for this :)

#185 chandrakant on 11.13.14 at 10:24 am

This is very good and helpful article. Nice job done by you.

Thanks for your time :)

#186 rachana on 11.24.14 at 7:59 am

Very helpful document. It helped me alot.
Nice Job.Thanks for posting :)

#187 Dinesh on 11.24.14 at 10:41 am

Very helpful Article. Thanks.. :-)

#188 teja on 11.26.14 at 4:37 pm

for the first time im learning s/w testing…and this article is really a gud start for me…thanks a lot…hope u make many more articles…

Leave a Comment