100+ Ready-to-Execute Test Cases (Checklists) You Can Use to Test the Most Common Components of AUT

How to test the most common components of your AUT effectively, every single time

This article is a list of common validations on most widely found elements of AUT – that is put together for the convenience of testers (especially in agile environment where frequent short term releases happen).

Every AUT (Application Under Test) is unique and has a very specific business purpose. The individual aspects (modules) of the AUT cater to different operations/actions that are crucial for the success of the business that the AUT supports. Though each AUT is designed differently, individual components/fields that we encounter on most pages/screens/applications are same with more or less similar behavior.

ready test cases

Some Common Components of AUT:

  • Save, Update, Delete, Reset, Cancel, OK – links/buttons- whose functionality is as the label of the object indicates.
  • Text box, drop downs, checkboxes, radio buttons, date control fields – that work the same way every time.
  • Data grids, impacted areas, etc. to facilitate reports.

The way these individual elements contribute to the overall functionality of the application might be different but the steps to validate them are always the same.

Let’s continue with the list of most common validations for web or desktop application pages/forms.

Note: The actual result, expected result, test data and other parameters that are typically a part of a test case are omitted for the sake of simplicity – A general checklist approach is employed.

Purpose of this comprehensive checklist:

The primary purpose of these checklists (or test cases) is to ensure maximum test coverage on field level validations without spending too much time, at the same time not compromise the quality of testing them.

After all, confidence in a product can only be attained by testing every single element to the best extent possible.

The Complete Checklist (Test Cases) for Most Common Components of AUT

Note: You can use these checklists as it is in Microsoft Excel format (download provided at the end of the article). You can even track the test execution in same file with pass/fail result and status.

This could be an all-in-one resource for QA teams to test and track the most common components of AUT.  You can add or update test cases specific to your application and make it even more comprehensive list.

Checklist #1: For a module, we have to check the below points:

Module Name:
Module Functionality:
Module Impact over the application:
Module Flow:
Menu & Submenu:
Spellings and Order & Suitability:
Control for each sub menu:

Checklist #2: For each screen, we have to verify the below points

Form Functionality:
Form Impact over the application:
Form Flow:
Designing:
Alignments:
Title:
Field Names:
Spellings:
Mandatory Marks:
Alerts of Mandatory fields:
Buttons:
Default Cursor Position:
Tab Sequence:
Page before entering any data:
Page after entering data:

Checklist #3: For each text box in the screen we have to verify the below points

Text Box:

ADD(In add screen) EDIT (in Edit screen)
Characters
Special Characters
Numbers
Limit
Alert
Spelling & Grammar in Alert message:

BVA (Size) for Text Box:

Min —>—> Pass
Min-1 —> —> Fail
Min+1 —> —> Pass
Max-1 —> —> Pass
Max+1 —> —> Fail
Max —> —> Pass

ECP for Text Box:

 Valid  In Valid
 –  –
 –  –

Checklist #4: For each list box/drop down in the screen we have to verify the below points

List Box/Dropdown:

ADD(In add screen) EDIT (in Edit screen)
Header
Correctness of Existed Data
Order of Data
Selection and Deselect ion
Alert:
Spelling and Grammar of Alert message  
Cursor after alert
Reflection of Selection and De selection in remaining fields

Checklist #5: For each Check box in the screen we have to verify the below points

Check Box:

ADD(In add screen) EDIT (in Edit screen)
Default Selection
Action after selection
Action after de-selection
Selection and Deselect ion
Alert:
Spelling and Grammar of Alert message  
Cursor after alert
Reflection of Selection and De selection in remaining fields

Checklist #6: For each Radio button in the screen we have to verify the below points

Radio button:

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

ADD(In add screen) EDIT (in Edit screen)
Default Selection
Action after selection
Action after de-selection
Selection and Deselect ion
Alert:
Spelling and Grammar of Alert message  
Cursor after alert
Reflection of Selection and De selection in remaining fields

 

Checklist #7: For each date field in the screen we have to verify the below points

Date field:

ADD(In add screen) EDIT (in Edit screen)
Default date display
Design of calendar
Navigation for different months and years in date control
Manual Entry in date text box
Date format and uniformity with overall application
Alert:
Spelling and Grammar of Alert message  
Cursor after alert
Reflection of Selection and De selection in remaining fields

 

Checklist #8: For each save button in the screen we have to verify the below points

Save/update:

ADD(In add screen) EDIT (in Edit screen)
Without giving any data:
With only mandatory fields:
With All fields:
With Max limit:
With min limit
Spelling & Grammar in Confirmation  Alert message:
Cursor
Duplication of Unique fields:
Spelling & Grammar in duplication Alert message:
Cursor

Checklist #9: For each Cancel button in the screen we have to verify the below points

Cancel:

With data in all fields
With only mandatory fields:
With All fields:

Checklist #10: For each Delete button in the screen we have to verify the below points

Delete:

EDIT (in Edit screen)
Delete the record which is not used anywhere in the application
Delete the record which has dependency
Add the new record with same deleted details again

Checklist #11: To verify impacted areas after saving/updating

After Saving/updating:

Display in View
Reflection in impacted forms in the application

Checklist #12: For each data grid in the screen we have to verify the below points

Data Grid:

Grid Title and spelling
Form Before giving any data
Message Before giving any data
Spellings
Alignments
S No
Field Names & Order
Correctness of Existed data
Order of Existed data
Alignment of Existed data
Page navigators
Data when navigating with different pages

Edit Link Functionality

Page after Edit:
Title and spellings
Existed data of Selected record in each field
Buttons

While this list might not be exhaustive, it is indeed extensive.

==> You can download all these checklists in MS Excel format: Download in Excel format

Points to note:

  1. Depending on your need, additional tests under each category/for each field can be added or existing fields can be removed. In other words, these lists are completely customizable.
  2. When in need to include field level validations to your test suites, all you have to do is pick up the respective list and use it for the screen/page that you would like to test.
  3. Maintain the checklist by updating the pass/fail status to make this a one-stop-shop for listing features, validating them and recording the test results.

As always, the intent is to provide our readers with some easy to use techniques, tips and tools that make our work efficient and of course, easy. 

About The Author: Thanks to Mamatha for helping us to compile this useful list. She is having 6+ years of software testing experience and currently working on different projects as a Sr. QA.

SEE ALSO: 180+ Sample Test Cases for Testing Web and Desktop Applications.

Please let us know your feedback.




28 comments ↓

#1 sudheer

Excellent Article. Thanks for sharing such information with all.

#2 vineeta

thanks for sharing. website is really helpful thanks alot.

#3 Anju

Superb!!! Thanks for sharing.

#4 nick

Great article.. very useful

#5 Maqsoo Syed

Awesome !!!
All required information at one place that to available in spread sheet place.I can say that this is really very useful.

Thanks a lot buddy !!

#6 Mathi

Thank u very much author to provide this useful checklist, also i need testing coverage

#7 Priyadharshini

Thankyou so much for such an excellent article which will help the testers for a time saving work.

#8 Jemari

You are my favorite blogger. I love all of your posts and emails, but this one is absolutely amazing.

#9 Jemari

I have a Question: In checklists 1 and 2, what is intended by “module flow” and “form flow”? My first inclination was for tab sequence, but I see that is a separate item in checklist 2.

Thank you,
Jemari in Maine, USA

#10 Irfan

@Jemari

Module is one component of the application and within a module there will be more than 1 forms based on project requirements.

E.g. Loan is one module and retail sale is an another module and under loan there will be several forms..like customer information.

Loan will have a flow so as a form. that’s what the author is mentioning about. hope this helps.

#11 Mamatha

@Jemari

As Irfan mentioned, Module is one component form (screen) means no. of forms/screen in that module.

Ex: Payroll Accounting is one module in that we may have employee contact details, Wage cost preparation and Payment details are no. of screen.

In the given excel sheet, Depends upon a project we may use only module checklist or only form check list or sometimes both.

Thanks
Mamatha

#12 Mamatha

Thank a lot for each and every one for your response

Regards
Mamatha

#13 G Murali

Very good article and each check list has its own significance ; there is no doubt we should keep all these points in our brain instead of excel sheet because it is a regular practice in any QA industry… :)
Mamatha garu very happy to see your interest and efforts please keep it up…..

#14 k Roma

Hi Mr Vijay
I need your urgent help to write test cases in format for Microsoft outlook 2007. I created test scenarios but bit of confused about writing test cases in test case excel format. I am providing you test scenarios which I am created these are mentioned below.
Please anyone can help me in this then do reply on my I’d kromi_1234@yahoo.co.in

>1 Always BCC •Performs a CC or a BCC automatically for every email.
>•Customize the email messages that get CC’ed or BCC’ed.
>2 Attachment Reminder • Check your outgoing email for keywords and prompt you in case you
> forgot to attach a file.
>• Keywords are configurable.
>• Intelligently considers signature files.
>3 Attachment Save •Replaces attachments with links.
>•Reduces Outlook storage spaces.
>•Improve Outlook performance.
>•Delete the attachment when deleting an email.
>4 Duplicate Appointment Remover •Removes duplicate appointments.
>•Customizable
>•Fast
>5 Duplicate Contact Remover •Removes duplicate contacts.
>•Customizable
>•Fast
>6 Duplicate Email Remover •Remove duplicate emails in Microsoft Outlook.
>•Customizable
>•Fast
>7 Duplicate Note Remover •Delete duplicates or move them to a folder.
>•Comparisons of two appointments based on subject, body and color.
>•Works with a single folder or multiple folders at once.
>8 Duplicate Task Remover •Delete duplicates or move them to a folder.
>•Comparisons of two tasks based on subject, due date, categories,
> contacts, company, body and start date.
>•Works with a single folder or multiple folders at once.
>•Works with Microsoft Outlook 2013, Outlook 2010 and Outlook 2007.
>9 Follow Up Reminder •Reminds you if you have not heard back from someone.
>•List all your pending reminders with a click of a button.
>•Add follow up reminders to any email in any Outlook folder.
>•Quick Snooze.
>10 Remove Subject Prefix •Remove redundant ‘Re:’, ‘Fw:’ etc. from message subjects.
>11 Reply To All •Prompts you when you reply to everyone. Avoid sending out information
> you may not want to share with everyone.
>• Prevent Outlook from including your name and email address in a reply to all message thus avoiding extra copies.
>• Prompts with a confirmation message if you were BCC’ed on the
> message.
>12 Save as PDF •Saves all your emails as PDF files.
>•Saves attachments as PDF files.
>•Save the emails on receipt or batch mode.
>•No other PDF printer driver needed.
>13 Send Individually •Sends email marketing to each of your recipients, one at a time.
>•Adds a convenient “Send Individually” Outlook button.
>•Easily handles distribution lists, contact groups, and Excel lists.

#15 min

Thanku so much for your help

#16 mano

hi vijay,
recently i have completed a 2 month course on manual and Qtp…before starting my career i want your guidance..should i directly jump to the job or i should do some homework..can you help me in getting some home based testing jobs as i have no idea about this and you are the best person in answering all this..thank you..

#17 NIjoe Varkey

Excellent Article. Thanks for sharing!!!!!

#18 Sneha

Thanks Mamtha… it was simply great article…well explained and very imp to remember things!

#19 sahil

How long does it take to do smoke testing and to execute all the test cases in 1 year project as Manual tester?

#20 Rajesh Kumar

Beauty and moreover provides strong fundamental for begineer’s thank you

#21 Ali

Thanks for providing a very basic yet useful checklist

#22 Haranath

Hi Software Testing,

100+ or 180+ test cases , I found only few of them.
Where can I find all of them.

#23 umesh kumar

its very good article

#24 sridhar

Really very usefull, thanks for your hardwork.

#25 Vinayak

Thanks.
This test case article is very helpful for my startup carrier .

#26 erin

Thanks a lot for such great article, it is very helpful. A question: in the checklist for the Save Button, in which scenario “Duplication of Unique fields” could happen?

#27 erin

Ok, never mind my question. I think I got the answer, when we save an item having the same unique field that has been added.

#28 munawar ali A S

its very useful thank u for making this kind of posts …..

Leave a Comment