Figure. 1.
Roadside Assistance Application Activity Diagram
Fig. 2.
Use Case Diagram for Customer and Mechanic
Figure. 3.
Request Process through Smart Contract
Figure. 4.
Mechanic Verification through Blockchain
Table 1.
Test Phases for Roadside Assistance Application
| Test Phase | Description |
|---|---|
| Unit Testing | Validate individual components and functions of the service application, ensuring proper functionality of customer and mechanic modules. |
| Integration Testing | Verify interactions between application components, backend systems, and mobile platforms for seamless integration of customer requests and mechanic responses. |
| System Testing | Validate end-to-end scenarios of roadside assistance requests, including customer request processing, mechanic assignment, and status updates. |
| Acceptance Testing | Ensure the cross-platform application meets user requirements, including smooth interactions for customers and mechanics on various devices. |
Table 2.
Test Cases for Roadside Assistance Application
| Test Case ID | Description | Expected Result | Actual Result | Status |
|---|---|---|---|---|
| TC001 | Verify customer request processing. | Successful processing of the customer request with accurate details. | Acknowledgment received with correct service details. | Pass |
| TC002 | Test mechanic assignment and status updates. | Proper assignment and timely status updates for the assigned mechanic. | Mechanic assigned successfully, real-time updates observed. | Pass |
| TC003 | Test customer cancellation of a service request. | System cancels the request without assigning a mechanic. | Request canceled successfully before mechanic assignment. | Pass |
| TC004 | Validate mechanic response to a service request. | Mechanic acknowledges and accepts the service request promptly. | Mechanic accepted the request successfully. | Pass |
| TC005 | Verify notification system for both customers and mechanics. | Timely and accurate notifications for customers and mechanics. | Notifications received promptly on both ends. | Pass |
| TC006 | Validate payment processing for completed service. | Secure and accurate processing of payment for the completed service. | Payment processed successfully, and the transaction reflects the correct amount. | Pass |
Figure. 5.
Mechanic Markers on the User Application
Figure. 6.
Mechanic Information on the Map
Figure. 7.
Service Requests on the Mechanic Application