One Stop for Testing and Tools
Test Case Design
Control level Test cases
UI Cases Matrix
Text Box / Text Area
Rich Text Editor
Calendar or Date
Mega or Hamburger Menu
Messages and pop up
Result grid/Search result
GUI Test Cases and Checklist
Field Level test cases
Functional test cases
End to End test cases
Cyclomatic Complexity tool
Test Design tools
DAR and Pairwise tools
Test design techniques
Boundary Value Technique
Testing Life Cycle
Product Backlog vs Sprint Backlog
Scrum and Scrum teams
Definition Of Ready
Sprint Planning Meeting
Sprint Review/Demonstration Meeting
Sprint Retrospective Meeting
Definition Of Done
Misc in Agile
Test Driven Development
Simple Testing Life Cycle
Complete/Full Testing Life Cycle
Simple Automation Testing Life Cycle
Test Case Review
Test Metrics Template
Test Point Analysis
Basic Excel Formule
Excel Column Compare
File List Generator
Dummy File Creator
VB Regular Expression Checker
Fresh HTML Creator
Test Data Generator
Randam Data Generator
Combinations and Permutations
Non Transactional Test Cases
Navigational Steps Template
Project Directory Strcuture
File Conversion tool
Differencing and Merging tool
Large Text File Viewer
Text File Splitter
Replace Text Generator
Selenium Reporting tool
Test Case Template
Pre QA Checklist
Build History and Planning
Here are some of the sample test cases for Page.
Page should have a title with image
Page text should be left justified.
All mandatory fields should be indicated by an asterisk (*) symbol.
Are default values provided in fields, where appropriate?
The scrollbar should be enabled only when necessary.
Tooltips text should be meaningful.
Description of label should be aligned properly
Page level help messages should be available
Home link should be there on every single page or provision to go to dashboard
The Default Focus should be shown on the first editable field.
Enough space should be provided between field labels, columns, rows, error messages etc.
Font size, style, and color for headline, description text, labels, and grid info should be standard as specified in SRS.
Default radio options should be pre-selected on the page load.
Validation error messages should be displayed properly at a correct position and in the same CSS style
Numeric values should be justified correctly unless specified otherwise.
Disabled fields should be greyed out and users should not be able to set focus on these fields.
If a field is disabled (greyed) then it should not get focus. It should not be possible to select them with either the mouse or by using TAB. Try this for every greyed control.
Are related menu items grouped together and visually separated by lines?
Is a tool bar used to allow the user an alternative method to access commonly used processes?
Are tool bar items grouped according to the function they perform?
Does static text follow the project standards for consistent placement on the screen (e.g., field labels to the left of an entry field)?
Does static text follow project standards for consistent terminology (e.g., Employee No., Employee Number, or Employee #)?
Do buttons follow the project standards for size and position (e.g., Cancel button is correct size and below the OK button)?
Is the screen designed to fit the requirements for international use?
Is the text easy to translate (e.g., are slang, acronyms, and abbreviations avoided)?
Is there enough space on the screen to fit expanded (30 percent or more) translated text?
Check images are of good quality and clarity
Verify that the width of data inputted into the textbox is less than the width of field
The dropdown list should include “type ahead or Search” function to facilitate selection of the desired name/value.
Amount values should be displayed with correct currency symbols.
Check text on a page for spelling and grammatical errors.
Check the page on different resolutions (640 x 480, 600x800 etc.?)
Verify the “View Source code” option is disabled and should not be visible to the user.
Ctrl + F6 opens next tab within tabbed window
Shift + Ctrl + F6 opens previous tab within tabbed window
If page allows short cut keys (like CTRL+S to save), test each shortcut to ensure it works in all different browsers (if the application is web based)
Use a style guide to document what choices are available for dialog boxes. You should have not have Save/Cancel dialog on one screen and an OK/Cancel on another, this is inconsistent
The user should not be able to type in drop down select lists.
Check field labels are used in error messages when no data is provided in mandatory field.
Tab and Shift+Tab order should work properly.
Are menus (including pop-up and cascading) defined consistently and according to established standards (e.g., File menu first, Edit menu second, Help menu last)?
Check the occurrence of error messages for any faulty input or process
The user should not be able to submit page twice by pressing submit button in quick succession.
Have the menu “options” which apply to your screen got fast keys associated and should they have?
Ensure that duplicate hot keys do not exist on each screen
When an error message occurs does the focus return to the field in error when the user cancels it?
Verify if the time zone of the API is matching the specification of the time zone of a geographical area
Confirmation messages should be displayed before performing any update or delete operation.
Hourglass or loading icon should be displayed when the application is busy or page is taking more than 5 seconds to produce results.
Check application behavior after operation timeout.
Check cookies used in an application.
Check if downloadable files are pointing to the correct file paths.
All resource keys should be configurable in config files or database instead of hard coding.
Application crash or unavailable pages should be redirected to the error page.
Divide by zero errors should be handled for any calculations.
Check client script (java script, VB script etc) is properly working in different browsers (IE, Firefox, Chrome, safari and Opera).
Test to see what happens if a user deletes cookies while in the site.
Test to see what happens if a user deletes cookies after visiting a site.
Verify the user account gets locked out if the user is entering the wrong password several times.
Verify the cookies should not store passwords and any sensitive information
Verify if, any functionality is not working, the system should not display any application, server, or database information. Instead, it should display the custom error page.
Verify the important operations are written in log files, and that information should be traceable.
Verify the session values are in an encrypted format in the address bar.
Verify the cookie information is stored in encrypted format.
Verify the SQL injection attacks.
Ensure restricted files are not downloadable without appropriate access
Persist the values on the Page.
Check Captcha field with reset button
Create your own unique website with customizable templates.