How to Write Test Cases for Freshers
How do you write a test case? Write the test case ID, title, preconditions, test steps, test data, expected result, actual result and status for one specific check. Start from a requirement, list positive and negative scenarios, apply techniques like boundary value analysis and equivalence partitioning, then turn each scenario into clear, repeatable steps that anyone on the team could run. A good test case checks one thing, is easy to follow and has a clear expected result.
This guide from VibrantMinds Technologies in Pune explains how to write test cases for freshers with a ready template, four design techniques, worked examples (login page, ATM withdrawal, search box, age field), a review checklist and interview answers. It is written for anyone searching how to write test cases for freshers, test case writing for freshers, test case template with examples, test cases for login page, manual testing test case examples, boundary value analysis and equivalence partitioning, positive and negative test cases, test case vs test scenario or a free IT job WhatsApp group for testing freshers in Pune.
Test case formats vary by company and tool (Excel, Jira, TestRail and others). The principles here carry across all of them. This guide avoids salary figures and unverified statistics.
KEY TAKEAWAYS (READ THIS FIRST)
Takeaway | Detail |
|---|---|
One test case, one objective | Don’t mix many checks in a single test case. |
Always write expected results | Without one, nobody knows if the test passed. |
Use techniques, not guesses | Equivalence partitioning and boundary value analysis cut the number of tests while keeping coverage. |
Cover negative cases | Most bugs hide in invalid inputs and edge values. |
Write for someone else to run | Clear steps, exact data, no assumptions. |
Link to requirements | Every test case should trace back to a requirement. |
TEST CASE VS TEST SCENARIO
Point | Test scenario | Test case |
|---|---|---|
What it is | A high-level idea of what to test | A detailed set of steps to test it |
Detail level | One line | Steps, data, expected result |
Example | “Verify the login functionality” | “Verify login with a valid email and valid password” |
Ratio | One scenario | Many test cases |
THE ANATOMY OF A TEST CASE (COPY THIS TEMPLATE)
Field | What to write | Example |
|---|---|---|
Test Case ID | A unique ID | TC_LOGIN_001 |
Module | Feature area | Login |
Title / Summary | One clear line | Verify login with valid credentials |
Priority | High / Medium / Low | High |
Preconditions | What must be true before starting | User account exists and is active |
Test Steps | Numbered, exact actions | 1. Open the login page 2. Enter email 3. Enter password 4. Click Login |
Test Data | The exact values | user@example.com / Test@1234 |
Expected Result | What should happen | User lands on the dashboard |
Actual Result | What really happened | (filled during execution) |
Status | Pass / Fail / Blocked / Not run | Pass |
Remarks | Notes, defect ID | (optional) |
Excel header row to copy:TC ID | Module | Title | Priority | Preconditions | Steps | Test Data | Expected Result | Actual Result | Status | Defect ID
THE 6-STEP METHOD TO WRITE TEST CASES
TECHNIQUE 1: EQUIVALENCE PARTITIONING
Idea: split inputs into groups (partitions) that should behave the same, then test one value from each group instead of every value.
Example: an age field that accepts 18 to 60
Partition | Range | Pick one value | Expected |
|---|---|---|---|
Invalid (too low) | below 18 | 10 | Rejected |
Valid | 18 to 60 | 35 | Accepted |
Invalid (too high) | above 60 | 75 | Rejected |
Three test values cover three behaviours instead of dozens.
TECHNIQUE 2: BOUNDARY VALUE ANALYSIS
Idea: bugs often occur at the edges of ranges, so test the boundary values and the values just next to them.
Example: the same age field (18 to 60)
Test value | Why | Expected |
|---|---|---|
17 | Just below minimum | Rejected |
18 | Minimum | Accepted |
19 | Just above minimum | Accepted |
59 | Just below maximum | Accepted |
60 | Maximum | Accepted |
61 | Just above maximum | Rejected |
Tip: use boundary analysis together with equivalence partitioning. Partitions find the groups, boundaries test the edges.
TECHNIQUE 3: DECISION TABLE
Idea: when the result depends on a combination of conditions, list every combination.
Example: login with email and password
Rule | Email valid? | Password valid? | Expected result |
|---|---|---|---|
1 | Yes | Yes | Login successful |
2 | Yes | No | Error: invalid credentials |
3 | No | Yes | Error: invalid credentials |
4 | No | No | Error: invalid credentials |
Each rule becomes at least one test case.
TECHNIQUE 4: ERROR GUESSING
Idea: use experience and curiosity to guess where bugs may hide.
Common guesses: blank fields, only spaces, very long text, special characters (@#$%), copy-pasted input, SQL-like text in a text box, double-clicking a button, pressing Back after submitting, session timeout, slow network.
Note: error guessing supports the other techniques. It doesn’t replace them.
WORKED EXAMPLE 1: LOGIN PAGE TEST CASES
Requirement: a user logs in with email and password. Five wrong attempts lock the account for a period. (This is a sample requirement for practice.)
TC ID | Title | Test data | Expected result | Type |
|---|---|---|---|---|
TC_LOGIN_001 | Login with valid email and valid password | valid / valid | Dashboard opens | Positive |
TC_LOGIN_002 | Login with valid email and wrong password | valid / wrong | Error message, no login | Negative |
TC_LOGIN_003 | Login with unregistered email | unknown / any | Error message, no login | Negative |
TC_LOGIN_004 | Login with both fields blank | blank / blank | Required-field messages | Negative |
TC_LOGIN_005 | Login with only the email entered | valid / blank | “Password required” message | Negative |
TC_LOGIN_006 | Email without “@” | userexample.com / any | Invalid email format message | Negative |
TC_LOGIN_007 | Password field masks characters | typing a password | Characters appear as dots | UI |
TC_LOGIN_008 | Show-password icon (if present) | click the icon | Password becomes visible, hides again on click | Functional |
TC_LOGIN_009 | Enter key submits the form | valid / valid, press Enter | Login happens | Usability |
TC_LOGIN_010 | Account locks after repeated wrong attempts | wrong password 5 times | Lock message shown, per requirement | Security |
TC_LOGIN_011 | Case sensitivity of password | “test@1234” vs “Test@1234” | Rejected if passwords are case-sensitive | Negative |
TC_LOGIN_012 | Leading and trailing spaces in email | “ user@example.com “ | Behaviour matches the requirement (trimmed or rejected) | Edge |
TC_LOGIN_013 | Back button after logout | logout, then press Back | Login page shows, no private data visible | Security |
TC_LOGIN_014 | Session after closing and reopening browser | log in, close browser, reopen | Behaviour as per session rules | Functional |
One test case written in full (copy this style):
WORKED EXAMPLE 2: ATM WITHDRAWAL TEST CASES
Requirement (sample): a customer can withdraw cash in multiples of 100, minimum 100, maximum 10,000 per transaction, and not more than the account balance.
TC ID | Scenario | Test data | Expected result |
|---|---|---|---|
TC_ATM_001 | Withdraw a valid amount | 500, balance 5,000 | Cash dispensed, balance reduced |
TC_ATM_002 | Minimum amount | 100 | Accepted |
TC_ATM_003 | Below minimum | 50 | Rejected with message |
TC_ATM_004 | Maximum amount | 10,000, balance 20,000 | Accepted |
TC_ATM_005 | Above maximum | 10,100 | Rejected with message |
TC_ATM_006 | Not a multiple of 100 | 550 | Rejected with message |
TC_ATM_007 | Amount greater than balance | 2,000, balance 1,500 | “Insufficient balance” |
TC_ATM_008 | Zero or negative amount | 0 and -100 | Rejected |
TC_ATM_009 | Non-numeric entry | “abc” | Not accepted |
TC_ATM_010 | Wrong PIN entered | wrong PIN | Access denied, retry rules apply |
TC_ATM_011 | Cancel during the transaction | press Cancel | No money deducted, card returned |
TC_ATM_012 | Machine out of cash | any amount | Proper message, no deduction |
Notice: rows 002, 003, 004, 005 are boundary value analysis. Rows 006 to 009 come from equivalence partitioning and error guessing.
WORKED EXAMPLE 3: SEARCH BOX TEST CASES
TC ID | Scenario | Test data | Expected result |
|---|---|---|---|
TC_SRCH_001 | Search with a valid keyword | “laptop” | Relevant results appear |
TC_SRCH_002 | Search with no results | “zzzxxyy” | “No results found” message |
TC_SRCH_003 | Empty search | blank | No crash, sensible behaviour per requirement |
TC_SRCH_004 | Case insensitivity | “LAPTOP” vs “laptop” | Same results |
TC_SRCH_005 | Special characters | “@#$%” | No error page, safe handling |
TC_SRCH_006 | Very long text | 500 characters | Handled gracefully |
TC_SRCH_007 | Leading and trailing spaces | “ laptop “ | Works like “laptop” |
TC_SRCH_008 | Partial word | “lapt” | Per requirement (suggestions or results) |
TC_SRCH_009 | Search with Enter key and with button | “laptop” | Both give the same results |
TC_SRCH_010 | Result count and pagination | broad keyword | Count matches, next and previous pages work |
POSITIVE VS NEGATIVE TEST CASES
Point | Positive test case | Negative test case |
|---|---|---|
Goal | Confirm the feature works with valid input | Confirm the system handles invalid input safely |
Input | Valid data | Invalid, missing or unexpected data |
Expected | Success | A clear error message, no crash |
Login example | Correct email and password | Wrong password, blank fields |
Share of testing | Needed | Often finds more bugs, so don’t skip |
GOOD VS BAD TEST CASES
Bad test case | Why it’s bad | Better version |
|---|---|---|
“Check login” | Vague | “Verify login with valid email and valid password” |
“Enter details and click submit” | Missing exact data | “Enter email user@example.com and password Test@1234” |
“Should work properly” | No measurable expected result | “User lands on the dashboard and sees their name” |
One test case checking login, profile and logout | Too many objectives | Split into separate cases |
Steps assume knowledge (“do the usual setup”) | Others can’t repeat it | Put setup in preconditions |
No priority or ID | Hard to manage | Add ID and priority |
TEST CASE REVIEW CHECKLIST (RUN THIS BEFORE SUBMITTING)
Check | Yes / No |
|---|---|
Does it have a unique ID and a clear title? | |
Are preconditions stated? | |
Are steps numbered and exact? | |
Is the test data specific? | |
Is the expected result clear and measurable? | |
Does it test only one objective? | |
Are positive and negative cases both covered? | |
Are boundary values covered where ranges exist? | |
Does it trace back to a requirement? | |
Is there no duplicate of another test case? | |
Could a new teammate run it without asking you? |
TEST CASE INTERVIEW QUESTIONS FOR FRESHERS
Question | Short answer |
|---|---|
What is a test case? | A set of conditions, steps, data and an expected result used to verify one specific behaviour of the software. |
Test case vs test scenario? | A scenario is a high-level idea. A test case is the detailed, step-by-step version. |
What makes a good test case? | Clear, specific, single objective, repeatable, with an expected result and traceable to a requirement. |
What is boundary value analysis? | Testing at the edges of input ranges, such as min, max and the values just outside. |
What is equivalence partitioning? | Grouping inputs that behave alike and testing one value from each group. |
What is a positive vs negative test case? | Valid input should work, invalid input should be handled safely. |
What is a traceability matrix? | A table mapping requirements to the test cases that cover them. |
What do you do when the requirement is unclear? | Ask the business analyst or developer for clarification and document the assumption. |
How do you prioritise test cases? | By business risk, usage frequency and impact if it fails. |
Can you write test cases for a pen or a lift? | Yes. Cover functionality, usability, boundaries, safety and failure behaviour. |
COMMON MISTAKES FRESHERS MAKE WHEN WRITING TEST CASES
Mistake | Why it hurts | Better approach |
|---|---|---|
Only writing positive cases | Misses most bugs | Add negative and edge cases |
Vague expected results | Can’t decide pass or fail | Make them specific |
Writing without reading the requirement | Wrong tests | Read it first and ask questions |
Too many steps in one case | Hard to debug | Split by objective |
Copy-pasting with small changes and no thought | Duplicates, gaps | Use techniques |
Not reviewing | Typos and gaps remain | Use the checklist |
Ignoring priority | Time wasted on low-risk tests | Mark High, Medium, Low |
Never updating after changes | Outdated tests | Maintain them with each change |
14-DAY TEST CASE PRACTICE PLAN
Day | Focus | Task |
|---|---|---|
1 | Basics | Learn test case vs scenario, and the template |
2 | Template in Excel | Build your own template with all fields |
3 | Equivalence partitioning | Practise on three input fields (age, marks, quantity) |
4 | Boundary value analysis | Practise on the same three fields |
5 | Decision table | Make one for login and one for a discount rule |
6 | Login page | Write 15 test cases |
7 | Review | Review your login cases with the checklist |
8 | ATM or payment form | Write 12 test cases |
9 | Search box | Write 10 test cases |
10 | Registration form | Write cases for each field, plus validations |
11 | Everyday objects | Write cases for a pen, a lift and a water bottle |
12 | Real website practice | Pick a public site and write 20 cases for one feature |
13 | Interview practice | Answer the interview table aloud |
14 | Portfolio | Clean your best sheets and add them to a GitHub repository or PDF to show interviewers |
MYTH VS REALITY
Myth | Reality |
|---|---|
“Test cases are just a formality.” | They are the base for repeatable, reliable testing. |
“More test cases means better testing.” | Well-designed cases beat sheer numbers. |
“Automation removes the need for test cases.” | Automation scripts are built from good test cases. |
“Only testers need test cases.” | Developers, BAs and clients also use them to understand behaviour. |
“Negative testing is optional.” | Many real bugs surface with invalid input. |
“Freshers can’t write good test cases.” | With the template and techniques, you can write clear ones quickly. |
HOW VIBRANTMINDS HELPS FRESHERS BUILD TESTING CAREERS
VibrantMinds Technologies Pvt. Ltd. is a Pune-based IT training and placement support company. If you searched for VibrantMinds or VibrantMinds Technologies, here is what it offers:
Software Testing (Manual + Automation) (about 2 to 5 months): test case design, STLC, bug tracking, SQL, Selenium basics and practice projects. Please check the candidate portal for the latest syllabus and tools.
Full Stack Java Development (about 4 to 6 months), Core Java and Python & Data Science for other career paths
Interview preparation: Technical rounds, test case and scenario questions, HR rounds, aptitude, communication and mock interviews
Resume and portfolio guidance: Showing your test case work honestly
Placement support: Screening, drive coordination and interview support. Check https://candidates.vibrantminds.in/ for current openings.
Free WhatsApp job alert groups for fresher IT jobs and drives
Honesty first: VibrantMinds offers placement support, not a guaranteed job, and no legitimate recruiter should ask you to pay to be interviewed.
VibrantMinds works as a talent ecosystem connecting candidates, colleges and companies, with 1900+ partner colleges and 600+ hiring companies. More fresher job guidance: https://candidates.vibrantminds.in/blog/fresher-jobs-pune-2026
VIBRANTMINDS COURSES AT A GLANCE
Course | Duration | Key topics |
|---|---|---|
Full Stack Java Development | 4 to 6 months | Core Java, OOP, JDBC, SQL, Spring Boot, REST APIs, front-end basics, projects, aptitude and interview preparation |
Software Testing (Manual + Automation) | 2 to 5 months | Test cases, STLC, bug tracking, SQL, Selenium basics |
Core Java | 1 to 2 months | Syntax, OOP, collections, exceptions, strings |
Python & Data Science | 2 to 4 months | Python basics, data handling, analysis fundamentals |
Fees, syllabus and batch dates are on https://candidates.vibrantminds.in/. Please confirm them directly before enrolling.
THE VIBRANTMINDS PLACEMENT PIPELINE: SIX STEPS
REAL OUTCOMES: WHAT TO EXPECT AND WHAT NOT TO
Past students have shared positive feedback about the training and support, and have gone on to roles at companies such as Aress Software and Education Technologies, Saama Technologies and Three M Software. Results vary by candidate, skill level, effort and market conditions, so please confirm details directly with the VibrantMinds team. No one can honestly promise a guaranteed job.
JOIN FREE VIBRANTMINDS WHATSAPP GROUPS: IT AND TESTING JOB UPDATES FOR FRESHERS IN PUNE AND INDIA
Looking for free WhatsApp groups, free IT job WhatsApp groups, a Java WhatsApp group for freshers or a job updates WhatsApp group in India? The VibrantMinds groups share fresher IT and testing openings, campus drives, walk-in interview alerts and interview preparation updates, free of charge. Join whichever group has space. All three carry the same type of updates.
Group | What it offers | Link |
|---|---|---|
VibrantMinds Fresher IT Jobs, Group 1 | Fresher openings, campus drives, walk-in alerts | |
VibrantMinds Fresher IT Jobs, Group 2 | Fresher openings, campus drives, walk-in alerts | |
VibrantMinds Fresher IT Jobs, Group 3 | Fresher openings, campus drives, walk-in alerts |
Never pay to apply. Legitimate recruiters do not charge candidates for tests, interviews or offer letters. Do not share sensitive personal or financial details in any group chat.
FREQUENTLY ASKED QUESTIONS
1. How do I write test cases for freshers step by step?
Read the requirement, list test scenarios, apply techniques (equivalence partitioning, boundary value analysis, decision tables), then write each case with an ID, title, preconditions, numbered steps, exact test data and a clear expected result. Review it with a checklist, execute it and record the status.
2. What is the difference between a test case and a test scenario?
A test scenario is a high-level idea of what to test, such as “verify login”. A test case is the detailed version with steps, data and an expected result, such as “verify login with a valid email and a wrong password”. One scenario usually leads to many test cases.
3. What is a boundary value analysis example for an age field?
For an age field that accepts 18 to 60, test 17, 18, 19, 59, 60 and 61. The values 17 and 61 should be rejected, and 18, 19, 59 and 60 should be accepted.
4. How do I write test cases for a login page?
Cover valid credentials, wrong password, unregistered email, blank fields, invalid email format, password masking, Enter-key submission, account lock after repeated failures, case sensitivity, session behaviour and the Back button after logout. The table above has 14 ready examples.
5. Is there a free WhatsApp group for testing freshers in Pune?
Yes. VibrantMinds runs free fresher IT job WhatsApp groups that share testing, Java and other IT openings, campus drives and walk-in alerts. Join through the links above, and always verify a job post and never pay to apply.
CONCLUSION: WRITE TEST CASES ANYONE CAN RUN
The skill behind how to write test cases for freshers is clarity. Read the requirement, use equivalence partitioning and boundary value analysis, cover both positive and negative cases, write specific steps with exact data and a measurable expected result, and review your work with the checklist. Practise on login, ATM and search examples, follow the 14-day plan and keep your best sheets as a portfolio.
If you’re in Pune and want structured software testing training with real practice, interview preparation and placement support, VibrantMinds Technologies is here to help.
Call to action:
Website: https://vibrantminds.in/
Candidate portal and courses: https://candidates.vibrantminds.in/
Fresher jobs guide: https://candidates.vibrantminds.in/blog/fresher-jobs-pune-2026
Join the free WhatsApp groups: the three links above
VISIT OR CONTACT VIBRANTMINDS IN PUNE
Company: VibrantMinds Technologies Pvt. Ltd.
Address: Viva Academy Building, Warje, Pune, Maharashtra 411052
Phone: +91 95035 79517
Email: support@vibrantmindstech.com
Website: https://vibrantminds.in/
Candidate portal and courses: https://candidates.vibrantminds.in/
