Assignment: Case Study on Software Testing
Objective:
To understand and analyze the software testing life cycle, techniques, strategies, and real-world
challenges by examining a practical case study.
Assignment Title:
"Analyzing Software Testing Practices: A Case Study Approach"
Assignment Structure:
Part 1: Case Study Description
Choose or provide a case study of a real-world software project (e.g., an e-commerce app, banking
system, health management system, etc.). It may be:
An actual company project (public case study)
A detailed hypothetical project
A past academic project with testing details
Example Case Study ( Choose any of your choice):
A company is developing a web-based e-commerce platform. During testing, multiple critical issues were
found in the payment module, and several bugs escaped into production causing customer
dissatisfaction. The QA team used manual testing and partial automation with Selenium.
Part 2: Case Study Analysis Questions
Students are required to answer the following questions based on the case study:
1. Project Overview
Briefly describe the software project.
What is the scope and primary functionality of the software?
2. Testing Strategy
What testing methods were used (Manual, Automated, Unit, Integration, etc.)?
Were white-box or black-box techniques applied?
3. Defect Analysis
What were the major bugs identified?
At what stage were they discovered?
Could they have been detected earlier? How?
4. Testing Tools
What tools (if any) were used for testing?
Evaluate the suitability and effectiveness of the tools used.
5. Challenges Faced
What challenges did the testing team face during the project?
How were those challenges addressed (or not addressed)?
6. Recommendations
Suggest improvements in the testing process.
How can the use of automation or CI/CD pipelines enhance testing?
Propose a revised testing strategy.
Deliverables:
A written report (1500–2500 words) answering the above questions.
Visuals: Include diagrams such as a bug lifecycle, test case flow, testing pyramid, etc.
Optional: Screenshots of tools (if any are used in a demo/project).
Evaluation Criteria:
Criteria Marks
Case Study Understanding 10
Criteria Marks
Depth of Analysis 20
Testing Strategy Evaluation 15
Realistic Recommendations 15
Clarity and Presentation 10
Use of Diagrams/Visuals 10
Total 80
Assignment: Software Testing for Recruitment Website
Objective
To design and execute a comprehensive software testing strategy for a Recruitment Website Project,
ensuring functionality, usability, performance, and security of the system.
Project Description (Context)
The recruitment website should allow:
Job seekers to register, create profiles, upload resumes, and apply for jobs.
Recruiters to post jobs, manage applications, and shortlist candidates.
Admin to manage users, monitor activities, and generate reports.
Assignment Tasks
Part A: Test Planning (15 Marks)
1. Write a Test Plan Document including:
o Objective of testing
o Scope (in-scope, out-of-scope features)
o Testing types to be used (functional, usability, performance, security, etc.)
o Roles & responsibilities
o Test environment details
o Entry and exit criteria
Part B: Test Case Design (25 Marks)
Prepare at least 10 test cases covering different modules. Each test case must include:
Test Case ID
Test Scenario
Preconditions
Test Steps
Expected Result
Actual Result (to be filled after execution)
Status (Pass/Fail)
Example:
Test Case ID: TC-001
Scenario: Verify user registration with valid details
Precondition: User not registered before
Steps: Enter name, email, password → Submit
Expected Result: Registration successful, confirmation email sent
Part C: Testing Types (20 Marks)
Perform and document the following testing types:
1. Functional Testing: Verify login, job posting, job application, and search functionalities.
2. Usability Testing: Check ease of navigation, readability, and UI clarity.
3. Performance Testing: Test response time for job search under load.
4. Security Testing: Check password strength, SQL injection vulnerability, and session handling.
Part D: Defect Reporting (15 Marks)
Identify minimum 5 defects/bugs during testing.
Record them using a Defect Report Template including:
o Defect ID
o Description
o Severity (Critical, Major, Minor)
o Steps to Reproduce
o Expected vs Actual Result
o Status (New, Open, Fixed, Closed)
Part E: Test Automation (Optional for Bonus Marks +10)
Select one feature (e.g., Login or Job Application).
Automate the test case using any tool (Selenium, JUnit, or PyTest).
Submit the automation script along with a short explanation.
Submission Guidelines
Format: PDF/Doc with screenshots (if available).
Deadline: [Insert Date]
Marks Distribution:
o Test Plan: 15
o Test Cases: 25
o Testing Types: 20
o Defect Report: 15
o Documentation Quality: 10
o Bonus Automation: 10
