Test Script Template

Doc Ref: SDM 315

Jul 27, 2015

ELABORATION

SDM.316

Test Scripts for Provisional BillNigerian Port AuthorityRevenue and Invoice Management SystemAuthor:Adegbite, AbimbolaCreation Date:July 27, 2015Last Updated:August 21, 2015Table of Contents

iiiDocument Control

iiiChange Record

iiiReviewers

iiiDistribution

11Billings Test Scripts

1Purpose

11.1.2Scope and Application

11.1.3Dependecies / Preconditions

21.1.4ENVIRONMENT

21.1.6ESTIMATED RUNNING TIME

32Billings Modules Test Sequence

133Open and Closed Issues

133.1Open Issues

133.2Closed Issues

Document Control

Change Record

3DateAuthorVersionChange Reference

27-Jul-2015Adegbite, AbimbolaDraft 1aNo Previous Document

18-Jul-2015Adegbite, AbimbolaUsability Testing

Reviewers

NamePosition

Olatunde AlaladeGeneral Manager, Software Development

Bisi AinaDirector, Solutions Delivery

Adeola AdepojuDirector, Corporate HQ

DistributionCopy No.NameLocation

1 Document RepositorySoftLAB

2

3

4

1 Billings Test Scripts

Purpose

The purpose of this Test Scripts document is to describe the step-by-step instructions that realize a test, enabling its execution. It is to provide the implementation of a subset of required tests in an efficient and effective manner. This Test Script, takes the form of textual instructions that are to be executed manually. Upon successful completion of the testing, the application will be considered ready for Everyday use. SMEs from all participating departments are intended to review this document. Approval of this document implies that reviewers are confident that following the execution of the test scripts, the resulting system will be considered fully-tested and eligible for implementation. The essence of a UAT is to have intending users of the application test it with realistic data. It gives Users an advanced Look of the Application in development which encourages adoption. Conducting user acceptance testing also demonstrates that the deploying organization is proactive and responsive to the needs of the people who are using the application.

User acceptance testing often uncovers problems and clarifies requirements for the application in development. The users might also find issues that are specific to aspects of the application that were not tested in other environments. Although detecting problems in earlier phases is Preferable in development, finding problems during user acceptance testing is still much better than finding problems after you upgrade to the Production environment.

Even if you ultimately decide to go into production with issues or limitations, you will know about these issues or limitations ahead of time. Key users are then prepared to communicate the problems and any workarounds to other users of the application.1.1.1 Scope and Application

This document will describe in detail each of the transaction steps. It is important to keep in mind that the transactions selected, represent a simulation of the production workload.

User Acceptance Testing is conducted to ensure that the system satisfies the needs of the business as specified in the functional requirements and provides confidence in its use. Modifications to the aforementioned requirements will be captured and tested to the highest level of quality allowed within the project timeline. The Applications system to be tested is the Revenue and Invoice Management System and the Modules to be tested include:

Provisional Bill Final Bill

1.1.2 Dependencies/Preconditions

The criteria that determine when testing can begin include the following:

No critical or major severity issues remaining from development

Correct version of application is moved into the user acceptance testing environment

Database modifications are complete and tables are populated with initial data

Roles and test user ids have been established

The criteria that determine when the testing is complete, or that continued execution provides no further benefit, include the following:

Successful execution of Test Scripts

No open critical, major or average severity issues unless the issue is determined to be low impact, low risk. To be reviewed with Project Manager, Test Manager and development team for acceptable resolution. When a defect is detected during Testing, testing should halt and the tester would log the defect in the Test Report. If the defect is not critical or major severity then testing may continue.

To resume a suspended test, the defects must be corrected and the application promoted to the testing environment. Initialization steps may be required to resume the test script depending on where the defect occurred.

1.1.3 UA Test DesktopsEach participant will be provided with an access to the application within the defined scope of testing. The tester will then log in and validate the sign-on data generates the expected results for each application. This includes, but is not limited to, correct menus, permissions, and general access.

Any applications identified as missing from the test workstation desktops should be formally requested and installed prior to testing.

1.1.4 SECURITY IMPLICATIONS

There arent any known security Implications using this test script to test the Application.

1.1.5 ESTIMATED RUNNING TIME

The running time for the test cannot be determined immediately as it is dependent on the Number individuals who will be engaging the application. To make this concept clearer it has been broken down to Requests/Second = (Users/Download Time + Think Time) (Requests/Page).

1.1.6 Comments

SoftAlliance and Resources Limited values and appreciates your comments as a user and reader of this manual. As we write, revise, and evaluate our documentation, your comments are the most valuable input we receive. If you would like to contact us regarding comments and suggestions on future releases of the Revenue and Invoice Management System, please use the following address or telephone numbers:

SoftAlliance and Resources Limited9, NERDC Road, Central Business District, Alausa Ikeja.

Email: [email protected] Billings Modules Test Sequence

The following are lists of the process steps to be tested. As the testing progresses, additional test conditions beyond those developed may arise. Should this occur, add the new conditions to the test and prepare the supporting control documentation.

Sequence #DateTimeTest NameTesterTest StatusNotes

RIMS-TS-003.01Login to Back Office

RIMS-TS-003.02Accessing Manifest Entry Screen

RIMS-TS-003.03Creating a Manifest Entry

RIMS-TS-003.04Accessing Provisional Bill Module

RIMS-TS-003.05Review/Creating a Provisional Bill

RIMS-TS-003.06Approval Requests and Notifications

RIMS-TS-003.07Provisional Bills

RIMS-TS-003.08Voyage Reconciliation

RIMS-TS-003.09Navigating The Final Bill Module

RIMS-TS-003.10Creating a Final Bill

RIMS-TS-003.11Final Bills

2.1.1 Test Forms

Test IDRIMS-TS-003.01Test Name: User Login To Back Office

Requirement(s)PC system to be Used must have access to the database. A browser must be installed

DateAuthorVersionDescription

27-Jul-2015Adegbite, AbimbolaDraft 1Test Case created.

18-Jul-2015Adegbite, AbimbolaUsability TestingTest Script Created.

ObjectivesUser Login to Back Office Successfully

Pre-conditionsThe User must be a staff of NPA. User must have powered on PC and opened a familiar browser.

Test DataUsername

Test Procedure

Step #Step DetailsExpected ResultActual Results/Status

01Navigate to login page at http://backoffice.nigerianports.orgUser should be able to see login page

02Provide valid usernameUser should be able to provide unused username

03 Provide valid passwordUser Should be able to provide a memorable password

04 Click on Login buttonUser should see the dashboard for Approval Requests & Notifications as well as the Concessionaire Lease Module

Comments

Completed

Test Log

DateTester NameActual Results(Pass/Fail)Comments

27/07/2015

Test IDRIMS-TS-003.02Test Name: Accessing Manifest Entry Screen



27-Jul-2015Adegbite, AbimbolaDraft 1Test Case draft created.

18-Jul-2015Adegbite, AbimbolaUsability TestingTest Script Created.

ObjectivesNavigate to The Manifest Entry Module

Pre-conditionsThe User Must have Logged in to the Back Office. User Must have the access right to perform action

Test Data

Test Procedure


01Click on Manifest Entry on the Main Menu.User should see a sub Menu with the title Manifest Entry

02Select Manifest Entry on the sub MenuUser would see a listing of Fields to be filled.

03Step Ends

Comments

Completed

Test Log


25/07/2015

Test IDRIMS-TS-003.03Test Name: Creating a Manifest Entry




18-Aug-2015Adegbite, AbimbolaUsability TestingTest Script Created.

ObjectivesCreate a Manifest Entry

Pre-conditionsUser must have navigated to the Manifest Entry Page.

Test DataShippers Manifest

Test Procedure


01Enter a Valid Customer IDUser should define the Customer ID

02Enter a Valid eSEN NumberUser should define a valid eSEN Number

03Click on the Search ButtonUser would see Fields like the Ship Name, Nationality of Vessel, GRT, NRT, IMO Number, and Length of Vessel. If the customer has an eSEN Number If not proceed to the Next Step.

04Select a CustomerUser would see a listing of registered NPA customers.

05Enter a Ship Name User should be able to define a Vessel Name

06Select The Nationality of the VesselUser should see a listing of Countries

07Select The Estimated Date of ArrivalUser should be able to select a date from the Date Picker.


09Select the Operation timeUser should see the list of Operation types.

10Select The Operating PortUser should see the list of available ports.

11Select the Jetty/TerminalUser should see a list of Jetty/Terminal based on the Port selected above.

12Select Destination/Departing CountryUser should see a List of Countries depending on Operation Type.

13Enter The Gross Registered TonnageUser should be able to define the GRT of the Vessel.

14Enter The Net Registered TonnageUser should be able to define the NRT of the Vessel.

15Enter The IMO NumberUser should define the Vessels IMO number.

16Enter the Length of VesselUser should define the Vessels Overall Length.

17Select the Type of VesselUser would see the listing of Various Vessel types and the Number of Days is driven by the vessel type selected.

18Enter the Vessels Rotation numberUser should define the Vessels Rotation number as supplied by NCS.

19Check the 2 Boxes User should click on the spaces in the Boxes to agree to T & Cs and also confirm Manifest Entries

20Click on the Create Manifest ButtonUser would see an Ok Message confirming the temporal storage of the Entry.

21Click on the New BOL ButtonUser would be directed to a Page to Enter BOL details

22Skip the BOL Reference Field and Enter the Total Gross ManifestedUser should define the Total Gross Manifested.

23Enter the Goods DescriptionUser should define the Goods Description.

24Select the BOL TypeUser would see a Listing of BOL types

25Enter the Unit/Tonnage/QuantityUser should define the total Unit/Tonnage/Quantity.

26Click on the Save Button to complete the EntryUser should be redirected to the Manifest Entry Page. Repeat Step 21 to 26 to enter as many BOLs as required. Step 1 26 applies for Additional Manifest and Part Discharge Entries.

27Click on Ship Entry Notices Via the Provisional Bill ModuleUser would see a the Newly created entry on top of list on the Page.

Comments

Completed

Test Log


12/01/2014

Test IDRIMS-TS-003.04Test Name: Accessing Provisional Bill Module



27-Jul-2015Adegbite, AbimbolaDraft 1Test Case draft created.


ObjectivesNavigate to The Provisional Bill Module

Pre-conditionsThe User Must have Logged in to the Back Office. User Must have the access right to perform action

Test Data

Test Procedure


01Click on Provisional Bill on the Main Menu.User should see a sub Menu

02Select Ship Entry Notices on the sub MenuUser would see a listing of Manifest Entries with their System IDs, eSEN Number, Account/Customer Name, Ship Name, Estimated Time Arrival, Loading Port, Gross Registered Tonnage, Workflow Status, and the Actions available to the Billing Officer.

03Step Ends

Comments

Completed

Test Log


26/08/2015

Test IDRIMS-TS-003.05Test Name: Review/Creating a Provisional Bill





ObjectivesReview / Creating a Provisional Bill

Pre-conditionsThe User Must have Logged in to the Back Office. User Must have navigated to The Provisional Bill Module.

Test Data

Test Procedure


01Find the Manifest to Be reviewed using the Search FieldUser should see the List of Entries based on the Search Value

02Select the Review Button on the Manifest EntryUser would see the Ship Entry Summary, Manifest Summary, Particulars of Dues for Dollar and Naira, List of Uncategorized items and the Amount and Amount in Figures

03Review Ship Entry Summary and Manifest Entry Summary.User should See important Fields for Billing The Entry.

04Scroll to The Dollar Particular of DuesUser will see a list of Bill Items on the Reviewed Manifest Entry

05Select all or Some of the Items to be Billed using the Button on the rightUser should be able to select the Bill item to be billed on the Reviewed Entry.

06Select Additional Items like Rebates, Penalties or Charges to be included on the Particulars of DuesUser should see a list of items to be added.

07Enter the Quantity and Click on ApplyUser would see the Page refresh with the Items added to the Particulars of Dues

08Scroll to The Naira Particular of DuesUser will see a list of Bill Items on the Reviewed Manifest Entry

09Select all or Some of the Items to be Billed using the Button on the rightUser should be able to select the Bill item to be billed on the Reviewed Entry.

10Select Additional Items like Rebates, Penalties or Charges to be included on the Particulars of DuesUser should see a list of items to be added.

11Click on The Button ApplyUser would see the page refresh with the Calculated Amount Below and VAT item added to the Particulars of Dues and the Create Provisional Bill Button at the Bottom of the Screen.

12Click on the Create Provisional Bill Button at the Bottom of the Screen to create a billPage will ask user to confirm Bill Creation. User will be redirected to The Ship Entry Notices Page with the Transaction ID in Green.

Comments

Completed


2/08/2015

Test IDRIMS-TS-003.06Test Name: Approvals Requests and Notifications



22-Aug-2015Adegbite, AbimbolaDraft 1Test Case created.


ObjectivesApprove requests and Notification of Requests

Pre-conditionsA bill must have been Sent for approval. User must have the Privileges to approve Bills

Test Data

Test Procedure


01Click on Dashboard Button on the Main Menu.User would be taken to a page where Approvals Requests and Notifications can be carried out

02Click On Requested by Me Tab to see a list of Approval Requested by the Logged in UserUser would see a list of Bills Requested to be approved by a supervising Officer.

This is After creating the bill, the First Level Approver (Checked by) would have been notified via mail of a new invoice that needs approval.

03Click On Assigned to Me Tab to see a list of Approval Requested by a Billing Officer.User would see a list of Bills to be approved by the Logged in Officer.

04Click On the Highlighted linked Process for the Invoice to be approvedThe action redirects to a Page showing a copy of the generated Invoice.

05Select the Next Available Status from the drop down menu and click ProceedThe User would have the option to reject or approve the Bill.

06Scroll Down and Select the next approver from the processor listThe User would see a List of the Next Available Processor/Approver.

07Enter In the Comment Field if AnyUser should be able to define comments if any.

08Click on The Browse Button if there are any relevant Document to be attachedUser should see a Pop up of File Explorer where User can pick a soft copy of the document to be attached.

09Click on Open button to attach the FileUser would see a partial Link to the file attached.

10Click on Submit for Next ApproverUser would be directed to the Dashboard with Successful Notification Message as the next approver that has been configured will get a mail notification and the process will begin again from step 01 for all the approvers that has been set up by the system administrator.

Comments

Completed

Test Log


12/01/2014

Test IDRIMS-TS-003.07Test Name: Provisional Bills





ObjectivesNavigate to The List of Provisional Bills

Pre-conditionsA Provisional bill must have been Created and Sent for approval. User must have navigated to the Provisional Bill Module

Test Data

Test Procedure


01Click on Provisional Bill on the Main Menu.User should see a sub-Menu

02Select Provisional Bill tab on the Sub Menu that dropsUser would be directed to a page displaying a list of Provisional Bills. That must have been created. Bills with the Status Pending have not been fully approved

Bills with the Status Approved have been fully approved. Such Bills can be printed for record keeping and handed over to the customer.

03To filter Click on the search field and enter a search value either by Account Name, Status or Bill NumberUser should be able to search from the list with either the Bill Number, Account Name and Status

04Click On the Highlighted linked View The action redirects to a Page showing a copy of the generated Provisional Bill/Invoice.

05Step Ends

Comments

Completed

Test Log


12/01/2014

Test IDRIMS-TS-003.08Test Name: Voyage Reconciliation





ObjectivesEntering Voyage Reconciliation Figures

Pre-conditionsA Provisional bill must have been Fully approval. User must have navigated to the Provisional Bill Module

Test Data

Test Procedure


01To filter Click on the search field and enter a search value either by Account Name, Status or Bill Number to find the Entry.User should be able to see a filtered entry based on search criteria.

02Click on Voyage Reconciliation Button on the Ship Entry Notices Page.User would be directed to a page displaying Ship Entry Summary, List of Fields to be Filled and a Button to submit reconciled Values at the Bottom of the Screen.

03Select Terminal/Jetty if requiredUser would see a List of Terminals/Jetties at Various Nigerian Ports.

04Enter The Gross Registered TonnageUser should be able to define the GRT of the Vessel.



07Enter the Number of Days If RequiredUser should be able to define the number of Berthing days of the Vessel.

08Enter The Reconciled Quantity of the General Cargo If anyUser should be able to define the Reconciled

09Enter Liquid Bulk QuantityUser should be able to define the Liquid Bulk Quantity.

10Enter Dry Bulk QuantityUser should be able to define the Dry Bulk Quantity.

11Enter 20" Container LadenUser should be able to define the 20 Container Laden Quantity.

12Enter 20" Container EmptyUser should be able to define the 20 Container Empty Quantity.

13Enter 40" Container LadenUser should be able to define the 40 Container Laden Quantity.

14Enter 40" Container EmptyUser should be able to define the 40 Container Empty Quantity.

15Enter Vehicles - Less than 15 CBMUser should be able to define Vehicles - Less than 15 CBM Quantity

16Enter Vehicles - Less than 16 CBM to 25 CBMUser should be able to define Vehicles - Less than 16 CBM to 25 CBM Quantity

17Enter Vehicles - Over 25 CBMUser should be able to define the Vehicles - Over 25 CBM Quantity

18Enter Vehicles - Trailer/MAFIUser should be able to define the Vehicles - Trailer/MAFI Quantity

19Click on the Button Submit Reconciled ValuesUser is redirected to the Ship Entry Notifications Page with the status of the Entry changed to Reconciled.

20Step Ends

Comments

Completed

Test Log


12/01/2014

Test IDRIMS-TS-003.09Test Name: Navigating the Final Bill Module





ObjectivesNavigate to The Final Bill Module

Pre-conditionsA Voyage Reconciliation Meeting must have been held. User must have navigated to the Final Bill Module

Test Data

Test Procedure


01Click on Final Bill on the Main Menu.User should see a drop down Menu

02Select Reconciled SheetsUser would be directed to a page displaying a list of Reconciled Sheets Created. Displaying the Account/Customer, Ship Name, Estimated Time of Arrival, Loading Port, G.R.T, Status, and the Action button View available.

03Step Ends

Comments

Completed

Test Log


12/01/2014

Test IDRIMS-TS-003.10Test Name: Creating a Final Bill





ObjectivesCreate a Final Bill

Pre-conditionsUser must have navigated to the Reconciled Sheets Page via the Final Bill Module

Test Data

Test Procedure


01Search for the Entry using the Search Field using any of the Column names.User should see a filtered entry.

02Select the Button ViewUser would be directed to a page Titled Final Bill Approval as well as Ship Entry Summary, Particular of Dues and the Button to create Final Bill.

03Click on the Create Final Bill Button.User would be directed to a page Titled Final Bills as well as Bill Number, Accounts, Value Date, Approval Status, Invoice Status and The View Bill Button.

04Step Ends

Comments

Completed

Test Log


12/01/2014

Test IDRIMS-TS-003.11Test Name: Final Bills





ObjectivesNavigate to The List of Provisional Bills

Pre-conditionsA Final bill must have been Created and Sent for approval. User must have navigated to the Final Bill Module

Test Data

Test Procedure


01Click on Final Bill on the Main Menu.User should see a sub-Menu

02Select Final Bill tab on the Sub Menu that dropsUser would be directed to a page displaying a list of Final Bills. That must have been created. Bills with the Status Pending have not been fully approved

Bills with the Status Approved have been fully approved. Such Bills can be printed for record keeping and handed over to the customer.

03To filter Click on the search field and enter a search value either by Account Name, Status or Bill NumberUser should be able to search from the list with either the Bill Number, Account Name and Status

04Click On the Highlighted linked View The action redirects to a Page showing a copy of the generated Provisional Bill/Invoice.

05Step Ends

Comments

Completed

Test Log


12/01/2014

3 Open and Closed Issues

Note: Add open issues that you identify while writing or reviewing this document to the open issues section. As you resolve issues, move them to the closed issues section and keep the issue ID the same. Include an explanation of the resolution.

When this work product is complete, any open issues should be transferred to the project- or process-level Issue Log (Manage focus area) and managed using a project level Issue Form (Manage focus area). In addition, the open items should remain in the open issues section of this work product, but flagged in the resolution column as being transferred.

3.1 Open Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

3.2 Closed Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

SIGN OFF

1. NAME:

SIGNATURE

DATE

2. NAME

SIGNATURE

DATE

ivBillings Modules Test Sequence 1 If > 1 19 of 23 = - Sec1 20 8 8

Revenue and Invoice Management SystemSDM.316 Test Scripts

Documents

Test Script Template