SECTION 1 — WEBSITE TESTING GUIDE
Step-by-Step Manual Testing Process for [Link]
Target Website: [Link]
What Is Manual Testing?
Manual testing means you visit the website yourself, click through every page, fill out forms, test
buttons, and check whether everything works correctly — just like a real user would. You then
document your findings clearly so developers can understand and fix any issues.
STEP 1 — Explore the Website First (Do Not Test Yet)
Before testing anything, spend 10–15 minutes just browsing the website like a normal visitor. This
helps you understand its structure.
What To Do:
Go to [Link] and browse all pages
Note down every page and section you find (Home, About, Products, Contact, etc.)
Look for: menus, buttons, forms, images, links, and pop-ups
Do NOT click to test yet — just observe and understand the layout
Pages To Look For:
Page / Section What To Notice
Homepage Hero section, CTA buttons, banners, navigation
links
About / Company Team info, mission statement, content accuracy
Products / Services Feature descriptions, demo links, pricing
Contact Page Forms, phone/email, address, map
Footer Social media links, legal links, copyright text
Login / Sign Up If present — registration and login forms
STEP 2 — Know What To Test (Your Checklist)
Before you start testing, prepare your checklist. These are the main areas you will test one by one:
# Area To Test What To Check
1 Navigation Do all menu links open the
correct page? Are there any
broken pages?
2 Forms Does the form show errors for
empty fields, wrong email, or
invalid input?
3 Buttons Does every button perform an
action? Are any buttons non-
functional?
4 Links Do all links work? Are there
any 404 errors or dead links?
5 UI / Design Is the layout aligned? Are
fonts, colors, and spacing
consistent?
6 Mobile View Does the website look correct
(Responsiveness) on phone or tablet screen
sizes?
7 Page Load Speed Does any page take too long to
load?
8 Spelling & Grammar Are there any typos or
grammatical mistakes in the
content?
9 Images Are all images loading? Are
there any broken or missing
images?
10 Error Messages Do error messages appear
clearly when something goes
wrong?
STEP 3 — Start Testing Page by Page
Go through each page in this order. Test each area methodically — do not skip pages.
Order Page What To Check
1 Homepage Check hero section, CTA
buttons, images, navigation
links, banners
2 Navigation Menu Click every single menu item
— check if correct page opens
3 Contact / Form Page Most important — test all
form validations thoroughly
4 About / Services Pages Check content, links, images,
and any embedded media
5 Footer Test all social links, legal links,
copyright text, and other links
6 Login / Sign Up If present — test with empty,
invalid, and valid credentials
STEP 4 — Document Every Finding in Google Sheets or Excel
Open Google Sheets or Excel. Create a new sheet and add these columns for every test case you run:
Column Name What To Write
Test Case ID TC001, TC002, TC003 ... (number each test
case)
Page / Section Which page are you testing? e.g., Contact Form,
Homepage
What You Tested Short description — e.g., Submit form with all
fields empty
Steps To Reproduce Numbered steps: 1. Go to page, 2. Do this, 3.
Click that
Expected Result What SHOULD happen — e.g., Error message
should appear
Actual Result What ACTUALLY happened — e.g., No message
appeared, nothing happened
Status PASS (works correctly) or FAIL (something is
wrong)
Severity High = broken feature | Medium = bad UX | Low
= cosmetic issue
Screenshot Attach a screenshot image of the issue
Example of a complete test case entry:
Test Case ID: TC003
Page: Contact Form
What You Tested: Submit form with empty fields
Steps: 1. Go to /contact 2. Leave all fields empty 3. Click Submit
Expected: Error message shown for required fields
Actual: Nothing happened — no error, no response
Status: FAIL | Severity: High
STEP 5 — Take Screenshots of Every Issue
Every bug you find must have a screenshot as proof. Here is how to take screenshots:
How To Take Screenshots:
Press Win + Shift + S to open Snipping Tool and select the areaWindows:
Press Cmd + Shift + 4 and drag to select the areaMac:
Save each screenshot with a clear name like: [Link]
Attach the screenshot to the matching row in your Google Sheet / Excel
What To Screenshot:
The error message (or lack of one) when a form fails
A broken/missing image on the page
A button that does not respond when clicked
Misaligned text or overlapping design elements
A 404 page or broken link destination
STEP 6 — Test Forms Thoroughly (Most Important Step)
Forms are the most critical part of any website to test. For every form you find on the site, run ALL
of these test scenarios:
Test ID What To Test Expected Result Severity
TC-F1 Submit completely Error messages High
empty form shown for all required
fields
TC-F2 Enter invalid email Error: 'Please enter a High
(abc@ or [Link]) valid email address'
TC-F3 Enter only spaces in Should be treated as High
all text fields empty — error should
appear
TC-F4 Enter very long text Field should limit or Medium
(100+ characters) show an error
TC-F5 Enter special No crash — should Medium
characters either accept or show
(!@#$%^&*) error
TC-F6 Fill all fields with valid Success message or High
data and submit confirmation shown
TC-F7 Enter valid data but Only that one field High
leave one required shows an error
field empty
STEP 7 — Check Mobile Responsiveness
Mobile responsiveness means: does the website look and work correctly on a phone or tablet?
Many websites break on smaller screens.
How To Test Mobile View in Chrome (No Phone Needed):
1. Open the website in Google Chrome
2. Press F12 on your keyboard — Developer Tools will open
3. Click the phone/tablet icon at the top (called 'Toggle Device Toolbar')
4. Select different devices: iPhone SE, iPhone 14, iPad, Samsung Galaxy
5. Check these things on each device size:
What To Check on Mobile:
Does the navigation menu collapse into a hamburger icon?
Is all text readable without zooming in?
Are buttons large enough to tap with a finger?
Do images resize properly without overflowing?
Does any text overlap with other elements?
Is the layout stacked vertically (single column)?
Are forms easy to fill out on a small screen?
STEP 8 — Final Review of Your Document
Before submitting, go through this final checklist to make sure your testing document is complete:
Checklist Item Details Done?
Minimum 15–20 test cases Include both PASS and FAIL []
written results
Clear steps to reproduce for Anyone should be able to []
every issue follow your steps
Screenshots attached for Named clearly — TC003- []
every bug found [Link]
Severity marked for all FAIL High / Medium / Low []
cases
Both Pass and Fail test cases Not just bugs — also confirm []
included what works
Document is well-organized No spelling mistakes in your []
and readable own document
Quick Summary — Order of Steps
STEP 1 → Explore the website casually (10–15 mins)
STEP 2 → Prepare your testing checklist
STEP 3 → Test each page one by one
STEP 4 → Document every test case in Google Sheets / Excel
STEP 5 → Take screenshots of every bug you find
STEP 6 → Test all forms with multiple scenarios
STEP 7 → Check mobile responsiveness using Chrome DevTools
STEP 8 → Review and finalize your document before submitting