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 | |||
4.01 |
Step | Action | Result | Remarks | P/F |
5 | Services | |||
5.01 | Entry of all elements, based on configuration |
Step | Action | Result | Remarks | P/F |
6 | Imaging | |||
6.01 | Document Photo |
Step | Action | Result | Remarks | P/F |
7 | Additional Functionality | |||
7.01 | Navigation | |||
7.02 | Telephony | |||
7.03 | Multiple Signatures on Collection/Delivery |