Based on the Automation Testing Tools, students should gain hands-on experience with testing tools such as Selenium, JIRA, Bugzilla, Mantis, JMeter, and other automation frameworks.
Here, define step by step how to prepared simple case study on testing point of view.
Industry-Oriented
Mini Project / Case Study
Title: Automated Testing of Online Student Admission Portal
Project Duration: 4–6 Weeks
Group Size: 2–3 Students
Domain: Software Testing
Testing Types:
- Functional
Testing
- Automation
Testing
- API
Testing
- Performance
Testing
- Bug
Tracking (Bugzilla, Mentis, Jira)
- Security
Testing (Basic)
Tools Used:
|
Activity |
Tool |
|
Test Case Design |
MS Excel |
|
Automation Testing |
Selenium WebDriver + Java +Python + TestNG |
|
Bug Tracking |
JIRA / Bugzilla / MantisBT |
|
API Testing |
Postman or other tools |
|
Performance Testing |
Apache JMeter |
|
Reporting |
MS Word / Excel |
|
Screenshots |
Snipping Tool |
Objective
To
perform functional, bug-tracking, and performance testing of a web-based
Student Admission Portal using automation testing tools and prepare a
comprehensive testing report.
Problem Statement
A
university has developed an Online Student Admission Portal for student
registration, login, course selection, fee payment, and admission confirmation.
The university wants to ensure that the portal works correctly, is free from
critical defects, and can handle multiple users simultaneously.
Students
must test the application using automation testing tools and provide
recommendations for improvement.
Case Study/Mini Project
GUNI University wants to automate its online
admission process.
Students can
- Register
- Login
- Select
Course
- Upload
Documents
- Pay
Fees
- Receive
Admission Confirmation
The Testing Team must verify whether the portal
works correctly before deployment.
Modules to Test
1. Registration
2. Login
3. Course
Selection
4. Document
Upload
5. Fee
Payment
6. Admission
Confirmation
7. Logout
Step 1: Software Requirement Analysis (SRS)
Objective
Verify all admission functionalities.
Functional Requirements
FR1 Student Registration
FR2 Student Login
FR3 Course Selection
FR4 Upload Documents
FR5 Online Payment
FR6 Admission Confirmation
FR7 Email Confirmation
Non-Functional Requirements
Performance
- Login
within 3 sec
Security
- Password
encrypted
Compatibility
- Chrome
- Edge
- Firefox
Availability
- 24x7
Assumptions
Internet available
Student has Email ID
Payment Gateway working
Step 2: Test Plan Document
Project Name: Online Student Admission Portal Testing
Scope
Testing of
✔
Registration
✔ Login
✔ Course
Selection
✔ Payment
✔
Confirmation
Out of Scope
Database Testing
Source Code Review
Which Test Strategy applied
|
Testing Type |
Tool |
|
Manual |
Excel |
|
Automation |
Selenium |
|
API |
Postman |
|
Performance |
JMeter |
|
Bug Tracking |
JIRA |
To check Entry Criteria
Application deployed
Build available
Test Data ready
To check Exit Criteria
95% Test Cases Passed
No Critical Bug Open
Step 3: Prepare Test Cases and Test Data
Module 1 Registration
|
TC ID |
Test Scenario |
Test Data |
Expected Result |
|
TC01 |
Valid Registration |
Name, Email |
Registration Success |
|
TC02 |
Blank Name |
Empty |
Error Message |
|
TC03 |
Invalid Email |
abc.com |
Invalid Email |
|
TC04 |
Weak Password |
123 |
Validation Message |
Module 2 Login
|
TC ID |
Test Case |
Input |
Expected |
|
TC05 |
Valid Login |
Admin/Admin123 |
Login Success |
|
TC06 |
Wrong Password |
Admin/123 |
Invalid Password |
|
TC07 |
Empty Username |
Blank |
Validation |
Module 3 Course Selection
|
TC ID |
Scenario |
Expected |
|
TC08 |
Select BCA |
Selected |
|
TC09 |
Select MCA |
Selected |
|
TC10 |
No Course |
Error |
Module 4 Payment
|
TC ID |
Scenario |
Expected |
|
TC11 |
Credit Card |
Success |
|
TC12 |
Invalid Card |
Failed |
|
TC13 |
UPI Payment |
Success |
Test Data
|
Username |
Password |
|
student1 |
Student@123 |
|
admin |
Admin@123 |
|
Card No |
CVV |
|
4111111111111111 |
123 |
Step 4: Selenium Automation (Using Java or Python)
Step by step Scenario
Open Browser
↓
Open Website
↓
Login
↓
Select Course
↓
Payment
↓
Logout
Sample Selenium Code
WebDriver driver=new ChromeDriver();
driver.get("https://admissionportal.com");
driver.findElement(By.id("username")).sendKeys("student1");
driver.findElement(By.id("password")).sendKeys("Student@123");
driver.findElement(By.id("login")).click();
driver.findElement(By.id("course")).click();
driver.findElement(By.id("submit")).click();
driver.quit();
Automation Framework
Project
│
├── Test Cases
├── Utilities
├── Reports
├── Drivers
└── Screenshots
Step 5: Bug Report
(For example report prepared in JIRA/Bugzilla/Mantis)
|
Field |
Value |
|
Bug ID |
BUG001 |
|
Module |
Login |
|
Severity |
High |
|
Priority |
High |
|
Reporter |
Student |
|
Assigned To |
Developer |
|
Status |
Open |
|
Environment |
Chrome |
Bug Description
Login accepts invalid password and redirects to Dashboard.
Expected Result
Should display
Invalid Username or Password.
Actual Result
Dashboard Opened.
Screenshot
Attach Screenshot
Example Bug Lifecycle
New
↓
Assigned
↓
Open
↓
Fixed
↓
Retest
↓
Closed
Step 6: API Testing (Postman or other automation tools)
API
POST
/api/login
Request
{
"username":"student1",
"password":"Student@123"
}
Response
{
"status":"Success",
"token":"ABC123XYZ"
}
Validation
Status Code
200
Response Time
<1000 ms
Negative Testing
Wrong Password
Expect
401 Unauthorized
Step 7: JMeter Test Plan
Objective
Check performance for 100 Users
Test Plan
Thread Group
↓
HTTP Request
↓
View Result Tree
↓
Summary Report
↓
Aggregate Report
Configuration
Users 100
Ramp-up 20 Seconds
Loop Count 5
Request
Login
Registration
Course Selection
Payment
Expected Result
Average Response <3 sec
Error Rate 0%
Throughput High
Step 8: Performance Analysis Report
|
Parameter |
Result |
|
Users |
100 |
|
Avg Response |
2.4 sec |
|
Max Response |
3.2 sec |
|
Error |
1% |
|
Throughput |
185 req/min |
Prepard below Graphs
- Response
Time Graph
- Aggregate
Report
- Throughput
Graph
- Error
Percentage
- Transactions
Per Second
Observation
Application performs well up to 100 users.
Above 250 users, response time increases.
Step 9: Security Testing (Basic)
|
Test |
Expected |
|
SQL Injection |
Blocked |
|
XSS |
Blocked |
|
Password Masking |
Yes |
|
HTTPS |
Enabled |
|
Session Timeout |
15 Minutes |
Example SQL Injection
Username
' OR '1'='1
Expected
Login should fail.
Step 10: Final Testing Report
Project Summary
|
Item |
Count |
|
Total Test Cases |
30 |
|
Passed |
28 |
|
Failed |
2 |
|
Automation Scripts |
15 |
|
Bugs Reported |
8 |
|
Bugs Closed |
7 |
|
Open Bugs |
1 |
Defect Summary
|
Severity |
Count |
|
Critical |
0 |
|
High |
2 |
|
Medium |
3 |
|
Low |
3 |
Test Execution Chart
Executed
█████████████████
Passed
███████████████
Failed
██
Screenshots to Include
- Home
Page
- Registration
Form
- Login
Page
- Course
Selection
- Payment
Page
- Admission
Confirmation
- Selenium
Execution
- JIRA/Bugzilla/Mantis
Bug
- Postman
API Response
- JMeter
Summary Report
- JMeter
Aggregate Report
- Final
Dashboard
Suggested Work Distribution (2–3 Students)
|
Student |
Responsibilities |
|
Student 1 |
SRS, Test Plan, Test Cases, Test Data |
|
Student 2 |
Selenium Automation, API Testing, Basic Security Testing |
|
Student 3 |
JIRA/Bugzilla/Mantis Bug Reporting, JMeter Performance Testing, Final Report with Screenshots |
Expected Deliverables (in Report or PPT form)
1. Software
Requirement Specification (SRS)
2. Test Plan
Document
3. Test
Cases with Test Data
4. Selenium
WebDriver Automation Scripts
5. Bug
Reports using JIRA, Bugzilla, or MantisBT
6. Postman
API Collection and Test Results
7. Apache
JMeter Test Plan (.jmx) and Performance Results
8. Performance
Analysis Report with Graphs
9. Final
Testing Report including screenshots, defect summary, conclusions, and
recommendations
---------------------------------------------------------------------------------------------------------------
This mini project closely mirrors a real software testing workflow
followed in IT companies, allowing students to gain practical experience in
requirements analysis, manual testing, automation, API validation, defect
management, performance testing, and reporting.
Learning Outcomes
After
completing this mini project, students will be able to:
- Understand
real-world software testing processes.
- Create
and execute automated test cases.
- Use
Selenium for web application testing.
- Track
defects using JIRA/Bugzilla/Mantis.
- Perform
API testing using Postman.
- Conduct
load and performance testing using JMeter.
- Prepare
professional testing documentation and reports.
Note: These
titles cover all practical exposure to test
case preparation, automation testing, defect management, API validation, and
performance testing.
Or follow my blog from the below link
){kind=link}
0 Comments