Bug #3203

UAT_B007 - BIB : New Bill Payment & Favourite Payee

Added by Lizahwati Basirun about 11 years ago. Updated about 11 years ago.

Status:Closed - End of life cycleStart date:July 09, 2013
Priority:NormalDue date:
Assignee:Norhaidah Md Dasuki% Done:

100%

Category:Others - TokenSpent time:1.00 hour
Target version:-

Description

Hi Alwi,

Kindly assist on the issues.

1) Enter alphabet or special character

Step to re-produce:
  1. Click on New Bill Payments
  2. Fill up the required fields until Step 4/5
  3. Enter "abcd" or special character to Enter Secure Pass PIN Number field
  4. Click Confirm button

Current Result:
System throw "Token serial invalid"

Expected Result:
System should throw "Secure Pass PIN must be numeric. "

2) Enter less than 6 digit

Step to re-produce:
  1. Click on New Bill Payments
  2. Fill up the required fields until Step 4/5
  3. Enter "1234" to Enter Secure Pass PIN Number field
  4. Click Confirm button

Current Result:
System throw "Token serial invalid"

Expected Result:
System should throw "Secure Pass PIN must consist of 6 digits."

3) Enter invalid or expired Secure Pass PIN number

Step to re-produce:
  1. Click on New Bill Payments
  2. Fill up the required fields until Step 4/5
  3. Enter invalid data to Enter Secure Pass PIN Number field
  4. Click Confirm button

Current Result:
System throw "Token serial invalid"

Expected Result:
System should throw "Secure Pass Pin is invalid"

4) Enter empty or space to Secure Pass PIN Number

Step to re-produce:
  1. Click on New Bill Payments
  2. Fill up the required fields until Step 4/5
  3. Enter invalid data to Enter Secure Pass PIN Number field
  4. Click Confirm button

Current Result:
System throw "???en.general.default???"

Expected Result:
System should throw "Secure Pass Pin is required"

History

#1 Updated by Alwi Husada about 11 years ago

  • Status changed from New - Begin Life Cycle to Finished Development
  • % Done changed from 0 to 100

#2 Updated by Alwi Husada about 11 years ago

  • Status changed from Finished Development to Internal Testing
  • Assignee changed from Alwi Husada to Lizahwati Basirun

Amended secure pass error message.

#3 Updated by Lizahwati Basirun about 11 years ago

  • Status changed from Internal Testing to Development / Work In Progress
  • Assignee changed from Lizahwati Basirun to Alwi Husada
  • % Done changed from 100 to 90

Salam Alwi,

All issues have been tested and passed. But, kindly change the term label from "Secure Pass" to "Security Token." Please change for all modules.

#4 Updated by Alwi Husada about 11 years ago

  • Status changed from Development / Work In Progress to Finished Development
  • % Done changed from 90 to 100

#5 Updated by Alwi Husada about 11 years ago

  • Status changed from Finished Development to Internal Testing
  • Assignee changed from Alwi Husada to Lizahwati Basirun

Change the term label from "Secure Pass" to "Security Token."

#6 Updated by Lizahwati Basirun about 11 years ago

  • Status changed from Internal Testing to Pending Customer Feedback

Tested and passed.

#7 Updated by Norhaidah Md Dasuki about 11 years ago

  • Category set to Others - Token
  • Status changed from Pending Customer Feedback to Closed - End of life cycle
  • Assignee changed from Lizahwati Basirun to Norhaidah Md Dasuki

15/07/2013 [Halimah] - Had been tested at BIB UAT and ok.

Also available in: Atom PDF