EPOD PDA Test Plan
From EPOD
Test Script / Scenario Reference | EPOD - PDA Client/Server Test Plan | Call Number(s): 292887 |
Test Script / Scenario Description | Test the PDA and Server functionality | PASS / ISSUES / FAIL |
Menu Access | EPOD PDA Application | |
Pre-requisites | Assign a load to the test operator with multiple of the following:
Ensure that the system is installed with the latest Updater but an out-of-date application. Ensure that the PDA is configured correctly to connect to the test system being used. Ensure that the system is configured initially as standard. | Tested By: |
Test Objective | To ensure that the PDA operates as expected | Date: |
Step | Action | Result | Remarks | P/F |
1 | General Operation | |||
1.01 | Start the application. | The system should note that there is an update required and start the updater. | ||
1.02 | Update the application. | The system starts the application. | ||
1.03 | Log on with an invalid user/password/vehicle | The system will not allow log in | ||
1.04 | Log on with an Admin user. | The system should show the configuration screen. | ||
1.05 | Ensure that the system is configured to connect to the test system correctly. Exit the configuration screen. | The system should show the Logon screen. All standing data should be updated on the system. | ||
1.06 | Log on with a PDA user with no load assigned and a vehicle that is unchecked. | The system should force the user through the Vehicle Checks for the Vehicle. | ||
1.07 | Complete the Vehicle Checks. | The system should display that no load is found. The complete Vehicle Checks should be available for viewing within the Admin system. | ||
1.08 | Assign a load to the user in Admin. Click to fetch the load again. | The system should show the Jobs on the Load. | ||
1.09 | Change the details of the Load in Admin (add a container or product, change the quantity of a product, change the job instructions, add a job to the load) | The PDA should display a screen showing the changes to the Load (within a 5-minute timer). A new column should show whether the job is Edited, Added or Cancelled from the load. | ||
1.10 | Click the button to clear the update. | The PDA should show the job list again, showing all new jobs, with all cancelled jobs removed. |
Step | Action | Result | Remarks | P/F |
2 | Collections | |||
2.01 | Start a stand-alone Collection job from the Job List with no products or containers | The Job Details screen should be shown allowing the user to see the details of the job. | ||
2.02 | Press OK | The Job should be In Progress in the Admin system. Ad Hoc Collection should be shown. A message should be displayed, showing that the job may not be correctly updated. | ||
2.03 | Choose products from the drop-down list and enter quantities before adding. | The product should be added to the list. | ||
2.04 | After adding several products, click OK. | The PDA should allow the user to confirm the job, through signature entry. | ||
2.05 | Enter the signature and confirm. | The system should show the job list again. The job should be removed. The job should be confirmed in Admin. The signature should be visible against the POC. | ||
2.06 | Start a stand-alone Collection job from the Job list with only Products. | The Job Details screen should be shown allowing the user to see the details of the job. | ||
2.07 | Press OK | The Job should be In Progress in the Admin system. The Collection screen should be shown with no Containers tab. | ||
2.08 | Select a product and enter a quantity and confirm. | The product should be removed from the list. | ||
2.09 | Change a product quantity. | The unit should allow reason code entry and confirmation. | ||
2.10 | Complete all products. | The PDA should allow the user to confirm the job, through signature entry. | ||
2.11 | Enter the signature and confirm. | The system should show the job list again. The job should be removed. The job should be confirmed in Admin. The signature should be visible against the POC. | ||
2.12 | Start a stand-alone Collection job from the Job list with only Containers. | The Job Details screen should be shown allowing the user to see the details of the job. | ||
2.13 | Press OK | The Job should be In Progress in the Admin system. The Collection screen should be shown with no Products tab. | ||
2.14 | Select a container and confirm as collected. | The container should be removed from the list. | ||
2.15 | Select a container and confirm as Not Collected. | The unit should allow reason code entry and confirmation. | ||
2.16 | Complete all containers. | The PDA should allow the user to confirm the job, through signature entry. | ||
2.17 | Enter the signature and confirm. | The system should show the job list again. The job should be removed. The job should be confirmed in Admin. The signature should be visible against the POC. | ||
2.18 | Start a stand-alone Collection job from the Job list with Containers and Products. | The Job Details screen should be shown allowing the user to see the details of the job. | ||
2.19 | Press OK | The Job should be In Progress in the Admin system. The Collection screen should be shown with the Containers and Products tabs. | ||
2.20 | Select a container and confirm as collected. | The screen will prompt for Product entry. | ||
2.21 | Select a product and confirm the quantity. | The product should be removed from the list. | ||
2.22 | Change a product quantity. | The unit should allow reason code entry and confirmation. | ||
2.23 | Complete all products. | The PDA should return to the containers list. The Container confirmed as collected should be removed from the list. | ||
2.24 | Select a container and confirm as Not Collected. | The unit should allow reason code entry and confirmation. | ||
2.25 | Complete all containers and their products. | The PDA should allow the user to confirm the job, through signature entry. | ||
2.26 | Enter the signature and confirm. | The system should show the job list again. The job should be removed. The job should be confirmed in Admin. The signature should be visible against the POC. | ||
2.27 | Start a stand-alone Collection job from the Job list with Loose products and Containers and Products. | The Job Details screen should be shown allowing the user to see the details of the job. | ||
2.28 | Press OK | The Job should be In Progress in the Admin system. The Collection screen should be shown with the Containers and Products tabs. | ||
2.29 | Select a container and and confirm as Collected. | The screen will prompt for Product entry. | ||
2.30 | Select a product and confirm the quantity. | The product should be removed from the list. | ||
2.31 | Change a product quantity. | The unit should allow reason code entry and confirmation. | ||
2.32 | Complete all products. | The PDA should return to the containers list. The Container confirmed as collected should be removed from the list. | ||
2.33 | Select a container and confirm as not collected. | The unit should allow reason code entry and confirmation. | ||
2.34 | Complete all containers and their products. | The PDA should prompt for the entry of loose products, showing the Products tab. | ||
2.35 | Select a product and confirm the quantity. | The product should be removed from the list. | ||
2.36 | Change a product quantity. | The unit should allow reason code entry and confirmation. | ||
2.37 | Complete all products. | The PDA should allow the user to confirm the job, through signature entry. | ||
2.38 | Enter the signature and confirm. | The system should show the job list again. The job should be removed. The job should be confirmed in Admin. The signature should be visible against the POC. | ||
2.39 | Start a Collection job from the Job List of any type. | The Job Details screen should be shown allowing the user to see the details of the job. | ||
2.40 | Press OK | The Job should be In Progress in the Admin system. The collection process for this collection type should be started. | ||
2.41 | Press Cancel | The unit should allow reason code entry and confirmation that the job is cancelled. | ||
2.42 | Start a Collection job from the Job List of any type that is linked to a Delivery on the same load. | The Job Details screen should be shown allowing the user to see the details of the job. | ||
2.43 | Press OK | The Job should be In Progress in the Admin system. The collection process for this collection type should be started. | ||
2.44 | Complete the Collection, changing some quantities or failing to collect some containers. | The system should show the job list again. The job should be removed. The job should be confirmed in Admin. The signature should be visible against the POC. The Delivery should be updated in Admin and the device, reflecting the changes made to the Collection. |
Step | Action | Result | Remarks | P/F |
3 | Deliveries | |||
3.01 | Repeat tests 2.01 to 2.41 above for Delivery processing. | As expected. |
Step | Action | Result | Remarks | P/F |
4 | Collections/Deliveries Without Products | |||
Set up a collection and delivery with 2 containers and multiple products on a new load and assign it to a PDA user. Ensure that the system is configured for Collections and Deliveries without products. | ||||
4.01 | Start the load with the PDA user. Select the collection and start it. | The collections screen should be displayed with the Instructions and Containers tabs, with no Products tabs. | ||
4.02 | Long-press on a container | A popup should be displayed allowing you to display the products within the container. | ||
4.03 | Select this. | A screen should be displayed showing the products within the container. | ||
4.04 | Return to the collections screen. key, scan or select one of the containers from the list and mark as Collected. | The container should be removed from the list. Product quantities should no be prompted for. | ||
4.05 | Long press on the second container and choose to display the products. | The products only for this container should be displayed. | ||
4.06 | Complete the collection by marking the second container as not collected. | The PDA should require you to enter a reason code for the non-collection of the second container. | ||
4.07 | Enter a reason code and confirm. | The collection should be completed. You will be prompted for signature capture. | ||
4.08 | Enter the signature and confirm. | The collection should be completed. The PDA should display the job list with only the delivery remaining. The collection details should be sent back to the server, showing that the 1st container was collected and the second was not, with the chosen reason code. The Job should be marked as complete. | ||
4.09 | Select the delivery. Repeat tests 2-8 for the delivery. | As expected. The Load should be marked complete on the server. The PDA should request a new load. |
Step | Action | Result | Remarks | P/F |
5 | Services | |||
Configure Services for the job group as requiring all items to be entered. Ensure that both the site and vehicle have at least 3 service products with a quantity of at least 3 against them. Create at least 7 Service jobs and assign to a Load. Assign this to a PDA user. | ||||
5.01 | Start the load with a PDA user. | The PDA should show the Job list with the service on it. | ||
5.02 | Select the service. | The Job Details screen should be displayed, showing the Service ID, Customer address and contact details and any job instructions. | ||
5.03 | Start the service. | The Services screen should be shown, displaying the following tabs in this sequence:
|
||
5.04 | Click OK | The Pre-work tab should be displayed. | ||
5.05 | Check each box and enter a comment if required. Click OK. | The data should be entered and the PDA should move onto the Info tab. | ||
5.06 | Enter data in any of the requested fields. Click OK. | The data should be entered and the PDA should move onto the Activities tab. | ||
5.07 | Select an activity from the list and click Add. | The activity should be added to the grid view. | ||
5.08 | Add another activity, then click the first activity and click Remove. | The first activity should be removed from the list. | ||
5.09 | Click OK. | The PDA should move onto the Installed Products tab. | ||
5.10 | Select a product from the drop-down list and click Add. | The product should be added to the list with a quantity of 1. | ||
5.11 | Click Add again. | The quantity against that product should increase to 2. | ||
5.12 | Add 2 different products to the list. Select the first product and click Remove. | The quantity should reduce to 1. | ||
5.13 | Click Remove again. | The first product should be removed from the list. | ||
5.14 | Press OK. | The PDA should move onto the Removed Products tab. | ||
5.15 | Enter any text in the entry box and click Add. | The product should be added to the list with a quantity of 1. | ||
5.16 | Click Add again. | The quantity against that product should increase to 2. | ||
5.17 | Add 2 different products to the list. Select the first product and click Remove. | The quantity should reduce to 1. | ||
5.18 | Click Remove again. | The first product should be removed from the list. | ||
5.19 | Press OK. | The PDA should move onto the MC Ref tab. | ||
5.20 | Enter MC References and dialogue. | Only numeric data should be enterable in the Ref fields. Any text can be entered in the Dialogue field. | ||
5.21 | Click OK. | The data should be entered and the PDA should move onto the Postwork Checks tab. | ||
5.22 | Check each box and enter a comment if required. Click OK. | The data should be entered and the PDA should move onto the Diagnosis tab. | ||
5.23 | Enter a diagnosis comment. Check any of the check boxes. Click OK. | The data should be entered and the PDA should move to signature capture. | ||
5.24 | Enter the signature and confirm as complete. | The service should be completed. The PDA should return to the Job list. The service completed should be removed from the list. The server should be updated with all the entered details. The Vehicle Products should be reduced by the amount of products used. The Site Products should be reduced by the amount of products used. | ||
5.25 | Select the next service, then click Cancel. | The PDA should prompt for a reason code as to why this service job is to be cancelled. | ||
5.26 | Select a reason code from the list and confirm. | The service job should be cancelled. The PDA should return to the Job list with the service just cancelled removed from the list. The server should be updated, marking the service as cancelled with the reason code. | ||
5.27 | Select the next service and start it. Enter no information in any of the tabs, but keep clicking OK. | The PDA should keep prompting for all required data. | ||
5.28 | Enter information in one tab at a time, clicking OK through all other tabs after each tab entry. | Until all required data is entered in all tabs, the PDA will keep requesting data to be entered. When complete, the PDA will request signature entry. | ||
5.29 | Enter the signature and confirm as complete. | The service should be completed. The PDA should return to the Job list. The service completed should be removed from the list. The server should be updated with all the entered details. The Vehicle Products should be reduced by the amount of products used. The Site Products should be reduced by the amount of products used. | ||
5.30 | Cancel out of the PDA application. Change the job group configuration remove each tab in sequence. After each configuration change, complete a service from the PDA application. | The service should complete, but without showing the tabs excluded by the configuration. The PDA should not require the removed tab information to be entered. The services completed should be sent back to the server with only the entered information against them. |
Step | Action | Result | Remarks | P/F |
6 | Imaging | |||
Set up several collections, deliveries and services on a load and assign to a user. Collections and Deliveries should include empty containers, containers with products and loose products. Ensure that the Collection/Delivery Without Products is NOT enabled. Ensure that the PDA is configured for Document Photo Capture. ![]() |
||||
6.01 | Start a collection job. | The PDA should prompt for collection of the containers and products. | ||
6.02 | Cancel an empty container | The PDA should prompt for a reason code for the exception. | ||
6.03 | Click the Image button. | The Photo application should start. | ||
6.04 | Capture an image. | Device dependant: ES400: The unit should allow image capture until you exit the photo application with the X. HTC: The photo application should return the image immediately. | ||
6.05 | Whe returned to the Exception screen, click the Browse Image button. | The unit will show the devices Image Browser application, for you to see the image captured. | ||
6.06 | Press Image again. | The device should allow you to capture another image as before. | ||
6.07 | Capture another image and browse the images. | The device should show the new image captured. | ||
6.08 | Cancel a container with products | As above tests 1-7. | ||
6.09 | Change a product qty in a container to any different value that that planned (including zero). | As above tests 1-7. | ||
6.10 | Change a loose product qty in a container to any different value that that planned (including zero). | As above tests 1-7 | ||
6.11 | Complete the job and capture the signature. | The device should prompt for document capture, with further results as tests 2-7 above. When complete, the job should be updated to complete with all images passed back to the server. The PDA should display the job list with the completed job removed from the list. | ||
6.12 | Repeat the above tests with a Delivery job | As above | ||
6.13 | Cancel a collection, delivery and service from the Job Details screen. | The exception screen should be shown, | ||
6.14 | Choose a reason. Follow tests 3-7 above. | As above. The job should be completed. The server shoould be update with the status of the job set to cancelled and the image. The PDA should display the Job List with the cancelled job removed from the list. |
Step | Action | Result | Remarks | P/F |
7 | Additional Functionality | |||
Create multiple collection and delivery jobs on a load an assign to a PDA user. Ensure that Driver Sign Collection and Delivery and Delivery Payment are enabled on the job group. ![]() |
||||
7.01 | Start a collection on the PDA. From the Job Details screen, click on the Contact tab. | Navigation and Call buttons should be present. | ||
7.02 | Click Navigation. | Copilot should start and the address should be loaded. The route should be planned to the address. | ||
7.03 | Click to close or hide CoPilot | The device should return to the EPOD application. | ||
7.04 | From the Job Details screen, click on the Contact tab and click Call. | The device should call the client on the number provided on the contact tab. | ||
7.05 | Complete the job. | Both the Driver and Customer should be prompted to sign for the job. | ||
7.06 | Check the box marked Sign Unchecked when signing for the job. | The job should complete. The PDA should return to the Job List screen, with the completed collection removed from the list. The server should be updated with the multiple signatures and the Sign Unchecked data entered. | ||
7.07 | Start a delivery. Repeat tests 2-4. | As above | ||
7.08 | Click OK to see the delivery. | As well as the normal tabs expected for the delivery, there should also be a Payment Received tab present. | ||
7.09 | Complete the details of the job. | The device will move to the Payment Received tab. | ||
7.10 | Check the Payment Received box and click OK. | The device should move to signature capture. | ||
7.11 | Repeat tests 5-6 | As above. | ||
7.12 | Start a service. Repeat tests 2-4 above. | As above. | ||
7.13 | Complete the service. | No Payment Received should be prompted. No Driver signature should be prompted. |