Electronic Forms - MITA1 · Electronic Forms User Acceptance Testing (UAT) - Guidelines Date: 06 th...

57
Malta Information Technology Agency, Gattard House, National Road, Blata l-Bajda HMR 9010 Malta Telephone: (+356) 21234710 Facsimile: (+356) 21234701 Web Site: www.mita.gov.mt Electronic Forms User Acceptance Testing (UAT) - Guidelines Date: 06 th March, 2012 Version: 1.0 Department: eGovernment Direction, Execution and Operations

Transcript of Electronic Forms - MITA1 · Electronic Forms User Acceptance Testing (UAT) - Guidelines Date: 06 th...

Malta Information Technology Agency, Gattard House, National Road, Blata l-Bajda HMR 9010 Malta Telephone: (+356) 21234710 Facsimile: (+356) 21234701

Web Site: www.mita.gov.mt

Electronic Forms

User Acceptance Testing (UAT) - Guidelines

Date: 06th March, 2012

Version: 1.0 Department: eGovernment Direction, Execution and Operations

Page ii

Document Control Information

01. Document reference

EGOV-GDL-UserAcceptanceTestingGuidelines-v1.0.doc

02. Document type

Guidelines

03. Security classification

Unclassified

04. Synopsis

This document is intended to assist the Testing Execution Team in thoroughly testing their respective forms. This also helps to ensure that the User Acceptance testing adequately covers for both the front-end and back-end websites.

05. Document control

Author Change controller Distribution controller

eGovernment Projects, Execution and Operations

eGovernment Projects, Execution and Operations

eGovernment Projects, Execution and Operations

This document may be viewed and/or downloaded from the EDEV Portal, which maintains the latest issues of all documents and forms.

06. Authorisation

Issuing authority Approval Authority Client Approval (*)

Signature / Date Signature / Date Signature / Date

(*) Client approval may be attached as an appendix and may thus replace the signature.

07. Modification history

Version Date Comments

Draft Version 0.1 16/06/2011 First draft release issued for internal review.

Draft Version 0.2 05/09/2011 Second draft release issued for internal review.

Draft Version 0.3 15/09/2011 Third draft release issued for internal review.

Draft Version 0.4 21/12/2011 Fourth draft release issued for internal review.

Draft Version 0.5 03/02/2012 Fifth draft release issued for internal review.

First Release 1.0 06/03/2012 First release

Page iii

Table of Contents

DOCUMENT CONTROL INFORMATION ................................................................................................................................. II

TABLE OF CONTENTS............................................................................................................................................................ III

01. DEFINITIONS ...............................................................................................................................................................1

02. SCOPE .........................................................................................................................................................................2

02.1 ELECTRONIC FORMS OVERVIEW ..................................................................................................................................2 02.2 PURPOSE AND SCOPE OF THE USER ACCEPTANCE TESTING ..........................................................................................2

02.2.1 User Acceptance Testing Procedures .............................................................................................................3 02.2.2 Personnel Roles for User Acceptance Testing................................................................................................3 02.2.3 Checklist for successful UAT Levels ...............................................................................................................4 02.2.4 Incident Report ................................................................................................................................................4

APPENDIX A – SAMPLE USER ACCEPTANCE CHECK LIST ................................................................................................5

A1. TESTING THE ‘STANDARD’ PAGE ELEMENTS............................................................................................................5 A2. TESTING THE “INTRODUCTION” PAGE .......................................................................................................................7 A3. TESTING THE “PERSONAL DETAILS” PAGE (IF APPLICABLE) .......................................................................................9 A4. TESTING THE “ORGANISATION” PAGE (IF APPLICABLE) .............................................................................................12 A5. TESTING THE “BUSINESS DETAILS” PAGE (IF APPLICABLE).......................................................................................14 A6. TESTING THE “QUALIFICATIONS” PAGE (IF APPLICABLE)...........................................................................................16 A7. TESTING THE “TRAINING” PAGE (IF APPLICABLE) .......................................................................................................18 A8. TESTING THE “WORK EXPERIENCE” PAGE (IF APPLICABLE) .....................................................................................20 A9. TESTING THE “REFEREES” PAGE (IF APPLICABLE) .....................................................................................................22 A10. TESTING THE “ATTACHMENTS” PAGE (IF APPLICABLE)............................................................................................24 A10. TESTING THE “ATTACHMENTS” PAGE IF UNAUTHENTICATED (ANONYMOUS USER) (IF APPLICABLE) ............................26 A11. TESTING THE “SIGNATURE” PAGE..........................................................................................................................27 A12. TESTING THE “SUBMIT” PAGE .................................................................................................................................29 A13. TESTING THE “MAILBOX” – AFTER SUBMITTING FORM........................................................................................31 A14. TESTING THE “VETTING” STAGE - ADMINISTRATION SIDE ..................................................................................33 A15. TESTING THE “MAILBOX” – FORM RETURNED FOR AMENDMENTS DURING VETTING (IF APPLICABLE) ............36 A16. TESTING THE COMMENTS SECTION ......................................................................................................................37 A17. TESTING THE “PAYMENT” PAGE (IF APPLICABLE) .....................................................................................................39 A18. TESTING THE “CASH OFFICE” STAGE - ADMINISTRATION SIDE (IF APPLICABLE)..................................................40 A19. TESTING THE “APPROVAL” STAGE – ADMINISTRATION SIDE..............................................................................42 A20. TESTING THE “COMMITTEE” / “BOARD” STAGE – ADMINISTRATION SIDE (IF APPLICABLE)..................................45 A21. TESTING THE “PAYMENT VERIFICATION” STAGE – ADMINISTRATION SIDE (IF APPLICABLE)......................................48 A22. TESTING THE “MAILBOX” – FORM COMPLETED (IF APPLICABLE) ............................................................................50 A23. TESTING THE “MAILBOX” – AFTER SAVING FORM AS A DRAFT (IF APPLICABLE)...................................................51 A24. TESTING THE “MAILBOX” – FORM WITHDRAWN (IF APPLICABLE)............................................................................53

APPENDIX B – INCIDENT REPORT ......................................................................................................................................54

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 1

01. Definitions

MITA Malta Information Technology Agency.

eForms The platform used to deliver eServices to the Government of Malta.

eGovernment Electronic Government

eID Electronic Identity

eServices Services composed of forms and workflows delivered using the eForms Platform.

UAT User Acceptance Testing

e-Form An eForm is an electronic form which can be completed on-line through the e-Forms Service and submitted to the e-Service Provider.

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 2

02. Scope

02.1 Electronic Forms Overview

As a Government platform, the electronic forms (eForms) solution enables all Government entities to publish any of their services as electronic services (eServices) with minimal effort and cost. Thus, it provides Customers/Citizens the facility to use Government services from the comfort of their own home, by accessing a single portal www.forms.mygov.mt. In line with the Government strategy to combine its e-Presence homogeneously rather than having isolated entities offering their own respective services, the eForms Solution is offering a two-fold advantage solution: • Benefits for the Public Service Unit

o Ease of introduction of e-Services and subsequent modification through the use of a predefined framework,

o Reduce queuing at Government Offices, o Implement a common platform for all Government Services – One-stop-shop, o Reduce unnecessary Government paperwork, o Improve traceability through a standard and complete audit trail.

• Benefits for client/citizen

o Common interface for citizens to engender familiarity with Government eServices, o Allows Customers/Citizens to use the Government services at any time from the comfort

of their own homes, o eForms are much more traceable (i.e. they are not susceptible to loss like physical forms

are), o Make it easier for citizens to monitor the progress of any forms submitted to Government

Entities, o Pre-filling of forms where the Government already has the information such as Identity

Card Number, Name, Surname, Permanent Address etc. 02.2 Purpose and scope of the User Acceptance Testing

User Acceptance Testing (UAT) on eForms is required to verify that the e-Service concerning the Entity is functioning well together with the business environment and further fulfil the user’s expectations as defined in the Entity’s business requirements and functional specifications. The UAT procedure also provides a formal means for validating the e-Form and actually checking that it meets the necessary user requirements both from the users’ and customer’s perspectives before moving the form(s) into production. Therefore, this is facilitating the eventual signoff of the e-Service as delivered by the Contractor. In addition, the UAT involves the users and business managers in an actual test cycle. This helps them gain the necessary confidence that the e-form in question, meets their real world business needs. To ensure effective UAT, a test case check list (Appendix A – Sample User Acceptance Check List) and a sample incident report (Appendix B – Incident Report) have been provided. During this type of testing, the specific focus is to mimic the exact real world usage of the form.

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 3

02.2.1 User Acceptance Testing Procedures

In view that neither the eGovernment Department within the Malta Information Technology Agency (MITA) nor the software provider (contractor), are experts in each and every Entity’s business process, a selected team represented by an eGovernment Leader, from each Entity, need to be identified to execute the UAT checklist test cases and compile any further related incident reports and test cases. The UAT Team should generally provide a good representation of the real world end users. The “Team” should thus comprise of the actual end users who will be using the respective form(s). The best candidates for UAT are:

• Staff directly impacted by the upcoming system and business process changes, • Frequent users of current process, • Individuals with a sound understanding of business process in the areas they represent, • Individuals with the necessary time to commit to this endeavor, • Individuals willing to try various methods to see what works and what does not work.

In order to help each and every Entity in their User Acceptance Testing, MITA has designed a set of guidelines, which can be used as a model to extend the test cases as required. These test cases can be created using various use cases identified during the requirements definition stage. The test cases ensure proper coverage of all scenarios during testing. 02.2.2 Personnel Roles for User Acceptance Testing

Operational Testers: These are the people who have the most knowledge of what is required for the day-to-day running of the Entity. These people shall be the ones actually using the eForms system. Authorised Personnel: This is someone who has the authority to approve the conclusion (successful or otherwise) of User Acceptance Testing. UAT should be conducted by ‘Operational Testers’ and should be supervised by an ‘Authorised Personnel’. Issues encountered during the UAT should be collated into one report, the incident report (Appendix B – Incident Report) and submitted to the Contractor. It is imperative to keep the MITA eGovernment team in copy (Email Address: [email protected] ) to monitor the progress. If any issues are identified during UAT, in order to ensure that no additional issues have arisen following the updates, the Entity should perform another full iteration of testing (including a regression test), following a confirmation from the Contractor that:

a. All reported issues have been fixed and; b. the Contractor has fully tested the updated form(s)

The Contractor should also provide adequate and updated testing documentation. The Entity should then be in a position to confirm successful UAT closure. This means that the following conditions have been met:

i. The Entity has fully tested the functionality of the e-Service. ii. If applicable, all the issues encountered have been reported to the Contractor. iii. If applicable, the Contractor has fixed all the issues reported by the Entity. iv. If applicable, the Contractor has fully tested the updated system. v. If applicable, the Entity has fully re-tested the updated functionality of the e-Service.

Once the User Acceptance Testing has been concluded successfully and the necessary approval is obtained, the eForm is ready to go live.

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 4

02.2.3 Checklist for successful UAT Levels

The User Acceptance Testing on eForms has to be performed on a number of levels as follows:

i. General UAT (Common functionality across the pla tform) Check that all the information (e.g. Contact Details, Data Protection Statement, etc) provided in the Information Sheet is correct.

ii. Information provided by the Competent Authority Check that all information (including hints and upload functionality for the necessary documentation) is present on the form.

iii. Application form details

Check that the appropriate validations (such as mandatory fields and Entity’s business validations) are being enforced.

iv. Submission verification

The form can be successfully submitted to the Competent Authority and back to the user for additional detail and / or documentation.

v. Workflow verification The Approval workflow works as required (e.g. Vetting, Approval, Rejection, Payment, etc.)

vi. Payment verification

Payment functionality (if applicable) is verified.

vii. Timeline verification Details on the timeline screen are correct (e.g. the Competent Authority details, stages in the workflow, etc). Additionally, ensure that the timeframes on the timeline are correct and reflect the actual processes.

A more comprehensive checklist is provided in Appendix A – Sample User Acceptance Check List. 02.2.4 Incident Report

The Incident Report is intended for use by the Competent Authority (Entity). An incident report template (refer to Appendix B - Incident Report) has been prepared for the Entity to report any issues encountered during the User Acceptance Phase. UAT checklist (refer to Appendix A - Sample User Acceptance Check List) can be used as part of the User Acceptance phase; however it should not be the sole source of test cases. Besides the UAT checklist, the Client might choose to create his own tests or use a combination of both. Both the User Acceptance Check Lists and Incident Reports are meant to be handed to the Contractor to review, replicate and further resolve any issues highlighted in the Incident Report. It is recommended that a common incident report is used for every e-Form within an e-Service. This should be updated by the Entity to keep track of all the issues encountered, together with details of their resolution. Kindly update and modify the incident report template provided in Appendix B – Incident Report, as deemed necessary.

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 5

Appendix A – Sample User Acceptance Check List

A1. TESTING THE ‘STANDARD’ PAGE ELEMENTS

Yes No Comments Does the “ search” help you find the required eForm?

• Enter keyword to perform search for a particular eForm. Does the required eForm load successfully in the search results?

E.g. If application name is “Application for a VRT Contracted Operator”, the keyword to find the eform can be “contracted”.

Yes No Comments Links redirect to expected page/s? Click on every link to verify that the expected page is displayed.

• Does the “Entity’s” link provide links to websites about the entity providing this Service?

• Does the “Related Links” link provide related links about the legislation, standards and guidelines that govern this service?

• Does the “Click for submission guidelines” provide help tips, including the information required in order to fill-in the form, applicable fees and what goes on after submitting the application?

• Does the “Data Protection Statement” show a statement that the applicant will have to agree upon, before submitting the electronic form?

• Does the “Click here to print form” link provide an option to open the form in PDF, giving the citizen the possibility to print, fill, and send application by post?

• Are the contents when clicking on links, valid and correct?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 6

Yes No Comments Does the language of the application display correc tly? Click on the language flag located top right of the page to verify that the website language is changing accordingly.

• If the flag located top right is the Maltese flag, is the text of the application (including PDFs and acknowledgements) loaded all in English?

• If the flag located top right is the English flag, is the text of the application (including PDFs and acknowledgements) loaded all in Maltese?

Yes No Comments Does the Information page display properly?

• Is the “Application Form Title” correct? • Is the Entity logo correct? • Does the logo represent the Entity that provides this service? • Does clicking on the Entity logo redirect the applicant to the Entity’s

website?

• There are forms that can be filled-in either by the applicant, or by a delegate or a professional on behalf of the citizen or business. Is the individual presented with the option, “How will you be filling in the online form”, if both methods are available?

• Does the “Important Notice” attract your attention? It is important for the applicant to take note of the latter before looking further into how to start off the form.

• Do the “Competent Authority Details” represent the Entity? • Are the spelling and/or grammar correct? • Is the page rendering well (i.e. layout looks good and no element in

the page is being overwritten/partially hidden, etc)?

Yes No Comments Testing the “ continue to online form” button

• Does the “continue to online form” take you to a new page with an introduction about the application?

Yes No Comments Does the “ Please Wait” (grey background) display properly while the form is loading?

• Are the form buttons and fields read-only during the loading of the application?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 7

A2. TESTING THE “INTRODUCTION” PAGE

Yes No Comments Does the “ Introduction” page display properly?

• Is the “Title of Activity” correct? • Does the “Competent Authority Details” represent the Entity? • Does the “Competent Authority Details Email Address” result in an email to

an appropriate person/group?

• Is the Information on the application meaningful and correct? • Are the hints on the right (grey box) detailed enough to guide

applicant on what to fill in?

• Is the “Introduction” sub-heading box on the left highlighted? • Are the section headings on the left (under the “Introduction” box)

grouped well?

• Is the “Next” button visible and enabled? • Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Yes No Comments Does the navigation through the sections work well?

• Click on the sub-heading boxes on the left to go from one section to another. Are all sections in order?

• When navigating from one section to another using the “Next” and “Previous” buttons, are all sections in order (e.g. “Introduction”, “Personal Details”, “Testing Station”, “Attachments”, “Signature” and “Submit”)?

• There are forms where the applicant has to attach certain documentation on submission. When navigating from one section to another, using the “Next” and the “Previous” buttons, is the “Would you like to proceed to the attachments page” dialog box opened?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 8

Yes No Comments

• Click on the “OK” option of the dialog box. Is the attachments page opened?

• Click on the “Cancel” option of the dialog box. Is the request to open the attachments’ page cancelled?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 9

A3. TESTING THE “PERSONAL DETAILS” PAGE (if applicable)

Yes No Comments Does the “ Personal Details” page display properly?

• If logged in using the electronic identity (eID), are the “ID Number” , “Surname”, and “Name” read-only, and marked as mandatory with an asterisk (*)?

• Is the “Title” drop-down list changed to a free text field, if the ‘[Other…]’ option is selected (in case the applicant’s title is not in the list provided)?

• If the applicant keys-in a new title (that does exist in the list), does the system accept it?

• Are the “Place of Birth”, “Date of Birth” and “Nationality” marked as mandatory with an asterisk (*)? (if applicable)

• Does the “Name” reject digits? • Does the “Surname” reject digits? • Does the “Place of Birth” accept spaces? (if applicable) • Does the calendar (near the “Date of Birth” field) load well and work in

all date fields?

• Are there any validations on the “Date of Birth”? (if applicable) • The “Date of Birth” cannot be in the future. Is the applicant prompted

to correct date when a future date is captured? (if applicable)

Yes No Comments Do the “ Address” details display properly?

• Is the “Permanent Address” filled automatically? • If the country selected from the list is Malta, is the “Town” showing a

list of towns and cities in Malta and Gozo?

• If the country selected from the list is a foreign country (i.e. not Malta), is the “Town” field changed to a free text field?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 10

Yes No Comments • Does the “House No” field accept alphanumeric characters

(E.g. Apt 1/A, Flat 12-14 etc.)?

• Does the “House Name” field accept alphanumeric characters? • Does the “Street” accept alphanumeric characters? • Does the “Post Code” field accept alphanumeric characters

(E.g. VLT 3000)?

• Is the applicant prompted to fill in all mandatory fields (marked with an asterisk [*]) that are left blank and guided to which fields are still not filled?

• Can fields that are not mandatory be left blank? Yes No Comments Do the Contact details display properly?

• Does the “Telephone” field reject the alphabetical characters? • Is the applicant prompted to fill in the “Telephone” field if this is

mandatory, i.e. marked with an asterisk (*) and it is left blank?

• Can the “Telephone” field, if it is not mandatory be left blank? • Does the “Mobile No” field reject the alphabetical characters? • Is the applicant prompted to fill in the “Mobile No” field if this is

mandatory, i.e. marked with an asterisk (*) and it is left blank?

• Can the “Mobile No” field, if it is not mandatory be left blank? • Does the “Fax No” field reject the characters? • Is the applicant prompted to fill in the “Fax No” field if this is

mandatory, i.e. marked with an asterisk (*) and it is left blank?

• Can the “Fax No” field, if it is not mandatory, be left blank? • Does the “Email Address” field accept both characters and digits? (if

applicable)

• Is the “Email Address” rejected if an incorrectly formatted (invalid) email address is entered? (if applicable)

• Is the applicant prompted to fill in the “Email Address” field if this is mandatory, i.e. marked with an asterisk (*) and it is left blank?

• Can the “Email Address” field, if it is not mandatory, be left blank? Yes No Comments There are instances where the fields marked with tw o (2) asterisks [**] can be left blank.

• Is help provided and is help detailed enough on the right (grey box) to guide applicant what to fill-in?

• Can these fields be left blank? Yes No Comments Does the “ Personal Details” page display properly?

• Is the “Personal Details” sub-heading box on the left highlighted? • Are the applicant’s details filled automatically? • Are all mandatory fields marked with an asterisk (*)? • Do all fields accept the required characters and reject unnecessary

characters?

• Are restrictions enforced in the current business process reflected in this eForm?

• Are the hints on the right (grey box) detailed enough to guide applicant on what to fill-in?

• Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 11

Yes No Comments Does the PDF version of the eForm work as expected?

• Click on the “Open PDF” button. Is the “Do you want to open or save this file?” dialog box opened?

• If the “Open” option is selected, does the form load properly in PDF? • If the “Save” option is selected, is the “Save As” dialog box opened

and PDF saved in the requested path?

• Is the data filled in the form displayed in the PDF version of the e-Form if the Save for Later button is not clicked?

Yes No Comments Does the “ Save For Later” button function properly? Click on the button to verify that it is working as expected.

• Is the application saved in the citizen’s mailbox under the “Attention Required” section with status set to ‘Application being drafted by Applicant’?

• When the application is selected, is the form loaded with the contents as initially saved?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 12

A4. TESTING THE “ORGANISATION” PAGE (if applicable)

Yes No Comments Do the Organisational Details display properly?

• Are all fields editable? • Does the “Name of Organisation” accept alphanumeric characters? • Does the “VAT Number” accept alphanumeric characters (E.g.

MT12345678)? (if applicable)

• Are there any validations on the “VAT Number”, such as the format etc? (if applicable)

• Is the applicant prompted to fill in all mandatory fields (marked with an asterisk [*]), and guided to which fields still need to be filled?

• Can fields that are not mandatory, be left blank? Yes No Comments Does the “ Contact Address” display properly?

• If data is not automatically populated, is the “Country” set to “--SELECT ONE--“ by default?

• If data is not automatically populated, is the “Town” set to “--SELECT ONE--“ by default?

• If data is not automatically populated, are the “House No”, “House Name”, “Street” and “Post Code” fields left blank, by default?

• If the country selected from the list is Malta, is the “Town” showing a list of available towns and cities in Malta and Gozo?

• If the country selected from the list is a foreign country (i.e. not Malta), is the “Town” field changed to a free text field?

• Does the “House No” field accept alphanumeric characters (E.g. Apt 1/A, Flat 12-14 etc.)?

• Does the “House Name” field accept alphanumeric characters? • Does the “Street” field accept alphanumeric characters? • Does the “Post Code” field accept alphanumeric characters

(E.g. VLT 3000)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 13

Yes No Comments

• Is the applicant prompted to fill in all mandatory fields (marked with an asterisk [*]), and guided to which fields are left blank?

• Can fields that are not mandatory, be left blank? Yes No Comments Do the Contact details (such as “Telephone”, “Mobile No.”, “Fax No.” and “Email Address”) display properly?

• If data is not automatically populated, are the “Telephone”, “Mobile No”, “Fax No” and “Email Address” fields left blank, by default?

• Does the “Telephone” field reject the alphabetical characters? • If the “Telephone” field is mandatory i.e. it is marked with an

asterisk, is the applicant prompted to fill it in if it is left unfilled?

• If the “Telephone” field is not mandatory, can it be left blank? • Does the “Mobile No” field accept digits only? • Is the applicant prompted to fill in the “Mobile No” field if this is

mandatory, i.e. marked with an asterisk (*) and it is left blank? Alternatively, if the “Mobile No” field is not mandatory, it can be left blank.

• Does the “Fax No” field accept digits only? • Is the applicant prompted to fill in the “Fax No” field if this is

mandatory, i.e. marked with an asterisk (*) and it is left blank? Alternatively, if the “Fax No” field is not mandatory, it can be left blank.

• Does the “Email Address” field accept both characters and digits? (if applicable)

• Is the “Email Address” rejected if an incorrectly formatted (invalid) email address is entered? (if applicable)

• Is the applicant prompted to fill in the “Email Address” field if this is mandatory, i.e. marked with an asterisk (*) and it is left blank? Otherwise, if the “Email Address” field is not mandatory, it can be left blank.

Yes No Comments Does the “ Organisation” page display properly?

• Is the “Organisation” sub-heading box on the left highlighted? • Are all mandatory fields marked with an asterisk (*)? • Do all fields accept the required characters and reject unnecessary

characters?

• Are restrictions enforced in the current business process reflected in this e-form?

• Are the hints on the right (grey box) detailed enough to guide applicant on what to fill-in?

• Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 14

A5. TESTING THE “BUSINESS DETAILS” PAGE (if applicable)

Yes No Comments Does the “ Business Details” page display properly?

• Does the “Name under which applicant proposes to trade” accept alphanumeric characters?

• Does the “Company Registration Number” accept alphanumeric characters?

• Are there any other validations on the “Company Registration Number” such as the format etc? (if applicable)

• Does the “VAT Registration Number” accept alphanumeric characters (E.g. MT12345678)? (if applicable)

• Are there any other validations on the “VAT Registration Number” (such as the format etc? (if applicable)

Yes No Comments Does the “ Office Address” display properly?

• If data is not automatically populated, is the “Country” set to “--SELECT ONE--“ by default?

• If data is not automatically populated, is the “Town” set to “--SELECT ONE--“ by default?

• If data is not automatically populated, are the “House No”, “House Name”, “Street” and “Post Code” fields left blank, by default?

• If the country selected from the list is Malta, is the “Town” showing a list of available towns and cities in Malta and Gozo?

• If the country selected from the list is a foreign country (i.e. not Malta), is the “Town” field changed to a free text field?

• Does the “House No” field accept alphanumeric characters (E.g. Apt 1/A, Flat 12-14 etc.)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 15

Yes No Comments • Does the “House Name” field accept alphanumeric characters? • Does the “Street” field accept alphanumeric characters? • Does the “Post Code” field accept alphanumeric characters

(E.g. VLT 3000)?

• Is the applicant prompted to fill in all mandatory fields (marked with an asterisk [*]), and guided to which fields are still left blank?

• Can fields that are not mandatory, be left blank? Yes No Comments Does the “ Address in Malta for service or process or other notices” display properly?

• If data is not automatically populated, is the “Country” set to “--SELECT ONE--“ by default?

• If data is not automatically populated, is the “Town” set to “--SELECT ONE--“ by default?

• If data is not automatically populated, are the “House No”, “House Name”, “Street” and “Post Code” fields left blank, by default?

• If the country selected from the list is Malta, is the “Town” showing a list of available towns and cities in Malta and Gozo?

• If the country selected from the list is a foreign country (i.e. not Malta), is the “Town” field changed to a free text field?

• Does the “House No” field accept alphanumeric characters (E.g. Apt 1/A, Flat 12-14 etc.)?

• Does the “House Name” field accept alphanumeric characters? • Does the “Street” field accept alphanumeric characters? • Does the “Post Code” field accept alphanumeric characters

(E.g. VLT 3000)?

• Is the applicant prompted to fill in all mandatory fields (marked with an asterisk [*]), and guided to which fields are left blank?

• Can fields that are not mandatory, be left blank? Yes No Comments Does the page display properly?

• Is the “Business Details” sub-heading box on the left highlighted? • Are all mandatory fields marked with an asterisk (*)? • Do all fields accept the required characters and reject unnecessary

characters?

• Are restrictions enforced in the current business process reflected in this eform?

• Are the hints on the right (grey box) detailed enough to guide applicant on what to fill-in?

• Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 16

A6. TESTING THE “QUALIFICATIONS” PAGE (if applicable)

Yes No Comments Do the “ Qualifications” details display properly?

• Does the “Full title of degree” field accept alphanumeric characters and spaces (e.g. BSc in Computing and Information Systems (Hons) – Year 2011)?

• Is the applicant prompted to fill in the “Full title of degree” field if this is mandatory, i.e. marked with an asterisk (*) and it is left blank? Otherwise, if the field is not mandatory, it can be left blank.

• Does the “Specialisation” field accept alphanumeric characters and spaces?

• Is the applicant prompted to fill in the “Specialisation” field if this is mandatory, i.e. marked with an asterisk (*) and it is left blank? Otherwise, if the field is not mandatory, it can be left blank.

• Does the “Issuing Body” field accept alphanumeric characters and spaces?

• Is the applicant prompted to fill in the “Issuing Body” field if this is mandatory, i.e. marked with an asterisk (*) and it is left blank? Otherwise, if the field is not mandatory, it can be left blank.

• Does the “Year of Issue” field reject any alphabetic characters? • Does the “Year of Issue” field accept only 4 digits as a format (e.g.

2008)?

• Are there any other validations on the “Year of Issue” (such as Year cannot be in the future etc)?

• If the “Year of Issue” cannot be in the future, is the applicant prompted to correct it when entered in the future? (if applicable)

• Is the applicant prompted to fill in the “Year of Issue” field if this is mandatory, i.e. marked with an asterisk (*) and it is left blank? Otherwise, if the field is not mandatory, it can be left blank.

• Are five (5) Qualification lines enough to be filled-in? Yes No Comments Does the “ Qualifications” page display properly?

• Is the “Qualifications” sub-heading box on the left highlighted? • Are all mandatory fields marked with an asterisk (*)? • Do all fields accept the required characters and reject unnecessary

characters?

• Are restrictions enforced in the current business process reflected in this eform?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 17

Yes No Comments • Are the hints on the right (grey box) detailed enough to guide

applicant on what to fill-in?

• Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is the Qualifications section user-friendly and guides applicant to

what should be done?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 18

A7. TESTING THE “TRAINING” PAGE (if applicable)

Yes No Comments Does the “ Training” (1 to 4) display properly?

• Does the “From” field reject alphabetic characters? • Does the “From” field accept only dates in the “dd/mm/yyyy” format

(e.g. 06/02/2011)?

• Are there any logical input restrictions (e.g. a number greater than 12 cannot be entered in the month) in the “From” field?

• Are there any other validations on the “From” date (such as date cannot be in the future etc)?

• If the “From” date cannot be in the future. Is the applicant prompted to correct date when future date is captured? (if applicable)

• Does the calendar (near the “From” field) load well and work in all date fields?

• Does the “To” field reject alphabetic characters? • Does the “To” field accept only dates in the “dd/mm/yyyy” format

(e.g. 06/02/2011)?

• Are there any logical input restrictions (E.g. a number greater than 12 cannot be entered in the month) in the “To” field?

• Are there any other validations on the “To” date (such as date cannot be in the future etc)?

• If the “To” date cannot be in the future. Is the applicant prompted to correct date when future date is captured? (if applicable)

• Does the calendar (near the “To” field) load well and work in all date fields?

• Are there any validations that the “From” and “To” fields must be in a valid range (i.e. “From” date must be smaller than the “To” date)?

• Does the “Establishment or Organisation” accept alphanumeric characters and spaces?

• Does the “Details of Training Undertaken” accept alphanumeric characters and spaces?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 19

Yes No Comments • Is the applicant prompted to fill in all mandatory fields (marked with

an asterisk [*]), guided to which fields are still left blank?

• Can fields that are not mandatory, be left blank? • Is the applicant allowed enough space to enter the additional details

of training undertaken?

Yes No Comments Does the “ Training” page (1 to 4) display properly?

• Is the “Training” sub-heading box on the left highlighted? • Are all mandatory fields marked with an asterisk (*)? • Do all fields accept the required characters and reject unnecessary

characters?

• Are restrictions enforced in the current business process reflected in this eform?

• Are the hints on the right (grey box) detailed enough to guide applicant on what to fill-in?

• Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is the Training section user-friendly and guides applicant to what

should be done?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

Yes No Comments Does the “ Next” button take you in a new page to fill in the othe r Training (5 to 8)? (if applicable)

• Click button to fill in the 5th, 6th, 7th and 8th training details. Repeat the following checklists:

• ‘Does the “Training” (1 to 4) display properly?’ and • ‘Does the “Training” page (1 to 4) display properly?’

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 20

A8. TESTING THE “WORK EXPERIENCE” PAGE (if applicable)

Yes No Comments Does the “ Work Experience” (Page 1 of 3) display properly?

• Does the “From” field reject alphabetic characters? • Are there any logical input restrictions (E.g. a number greater than

12 cannot be entered in the month) in the “From” field?

• Does the calendar (near the “From” field) load well and work in all date fields?

• Does the “To” field reject alphabetic characters? • Are there any logical input restrictions (E.g. a number greater than

12 cannot be entered in the month) in the “To” field?

• Does the calendar (near the “To” field) load well and work in all date fields?

• Are there any validations that the “From” and “To” fields must be a valid range (i.e. “From” date must be smaller than the “To” date)?

• Does the “Organisation” field accept alphanumeric characters and spaces?

• Does the “Position Held / Job Title” field accept alphanumeric characters and spaces?

• If the country selected from the list is Malta, is the “Town” showing a list of available towns and cities in Malta and Gozo?

• If the country selected from the list is a foreign country (i.e. not Malta), is the “Town” field changed to a free text field?

• Does the “House No” field accept alphanumeric characters (E.g. Apt 1/A, Flat 12-14 etc.)?

• Does the “House Name” field accept alphanumeric characters? • Does the “Street” field accept alphanumeric characters? • Does the “Post Code” field accept alphanumeric characters

(E.g. VLT 3000)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 21

Yes No Comments • Does the “Email Address” field accept both characters and digits? (if

applicable)

• Is the “Email Address” rejected if an incorrectly formatted (invalid) email address is entered? (if applicable)

• Is the applicant prompted to fill in all mandatory fields (marked with an asterisk [*]) and guided to which fields are still left blank?

• Can fields that are not mandatory, be left blank? • Is the applicant allowed enough space to enter the additional work

experiences?

Yes No Comments Does the page (Page 1 of 3) display properly?

• Is the “Work Experience” sub-heading box on the left highlighted? • Are all mandatory fields marked with an asterisk (*)? • Do all fields accept the required characters and reject unnecessary

characters?

• Are restrictions enforced in the current business process reflected in this eform?

• Are the hints on the right (grey box) detailed enough to guide applicant on what to fill-in?

• Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is the “Work Experience” section user-friendly and guides applicant to

what should be done?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

Yes No Comments Does the “ Next” take you in a new page (Page 2 of 3) to fill in o ther work experiences?

• Click button to fill in the 3rd and 4th work experience. Repeat the following checklists:

• Does the “Work Experience” (Page 1 of 3) display properly?’ and • Does the page (Page 1 of 3) display properly?’’

Yes No Comments Does the “ Next” take you in a new page (Page 3 of 3) to fill in o ther work experiences?

• Click button to fill in the 5th and 6th work experience. Repeat the following checklists:

• Does the “Work Experience” (Page 1 of 3) display properly?’ and • Does the page (Page 1 of 3) display properly?’’

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 22

A9. TESTING THE “REFEREES” PAGE (if applicable)

Yes No Comments Do the “ Referees” Details display properly?

• Are the “ID Number”, “Title”, “Surname” and “Name” marked as mandatory with an asterisk (*)?

• Does “ID Card Number” accept alphanumeric characters? • Is the title fully displayed when selected from list? • Does the “Name” reject digits? • Does the “Surname” reject digits? • If the country selected from the list is Malta, is the Town showing a

list of towns and cities in Malta and Gozo?

• If the Country selected from the list is a foreign country (i.e. not Malta), is the “Town” changed to a free text field?

• Does the “House No” field accept alphanumeric characters (E.g. Apt 1/A, Flat 12-14 etc.)?

• Does the “House Name” field accept alphanumeric characters? • Does the “Street” field accept alphanumeric characters (E.g. Triq it-

13 ta’ Dicembru)

• Does the “Post Code” field accept alphanumeric characters (e.g. VLT 3000)

• Does the “Telephone” field reject the characters? • Does the “Email Address” accept characters and digits? (if applicable) • Is the “Email Address” rejected if an incorrectly formatted (invalid)

email address is entered? (if applicable)

• Is the applicant prompted to fill in all mandatory fields (marked with an asterisk [*]) and guided to which fields are left blank?

• Can the fields that are not mandatory be left blank? Repeat the above checklist to test the 2nd Referee fields.

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 23

Yes No Comments There are instances where the fields marked with tw o (2) asterisks [**] can be left blank.

• Is help provided and detailed enough on the right (grey box) to guide applicant what to fill-in?

• Can these fields be left blank? Yes No Comments Does the “ Referees” page display properly?

• Is the “Referees” sub-heading box on the left highlighted? • Are all mandatory fields marked with an asterisk (*)? • Do all fields accept the required characters and reject

unnecessary characters?

• Are restrictions enforced in the current business process reflected in this eform?

• Are the hints on the right (grey box) detailed enough to guide applicant on what to fill-in?

• Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is the “Referees” section user-friendly and guides applicant to what

should be done?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 24

A10. TESTING THE “ATTACHMENTS” PAGE (if applicable)

Yes No Comments Does the Attachments Upload page display successful ?

• Click on an attachment’s name to upload document Repeat the above check to test that all attachments can be accessed for upload. Yes No Comments Does the “ Attachments” popup display properly?

• Is all required documentation enforced in the current business process reflected in this eform?

• Are all attachment names correct? • Are the tool tips correct and descriptive for each attachment

name?

• Are all attachment names clickable (mouse cursor changes into the hand icon)?

• Are all mandatory documents marked as ‘Yes’ under the “Mandatory” column?

• Are documents that can be left unattached marked as ‘No’ under the Mandatory column?

• Do all attachment names that are not uploaded have an X under the “Uploaded” column?

• The “Links” link provides related links about the attachments? (if applicable)

• Is the “Close” button at the top right of the page visible and enabled?

• Are there any spelling and/or grammatical errors? • Is page rendering well (i.e. layout looks good and no element in

the page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 25

Yes No Comments Does the Attachments Upload page display successful ?

• Click on an attachment’s name to upload document Repeat the above check to test that all attachments can be accessed for upload. Yes No Comments Does the Upload page display and work successful?

• Does the “Links” link provide links related the documentation that needs to be attached with the application?

• Is the “File To Upload” textbox disabled? (i.e. not editable) • Are the “Upload”, “Done” and “Cancel” buttons visible and enabled? • When clicking the “Upload” button without selecting a file or not

even keying-in a comment for the Entity (in the free text ‘Comment’ box), is the “File not Found” red label displayed?

• If applicant selects a file from the path and then clicks the “Open” button, is the path of where the file is saved displayed in the “File To Upload” text box?

Once the file to attach is in the “File to Upload” text box, click on the “Upload” button.

• Is the uploaded filename displayed in the “Selected Documents” section (underneath the “Upload” button)?

To close the Upload page and return back to the Attachments page, click the “Done” button.

• Is the image under the “Uploaded” column changed to � for the uploaded attachment?

• Are there any spelling and/or grammatical errors? • Is the “Attachments” section user-friendly and guides applicant to

what should be done?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

Repeat the above checklist to test that all attachments can be uploaded successfully. Yes No Comments Does the “ Close” close the Attachments popup?

• Does the “Close” close the Attachments popup?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 26

A10. TESTING THE “ATTACHMENTS” PAGE if unauthenticated (Anonymous user) (if applicable)

Yes No Comments Does the Attachments Upload page display successful if unauthenticated?

• Click on the “Attach” to upload the documents needed Yes No Comments Does the “ Attachments” popup display properly in Liquid Office?

• Is the attachment’s name correct in the Address field? • Is an error message loaded in case the file attached is not as the

requested type?

• Is the attachment shown in the “Attachments for: MITA eForms Template” section after the Add button is selected?

• Are all attachment names correct under the section “Attachments for: MITA eForms Template”?

• Is the applicant redirected back to the initial attachment page if the Finish button is selected?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 27

A11. TESTING THE “SIGNATURE” PAGE

Yes No Comments Does the “ Signature” page display properly?

• Is the “Signature” sub-heading box on the left highlighted? • Is the applicant’s confirmation declaration displayed above the

clickable “Signature”?

• Is the confirmation declaration text correct? (if applicable) • Are all mandatory fields marked with an asterisk (*)? • If any of the mandatory fields (i.e. marked with an asterisk (*)) are

left blank or else fields are incorrectly keyed-in, on clicking on the Signature box, does an error message list display on screen (as displayed below) to guide the applicant which fields to correct?.

• If the field name of the field to correct is clicked, is the applicant redirected to the selected field and have the error message displayed in bubble format?

• Is the background of the fields to correct changed to red? • Are restrictions enforced in the current business process reflected

in this eform?

• Are the hints on the right (grey box) detailed enough to guide applicant on what to fill-in?

• Is the “Signature” marked as mandatory i.e. with an asterisk (*)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 28

Yes No Comments • If “Signature” is left blank, is the applicant prompted to fill it in? • Is the TAB control (using the keyboard) sequence correct? • Are the tool tips correct and descriptive? (if applicable) • Is the “Signature” box clickable (mouse cursor is changed into

hand)?

• Is a message from webpage including the signature details (“Role”, “Form”, “Signature Field” and “Signature Description”) displayed, when clicking the Signature box?

• When accepting the signature message popup, are the applicant details (such as the name, surname and current date and time) displayed in the box?

• Once digitally signed, are all the fields disabled (i.e. read-only)? • Are the “Next” and “Previous” buttons visible and enabled? • Are the spelling and/or grammar correct? • Is the “Signature” section user-friendly and guides applicant to what

should be done?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 29

A12. TESTING THE “SUBMIT” PAGE

Yes No Comments Does the “ Submit” page display properly?

• Is the “Submit” sub-heading box on the left highlighted? • Are the hints on the right (grey box) detailed enough to guide

applicant on what to do? (if applicable)

• Are the “Application Reference”, “Submission Reference”, “Date Received” and “File Reference” fields disabled (i.e. read-only)?

• If the form is never been submitted, are the “Submission Reference”, “Date Received” and the “File Reference Number” empty?

• Is the “Application Reference” field automatically filled in with a number?

• Is the applicant provided with a list to select an action (“Save”, “Submit” or “Withdraw”)?

• Is the TAB control (using the keyboard) sequence correct? (if applicable)

• Are the tool tips correct and descriptive? (if applicable) • Is the “Previous” button visible and enabled? • Are the spelling and/or grammar correct? • Is the “Submit” section user-friendly and guides the applicant to

what should be done?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

• Is the applicant redirected to another page when one chooses to “Save” the application for later reference?

• Is the acknowledgement page displayed on screen and an email received by the applicant to be informed that the form has been submitted?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 30

Yes No Comments • If the applicant has not signed the application, is one prompted (as

displayed in the screen shot below) to sign the application before proceeding with the submission?

• Is the applicant redirected to the ‘Signature’ page if the Signature field name is clicked from the validation popup?

• Once the form is submitted, is the applicant in possession of the filled application in PDF format?

• If applicable, is the applicant redirected to the “Payment” page once the “Submit” button is clicked?

• Additionally, once the application is submitted is the eForm displayed in the applicant’s “Mailbox” under the “In Progress” section, with the “Subject”, “ID Card Number”, “Reference Number” and “Status” correct?

• Alternatively, if the applicant clicks on the ‘Cancel’ button, is the application withdrawn and displayed in the applicant’s ‘Mailbox’ under the ‘Withdraw / Rejected’ section?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 31

A13. TESTING THE “MAILBOX” – AFTER SUBMITTING FORM

Yes No Comments Does the “Mailbox” display properly?

• Is form displayed in the “Mailbox” under the “In Progress” section, with the “Subject”, “ID Card Number”, “Status” and “Date Sent” correct? Subject must be the Form Title. ID Card Number must be the applicant’s ID Card Number. Status must be set to “Application being processed”. Date Sent must be the date and time of when the form was submitted.

• Are the tool tips correct and descriptive for each form title? (if applicable)

• Are all form titles clickable (mouse cursor is changed into hand)? • If attachment(s) have been submitted with the application, is an

attachment icon displayed near the form title? (if applicable)

• Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 32

Yes No Comments Attachments icon redirect to expected page/s? (if applicable) Click on the attachments icon to verify that the expected page is displayed.

• Is a list of attachments included in the application form displayed? • Are all attachment names clickable (mouse cursor changes into the

hand icon)?

• Does the “Links” link provide related links about the documentation that one has to attach with the application? (if applicable)

• Are there any spelling and/or grammatical errors? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Yes No Comments Does the attachment file display successful? (if applicable)

• Click on an attachment’s name to view document Repeat the above check to test that all attachments can be accessed. Yes No Comments Does the” X” icon close the Attachments window? (if applicable)

• Click icon to close window Yes No Comments Does the Progress Timeline page display successful?

Click on the form title to open page

• Is the “Process Name” correct? Process name should be the full form title.

• Is the information about the form correct (i.e. form title, applicant’s ID card number and reference status)?

• Is the “Form Progress Timeline” available and correct? • Is the current stage of the form highlighted? • Is the Entity displayed in the current stage box correct? • Is the Entity link clickable? • Does the Entity link result in an email to an appropriate

person/group?

• Are the “Print this record” and “Open Process” links visible and clickable? Yes No Comments Progress Timeline links redirect to the expected pa ge/s? Click on every link to verify that the expected page is displayed.

• Does the “Print this record” link provide the applicant with a print out of the Form Progress Timeline?

• Does the “Open Process” link provide the applicant with a PDF version of the submitted form?

• Are the contents when clicking on the links, valid and correct? Yes No Comments Does the PDF display successful?

• Are all the details displayed in PDF corresponding to the details submitted in the eform?

• Are the applicant details displayed in the “Signature of Applicant” box? • Is the “Total Amount Due” field filled in and visible only when payment

has been calculated from the administration side? (if applicable)

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 33

A14. TESTING THE “VETTING” STAGE - ADMINISTRATION SIDE

Work Queue Side

Yes No Comments Logged as a Vetter

• Are the “Work Queues” shown correctly? • Are the details of each application under “Vetting” shown correctly?

(Description, ID, Status, Date received).

• Under “Status” are forms stated as “Application being Assessed”? • Clicking on “Open PDF” is the data in the PDF shown correctly? • Clicking on form “Description” does the form opens and loads all the

data keyed-in by the applicant correctly?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 34

Vetting Information Page

Yes No Comments Logged as a Vetter

• Going through the application by selecting the left tabs “Form Sections” or by the “Next and Previous” at the bottom right. Are all mandatory data present?

• Selecting Tab “For Office Use” from the left tab are the following fields shown correctly?

o Application Reference o Submission Reference o Date Received o File Reference o Process Status o Form Submitted through o Form submitted on behalf of o Vetting Officer o Vetting Date

• Are the following fields disabled? o Application Reference o Submission Reference o Date Received o File Reference o Process Status o Form Submitted through o Form submitted on behalf of o Vetting Officer o Vetting Date

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 35

Yes No Comments • Are the following textboxes visible?

o Vetting Remarks o Vetting Internal Remarks

• Are the following textboxes enabled? o Vetting Remarks o Vetting Internal Remarks

• Is the “For Office Use” section on the right side visible? • Selecting “History Tab” on the right are the following Fields visible?

o Approval Remarks sent to applicant

• Selecting “History Tab” on the right are the following Fields enabled: o “Internal Remarks” (Show all the remarks (both internal and

those shown to the applicant) entered by the vetting officers in chronological order i.e. the newest first. Entries will be appended to the previous information with no over-writing).

o “Remarks History” (This field is to contain only the remarks that are available to the applicant. All this data is to be duplicated as a subset in the Remarks field. Entries are to be appended to previous information i.e. no over writing and are to be shown in a chronological order)

• If applicable, when selecting “Submit”, is “Total amount due: Euro” visible?

• In “Select an action to perform and then Click Go” drop down, are the following options available:

o “Return to Applicant” (Return to applicant when data is missing.)

o “Approve” (Approve form and proceed with workflow.) o “Cancel” (Cancel to cancel process. o “Save” (Save for later to continue working at a later stage.) o “Reject” (Reject form) – if necessary

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 36

A15. TESTING THE “MAILBOX” – FORM RETURNED FOR AMENDMENTS DURING VETTING (if applicable)

Yes No Comments Does the “Mailbox” display properly?

• Is form displayed in the “Mailbox” under the “Attention Required” section, with the “Subject”, “ID”, “Ref” and “Status” correct? Subject must be the Form Title. ID must be the applicant’s ID Card Number. Ref must be a reference number supplied by the person vetting the application. Status must be set to “Returned to Applicant”. Date Received must be the date and time of when the form was submitted.

• Are the tool tips correct and descriptive for each form title? (if applicable)

• Are all form titles clickable (mouse cursor is changed into hand)? • If attachment(s) have been included with the application, is an

attachment icon displayed near the form title? (if applicable)

• Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 37

A16. TESTING THE COMMENTS SECTION

Yes No Comments Is the “ Comments” page displayed successfully?

Click on the form title to open page for amendments • Is the “Comments” section automatically selected on loading?

• Is the “Comments” sub-heading box on the left highlighted? • Are all fields in the section disabled (i.e. not editable)?

• Are the following fields filled-in: o “Last Comment From Authority” o “Remark History”

• Does the “Last Comment From Authority” field display the following details:

o Date and time of when the form has been returned to the applicant,

o Process stage at which the form has been returned to the applicant

o Back Office User’s Name and Surname o Translated Action o Comments from the person vetting the application i.e. the

reason why the application has been returned for amendments

• Are the following Form Section tabs enabled? o About the form o Personal Details o Attachments o Signature o Comments o Submit

• Is the applicant given the opportunity to change the data inserted in the other Form Sections (as found on the left tab)?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 38

Yes No Comments

• Is the TAB control (using the keyboard) sequence correct? (if applicable)

• Are the tool tips correct and descriptive? (if applicable)

• Are the “Previous” and “Next” buttons visible and enabled?

• Are the spelling and/or grammar correct?

• Is page rendering well (i.e. layout looks good and no element in the page is being overwritten/partially hidden, etc)?

Navigate through all the sections. • Are all the details keyed-in on submission, displayed in form?

Amend application as per comments inserted by the V etter in the “ Remarks” field.

• Is an acknowledgement received, when the “Go” button is clicked (i.e. after selecting the “Submit” option from list)?

• Is form displayed in the “Mailbox” under the “In Progress” section, with the “Subject”, “ID Card Number”, “Reference Number” and “Status” correct?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 39

A17. TESTING THE “PAYMENT” PAGE (if applicable)

Type of Payment

Yes No Comments “ Payment Form”

• Under “Your Forms” “Attention Required” is application Status marked as “Payment”?

• Selecting Application description, does the “Payment Form” appears?

• Is the “Amount Due: €” displaying the correct value? • Are the following options available?

o “Pay Online” (Payment online will direct you to myBills Payment gateway.)

o “Bank Transfer” (Payment is done through a bank transfer.) o “Send Cheque” (Payment is effected by Cheque.) o “Internet Banking” (Payment is effect through internet banking.)

• Selecting “Pay Online” and clicking “Proceed to secure payment” does the page divert you to myBills “Card Payment Details” page?

• Selecting “Bank transfer” does the form ask you to input “Clearing Bank” and “Reference Number”?

• Selecting “Send Cheque” does the form ask you to input “Clearing Bank” and “Cheque number”?

• Selecting “Bank transfer” does the form ask you to input “Clearing Bank” and “Reference Number”?

• To proceed, did you click on the “Go” button?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 40

A18. TESTING THE “CASH OFFICE” STAGE - ADMINISTRATION SIDE (if applicable)

Work Queue Side

Cash Office Page

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 41

Yes No Comments Cash Office (If Applicable) Cash office stage is available when the payment is done manually i.e.: by bank transfer or by cheque.

• Is “Cash Office” shown under work queues? • Selecting the current eForm under the “Cash Office” section, does the

“Manual/ Banking Payment” page open up?

• In the “Manual/Banking Payment” page are the following fields disabled:

o “Amount Due”, o “Form Reference”, o “Form submission Reference”, o “Cheque Number”, o “Clearing Bank”, and o “Payment Reference”

• In the “Manual/Banking Payment” page are the following fields enabled: o “File Reference”, o “Payment Status”, and o “Cash Office Comments”

• Once the “Go” button is selected, would it let the user to proceed even if any of the following fields are left empty?

o “File Reference”, o “Payment Status”, and o “Cash Office Comments”

• If any of the above mentioned fields is left empty, is the validation message visible in a bubble on the respective field?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 42

A19. TESTING THE “APPROVAL” STAGE – ADMINISTRATION SIDE

Work Queue Side

Approval Page

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 43

Yes No Comments Logged as a Approving Officer

• Are the “Work Queues” shown correctly? • Are the details of each application under the “Approval” section

shown correctly? “Description”, “ID”, “Status”, “Date received” and, “Ref” should be filled during approval stage.

• Under “Status” are forms stated as “Under Approval”? • Clicking on “Open PDF” is the data in the PDF shown correctly

including the details under the Vetting stage?

• Clicking on form “Description”, does the eForm opens correctly? • Going through the application by selecting the left tabs “Form

Sections”, or by using the “Next and Previous” buttons at the bottom right; are all the mandatory data present?

• Selecting Tab “For Office Use” from the left tab are the following fields shown corectly?

o Submission Reference o Date Received o File Reference o Process Status o Form Submitted through o Form submitted on behalf of o Officer o Data

• Are the following fields disabled? o Submission Reference o Date Received o File Reference o Process Status o Form Submitted through o Form submitted on behalf of o Officer o Data

• Are the following textboxes visible? o Remarks to be sent to applicant o Internal Remarks o Approval Conditions

• Are the following textboxes enabled? o Remarks to be sent to applicant o Internal Remarks o Approval Conditions

• Selecting “History Tab” on the right are the following Fields enabled: o “Internal Remarks” (Show all the remarks (both internal and

those shown to the applicant) entered by the vetting officers in chronological order i.e. the newest first. Entries will be appended to the previous information with no over-writing).

o “Remarks History” (This field is to contain only the remarks that are available to the applicant. All this data is to be duplicated as a subset in the Remarks field. Entries are to be appended to previous information i.e. no over writing and are to be shown in a chronological order)

o “Approval Remarks” (This field is to be shown only at the Approval and the Committee stages. Entries are to be appended to previous information with no over writing and are to be shown in a chronological order (newest first).

• If applicable, when selecting the “Submit” tab, is the “Total Amount Due: Euro” visible?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 44

Yes No Comments • In “Select an action to perform and then click Go” drop down are the

following options available? o “Return to Applicant” (Return to applicant when data is

missing.) o “Approve” (Approve form and proceed with workflow.) o “Cancel” (Cancel to cancel process. o “Save” (Save for later to continue working at a later stage.) o “Reject” (Reject form) – if necessary

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 45

A20. TESTING THE “COMMITTEE” / “BOARD” STAGE – ADMINISTRATION SIDE (if applicable)

Work Queue Side

Committee Comment Page

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 46

Yes No Comments Logged as a Committee Officer or Board Officer

• Are the “Work Queues” shown correctly? • Are the details of each application under “Committee” / “Board”

shown correctly? “Description”, “ID”, “Status”, “Date received” and, “Ref” should be filled.

• Under “Status”, are forms stated as “In front of Committee” or “In front of Board”?

• Clicking on “Open PDF” is the data in the PDF shown correctly including details under the Vetting and Approval stages?

• Clicking on form “Description” does the eForm opens correctly? • Going through the application by selecting the left tabs “Form

Contents” or by using the “Next and Previous” buttons at the bottom right. Are all mandatory data present?

• Selecting Tab “For Office Use” from the left tab are the following fields shown correctly?

o Submission Reference o Date Received o File Reference o Process Status o Form Submitted through o Form submitted on behalf of o Officer o Data

• Are the following fields disabled? o Submission Reference o Date Received o File Reference o Process Status o Form Submitted through o Form submitted on behalf of o Officer o Data

• Are the following textboxes visible? o Remarks to be sent to applicant o Internal Remarks o Approval Conditions

• Are the following textboxes enabled? o Remarks to be sent to applicant o Internal Remarks o Approval Conditions

• Selecting “History Tab” on the right are the following Fields enabled: o “Internal Remarks” (Show all the remarks (both internal and

those shown to the applicant) entered by the vetting officers in chronological order i.e. the newest first. Entries will be appended to the previous information with no over-writing).

o “Remarks History” (This field is to contain only the remarks that are available to the applicant. All this data is to be duplicated as a subset in the Remarks field. Entries are to be appended to previous information i.e. no over writing and are to be shown in a chronological order)

o “Approval Remarks” (This field is to be shown only at the Approval and the Committee stages. Entries are to be appended to previous information with no over writing and are to be shown in a chronological order (newest first).

• If applicable, when selecting the “Submit” tab, is the “Total Amount Due: Euro” visible?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 47

Yes No Comments • In “Select an action to perform and then click Go” drop down are the

following options available? o “Return to Applicant” (Return to applicant when data is

missing.) o “Approve” (Approve form and proceed with workflow.) o “Cancel” (Cancel to cancel process. o “Save” (Save for later to continue working at a later stage.) o “Reject” (Reject form) – if necessary

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 48

A21. TESTING THE “Payment verification” STAGE – ADMINISTRATION SIDE (if applicable)

Work Queue Side

Payment Page

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 49

Yes No Comments Logged as an Approval Officer

• Are the “Work Queues” shown correctly? • Are the details of each application under “Committee” shown

correctly? “Description”, “ID”, “Status”, “Date received” and, “Ref” should be filled.

• Are the following fields disabled? o Payment Date, o Payment Amount, o Transaction Ref. o Submission Ref. o Payment Verified

Does the Payments Details page display correctly wh en affecting a payment by cheque?

• Are the following fields visible and details correctly populated on loading?

o Clearing bank name, and o Cheque No

• Are the following fields disabled (i.e. read-only)? o Clearing bank name, and o Cheque No

Does the Payments Details page display correctly wh en affecting a payment using the MyBills (i.e. by card)?

• Are the following fields visible and details correctly populated on loading?

o Cardholder Name, and o Card Number

• Is the “Card Number” masked compliant to PCI-DSS (i.e. only the first 6 and the last 4 digits are shown)?

• Are following fields disabled (i.e. read-only)? o Cardholder Name, and o Card Number

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 50

A22. TESTING THE “MAILBOX” – FORM COMPLETED (if applicable)

Yes No Comments Does the entire workflow work successfully?

Go through the entire workflow i.e. form submission, vetting of form, payment (if applicable), cash office (if payment is not done online), approval of form and under committee (if applicable) • Is the Progress Timeline correct?

Yes No Comments Does the “Mailbox” display properly?

• Once the application is approved and workflow completed, is the application displayed in the “Mailbox” under the “Completed” section, with the “Subject”, “ID”, “Ref”, “Status” and “Date Received” correct? Subject must be the Form Title. ID must be the applicant’s ID Card Number. Ref must be the File Reference Number issued by the Vetter during the approval stage. Status must be set to “Approved”. Date Received must be the date and time of when the form was received.

• Are the tool tips correct and descriptive for each form title? (if applicable)

• Are all form titles clickable (mouse cursor is changed into hand)? • If attachment(s) are submitted with the application, is an

attachment icon displayed near the form title? (if applicable)

• Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Click on the form title to display the eForm in PDF • Are details displayed in PDF corresponding to the details submitted

in the eform?

• Are the applicant details displayed in the “Signature of Applicant” box?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 51

A23. TESTING THE “MAILBOX” – AFTER SAVING FORM AS A DRAFT (if applicable)

Yes No Comments Does the saving as “ Draft” work successful?

Start filling the form and then select “Save” from the list provided in the “Submit” section. • Is an acknowledgement received, when the “Go” button is clicked?

Yes No Comments Does the “Mailbox” display properly?

• Is form displayed in the “Mailbox” under the “Attention Required” section, with the “Subject” and “Status” correct? Subject must be the Form Title. Status must be set to “Draft”. Date Sent must be the date and time of when the form was saved as draft.

• Are the tool tips correct and descriptive for each form title? (if applicable)

• Are all form titles clickable (mouse cursor is changed into hand)? • If attachment(s) have been included with the application, is an

attachment icon displayed near the form title? (if applicable)

• Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Yes No Comments Does the Form display successful? Click on the form title to open page

• Are details displayed in each section corresponding to the details keyed-in prior to saving the eForm as draft?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 52

Yes No Comments Does the Progress Timeline page display successful?

Click on the forms.mygov.mt icon to open page

• Is the “Process Name” correct? Process name should display the form title.

• Is the information about the form correct i.e. form title, applicant’s ID card number (if applicable) and reference status?

• Is the “Form Progress Timeline” available and correct? • Is the current stage of the form highlighted? • Is the Entity displayed in the current stage box correct? • Is the Entity link clickable? • Does the Entity link result in an email to an appropriate

person/group?

• Are the “Print this record” and “Open Process” links visible and clickable? Yes No Comments Progress Timeline links redirect to the expected pa ge/s? Click on every link to verify that the expected page is displayed.

• Does the “Print this record” link provide the applicant with a print out of the Form Progress Timeline?

• Does the “Open Process” link provide the applicant with the online form saved as draft?

• Are the contents when clicking on links, valid and correct?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 53

A24. TESTING THE “MAILBOX” – FORM WITHDRAWN (if applicable)

Yes No Comments Does the “ Withdrawn” work successfully? (Applicant side) Start filling the form and then select “Withdrawn” from the list provided in the “Submit” section.

• Is an acknowledgement received, when the “Go” button is clicked?

Yes No Comments Does the “ Withdrawn” work successfully? (Administration side) Start vetting or approving the eForm and then select “Reject” from the list provided in the “Submit” section.

• Is an email sent to the applicant when the “Go” button is clicked, to inform him that the application has been rejected?

Yes No Comments Does the “Mailbox” display properly?

• Once form has been withdrawn (by the applicant or administration), is the application displayed in the “Mailbox” under the “Withdrawn” section, with the “Subject”, “ID”, “Ref”, “Status” and “Date Received” correct (if applicable)? Subject must be the Form Title. ID must be the applicant’s ID Card Number. Ref must be the File Reference Number issued by the Vetter during the approval stage (if applicable). Status must be set to “Withdrawn”. Date Received must be the date and time of when the form was received.

• Are the tool tips correct and descriptive for each form title? (if applicable)

• Are all form titles clickable (mouse cursor is changed into hand)? • If attachment(s) have been attached with the application, is an

attachment icon displayed near the form title? (if applicable)

• Are the spelling and/or grammar correct? • Is page rendering well (i.e. layout looks good and no element in the

page is being overwritten/partially hidden, etc)?

Click on the form title • Is a PDF with a message that “You have withdrawn your application”

opened?

Unclassified Electronic Forms User Acceptance Testing - Guidelines

Page 54

Appendix B – Incident Report

eForm Reference: Date:

eForm Name:

Raised By:

Incident Number:

Incident Severity: * 1 - Severe Error, 2 - Serious Error, 3 - Minor error, 4 - Comment

Test Case / Incident Root

Incident Description

Comments / Image Included (if applicable)

Closure Category Closure Date Closure Version

* F – Fixed, W – Withdrawn, S – Solved, D – Deferred,

P – Partial Fix

Client Approval Name:

Client Approval Date: