Rio Tinto Track Navigation - Meeting Notes

Explore

2024 Meetings

Nov 19 - Test Plan

V. Software Quality Assurance

5.1 Documentation

5.1.1 Test Cases

Refer to the following table for the test scenarios per Milestone (expand each group to reveal test cases):

List of Test Cases (Milestone-based)

List of Test Cases (Milestone-based)

Milestone

Feature/Class/Group

Status

Scenario ID

Scenario Name

Description

Expected Results

1.1

Users should be able to navigate to LoA selection screen

In general, user can press on the LoA button on the right menu

Pressing on the LoA button should navigate to LoA selection screen

1.2A

LoA selection screen should show the signal list and necessary information to help users select a signal

Users should see the signals list for LoA selection sorted by distance from the current position, the set proximity distance for signals, directional filters for the signal list, and a close icon

Selection screen should show Signal List sorted by distance from the current location of the user

Selection screen should show the set proximity distance for signals

Selection screen should show directional filters for the signal list

Selection screen should show close icon

1.2B

LoA selection screen displays an error message when data from the .mmpk’s Signal layer fails to load

If the App is unable to read the data of the Signal layer, an error message is shown when the User presses the LoA button on the right-hand navigation bar.

LoA Selection screen shows an error message

1.3

LoA selection screen should still show the distance of the signals from the device’s current location and sort based on nearest to farthest even in cases of intermittent GPS data

Users should still see the signal list with the signal’s distance from the device’s current location and sorted based nearest to farthest even in cases of intermittent GPS data

Selection screen should show Signal List sorted by distance from the derived position of the user

1.4

LoA selection screen shows up to 8 Signals to choose from at a time.

Users can see 8 Signals before they need to scroll to see more.

Signal list should display 8 signals at a time

1.5

In the LoA selection screen, users should be able to navigate back to the Map screen

Users can close the LoA selection screen by pressing on close icon

Pressing on the close icon should navigate to map screen

1.6

Signals from list on the LoA screen shows how far it is based on device’s current location and can be filtered by bearing/direction.

Validate if the signals from the list shows the distance from from the device’s current location and can be filtered by “All”, “North” or “South” bearing.

Signals should show its distance from the device’s current location

Pressing “North” shows only Signals in the North Line Direction, sorted nearest to farthest

Pressing “South” shows only Signals in the South Line Direction, sorted nearest to farthest

Pressing “All” shows all Signals regardless of their line direction, sorted nearest to farthest

1.7

The Signals displayed by both “North” and “South” filters dynamically change based on device’s current location.

Verify if the signals shown whenever the list is filtered by direction, have their distance changing with reference to the current GPS coordinates of the device or vehicle.

Signals displayed when the North filter is on, change their distance and maintain the nearest to farthest sorting when the vehicle is moving northwards.

Signals displayed when the South filter is on, change their distance and maintain the nearest to farthest sorting when the vehicle is moving southwards.

1.8

Proximity Alarm for the Signal layer is displayed on the LoA screen.

Ensure that the Proximity Alarm distance for Signals is shown on the upper right corner of the LoA screen, below the Close “X” button. Distance can be configured in the Settings screen.

Signals’ Proximity Alarm radius is shown near the Close “X” button of the LoA screen.

Proximity Alarm distance is uninteractable in the LoA screen. (User needs to access the Settings screen to change values).

1.9

Select Signal for Journey Planning in LoA selection screen

Verify that users can select a signal as the LoA from the LoA signal list

The application should proceed to LoA confirmation screen

1.10

LoA confirmation screen should show necessary information about the destination

Users should see more information about the selected signal as LoA

Confirmation Screen should show Signal Name, Direction, distance to signal, and proximity alarm distance

Preview of the route journey should be visible in the map

Preview of the route journey should show a proximity radius on the LoA signal point as well as other signals along the journey to LoA

Cancel, back, and GO buttons should also be visible

1.11

Route preview in LoA confirmation screen should still show a starting point, even on intermittent GPS data

Users should still see preview of route journey on the map in the LoA selection screen

Derived position of the user in the map should be used in cases of intermittent GPS data

Preview of the route journey should still be visible in the map

1.12

Pressing on back button in the LoA confirmation screen should navigate the application back to LoA selection screen

Users should be able to navigate back to LoA selection screen using back button

Pressing on the back button should navigate to LoA selection screen

1.13

Pressing on cancel button in the LoA confirmation screen should close the LoA selection process

Users should be able to cancel LoA selection and return to the Map Screen using cancel button

Pressing on the cancel button should lead back to the Map/Main Screen

1.14

Pressing the GO button in the LoA confirmation screen will confirm the selected signal as the LoA for Journey Planning

Users should be able to press on the GO button to confirm the selection of signal for LoA

Pressing GO button will navigate back to the map view

The selected signal is set as the LoA destination

Distance to LoA should update with the distance to the selected signal in the map screen

Route to the selected LoA should be highlighted in the map

1.17

On a journey, route navigation should only show signals between start point and the selected LoA

Verify that the user can navigate between signals within a predefined Limit of Authority (LoA).

Navigation remains within the LoA.

Proximity alarms trigger only for the final destination signal.

1.18

A prompt to “End Journey” is displayed when user is inside the destination Signal proximity radius

Verify if Map screen changes to End Journey Screen when inside LoA Destination Signal proximity radius

End Journey screen is shown when inside LoA Destination Signal proximity radius

A button to End Journey is displayed

A Change LoA button is shown that navigates to LoA Selection screen

Details about the LoA Destination should also be shown

Signal Name

Direction

1.19

Pressing the LoA Destination (at the center of the information tab) or the LoA button mid-trip displayes a prompt to “End Journey”

Verify if pressing on LoA Destination or LoA in the right menu changes the screen to End Journey Screen

A button to End Journey is displayed

A back button that navigates back to Map screen when pressed

A Change LoA button is shown that navigates to LoA Selection screen

Details about the LoA Destination should also be shown

Signal Name

Direction

Distance left to Destination LoA

1.20

Pressing on End Journey button should navigate back to Map Screen with Initial state

Verify if End Journey button is pressed, the application goes to Map Screen with no LoA destination set

Application goes back to Map Screen

No LoA Destination is set

2.1

Ensure the App uses Hema Maps for navigation and route planning

The application must use pre-calibrated map data for navigation, ensuring routes are accurate and based on Rio Tinto data

Application loads Hema map upon Journey planning and navigation

Application loads navigation data saved on the device

2.2

App and Map Version displayed on Title/Splash screen

Verify that the App Version series number is shown upon loading/start-up of the app, on the Rio Tinto title screen.

App version number displayed at the bottom part of the Splash screen

2.3

Mobile Map Package not found

At the start, the app will try to load the Mobile Map Package (.mmpk), if it can’t find the package on the SD card, it should fall back to the .mmpk stored in the device. If that fails as well, the user should see a message indicator.

Application should fallback to mmpk saved in the device if the .mmpk is not found in the SD card

If that fails, Users should see a message showing the the mmpk cannot be found

2.4

Application should verify all layers inside the Mobile Map Package and notify if user if the verification fails

After successfully loading the .mmpk , the map layer contents and their feature fields should be verified based on the

data design - data dictionary section on the SLC

⁠

Each map layer and their feature fields should be verified

In case of failure, User should see a message showing that the required layers cannot be found

2.5

Route features should be 100% visible on the map during a journey

Displayed route in the map should not prevent visibility to currently toggled Track Assets along the journey

Check if visibility of toggled Track Assets is affected by the drawn route during a journey

4.1

Title screen (”Rio Tinto” splash screen) should navigate to initial map state

Upon application open, a title screen should show which then goes to initial map state

The system shows initial map state/

4.2

On the Title screen (”Rio Tinto” splash screen), Application should ask for location permissions and set up the location service

Upon application open during the splash screen, the application should handle asking for location permissions and set up the location service

Application should handle

Location permissions not yet granted state

Rationale recommended state

Location turned off state

4.3

Initial map state should show all relevant map values even if theres no journey yet

Initial map state shows current location of user, gps coordinates, bearing, and zero states for speed and distance.

Map should show current location of the user

Speed (0 on initial, changes based on actual vehicle speed)

Distance (0 on initial, changes based on distance from the destination)

LoA Destination Name (blank)

Bearing (based on the vehicles location)

GPS Coordinates (changes based on current location of the user)

4.4

During initial map state if there are no prior GPS position captured, when there are no gps coordinates data coming in, the map should zoom out to show the whole RT rail trackway

In cases GPS data fails, the map should zoom out to show all of the trackway instead, hiding the current location of the user on the map

Zoomed out view of the map showing the trackway

No current location of the user

GPS and bearing should show empty values

Centering should also go to the centroid of the rail trackway

4.5

Moving when in initial map state should update the speed, bearing, and GPS coordinates

At initial map state without starting any journey, moving along the track should update the speed, bearing, and GPS coordinates

GPS, Bearing, and speed values should update

1.15

Moving when a journey is set should update the speed, distance, bearing, and GPS coordinates

During a journey, moving along the track should dynamically update the speed, distance, bearing, and GPS coordinates

Speed (changes based on actual vehicle speed)

Distance (changes based on distance from the destination)

LoA Destination Name (fixed)

Bearing (changes based on the vehicles location)

GPS Coordinates (reflects the GPS coordinates of the device/vehicle)

1.16

On a journey, the current location of the user on the route should still show even on intermittent GPS data

During a journey, the current location of the user on the route should still show even on intermittent GPS data

Derived position of the user in the map along the route should be used in cases of intermittent GPS data

Derived position should be based on previous progress in the journey

3.1

Pressing on Assets should navigate to Map Assets screen

In general, user can press on the Assets button on the right menu

Pressing on the Assets button should navigate to Map Assets screen

3.2

Map Assets screen should first show track assets list.

In the Map Assets screen - Track asset list, track asset items are listed with each item showing a toggle if its going to be shown in the map, asset name, an editable proximity distance, and a toggle if its going to alert users. There should also be tabs above the list to scroll automatically to Track asset List or Map Layers list, and a close icon to navigate back to Map screen

On navigate to Map Assets screen, the Track Assets list should be shown

Each list item should have toggle visibility button, asset name, editable proximity, and toggle alarm button

Navigation tabs between track asset and map layers should be shown

Close icon should be shown

3.3

Toggle Track Asset Visibility On/Off

In the Maps Assets screen - Track Assets list, verify that users can toggle track asset layers on and off for viewing on the map.

The selected layers are displayed or hidden based on user preferences

When a track asset is turned on, it should be activated for the entire track network

The following layers should be included and toggleable

Non-Active Rail Road Crossings layer

NBS (Narrow Band Shunt)

DEDs (Dragging Equipment Detectors)

HBDs (Hot Bearing Detectors)

RFID Readers

SFDs (Stream Flow Detectors)

Turnouts

Bridges

3.4

Toggling visibility for Non-Active Rail Road Crossing layer should not affect Active Rail Road Crossing points

In the Maps Assets screen - Track Assets list, verify if toggling Non-Active Rail Road Crossing layer DOES NOT affect Active Rail Road Crossing points

ALX Points should still be visible if Non-ALX layer is turned off

3.5

Signals should not be part of the Track Asset list and should not be toggleable

Verify that no user can turn off signals during navigation

No element in the UI looks like button to turn on/off signals

The system prevents signals from being turned off

3.6

Signals Should Not Be Turned Off from a Layer

Verify that the .mmpk loaded should not have any Signal points in any layers other than Signal layers

Signal Layers and the rest of the layers should be checked based on the

data design - data dictionary section of the SLC

⁠

3.7

In the Map Assets screen - Track asset list, users should be able to navigate back to the Map screen

Users can close the Map Assets screen - Track asset list by pressing on close icon

Pressing on the close icon should navigate to map screen

3.8

In Map Assets screen, pressing on navigation tab should automatically scroll the list between Track assets and Map layers list. User should be able to scroll manually as well

In the Maps Assets screen, scrolling between Track assets and Map Layers list should be allowed. Pressing on the navigation tabs should automatically scroll between the two lists

Manually scrolling between the two lists should be allowed

Pressing on Assets tab should scroll up to top of Track assets list

Pressing on Map Layers tab should scroll down to top of Map layers list

3.9

Map Assets screen - Map Layers list should show map layer items

In Map Assets screen - Map Layers list, map layer items are listed showing a toggle if its going to be shown in the map and the layer name. There should also be tabs above the list to scroll automatically to Track asset List or Map Layers list, and a close icon to navigate back to Map screen

Each list item should have toggle visibility button and layer name

Navigation tabs between track asset and map layers should be shown

Close icon should be shown

3.10

Toggle Map Layers On/Off

In the Maps Assets screen - Track Assets list, verify that users can toggle map layers on and off for viewing on the map

The selected layers are displayed or hidden based on user preferences

When a map layer is turned on, it should be activated for the entire track network

The following layers should be included and toggleable

Track Chainage (KM Markings)

Track Names/Segments (e.g., GECKO NE2T, PP 1.33 30ST)

Station Names

3.11

Chainage, Track names, and Station Names layers should be on by default

In general, these layers should be toggled on and visible by default

Chainage Layer should be turned on by default

Track names Layer should be turned on by default

Station names layer should be turned on by default

3.12

In the Map Assets screen - Map Layers list, users should be able to navigate back to the Map screen

Users can close the Map Assets screen - Map Layers list by pressing on close icon

Pressing on the close icon should navigate to map screen

3.13

Application should be able to persist toggle visibility changes

Application should be able to persist toggle visibility changes even on app close

Toggle visibility settings must be stored in local storage for persistence

3.14

Pressing on Close “X” button in the Map Assets screen should close the drawer and show the Main/Map Screen

Users should be able to navigate back to LoA selection screen using back button

Pressing on the Close “X” button should close the drawer.

4.6

During initial map state, when the user has prior GPS data and it failed, the derived location of the user should still show on the map

At initial map state when the user already has prior GPS data, the user should see derived current location on the map

Derived current location of the user

GPS and bearing should show derived values

Centering should also go to derived position of user

4.7

Zoom in and out functionalities should work in the map

In general, the zoom in and out functionality of the map should work

Zooming in and out of the map should work

Asset names to change in size as it zooms to ensure they are viewable

Ensure minimum zoom in level of 250m

Ensure maximum zoom out level is encompassing the whole RT rail network

4.8

Changing between satellite and general view of the map

In general, user can change between satellite or general view of the map using the Map/Satellite toggle button.

Pressing on the map icon should change between general and satellite view

Switching to satellite view renders the map images

Switching to map view loads the map with route/track names and asset (with layer visibility set to ON), without the satellite images

4.9

Centering of the map to the current position of the user

In general, user can center the map to their location

Pressing on the center icon should center the map to the user’s current location

4.13

In the Settings screen, users should be able to navigate back to the Map screen

Users can close the Settings screen by pressing on close icon

Pressing on the close icon should navigate to map screen

5.7A

Application should be able to persist toggle alarm and Track Asset distance configuration changes

Application should be able to persist toggle alarm and Track Asset distance configuration changes even on app close

These configuration changes must be stored in local storage for persistence

Toggle alarm

Track Asset distance configuration

4.10

Pressing on Settings should navigate to Settings screen

In general, user can press on the Settings button on the right menu

Pressing on the Settings button should navigate to Settings screen

4.11

Settings screen should allow configuration for ALX and LoA alarm distance.

In the Settings screen, Users should see the configuration options for ALX and LoA Alarm distance.

Settings screen should show edit option for ALX alarm distance

Settings screen should show edit option for LoA alarm distance

Settings screen should show check for updates button

Settings screen should show close icon

Settings screen should also have information about

Date of last checking for updates

Application version

Map version

Date of last update of the application

Update warning to do it while not in operation and within network range

5.2

Maps Assets screen - Track Assets list should allow customization of proximity alarm distance

In the Maps Assets screen - Track Assets list, pressing the proximity distance of a Track Asset should navigate to its configuration screen

Pressing proximity distance should navigate to distance configuration screen of track assets

5.3

Distance Configuration - Track Asset screen should show a settings page for distance configuration

In the Distance Configuration - Track Asset screen, verify that the name of the track asset layer, all valid proximity alarm distance choices, and a Done button is shown

The screen should show the Track asset that is being edited

Options for values shown are 50m, 100m, 200m, 400m, 500m, 1000m

A Done button should be shown

5.4

Distance Configuration - Track Asset screen should allow users to set a distance

In the Distance Configuration - Track Asset screen, Users should be able to select a distance value and confirm selection

Only one value among the distance options should be selected

Upon selection, value is confirmed and saved

Check if changes have been correctly applied in the following screens

Maps Assets screen - Track Assets list item for the changed track asset

5.5

Distance Configuration - Track Asset screen should allow users to go back

In the Distance Configuration - Track Asset screen, pressing on Done button should navigate back to Map Assets screen - Track Assets list

Pressing on Done button should navigate back to Maps Assets screen - Track Assets list

5.6

Changing distance configuration of Non-Active Rail Road Crossing layer should not affect Active Rail Road Crossing points

In the Maps Assets screen - Track Assets list and Settings screen, verify if changing distance configuration of Non-Active Rail Road Crossing layer DOES NOT affect Active Rail Road Crossing points

ALX distance configuration should not change if Non-ALX distance is changed

5.7B

Application should be able to persist toggle alarm and Track Asset distance configuration changes

Application should be able to persist toggle alarm and Track Asset distance configuration changes even on app close

These configuration changes must be stored in local storage for persistence

Toggle alarm

Track Asset distance configuration

5.1

Toggle Track Asset Alarm On/Off

In the Maps Assets screen - Track Assets list, verify that users can toggle alarms on or off for specific rail assets.

The selected layers have their alarms toggled on and off

The following layers should be included and toggleable

Non-Active Rail Road Crossings layer

NBS (Narrow Band Shunt)

DEDs (Dragging Equipment Detectors)

HBDs (Hot Bearing Detectors)

RFID Readers

SFDs (Stream Flow Detectors)

Turnouts

Bridges

6.1

Settings screen should allow customization of LoA Alarm Distance

In the Settings screen, pressing LoA Alarm distance should navigate to its configuration screen

Pressing LoA Alarm distance should navigate to distance configuration screen of LoA

6.2

Distance Configuration - LoA screen should show a settings page for distance configuration

In the Distance Configuration - LoA screen, verify that all valid proximity alarm distance choices and a Done button is shown

Options for values shown are 50m, 100m, 200m, 400m, 500m, 1000m

A Done button should be shown

6.3

Distance Configuration - LoA screen should allow users to set a distance

In the Distance Configuration - LoA screen, Users should be able to select a distance value and confirm selection

Only one value among the distance options should be selected

Upon selection, value is confirmed and saved

Check if changes have been correctly applied in the following screens

Map screen as a shaded proximity radius on Signal asset points

If on a journey, only show shaded proximity radius on Signal asset points along LoA

LoA selection screen

LoA confirmation screen

Settings screen

6.4

Distance Configuration - LoA screen should allow users to go back

In the Distance Configuration - LoA screen, pressing on Done button should navigate back to Settings screen

Pressing on Done button should navigate back to Settings screen

6.5

Prevent Triggering Alarms for Adjacent Tracks, and Alarms for Signals prior the destination Signal

Verify that alarms only trigger for the destination Signal

Signals en-route, and Signals on other tracks near the track being traversed do not sound alarms

Alarm is triggered within proximity radius of destination Signal

6.6

Settings screen should allow customization of ALX Alarm Distance

In the Settings screen, pressing ALX Alarm distance should navigate to its configuration screen

Pressing ALX Alarm distance should navigate to distance configuration screen of ALX

6.7

Distance Configuration - ALX screen should show a settings page for distance configuration

In the Distance Configuration - ALX screen, verify that all valid proximity alarm distance choices and a Done button is shown

Options for values shown are 50m, 100m, 200m, 400m, 500m, 1000m

A Done button should be shown

6.8

Distance Configuration - ALX screen should allow users to set a distance

In the Distance Configuration - ALX screen, Users should be able to select a distance value and confirm selection

Only one value among the distance options should be selected

Upon selection, value is confirmed and saved

Check if changes have been correctly applied in the following screens

Map screen as a shaded proximity radius on ALX asset points

Settings screen

6.9

Distance Configuration - ALX screen should allow users to go back

In the Distance Configuration - ALX screen, pressing on Done button should navigate back to Settings screen

Pressing on Done button should navigate back to Settings screen

6.10

Changing distance configuration of Active Rail Road Crossing layer should not affect Non-Active Rail Road Crossing points

In the Settings screen and Maps Assets screen - Track Assets list, verify if changing distance configuration of Active Rail Road Crossing layer DOES NOT affect Non-Active Rail Road Crossing points

Non-ALX distance configuration should not change if ALX distance is changed

6.11

Retain the settings for Signal distance configuration and ALX distance configuration on the Settings screen, on App close/restart.

Changes to Signal distance configuration and ALX distance configuration on the Settings screen should remain, even when the App is restarted.

These configuration changes must be stored in local storage for persistence

Signal distance configuration

ALX distance configuration

6.12

Alarm sounds between LoA, ALX, and Track assets should be different

User should hear different alarm sounds between LoA, ALX, and Track Assets

LoA should be three beeps

ALX should be distinguishable from LoA and sound more important than other Track Assets

All Track Assets have the same sound

6.13

ALX Alarms should also show a notification pop up in the Map screen

User should see a pop up notification in the map screen along with the alarm sound

Notification should show up on the upper right side of the Map screen along with alarm sound when crossing ALX proximity radius

ALX notification should contain distance to ALX and “ALX” with its map legend

Tapping anywhere in the screen dismisses the notification

Reaching 0m of the ALX point will also dismiss the notification

6.14

LoA Alarms should also change the background color of the LoA destination rectangle when nearing location

Users should see the LoA destination rectangle on the navigation bar above the map screen to change background colors as they approach LoA

When within LoA proximity alarm radius, the background color should change from light orange to dimmed red

When 0m or less inside LoA radius, background color should flash from dimmed red to bright red

6.15

Proximity Alarm triggers even when device is not connected to the internet (offline mode)

Verify that alarms work when device loses internet connectivity

Alarm is triggered within proximity of destination Signal based on GPS data alone

6.16

Alarms can be silenced when User presses anywhere in the screen

Verify that an alarm triggered and currently beeping, can be silenced when the User interacts with the screen

Tapping anywhere in the screen silences the alarm

A dialog with the message “Tap anywhere to dismiss the alarm” should be shown on the lower right side of the map screen

4.12

Settings screen should have different states for check for updates button

In the Settings screen, when a user presses Check for updates, the button should have a downloading state and an installing state

When pressed, check for updates button should switch to download state

Date of Last checked for updates should also update

After download state, check for updates button should switch to installing state

After installation, date of Last updated should also update

On installation of new builds of the application, the App Version information should also update

3.15

Map Assets screen default state and settings

Default Proximity Alarm Distance for all Assets should be 100m, and all should be OFF initially

Basis

Messages from RT about Scope, Oct 9 2024

⁠

Proximity Alarm Distance for all Assets is 100m by default

Alarm is Turned OFF by default

⁠

5.1.2 Results of the Tests

For the results of the tests performed, see

Software Test Documentation⁠

5.2 Software Reviews

5.2.1 Defined Metrics

Number of Tests: Tracks the total number of tests created and executed.

Test Coverage: Percentage of code covered by unit and integration tests.

Defect Density: Number of defects is reflected by the amount of failing test cases

Defect Resolution Time: Average time taken to resolve identified defects.

Customer-reported Defects: Number of defects reported by the end-users after release which is triaged by Hema

Test Execution Time: The total time taken to execute all test cases.

Requirement Traceability: Percentage of requirements with associated test cases and successful test execution.

5.2.2 Tools, Techniques, and Methodologies

Code Reviews:

Code Quality: Ensure adherence to coding standards, proper error handling, and maintainability.

Code Structure: Check for efficient algorithms, modular design, and reuse opportunities.

Documentation Review: Ensure comments and code documentation are sufficient and up-to-date.

Acceptance Tests:

Functional Completeness: Validate that the software meets all documented functional requirements.

User Interface (UI) Consistency: Ensure UI components match the design and provide consistent interaction patterns.

Usability Testing: Conduct tests to assess user satisfaction and ease of use.

Edge Case Handling: Verify the system’s behavior under rare or extreme conditions.

Design Reviews:

Architectural Integrity: Check that the system design aligns with architectural goals, including scalability and maintainability.

Module Interactions: Review module dependencies and interactions for efficiency and correctness.

5.3 Performance Testing

5.3.1 Defined Metrics

Load time - The amount of time it takes to load the .mmpk file

Render time - Time it takes to render map feature layers

Frame rate - Frames per second (FPS) while interacting with the application map (e.g., panning, zooming)

Memory Usage - Amount of memory consumed when the .mmpk file is loaded

CPU Usage - Percentage of CPU utilization during heavy operations such as waypoint navigation, toggling track assets, querying Signals for LoA selection

Battery Consumption - How the application impacts the battery life

5.3.2 Tools, Techniques, and Methodologies

To track the performance of the application for each build, the following benchmarks are used:

Testing Application Functionalities such as map navigation, journey selection, map layer management, etc.

Layer Feature Query Performance testing with LoA selection and evaluation of query execution time as well as memory and CPU consumption during these operations

Analysis of memory usage and leaks during initial map layer render and track asset toggling

Responsiveness of the Application during different states such as switching betwwen foreground and background tasks and the main Application Functionalities

Battery consumption analysis during the above benchmarks

Ensuring UI responsiveness and overall user experience fluidity while using the application offline

Application testing on extended usage scenarios as well as possible edge-case scenarios that can be encountered in the field

In order to track the defined performance metrics across all Application Performance Testing Benchmarks,

Android Profiler⁠

is used. This built-in tool allows tracing of the application and identifies areas in which your app makes inefficient use of resources such as the CPU, memory, graphics, network, or the device battery.

5.2 Software Reviews

5.2.1 Defined Metrics

Number of Tests: Tracks the total number of tests created and executed.

Test Coverage: Percentage of code covered by unit and integration tests.

Defect Density: Number of defects is reflected by the amount of failing test cases

Number of Code Reviews: Tracks the total number of peer reviews conducted.

Length of Code Reviews: Average time spent on peer reviews per code module.

Defect Resolution Time: Average time taken to resolve identified defects.

Customer-reported Defects: Number of defects reported by the end-users after release which is triaged by Hema

Test Execution Time: The total time taken to execute all test cases.

Requirement Traceability: Percentage of requirements with associated test cases and successful test execution.

5.2.2 Tools, Techniques, and Methodologies

Code Reviews:

Code Quality: Ensure adherence to coding standards, proper error handling, and maintainability.

Code Structure: Check for efficient algorithms, modular design, and reuse opportunities.

Documentation Review: Ensure comments and code documentation are sufficient and up-to-date.

Acceptance Tests:

Functional Completeness: Validate that the software meets all documented functional requirements.

User Interface (UI) Consistency: Ensure UI components match the design and provide consistent interaction patterns.

Usability Testing: Conduct tests to assess user satisfaction and ease of use.

Edge Case Handling: Verify the system’s behavior under rare or extreme conditions.

Design Reviews:

Architectural Integrity: Check that the system design aligns with architectural goals, including scalability and maintainability.

Module Interactions: Review module dependencies and interactions for efficiency and correctness.

5.3 Performance Testing

5.3.1 Defined Metrics

Load time - The amount of time it takes to load the .mmpk file

Render time - Time it takes to render map feature layers

Frame rate - Frames per second (FPS) while interacting with the application map (e.g., panning, zooming)

Memory Usage - Amount of memory consumed when the .mmpk file is loaded

CPU Usage - Percentage of CPU utilization during heavy operations such as waypoint navigation, toggling track assets, querying Signals for LoA selection

Battery Consumption - How the application impacts the battery life

5.3.2 Tools, Techniques, and Methodologies

To track the performance of the application for each build, the following benchmarks are used:

Testing Application Functionalities such as map navigation, journey selection, map layer management, etc.

Layer Feature Query Performance testing with LoA selection and evaluation of query execution time as well as memory and CPU consumption during these operations

Analysis of memory usage and leaks during initial map layer render and track asset toggling

Responsiveness of the Application during different states such as switching betwwen foreground and background tasks and the main Application Functionalities

Battery consumption analysis during the above benchmarks

Ensuring UI responsiveness and overall user experience fluidity while using the application offline

Application testing on extended usage scenarios as well as possible edge-case scenarios that can be encountered in the field

In order to track the defined performance metrics across all Application Performance Testing Benchmarks,

Android Profiler⁠

VI. Software Test Documentation

6.1 Overview

In this project, the team submits a list of test cases (ex.

Test Cases for M2⁠

) to the client as a baseline for milestone approval internally. Each significant testing is logged below in Test Log for tracking. An outstanding issue list table is maintained where issues are added after every testing, and their Issue IDs added in the Issues Found column of the Test Log. After the end of every testing, a Test Report entry is created summarizing the issues found and recommendations by the testers, if any.

6.2 Test Plan

6.2.1 Test Cases

Refer to the following for the Test Scenarios per Milestone:

⁠

Broken link⁠

⁠

6.2.2 Test Log

6.2.2 Test Log

Test No.

Test Date

Milestones

Testers

Issues Found

Test Cases for M2

There are no rows in this table

⁠

6.2.3 Outstanding Issue List

6.2.3 Outstanding Issue List

Issue ID

Name

Description

Status

Priority

Size

M2-12

There are no rows in this table

⁠

6.3 Test Report

6.3 Test Report

Test No.

Test Duration

Evaluations and Recommendations

There are no rows in this table

⁠

Gallery

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.