NaviAns
TS_015
Positive Test Case 1: Verify that "Search for Nearby Places" shows the correct categories of places.
Use Case: Ensure that when users press the right button to enter the "Nearby Places" menu, they see a list of categories such as petrol pump, restaurants, schools, shopping, etc.
Test Case Name: Nearby Places Categories Display Correctly
Test Description: This test case ensures that when users enter the "Nearby Places" menu, all the predefined categories such as petrol pump, restaurants, schools, and shopping options are displayed correctly.
Pre-condition: The user is in the voice search mode and presses the right button to enter "Nearby Places."
Steps:
Press the right button from the voice search page to enter the "Nearby Places" menu.
Check if the list of nearby places categories (e.g., petrol pump, restaurant, school, shopping, etc.) is displayed.
Expected Result:
The mobile screen should show the correct categories such as petrol pump, restaurant, school, shopping, and others.
The categories should be clickable, allowing the user to select one to continue.
Positive Test Case 2: Verify that the user can select a category and get relevant suggestions.
Use Case: Ensure that when a user selects a category (e.g., restaurant), a list of relevant suggestions appears.
Test Case Name: Selecting a Nearby Place Category Shows Relevant Suggestions
Test Description: This test case verifies that when a user selects a category from the "Nearby Places" list, the app displays a list of relevant places under that category.
Pre-condition: The user has accessed the "Nearby Places" menu and is viewing the list of categories.
Steps:
From the "Nearby Places" list, select a category such as "Restaurant."
Ensure that a list of restaurant suggestions (e.g., names of nearby restaurants) is displayed.
Expected Result:
A list of restaurants (or relevant suggestions based on the selected category) should be shown, with each suggestion clickable for further action.
Positive Test Case 3: Verify that the user can select a suggestion and navigate to the destination.
Use Case: Ensure that after selecting a nearby place suggestion, the user can press right to initiate navigation to the destination.
Test Case Name: Selecting a Suggestion Starts Navigation
Test Description: This test case ensures that when the user selects a nearby place suggestion and presses right, the navigation to the selected destination starts.
Pre-condition: The user has selected a nearby place suggestion from the "Nearby Places" category.
Steps:
From the list of suggestions (e.g., restaurants), select one suggestion.
Press the right button to confirm the selection.
Ensure that the navigation starts, with a message saying "Navigation Started."
Expected Result:
The mobile app should show the message "Navigation Started."
Google Maps should open in the background, and turn-by-turn navigation should be initiated on both the mobile and IVI screens.
Negative Test Case 1: Verify that no suggestions are shown if no places are available in the selected category.
Use Case: Ensure that if there are no nearby places available in a selected category, the system displays an appropriate message or empty list.
Test Case Name: No Suggestions for Selected Category
Test Description: This test case verifies that if no places are available in the selected category (e.g., "Restaurants"), the app shows a message like "No results found" or simply an empty list.
Pre-condition: The user has accessed the "Nearby Places" menu and selected a category (e.g., restaurant) where no results are available.
Steps:
From the "Nearby Places" list, select a category (e.g., "Restaurant") that has no nearby places available.
Observe if the system displays an empty list or a "No results found" message.
Expected Result:
The system should either display an empty list or show a message like "No results found" or "No places available in this category."
Negative Test Case 2: Verify that the "Nearby Places" menu does not show any categories if the location is disabled.
Use Case: Ensure that if the user disables location services, the "Nearby Places" menu does not show any categories.
Test Case Name: Nearby Places Categories Not Displayed When Location is Disabled
Test Description: This test case verifies that if the location services are turned off, the "Nearby Places" menu does not show any categories or suggestions.
Pre-condition: The location services are disabled.
Steps:
Disable the location services on the mobile device.
Open the mobile app and go to the Navigation menu.
Select "Nearby Places."
Observe if the categories are displayed.
Expected Result:
No categories should be displayed in the "Nearby Places" menu if location services are disabled.
The app may display a message like "Enable location services to view nearby places."
TS_016
Positive Test Case 1: Verify that the user can navigate to the Favorites page from Voice Search.
Use Case: Ensure that the user can navigate to the Favorites page by selecting the correct option from the Voice Search menu.
Test Case Name: Navigate to Favorites Page from Voice Search
Test Description: This test case ensures that pressing the right button from Voice Search correctly takes the user to the Favorites page.
Pre-condition: The user is on the Voice Search page.
Steps:
Press the right button from the Voice Search page to enter the Favorites page.
Observe whether the Favorites list is displayed correctly on the screen.
Expected Result:
The application should navigate to the Favorites page, displaying a list of the user's favorite places.
Positive Test Case 2: Verify that the user can select a favorite place from the list.
Use Case: Ensure that when the user selects a place from the Favorites list, it is highlighted or marked as selected.
Test Case Name: Select a Favorite Place from the List
Test Description: This test case ensures that when the user selects a place from the list of favorites, the selected place is visually marked or highlighted.
Pre-condition: The user is on the Favorites page with a list of available favorite places.
Steps:
From the Favorites page, scroll through the list of favorite places.
Select any place from the list using the right button on the handle switch bar or touchscreen.
Verify that the selected place is highlighted or marked as selected.
Expected Result:
The selected favorite place should be visually marked as selected (highlighted) on the mobile screen.
Positive Test Case 3: Verify that the user can confirm the selected favorite place and start navigation.
Use Case: Ensure that when the user confirms the selected favorite place, the navigation begins.
Test Case Name: Confirm Selected Favorite Place and Start Navigation
Test Description: This test case verifies that after selecting a favorite place, the user can confirm the place, and the navigation will begin, showing turn-by-turn directions.
Pre-condition: The user has selected a place from the Favorites list.
Steps:
Select a favorite place from the Favorites page.
Press the right button to confirm the selected destination.
Verify that the mobile application shows the message "Navigation Started" and turn-by-turn navigation starts.
Verify that Google Maps is opened in the background with the turn-by-turn navigation instructions displayed.
Ensure that the IVI screen shows turn-by-turn navigation indicators.
Expected Result:
The mobile app should show a message saying "Navigation Started".
Google Maps should be opened in the background and the navigation should start on both the mobile and IVI screens.
Negative Test Case 1: Verify that the user cannot confirm a favorite place without selecting one.
Use Case: Ensure that the Confirm button does not work unless a favorite place is selected from the list.
Test Case Name: No Confirmation without Selection
Test Description: This test case ensures that the user cannot confirm navigation without selecting a favorite place from the list.
Pre-condition: The user is on the Favorites page, but no place has been selected.
Steps:
Open the Favorites page.
Do not select any place from the list.
Attempt to press the right button to confirm a place.
Expected Result:
The system should prevent confirmation without selecting a favorite place and either remain on the Favorites screen or show a prompt saying "Please select a place first."
Negative Test Case 2: Verify that no favorite places are shown if the user has no favorites added.
Use Case: Ensure that the Favorites page is empty or shows a message if no favorite places have been added.
Test Case Name: Empty Favorites List
Test Description: This test case ensures that if the user has not added any favorites, the Favorites page should either be empty or show a "No Favorites Added" message.
Pre-condition: The user has not added any favorite places.
Steps:
Open the Favorites page.
Ensure there are no favorite places added.
Observe the behavior of the app.
Expected Result:
The Favorites page should either be empty or display a message such as "No Favorites Added."
TC_017
Positive Test Case 1: Verify that the user can add a new place to the favorites list.
Use Case: Ensure that the user can manually add a new place to their list of favorites from the mobile application.
Test Case Name: Add a New Place to Favorites
Test Description: This test case ensures that the user can manually add a place to their favorites list from the application interface.
Pre-condition: The user is on the Favorites page or any screen where they can access the "Add to Favorites" option.
Steps:
Navigate to a place (via search, map, etc.).
On the mobile screen, select the Add to Favorites option.
Confirm that the place is added to the Favorites list.
Expected Result:
The selected place should be added to the Favorites list and be visible in the list.
Positive Test Case 2: Verify that the user can remove a place from the favorites list.
Use Case: Ensure that the user can manually remove a place from their list of favorites.
Test Case Name: Remove a Place from Favorites
Test Description: This test case ensures that the user can remove an unwanted place from the favorites list using the mobile application.
Pre-condition: The user has at least one place added to the Favorites list.
Steps:
Open the Favorites page.
Select a favorite place.
Choose the Remove from Favorites option.
Confirm that the place is removed from the list.
Expected Result:
The selected place should be removed from the Favorites list, and it should no longer appear on the screen.
Positive Test Case 3: Verify that the user can select a favorite place and navigate to it.
Use Case: Ensure that the user can select a favorite place from the list and navigate to it.
Test Case Name: Select and Navigate to a Favorite Place
Test Description: This test case ensures that the user can select a favorite place from the list and initiate navigation.
Pre-condition: The user has added places to the Favorites list.
Steps:
Open the Favorites page.
Select a place from the list of favorites.
Press the right button to confirm the selection.
Confirm that navigation starts for the selected favorite place.
Expected Result:
The selected favorite place should trigger navigation, and turn-by-turn navigation should begin on both the mobile and IVI screens.
Negative Test Case 1: Verify that the user cannot add the same place to favorites more than once.
Use Case: Ensure that the system prevents the same place from being added multiple times to the Favorites list.
Test Case Name: Prevent Duplicate Favorite Place
Test Description: This test case ensures that the user cannot add the same place to the Favorites list more than once.
Pre-condition: The user has already added a place to the Favorites list.
Steps:
Go to a place already in the Favorites list.
Attempt to add the place to Favorites again.
Expected Result:
The system should prevent adding the same place again and either show a message or ignore the request.
Negative Test Case 2: Verify that the "Remove from Favorites" option is unavailable if the place is not in the list.
Use Case: Ensure that the user cannot remove a place from favorites if it is not already in the list.
Test Case Name: Remove from Favorites When Not Present
Test Description: This test case ensures that if a place is not in the Favorites list, the option to remove it is not available.
Pre-condition: The place is not in the Favorites list.
Steps:
Open the Favorites page.
Check if the option to Remove from Favorites is enabled for a place not in the list.
Expected Result:
The Remove from Favorites option should be disabled or not available for places that are not in the Favorites list.
TS_018
Positive Test Case 1: Verify that the system re-routes when the user deviates from the path.
Use Case: Ensure that the system automatically re-routes the user when they deviate from the intended path during navigation.
Test Case Name: Re-route After Deviation from Path
Test Description: This test case ensures that when the user deviates from the recommended navigation path, the system automatically re-routes the navigation to guide the user back on track.
Pre-condition: The user is actively navigating with turn-by-turn directions.
Steps:
Start navigation with the correct path.
Deviate from the path (take an alternate road, go off the route).
Observe the system's response to the deviation.
Verify that the system re-routes and updates the path to bring the user back on track.
Expected Result:
The system should automatically detect the deviation and re-route the navigation.
The system should provide new directions to get the user back on track.
Positive Test Case 2: Verify that the re-routing continues with voice prompts and visual updates.
Use Case: Ensure that after the re-route, the system continues providing both voice and visual guidance for the new path.
Test Case Name: Re-routing with Voice and Visual Prompts
Test Description: This test case ensures that after the re-routing, the system continues to provide accurate turn-by-turn directions via both voice prompts and visual cues on the screen.
Pre-condition: The user has deviated from the path and the system has initiated re-routing.
Steps:
Start navigation.
Deviate from the path and allow the system to re-route.
Verify that the system provides updated visual directions on the map.
Confirm that the system issues updated voice prompts reflecting the new path.
Expected Result:
The system should provide updated turn-by-turn directions, both visually on the map and audibly through voice prompts.
Positive Test Case 3: Verify that re-routing updates the ETA and arrival time correctly.
Use Case: Ensure that the Estimated Time of Arrival (ETA) is updated correctly after re-routing.
Test Case Name: Re-routing Updates ETA
Test Description: This test case ensures that when the user deviates from the path and re-routing occurs, the ETA is recalculated based on the new route.
Pre-condition: The user is actively navigating with a set ETA.
Steps:
Start navigation and note the ETA.
Deviate from the path (take an alternative route).
Allow the system to re-route.
Check the updated ETA after the system re-routes the navigation.
Expected Result:
The system should update the ETA to reflect the new route and provide an accurate arrival time.
Negative Test Case 1: Verify that the system does not continue on the old path after re-routing.
Use Case: Ensure that after the user deviates from the original path, the system does not continue providing instructions for the previous route.
Test Case Name: Avoid Old Path After Deviation
Test Description: This test case ensures that once the user deviates from the path, the system does not continue giving directions based on the old, incorrect path.
Pre-condition: The user is actively navigating.
Steps:
Start navigation with the correct path.
Deviate from the path (take an alternative route).
Observe the system’s behavior after the deviation.
Verify that the system stops providing instructions for the original path.
Expected Result:
The system should stop directing the user on the old path and should immediately begin giving instructions based on the new re-routed path.
Negative Test Case 2: Verify that re-routing is not triggered if the user makes a small, temporary deviation (such as moving off the road for a short time).
Use Case: Ensure that minor deviations (e.g., slight changes in the road, temporary stops) do not trigger re-routing unnecessarily.
Test Case Name: Minor Deviation Does Not Trigger Re-routing
Test Description: This test case ensures that the system does not trigger a re-route if the deviation is minor and does not affect the overall navigation path.
Pre-condition: The user is actively navigating and deviates from the path slightly (e.g., stops at a red light or makes a small detour).
Steps:
Start navigation.
Deviate slightly from the path (e.g., by stopping or taking a small detour).
Observe whether the system triggers a re-route.
Expected Result:
The system should not trigger a re-route if the deviation is minor and does not significantly affect the overall route.
Negative Test Case 3: Verify that the system does not re-route to a road that is blocked or closed.
Use Case: Ensure that the system does not re-route the user to an unavailable or closed road.
Test Case Name: Avoid Re-routing to Blocked or Closed Roads
Test Description: This test case ensures that when the system re-routes after a deviation, it takes into account road closures or restrictions and avoids suggesting blocked roads.
Pre-condition: The user is navigating and a road is known to be blocked or closed.
Steps:
Start navigation on a valid route.
Deviate from the path.
Ensure that the system attempts to re-route.
Verify that the re-route does not suggest a road that is closed or blocked.
Expected Result:
The system should provide a re-route that avoids roads that are blocked or closed.
Negative Test Case 4: Verify that the system does not get stuck in an endless re-routing loop when deviating multiple times.
Use Case: Ensure that after multiple deviations, the system does not enter into an endless re-routing loop where it continuously attempts to redirect the user.
Test Case Name: Avoid Endless Re-routing Loop
Test Description: This test case ensures that the system doesn’t keep re-routing the user indefinitely if they continue deviating from the path multiple times.
Pre-condition: The user is navigating and deviates multiple times.
Steps:
Start navigation.
Deviate from the path several times in quick succession.
Observe the system’s behavior after each deviation.
Expected Result:
The system should not enter into an endless loop of re-routing. It should eventually either provide a reasonable alternative route or alert the user if re-routing is not possible.
Negative Test Case 5: Verify that re-routing does not take too long.
Use Case: Ensure that when the user deviates from the path, the system does not take an unreasonably long time to re-route.
Test Case Name: Timely Re-routing After Deviation
Test Description: This test case ensures that re-routing is completed in a reasonable amount of time and does not cause significant delays.
Pre-condition: The user is navigating and deviates from the intended path.
Steps:
Start navigation with the original route.
Deviate from the path.
Measure the time it takes for the system to provide a re-route.
Verify that the system provides the re-route in a reasonable amount of time (e.g., within 10 seconds).
Expected Result:
The system should provide the re-route within a reasonable timeframe without causing excessive delays.
TC_019
Test Case 1: Verify that the reload button refreshes the navigation route.
Use Case: Ensure that when the user presses the "Reload" button during navigation, the system refreshes the current navigation route and recenters the map to the user's current location.
Test Case Name: Reload Button Refreshes Navigation Route
Test Description: This test case ensures that when the user presses the "Reload" button during active navigation, the system refreshes the route and recenters the map to the user’s current location, providing an updated path if necessary.
Pre-condition:
The user is currently navigating with the map and directions displayed.
The navigation is active and showing turn-by-turn directions.
The user is able to view the "Reload" button during navigation.
Steps:
Start the navigation and allow it to display the current route on the map.
Press the "Reload" button during active navigation (this button should be available in the navigation screen).
Observe the system's response to pressing the "Reload" button.
Verify that the map recenters to the current location of the user.
Check if the system refreshes and recalculates the navigation route (if necessary).
Confirm that the system updates the turn-by-turn directions (if the route was changed or refreshed).
Verify that the map displays the refreshed route and the user’s current location correctly.
Expected Result:
After pressing the "Reload" button, the system should refresh the navigation route.
The map should recenter to the user's current location.
If there was any route adjustment, it should be recalculated and displayed properly.
The updated navigation directions (turn-by-turn) should be visible, and the route should be visually refreshed on the map.
Test Case 2: Verify that the "Reload" button does not affect the ongoing navigation if the route is already accurate.
Use Case: Ensure that pressing the "Reload" button does not interfere with the navigation if the route is already accurate and up-to-date.
Test Case Name: Reload Button with Accurate Navigation Route
Test Description: This test case ensures that if the route is already correct and accurate, pressing the "Reload" button will not disrupt the navigation or change the route unnecessarily.
Pre-condition:
The user is navigating the correct route and the map is showing the correct turn-by-turn directions.
The "Reload" button is available on the navigation screen.
Steps:
Start the navigation, ensuring the route is accurate.
Press the "Reload" button during active navigation.
Observe the system’s response to pressing the "Reload" button.
Verify that the map stays centered on the correct route and does not change the path.
Confirm that the system does not recalculate the route unnecessarily.
Expected Result:
The system should not alter the route or directions if the path is correct.
The map should remain centered and accurate with no interruptions.
The "Reload" button should not trigger any unnecessary recalculations or changes to the navigation.
Test Case 3: Verify that pressing the "Reload" button restores the map to the user's location if the user is off-course.
Use Case: Ensure that when the user is off the path and presses the "Reload" button, the system restores the map view to the user's location and recalculates the route accordingly.
Test Case Name: Reload Button Restores Map to User’s Location if Off-Course
Test Description: This test case ensures that when the user is off-course or deviates from the planned route, pressing the "Reload" button recenters the map on the user’s current location and recalculates the route if necessary.
Pre-condition:
The user is off-course or has deviated from the planned navigation path.
The "Reload" button is displayed on the navigation screen.
Steps:
Start navigation with an active route.
Deviate from the planned route (e.g., take a wrong turn or go off-road).
Press the "Reload" button during the active navigation.
Observe if the map recenters to the user’s current location.
Verify if the system recalculates the route to guide the user back on track.
Confirm that the system updates the turn-by-turn directions for the new route.
Expected Result:
After pressing the "Reload" button, the system should recenter the map to the user’s current location.
The route should be recalculated if necessary, and the map should reflect the updated path.
The updated navigation instructions (turn-by-turn) should be displayed.
Test Case 4: Verify that pressing the "Reload" button while on the correct path does not result in unnecessary route recalculation.
Use Case: Ensure that the "Reload" button does not trigger unnecessary route recalculation if the user is already on the correct path.
Test Case Name: No Unnecessary Route Recalculation with Reload Button
Test Description: This test case ensures that pressing the "Reload" button while on the correct path does not trigger any unnecessary recalculation of the route.
Pre-condition:
The user is actively navigating the correct path.
The "Reload" button is available during active navigation.
Steps:
Start navigation with the correct route.
Confirm that the user is on the correct path with accurate directions.
Press the "Reload" button during active navigation.
Observe the system’s response to pressing the "Reload" button.
Ensure the route does not change or recalculate unnecessarily.
Expected Result:
Pressing the "Reload" button should not change the current path or recalculate the route if the user is on the correct path.
The system should maintain the current navigation without interruption.
TC_20
Test Case 1: Verify that the reload button refreshes the navigation route when the internet is available.
Use Case: Ensure that when the user presses the "Reload" button during navigation, and the internet is available, the system refreshes the current navigation route and recenters the map to the user's current location, providing an updated path if necessary.
Test Case Name: Reload Button Refreshes Navigation Route with Internet Available
Test Description: This test case ensures that when the user presses the "Reload" button during active navigation and the internet is available, the system will refresh the route, recenter the map, and update the navigation accordingly.
Pre-condition:
The user is currently navigating with the map and directions displayed.
The internet connection is active and stable.
The user is able to view the "Reload" button during navigation.
Steps:
Start the navigation and allow it to display the current route on the map.
Ensure the internet connection is active.
Press the "Reload" button during active navigation (this button should be available in the navigation screen).
Observe the system's response to pressing the "Reload" button.
Verify that the map recenters to the current location of the user.
Check if the system refreshes and recalculates the navigation route (if necessary).
Confirm that the system updates the turn-by-turn directions (if the route was changed or refreshed).
Verify that the map displays the refreshed route and the user’s current location correctly.
Expected Result:
After pressing the "Reload" button, the system should refresh the navigation route.
The map should recenter to the user's current location.
The updated navigation directions (turn-by-turn) should be visible.
The system should update the route if necessary with an active internet connection.
Test Case 2: Verify that the "Reload" button does not work when there is no internet connection.
Use Case: Ensure that when the "Reload" button is pressed and the internet is unavailable, the system does not refresh the navigation route and provides an error message indicating the lack of internet connectivity.
Test Case Name: Reload Button Does Not Work When No Internet Connection
Test Description: This test case ensures that when the user presses the "Reload" button during active navigation, and the internet connection is not available, the system does not attempt to refresh the route and instead shows an appropriate error message.
Pre-condition:
The user is navigating, and the map is displayed.
There is no internet connection (either disabled or unavailable).
The "Reload" button is available on the screen.
Steps:
Start the navigation and allow it to display the current route on the map.
Ensure there is no internet connection (disable Wi-Fi, data, or simulate no connectivity).
Press the "Reload" button during active navigation.
Observe the system’s response to pressing the "Reload" button.
Verify if the system provides an error message indicating that the reload failed due to no internet connection.
Check if the navigation map remains the same without refreshing.
Expected Result:
The system should not refresh the navigation route.
An error message should be displayed, indicating that the route cannot be refreshed due to a lack of internet connection.
The navigation path should remain the same without any changes or reloading.
Test Case 3: Verify that the "Reload" button does not function when the internet is not available and the user is off-course.
Use Case: Ensure that if the user deviates from the path and presses the "Reload" button, and the internet is unavailable, the system does not recalculate the route and provides an error message instead.
Test Case Name: Reload Button Does Not Recalculate Route When Off-Course and No Internet
Test Description: This test case ensures that when the user deviates from the path and presses the "Reload" button, if there is no internet connection, the system does not recalculate the route and shows an error message instead.
Pre-condition:
The user is navigating and is currently off-course (has deviated from the route).
The internet connection is not available.
Steps:
Start navigation with an active route.
Deviate from the route (e.g., take a wrong turn).
Ensure that the internet connection is disabled or unavailable.
Press the "Reload" button.
Observe the system's response to pressing the "Reload" button.
Verify that the system does not recalculate the route due to lack of internet connection.
Check if an error message is displayed indicating the inability to recalculate the route.
Expected Result:
The system should not recalculate the route or refresh the map due to no internet connection.
An error message should be shown indicating that the system cannot reload the route without internet access.
The user should remain off-course without an updated route or directions.
Test Case 4: Verify that the "Reload" button works correctly after internet is restored.
Use Case: Ensure that if the internet was previously unavailable and is restored, pressing the "Reload" button will refresh the navigation route correctly.
Test Case Name: Reload Button Works After Internet is Restored
Test Description: This test case ensures that after the internet connection is restored, pressing the "Reload" button successfully refreshes the route and recalculates the directions.
Pre-condition:
The user is actively navigating, but there is no internet connection at the start.
The "Reload" button is available.
Internet connection is restored during the navigation.
Steps:
Start navigation and ensure there is no internet connection initially.
Press the "Reload" button (it should not work due to no internet).
Restore the internet connection (enable Wi-Fi or data).
Press the "Reload" button again.
Observe the system’s response to pressing the "Reload" button after internet is restored.
Verify if the map recenters and the route is refreshed.
Confirm that the updated directions are visible.
Expected Result:
After internet is restored, pressing the "Reload" button should successfully refresh the navigation route.
The map should recenter to the user’s current location and the route should be updated if necessary.
The updated navigation instructions should be visible, with turn-by-turn directions recalculated.
TS_021
Positive Test Case 1: Verify that audio and visual guidance stops immediately after canceling navigation.
Test Case Name: Audio and Visual Guidance Stops Immediately After Canceling Navigation
Test Description: This test case ensures that both the audio and visual guidance stop immediately when the user cancels the navigation via the handlebar switch or mobile application.
Pre-condition:
The user is actively navigating with both audio and visual guidance enabled.
Navigation is in progress with the map displaying directions and audio guiding the user.
Steps:
Start the navigation, ensuring both audio and visual guidance are active.
Press the left button on the handlebar switch or click the “Cancel” button in the mobile application to cancel navigation.
Observe whether the audio guidance stops (no more turn-by-turn audio).
Check if the visual guidance stops on the screen (no more map or directions).
Confirm that the map returns to the main menu or previous screen.
Expected Result:
Both audio and visual guidance should stop immediately when the user cancels the navigation.
The map should stop showing turn-by-turn directions.
No more audio directions should be heard after canceling navigation.
Positive Test Case 2: Verify that audio stops and visual guidance returns to main menu after canceling navigation.
Test Case Name: Audio Stops and Visual Guidance Returns to Main Menu After Canceling Navigation
Test Description: This test case ensures that audio guidance stops immediately and the visual guidance takes the user back to the main menu after canceling the navigation.
Pre-condition:
The user is actively navigating with both audio and visual guidance enabled.
The "Cancel" button on the handlebar switch or mobile application is available.
Steps:
Start the navigation process with audio and visual guidance active.
Press the left button on the handlebar switch or select the "Cancel" option from the mobile app.
Observe the audio guidance stopping immediately.
Check that the visual guidance stops and redirects to the main menu or previous screen.
Expected Result:
The audio guidance should stop immediately when the user cancels the navigation.
The visual guidance should stop, and the map should transition back to the main menu or the previous screen.
The system should ensure no further audio or visual guidance is displayed after canceling.
Negative Test Case 1: Verify that audio guidance continues after canceling navigation if the cancel action is not processed correctly.
Test Case Name: Audio Continues After Canceling Navigation if Cancel Action Is Not Processed Correctly
Test Description: This test case checks if the audio guidance continues after the user presses the cancel button, but the cancel action is not processed correctly by the system.
Pre-condition:
Navigation is in progress with audio and visual guidance active.
The "Cancel" button on the handlebar switch or the mobile application is available.
Steps:
Start the navigation process with audio and visual guidance.
Press the left button on the handlebar switch or select the "Cancel" option from the mobile app.
Check if the audio guidance still continues playing despite the cancelation request.
Observe the visual guidance to see if it continues displaying turn-by-turn instructions or map.
Expected Result:
The test should fail, and the system should not allow audio guidance to continue after canceling navigation.
The system should display an error or fail to cancel the navigation process properly.
Negative Test Case 2: Verify that visual guidance continues after canceling navigation if the cancel action fails to stop visual instructions.
Test Case Name: Visual Guidance Continues After Canceling Navigation if Cancel Action Fails to Stop Instructions
Test Description: This test case checks if visual guidance continues to show instructions and the map remains visible after canceling navigation due to a system failure to process the cancel action.
Pre-condition:
Navigation is in progress, and both audio and visual guidance are active.
The "Cancel" button on the handlebar switch or mobile application is available.
Steps:
Start the navigation with both audio and visual guidance active.
Press the left button on the handlebar switch or select the "Cancel" option from the mobile app.
Observe whether the visual guidance continues to display turn-by-turn instructions on the screen.
Check if the map still shows the current route or directions after pressing cancel.
Expected Result:
The visual guidance should stop immediately after the user presses the cancel button.
The system should not allow the map to continue displaying the navigation route.
The test should fail if the visual guidance continues despite cancelation.
Positive Test Case 3: Verify that system shows confirmation before canceling navigation and stops guidance after confirmation.
Test Case Name: System Shows Confirmation Before Canceling Navigation and Stops Guidance After Confirmation
Test Description: This test case ensures that the system shows a confirmation screen when the user tries to cancel the navigation, and that both audio and visual guidance stop after the user confirms the cancellation.
Pre-condition:
Navigation is in progress with audio and visual guidance enabled.
The user is trying to cancel navigation via the mobile app or handlebar switch.
Steps:
Start navigation and ensure both audio and visual guidance are active.
Press the left button on the handlebar switch or select the "Cancel" button in the mobile app.
Wait for the confirmation prompt to appear.
Confirm the cancellation by pressing the "Yes" button on the confirmation prompt.
Observe if the audio guidance stops immediately.
Check if the visual guidance stops and the screen returns to the main menu or previous screen.
Expected Result:
A confirmation screen should appear after pressing the cancel button.
After confirming the cancellation, both audio and visual guidance should stop immediately.
The user should be returned to the main menu or previous screen after confirming the cancelation.