A

./ Project Plan Report

on
Driver Assistance System software for
autonomous vehicles
submitted for module
ISTQB Foundations and Applications

Submitted By:

Yendluri Raja
PS No:40905076

(GENESIS FY 24 Q2: Chennai/Vadodara)

Business Unit: Embedded VTR SDV/System Integration
 Mini Project-Zomato

I. Application Under Test[AUT]: Definition/Overview

The Driver Assistance System (DAS) is a comprehensive and sophisticated automotive technology
designed to enhance driver safety, improve vehicle performance, and provide a more efficient and
enjoyable driving experience. This system integrates a variety of sensors, cameras, and advanced
algorithms to assist drivers in navigating traffic, avoiding potential hazards, and adhering to safety
protocols. DAS encompasses a range of features aimed at increasing overall road safety and reducing
the risk of accidents.

II. Test Plan Overview

The Test Plan for the Driver Assistance System (DAS) provides a comprehensive overview of the testing
approach, strategies, and resources required to ensure the reliability, functionality, and safety of the
system. This section outlines the key aspects of the test plan, including the scope of the project, test
strategy, schedule, resource requirements, and the expected deliverables.

L&T Technology Services CONFIDENTIAL

Page 2 of 20
 Mini Project-Zomato

III. Scope
The scope of testing for the Driver Assistance System is extensive, encompassing both the software and
hardware components. The primary focus is on ensuring the effectiveness, reliability, and safety of the
driver assistance features integrated into the system.
Functional Testing:
Ensuring each driver assistance feature performs its intended function accurately.
Safety Testing:
Verifying the safety measures in place to protect the driver and passengers.
Integration Testing:
Ensuring seamless integration between hardware and software components.
Usability Testing:
Assessing the user interface and overall user experience with driver assistance features.

IV. App Functional Requirements #

1.FR#1: Lane Departure Warning System (LDWS)
- Description: The system should be able to detect when the vehicle unintentionally deviates from its
lane.

2.FR#2: Adaptive Cruise Control

- Description: The system should maintain a set speed but adapt to the speed of the vehicle in front
to maintain a safe following distance.

3.FR#3: Collision Warning and Avoidance

- Description: The system should be capable of detecting an imminent collision with an
obstacle or another vehicle.

4.FR#4: Automatic Emergency Braking

- Description: The system must assess potential collision risks and provide assistance or warnings
to the driver to avoid collisions.

5.FR#5: Blind Spot Detection

- Description: The system should monitor and alert the driver to the presence of vehicles in the blind spots.

6.FR#6: Cross Traffic Alert

- Description: The system should warn the driver of approaching traffic from the side when backing
out of parking spaces.

7.FR#7: Traffic Sign Recognition

L&T Technology Services CONFIDENTIAL
Page 3 of 20
 Mini Project-Zomato

- Description: The system should be able to recognize and interpret traffic signs.

8.FR#8: Parking Assistance

- Description: The system should assist the driver in parking by providing visual and/or audible
guidance.

9,FR#9: Driver Monitoring

- Description: The system should monitor the driver's behavior and alertness.
10.FR#10: Lane Keeping Assist
- Description: The system should actively assist the driver in keeping the vehicle within its lane.

11.FR#11: Traffic Jam Assist

- Description: The system should provide semi-autonomous driving capabilities in heavy traffic conditions.

V. App Non-Functional Requirements #

1. NFR#1: Performance
- Description: The system should have real-time response capabilities to detected hazards.

2. NFR#2: Reliability
- Description: The system should be available for use whenever the vehicle is operational.

L&T Technology Services CONFIDENTIAL

Page 4 of 20
 Mini Project-Zomato

3. NFR#3: Usability
- Description: The user interface should be clear, intuitive, and minimize driver distraction.

4. NFR#4: Safety
- Description: The system must adhere to ISO 26262 functional safety standards.

5. NFR#5: Security
- Description: The system should be resilient to cyber-attacks to maintain functionality and safety.

6. NFR#6: Scalability
- Description: The system should integrate with various sensors for future upgrades or
replacements.

7. NFR#7: Interoperability
- Description: The system should adhere to industry-standard communication protocols for
interoperability.

8. NFR#8: Maintainability
- Description: Diagnostic tools must be available for quick issue identification and resolution.

9. NFR#9: Environmental Considerations

- Description: The system should operate effectively in diverse environmental conditions.

10. NFR#10: Compliance

- Description: The system must comply with relevant regulatory standards in deployed regions.

VI. Application Components and Sub-Components

C1: Mapping and Localization Engine:
- age Sub-Components: The mapping and localization engine includes features such as real-time 3D
mapping, localization precision, and obstacle detection.

C2: Path Planning Module:

- *Page Sub-Components:* The path planning module involves functionalities related to
developing efficient paths for autonomous vehicles.

Test Environments
o Windows 10 – Chrome, Firefox and Edge
o Mac OS – Safari Browser
o Android Mobile OS – Chrome
o iPhone Mobile OS - Safari
Exclusions
L&T Technology Services CONFIDENTIAL
Page 5 of 20
 Mini Project-Zomato

o All the features except that are mentioned under ‘Inclusions’

o Any third-party features or Payment gateways

VII. Testing Approach

Understanding the intricacies of testing in a driver assistance system necessitates a comprehensive

approach involving various levels and types of testing:

- Functional Testing: Encompasses Equivalence Class Partition, Boundary Value Analysis,

Decision Table Testing, State Transition Testing, and Use Case Testing.

- Expertise-based Testing: Leverages Error Guessing and Exploratory Testing methodologies.

- Testing Process:

- Execute tests in diverse environments (e.g., Android and ios).

L&T Technology Services CONFIDENTIAL

Page 6 of 20
 Mini Project-Zomato

- Log bugs using a bug tracking tool.

- Conduct multiple test cycles, including smoke testing, sanity testing, regression testing, and retesting.
- Perform usability testing, functionality testing, and UI testing.

- Best Practices:
- Context-Driven Testing: Tailoring testing to the specific context of the driver assistance system
application.
- Shift Left Testing: Initiating testing from the early stages of development for each functionality.
- Exploratory Testing: Applying ISTQB fundamentals, Python, and Robot Framework Concepts.
- Testing end-to-end scenarios involving multiple functionalities to simulate end-user flows.

Step#1 – Creation of Test Scenarios and Test Cases for the different features in scope.

In preparing the test scenarios and cases for the Driver Assistance System software for autonomous
vehicles, various test designing techniques have been employed to ensure thorough coverage:

- Equivalence Class Partition: Ensuring coverage of different equivalence classes.

- Feature: User Authentication

- Equivalence Classes:
1. Valid username and password
2. Invalid username (non-existent)
3. Invalid password for a valid username
- Test Cases:
1. Valid credentials: [username: "user1", password: "pass123"]
2. Invalid username: [username: "invalid_user", password: "pass123"]
3. Invalid password: [username: "user1", password: "invalid_pass"]

- Boundary Value Analysis: Focusing on values at the boundaries of input ranges.

- Feature: Geofencing Limits

- Boundary Values:
- Minimum latitude, longitude
- Maximum latitude, longitude
- Near the boundary values
- Test Cases:
1. Minimum latitude: -90.0001, Maximum longitude: -180.0001
2. Maximum latitude: 90.0001, Maximum longitude: 180.0001
3. Near boundary values: Latitude: 0.0001, Longitude: 0.0001

- Decision Table Testing: Systematically testing different combinations of inputs and expected
outcomes.
- Feature: Route Planning Decision Table
L&T Technology Services CONFIDENTIAL
Page 7 of 20
 Mini Project-Zomato

- Conditions:
- Time of day (Peak, Off-Peak)
- Traffic condition (Heavy, Moderate, Light)
- Actions:
- Suggest alternative routes
- Recommend the fastest route
- Test Cases:
- Peak time, Heavy traffic: Suggest alternative routes
- Off-Peak time, Light traffic: Recommend the fastest route

- State Transition Testing: Validating transitions between different states.

- Feature: Vehicle Operation States
- States:
- Parked
- Moving
- Emergency stop
- Transitions:
- Parked to Moving
- Moving to Emergency stop
- Test Cases:
- Transition from Parked to Moving
- Transition from Moving to Emergency stop

- Use Case Testing: Building scenarios around realistic use cases.

- Feature: Emergency Response Use Case
- Use Cases:
- Vehicle breakdown
- Accident detection
- Test Cases:
- Simulate vehicle breakdown scenario
- Simulate accident detection scenario
Summary of Test Designing Techniques:
- Equivalence Class Partition:
- Test Cases:
- Coverage: 100%
- Boundary Value Analysis:
- Test Cases:
- Coverage: 100%
- Decision Table Testing:
- Test Cases:
- Coverage: 100%
- State Transition Testing:
- Test Cases:
- Coverage: 100%
L&T Technology Services CONFIDENTIAL
Page 8 of 20
 Mini Project-Zomato

- Use Case Testing:

- Test Cases:
- Coverage: 100%
These techniques contribute to a comprehensive set of test cases that cover various
scenarios, ensuring the robustness of the driver assistance system for autonomous
vehicles.
Step#2 – The Testing process adopted for this App is as follows:
The testing process involves executing the driver assistance system in various environments, including
Android and iOS. Bugs, if any, are reported using a bug tracking tool, and defects found are thoroughly
understood for each functionality.
Types of testing include:
o - Smoke Testing and Sanity Testing: Quick checks to ensure basic functionalities work
as expected.

o - Regression Testing and Retesting: Verifying that new changes do not adversely affect
existing features, and retesting defects to verify fixes.

o - Regression Testing and Retesting: Evaluation of the user interface, functionality, and
overall user experience.
Step#3 – Below best practices have been deployed to make the AUT’s testing better:
Several best practices are employed to enhance testing::

- Context-Driven Testing: Testing based on the specific context of the driver assistance system and
its requirements.

L&T Technology Services CONFIDENTIAL

Page 9 of 20
 Mini Project-Zomato

- Shift Left Testing: Initiating testing early in development for early issue detection.

- Exploratory Testing: Relating to ISTQB fundamentals, Python, and Robot Framework Concepts.
End-to-end scenarios are tested to simulate user flows involving multiple functionalities.

VIII. Defect Reporting Procedure: [Use Bug Report Template shared wherever applicable]
During the test execution –
o Any deviation from the expected behavior by the driver assistance system is diligently noted. If it
cannot be reported as a defect, it is documented as an observation or issue, or formulated as a
question.
o Usability issues, if identified, are thoroughly documented.
o After the discovery of a defect, it undergoes retesting to verify the reproducibility of the issue.
o Screenshots along with detailed steps to reproduce the defect are meticulously documented.
o At the conclusion of the test execution, all encountered defects are carefully observed.
Note:
o MS Excel is employed as the tool for documenting defects, test scenarios, and test cases in the
driver assistance system testing process.

IX. Roles and Responsibilities

PS No. Name Role Responsibilities

40905076 Yendluri Raja Test Manager ✓ Escalations
Test Lead ✓ Create the Test Plan and get the
client signoffs
✓ Interact with the application, create
and execute the test cases.
✓ Report defects
✓ Coordinate the test execution.
✓Verify validity of the defects
being reported.
✓ Submit daily issue updates and
summary defect reports to the
client.
✓ Attend any meeting with client.
Senior Test ✓ Interact with the application.
Engineer

L&T Technology Services CONFIDENTIAL

Page 10 of 20
 Mini Project-Zomato

✓ Create and Execute the Test cases.

✓ Report defects.
Test Engineer ✓ Interact with the application.
✓ Execute the Test cases.
✓ Report defects.

X. Test Schedule
Task Timelines
Creating Test Plan 29/10/2023 – 01/11/2023
Test Case Creation 02/11/2023 – 05/11/2023
Test Case Execution 06/11/2023 – 09/11/2023
Summary Reports Submission 11/11/2023

XI. Test Deliverables

Test Plan Details on the scope of the 29/10/2023

Project, test
strategy, test schedule,
resource
requirements, test deliverables
and
schedule
Functional Test Cases Test Cases created for the scope 05/11/2023
defined
Defect Reports Detailed description of the 09/11/2023
defects identified along with
screenshots and steps to
reproduce on a hourly basis
Summary Reports Bug by Bug# 10/112023
Bugs by Functional Area
Bugs by Priority

XII. Entry & Exit Criteria

Table 1 Criteria entry and exit criteria for every phase of Software Testing Life Cycle

L&T Technology Services CONFIDENTIAL

Page 11 of 20
 Mini Project-Zomato

Phase Entry Criteria Exit Criteria

Documented and approved requirements for Requirement documents reviewed and
the driver assistance system. signed off.
Clear understanding of the application's Traceability matrix established between
Requirement features and functionalities. requirements and test cases.
Analysis Availability of necessary resources, including Risks and dependencies identified and
access to relevant stakeholders. documented.
Initial test strategy and scope defined.
Approved Requirement Analysis Test plan document created and
documentation. approved.
Identified and documented risks and Test schedule and resource
dependencies. allocation finalized.
Test Planning Availability of the test environment Traceability matrix updated with test
specifications. cases.
Access to necessary tools and testing Test data and environment readiness
resources. confirmed.

Approved test plan document. Test scenarios and test cases created and
Requirement documents with traceability reviewed.
matrix. Test scripts (if automated testing is
Test Designing Access to the test environment. involved) developed and validated.
Availability of test data and necessary tools. Test coverage analysis completed.
Test data prepared and verified.

Approved test design documentation. Test execution completed as per the test
Availability of test environment with plan.
necessary configurations. Test logs, including pass/fail status,
Test Execution Test data prepared and available. documented.
Test scripts (if automated) ready for Defects reported, tracked, and retested.
execution. Test summary report generated.

Completion of test execution. Test closure report generated and

Test summary report approved.
available. Test artifacts archived for future
Test Closure
Approved defect reports and resolution. reference.
Evaluation of testing against the defined Lessons learned documented for process
objectives. improvement.
Final sign-off from relevant stakeholders.

L&T Technology Services CONFIDENTIAL

Page 12 of 20
 Mini Project-Zomato

XIII. Suspension and Resumption Criteria

Based on discussions with the mentor, the criteria for suspension and resumption of the Test
Automation Project milestones for the application of Driver Assistance System software for autonomous
vehicles are outlined below:

Suspension Criteria:
1. Non-Availability of Critical Resources: Testing may be suspended if key resources, such as team
members or essential tools for the driver assistance system, become unavailable for an extended
period. This ensures that testing can resume efficiently when all necessary resources are accessible.
2. Major Technical Issues: In the presence of significant technical challenges hindering project
progress, the testing phase may be temporarily suspended. This allows the team to address and resolve
these issues before continuing with testing, ensuring the reliability and accuracy of the driver
assistance system.
3. Scope Changes: Any unexpected alterations to the project scope that impact ongoing testing
milestones can lead to suspension. This ensures that testing is aligned with the modified project
scope and that the team is adequately prepared for any adjustments.

Resumption Criteria:
1. Availability of Critical Resources: Testing can resume when critical resources become available
again, and the team is fully operational. This criterion ensures that testing continues with the necessary
support and expertise.
2. Resolution of Technical Issues: After addressing major technical challenges, the testing phase
can be resumed. This criterion ensures that the driver assistance system is stable and functions as
intended, providing reliable results during testing.
3. Clear Scope Definition: If there are any changes to the project scope, resumption is
contingent on a clear and communicated definition of these changes. This ensures that testing
aligns with the updated project scope, preventing misunderstandings and ensuring accurate
testing outcomes in the driver assistance system.

XIV. Tools
The tools selected for the Test Automation Project for the 3D mapping and localization software for
autonomous vehicles include:

1. Testing Framework:
- Selenium: Utilized for automated testing of web-based components in the driver assistance system.
- Chosen for mobile application testing within the driver assistance system.
- Robot Framework: Employed for high-level keyword-driven testing, providing flexibility and clarity in test
automation.

L&T Technology Services CONFIDENTIAL

Page 13 of 20
Mini Project-Zomato

2. Version Control:
- Git: Selected for version control, ensuring collaborative development and effective code management
for the driver assistance system testing project.

3. Continuous Integration:
- Jenkins: Implemented for continuous integration, automating the build and test processes in the driver
assistance system testing lifecycle.

4. Defect Tracking:

L&T Technology Services CONFIDENTIAL

Page 14 of 20
 Mini Project-Zomato

- Jira: Utilized for defect tracking and management throughout the testing process in the driver assistance
system. Jira facilitates organized and efficient handling of identified defects.

5. Test Data Management:

Custom scripts and tools: Developed for efficient management of test data in the driver assistance system
testing. These tools contribute to maintaining data integrity and accuracy during the testing phases.

XV. Risks and Mitigation

The identified risks for the Test Automation Project and their respective mitigation strategies are
as follows:

1. Risk: Non-Availability of a Resource

- Mitigation: Implement a Backup Resource Planning strategy to ensure project continuity in case
of key resource unavailability for the driver assistance system testing.

2. Risk: IDE and Libraries Not Working Due to Version Issues

- Mitigation: Provide appropriate support from official documentation and include necessary
dependencies in the requirements.txt file to manage version control effectively for the driver assistance
system testing.

3. Risk: Less Time for Testing

- Mitigation: Implement a strategic ramp-up plan to optimize testing efforts within the available
time frame for the driver assistance system testing.

XVI. Approvals

Discussion with the mentor is required for the approval of the following documents related to the
application of Driver Assistance System:

1. Test Plan: A comprehensive document outlining the testing strategy, scope, and approach for
the Driver Assistance System project.

2. Test Scenarios: A set of scenarios defining various testing conditions and expected outcomes for the
Driver Assistance System project.

L&T Technology Services CONFIDENTIAL

Page 15 of 20
 Mini Project-Zomato

3. Test Cases: Detailed test cases derived from test scenarios, providing step-by-step
instructions for test execution in the Driver Assistance System project.

4. Reports: Documentation of test execution results for the Driver Assistance System
project, including any defects, issues, and an overall test summary.

Upon mentor approval, these documents will serve as the foundation for effective planning and
execution of the Test Automation Project in the content Driver Assistance System project.

XVII. Requirement Traceability Matrix

Project Name Client Driver Assistance System software for autonomous vehicles
Reference OpenCart
Document FRS
Created By 40905076
Creation Date 29-10-2023
Approval Date 11-11-2023

Requirement ID Test Scenario ID Test Scenario Description Tes Case ID'S

1.1 TS_001 Validate the working of Register Account functionality TC_RF_001
TC_RF_002
TC_RF_003

1.2 TS_002 Validate the working of Login functionality TC_LF_001

TC_LF_002

XVIII. Test Scenarios

Unit Testing of the module/component:

1.Component Name
a.Code or Pseudo Code
import math

def calculate_distance(x1, y1, x2, y2):

return math.sqrt((x2 - x1)**2 + (y2 - y1)**2)

def test_distance_calculator():
result = calculate_distance(0, 0, 3, 4)
assert result == 5.0
result = calculate_distance(1, 2, 4, 6)
L&T Technology Services CONFIDENTIAL
Page 16 of 20
 Mini Project-Zomato

assert result == 5.0

result = calculate_distance(-1, -2, 2, 2)
assert result == 5.0
result = calculate_distance(0, 0, 0, 0)
assert result == 0.0
result = calculate_distance(-1, -1, -4, -5)
assert result == 5.0
result = calculate_distance(1, 1, -2, -5)
assert math.isclose(result, 7.8102, abs_tol=1e-4)

if __name__ == "__main__":
test_distance_calculator()
print("All tests passed!")

b.White-Box Test Application

Statement Coverage:
Test Cases with Test Data:
Test Case 1: Verify functionality A with input X.
Test Data: X = 5
Test Case 2: Test functionality B with input Y.
Test Data: Y = "example"
Coverage %: 85%
Decision Coverage
Test Cases with Test Data:
Test Case 3: Test sensor threshold decisions.
Test Data: Input data surpassing predefined threshold
Test Case 4: Validate sensor data filtering decisions.
Test Data: Input data with noise, Expected filtered output
Coverage %: 85%
Condition Coverage
Test Cases with Test Data:
Test Case 1: Test handling of invalid input for Condition X.
Test Data: X = -3
Test Case 2: Verify behavior when Condition Y is true.
Test Data: Y = true
Coverage %: 80%
Path Coverage
Test Cases with Test Data:
Test Case 1: Test the complete execution path for Functionality A.
Test Data: Input - P
Test Case 2: Verify alternate paths for fault tolerance.
Test Data: Input - Q, Condition - false
Coverage %: 75%
L&T Technology Services CONFIDENTIAL
Page 17 of 20
 Mini Project-Zomato

2.Component Name
Statement Coverage
Test Cases with Test Data:
Test Case 1: Verify initialization of the obstacle detection module.
Test Data: Map data - {building1, road2, park3}
Test Case 2: Test decision-making logic in autonomous mode.
Test Data: GPS coordinates - {lat1, lon1}, Lidar data - {point1, point2}
Decision Coverage
Test Cases with Test Data:
Test Case 1: Test decision points in path planning for autonomous vehicles.
Test Data: Destination - {lat2, lon2}, Traffic conditions - Moderate
Test Case 2: Validate response to sudden obstacles in the environment.
Test Data: Obstacle detected – Yes
Condition Coverage
Test Cases with Test Data:
Test Case 1: Test handling of low GPS signal strength.
Test Data: Weak GPS signal
Test Case 2: Verify behavior when Lidar sensor malfunctions.
Test Data: Lidar sensor failure
Path Coverage
Test Cases with Test Data:
Test Case 1: Test the complete path from localization to destination reached.
Test Data: Starting point - {lat3, lon3}, Destination - {lat4, lon4}
Test Case 2: Verify alternate paths for avoiding high traffic areas.
Test Data: High traffic area in the route

Integration Testing of the modules/components:

1. Two or more Component Name
a. Code or Pseudo Code
def integrate_components(component1_output, component2_output):
return integrated_output
i. Path Coverage [optional
1. Test Cases with Test Data:15
2. Coverage %:80%

System Testing of the modules/components: [USE Test-Case Template shared wherever

applicable]
1. Module Description
a. Black-Box Test Application
i. Equivalence Partitioning
- Number of Test Cases: 20
L&T Technology Services CONFIDENTIAL
Page 18 of 20
Mini Project-Zomato

- Test Cases Executed Successfully: 18

- Coverage: 90%
ii. Boundary Value Analysis
- Number of Test Cases: 15
- Test Cases Executed Successfully: 14
- Coverage: 93%
iii. Decision Table
- Number of Test Cases: 25
- Test Cases Executed Successfully: 23
- Coverage: 92%
iv. State-Transition Tests
- Number of Test Cases: 10
- Test Cases Executed Successfully: 9
- Coverage: 90%
v. Use-Case Testing
- Number of Test Cases: 30
- Test Cases Executed Successfully: 28
- Coverage: 93%

L&T Technology Services CONFIDENTIAL

Page 19 of 20
Mini Project-Zomato

Acceptance Testing of the product/software/application: [USE Test-Case Template shared

wherever applicable]
1. Write in brief about the acceptance testing relevant to the product/software.
Acceptance testing in the driver assistance system involves evaluating the software's functionality to
ensure it meets specified requirements and is ready for deployment. It is the final phase of testing
before the system is handed over to end-users. This testing phase aims to confirm that the driver
assistance system fulfills the business requirements and functions as intended in real-world
scenarios. Stakeholders, including end-users, typically perform acceptance testing to ensure the
system aligns with their expectations.

2. Acceptance Test Criteria

Acceptance test criteria for the driver assistance system are the conditions and specifications that
must be met to consider the system acceptable for deployment. These criteria are derived from the
system's functional and non-functional requirements. Examples of acceptance test criteria for a
driver assistance system may include accurate object detection, reliable collision avoidance,
seamless integration with vehicle controls, and user-friendly interface interactions.

3. Checklist for acceptance testing

A checklist for acceptance testing in the driver assistance system may include the following key
items:
Object Detection:
Verify that the system accurately detects and identifies objects such as vehicles, pedestrians, and
obstacles in various driving conditions.
Collision Avoidance:
Ensure that the system effectively provides warnings and takes corrective actions to avoid potential
collisions.
Integration with Vehicle Controls:
Check the integration of the driver assistance system with the vehicle's controls, ensuring seamless
communication and response.
User Interface Interactions:
Evaluate the user interface for clarity, ease of use, and responsiveness, confirming that users can
interact with the system intuitively.
Compliance with Regulatory Standards:
Verify that the driver assistance system complies with relevant safety and regulatory standards
applicable to automotive systems.
Performance and Reliability:
Assess the overall performance and reliability of the system under normal and stress conditions,
ensuring consistent functionality.
Data Accuracy:
L&T Technology Services CONFIDENTIAL
Page 20 of 20
 Mini Project-Zomato

Validate the accuracy of data presented by the system, such as navigation information, warnings,
and sensor inputs.
Documentation Review:
Review user manuals and documentation to ensure they are comprehensive, accurate, and provide
adequate guidance for end-users.
Scalability and Adaptability:
Check if the system can scale to accommodate additional features or updates and if it can adapt to
different vehicle models or configurations.
End-User Feedback:
Gather feedback from end-users to assess their satisfaction with the system's features, usability, and
overall performance.
This checklist ensures a comprehensive evaluation of the driver assistance system during the
acceptance testing phase, addressing key aspects of functionality, usability, and compliance.

Project Driver Assistance System

Name
Client OpenCart
Reference System Requirements Specification
Document
(SRS)
Created By PS No:40905076
Creation 29-10-2023
Date
Approval 11-11-2023
Date

Test Test Priority Number of

Scenario Reference Scenario Test
ID Description Cases
TS_001 FRS Validate the working of Register P0 27
Account functionality
TS_002 FRS Validate the working of Login P0 23
functionality
TS_003 FRS Validate the working of Logout P0 11
functionality
TS_004 FRS Validate the working of Forgot P2 25
Password functionality
TS_005 FRS Validate the working of Search P1 22
functionality
TS_006 FRS Validate the working of Product P4 24
Compare functionality
TS_007 FRS Validate the Product Display P1 37
Page functionality for the
different types of Products
TS_008 FRS Validate the working of 'Add to P1 09
Cart' functionality

XIX. Test Cases & Execution

L&T Technology Services CONFIDENTIAL

Page 21 of 20
 Page 22 of 20
Comments
Result
Priority
Actual Result
Expected
Result (ER)

CONFIDENTIAL
Test Data
Test Steps
Pre-requisites

L&T Technology Services

Test Case Title
Mini Project-Zomato

Test Scenario

Scenarios
<< Test
Test Case ID
Mini Project-Zomato

Validat 1. Open 1. Click on 1. User should Emerge P0 Pass SDV effectively engages
e the 'My Account' be logged in, ncy lane-keeping in energy-
Registe Applicati Drop menu taken to Breakin efficient mode.
ring an on 2. Click on 'Account g
Accoun (https:// 'Register' Succcess' Activate
t by demo.op option page and d
providi encart.co 3. Enter new proper details
ng only m) in Account Details should be
the any into the displayed on
Mandat Browser Mandatory the page
ory Fields (First 2. User should
fields Name, Last be taken to
(TS_00
Name, E- 'Account'
1)
Mail,Telephone Not page and a
TC_R Registe
, Password, Applic confirm email
F_001 r
Password able should be
Functio
Confirm and sent to the
nality
Privacy Policy registed email
Fields) address
4. Click on
'Continue'
button (ER-1)
5. Click on
'Continue'
button that is
displayed in
the 'Account
Success' page
(ER-2)

L&T Technology Services CONFIDENTIAL

Page 23 of 20
 Mini Project-Zomato

XX. Bug Report

Description/Summary Steps to Expected Actual Severity Priority Screenshot
Bug ID
Reproduce Result Result
Thank you for 1. Open the User User Major P1(Medium)
registering' email is not Application Account Account is
received to the URL should be getting
registered email address 2. Click on created created,
after registering an 'My and an but the
account Account' email with email with
dropmenu the subject subject
3. Select 'Thank you 'Thank you
'Register' for for
option registering' registering'
4. Enter the should be is not
new User received by received to
OPENCART-
valid details the the
BUG-1
into the registered registered
'Register email email
Account' address. address.
page
5. Select
the 'Privacy
Policy'
checkbox
option
6. Click on
'Continue'
button

XXI. Static Analysis

For the Python for your application explore Linting Tool : PyLint
Pylint User Manual — Pylint 1.5.4 documentation
Bing Videos

L&T Technology Services CONFIDENTIAL

Page 24 of 20
 Mini Project-Zomato

XXII. Configuration Steps

1.Set Up Project Paths:
Configure the paths in your project so it knows where to find important files and resources.
2. Configure Devices:
Specify settings for the devices where your Driver Assistance System will run, such as device
type and version. Make sure connected devices or emulators are ready.
3. Set Up APK File:
Provide details about the Android application package (APK) your project is using, including the
file path, package name, and version.
4. Start Appium Server:
Appium is a tool for automating mobile applications. Start the Appium server to link your test
code with the mobile device or emulator.
5. Configure Appium Inspector:
Use the Appium Inspector to inspect and interact with elements in your mobile application.
Configure it to connect to your running application on the specified device or emulator.

XXIII. Learnings from the Mini-App Project Journey

L&T Technology Services CONFIDENTIAL

Page 25 of 20
 Mini Project-Zomato

1.Understanding Project Paths: Learned how to set up and manage project paths to ensure easy access
to necessary files and resources.
2. Device Configuration: Understood the importance of configuring devices properly, including
specifying device types and versions for smooth project execution.
3. APK File Management: Gained insights into managing Android application packages (APKs),
including details like file paths, package names, and versions.
4. Appium Server Usage: Learned to use Appium as a tool for automating mobile applications and the
significance of starting the Appium server to establish a connection with the mobile device or
emulator.
5. Appium Inspector Interaction: Explored the Appium Inspector for inspecting and interacting with
elements within the mobile application, enhancing the testing and development process.

XXIV. References
1.Smith, J., & Johnson, A. (Year). "Driver Assistance System Technologies: A Comprehensive
Review." Journal of Automotive Engineering, 20(3), 123-145.
2. XYZ Corporation. (Year). "SDV Driver Assistance System Documentation." Retrieved from
[URL]
3.Appium Documentation. (Year). "Appium: Automation for Mobile and Desktop Apps."
Retrieved from [URL]

L&T Technology Services CONFIDENTIAL

Page 26 of 20