ASSIGNMENT-4
1. Different Test Deliverables in Software Testing
Test deliverables are the artifacts created and maintained during the
software testing lifecycle. These help in planning, executing, and tracking
the quality assurance process.
Key Test Deliverables:
Test Plan: Document outlining scope, objectives, schedule, approach,
and resources.
Test Strategy: High-level document describing test levels and types.
Test Scenarios: High-level documentation of testable situations or
functionalities.
Test Cases: Detailed steps to validate specific functionalities.
Test Data: Data used for executing test cases.
Test Scripts: Automated test code/scripts.
Traceability Matrix: Mapping between requirements and test cases
to ensure coverage.
Test Logs: Execution details, including what passed/failed.
Defect Reports: Documentation of identified bugs or issues.
Test Summary Report: Final report summarizing the testing
activities and outcomes.
Release Notes: Information about the current software release
(features, fixes, known issues).
2. Test Plan and Test Approach Definitions
🔹 Test Plan:
A Test Plan is a formal document that outlines the objectives, resources,
scope, schedule, and approach for the testing process. It serves as a
blueprint for systematically performing testing activities.
Contents Typically Include:
Test objectives
Features to be tested
Test criteria (entry/exit)
Schedule & milestones
Resources & responsibilities
Tools to be used
Risk analysis and mitigation
🔹 Test Approach:
The Test Approach (or testing strategy) is a part of the test plan that
defines how testing will be carried out. It describes the testing techniques,
levels, roles, and types of testing to be performed.
Types of Approaches:
Preventive (early test design)
Reactive (post-development)
Risk-based testing
Exploratory testing
3. Importance of a Test Plan in Software Testing
A Test Plan is crucial for the success of any testing project due to the
following reasons:
Clarity & Direction: Clearly defines what needs to be tested, how,
and by whom.
Resource Management: Helps in allocating human and tool
resources effectively.
Risk Mitigation: Identifies potential risks and defines mitigation
strategies.
Schedule & Progress Tracking: Provides a roadmap to monitor
timelines and deliverables.
Improved Communication: Acts as a communication tool among
stakeholders (devs, QA, clients).
Traceability: Maintains requirement coverage through test cases and
traceability matrix.
4. Differences Between Traditional Testing and Agile Testing
Feature Traditional Testing Agile Testing
Sequential (Waterfall
Process Iterative & incremental
model)
Involvemen Testers involved after
Testers involved from the beginning
t development
Documenta
Heavily documented Lightweight documentation
tion
Feedback Late in the cycle Continuous feedback
Change
Difficult to manage Embraces change
Handling
Testing Often manual and phase- Emphasizes automation and
Type based continuous testing
Feature Traditional Testing Agile Testing
Release
Long Short sprints/releases
Cycle
5. Preparing a Test Summary Report for an E-commerce
Website
A Test Summary Report (TSR) summarizes the test execution results and
final quality assessment. For an e-commerce website, it might include:
🗂 Sample Structure:
1. Title: Test Summary Report – XYZ E-commerce Platform
2. Objective: Validate core features like user login, product search, cart,
checkout, and payment.
3. Scope: Functional, UI, and integration testing across web and mobile.
4. Test Environment: OS/browser versions, test tools, devices used.
5. Test Coverage:
o Total test cases: 150
o Executed: 145
o Passed: 135
o Failed: 10
6. Defect Summary:
o Critical: 2
o Major: 5
o Minor: 3
7. Risk Assessment:
o Payment gateway integration had intermittent issues.
8. Conclusion:
o Overall stability achieved with 95% test pass rate.
o Recommended for production deployment with minor fixes.
6. Manual Testing vs Automated Testing in Large-Scale
Projects
Criteria Manual Testing Automated Testing
Speed Slow, time-consuming Fast, suitable for regression
Accuracy Prone to human error High accuracy, consistent
Initial High (tools, script
Low
Cost development)
Maintena Easier to update test Scripts need regular
nce cases maintenance
Suitabilit Exploratory, usability, Regression, performance,
y ad-hoc load
Criteria Manual Testing Automated Testing
Scalabilit
Limited Highly scalable
y
Best Use UI testing, one-off Large-scale projects,
Case tasks frequent builds
Effectiveness Verdict:
For large-scale projects, automated testing is far more efficient for
repetitive and regression tests. However, manual testing is still essential
for exploratory, UX, and logic validation.
7. Impact of Agile Testing on the Software Development
Lifecycle (SDLC)
Agile Testing integrates testing activities directly into the Agile SDLC,
influencing it in the following ways:
✅ Positive Impacts:
Continuous Testing: Testing is performed in parallel with
development.
Early Bug Detection: Leads to cost-effective fixes.
Improved Collaboration: Testers, developers, and product owners
work closely.
Faster Time-to-Market: Shorter feedback loops and sprint cycles.
High Product Quality: Incremental testing ensures frequent
improvements.
🔁 Iterative SDLC Flow:
1. Requirements (user stories)
2. Design (short iterations)
3. Development & Unit Testing
4. Continuous Integration
5. Testing (automated/manual)
6. Sprint Review & Retrospective
Agile testing practices like TDD (Test-Driven Development) and BDD
(Behavior-Driven Development) further align testing tightly with
development, ensuring quality is built-in rather than tested-in.
