Bug #2922
IBAM>IBAM : Content - SECURITYQUESTION
Status: | Closed - End of life cycle | Start date: | July 03, 2013 | |
---|---|---|---|---|
Priority: | Normal | Due date: | July 04, 2013 | |
Assignee: | Norhaidah Md Dasuki | % Done: | 100% | |
Category: | IBAM>IBAM: Content | Estimated time: | 2.00 hours | |
Target version: | - | Spent time: | 3.00 hours |
Description
Hi Alwi,
Kindly assist on these bugs/issues:
Login as makerUser/aaaa1111
IBAM053 - User is able to input Security Question Code using special character.
Step to re-produce:- Click on IBAM>Content>SECURITYQUESTION
- Click on Category Name
- Click on Create Content
- Input "QUES%%^&" to Security Question Code
- Input Security Question (EN)
- Click on Done button
Current Result:
System accepted the special character.
Expected Result:
System should throw error message stated "Security Question Code is not an alphanumeric."
IBAM054 - User can create same Security Question Code and checker can approve both same code
Step to re-produce:- Click on IBAM>Content>SECURITYQUESTION
- Click on Category Name
- Click on Create Content
- Input "SQ2" to Security Question Code
- Input Security Question (EN)
- Click on Done button
- Repeat the step and using same data.
- Click on Authorization
- Click on Pending navigation
- Search on Create Security Code content: SQ2 by makerUser (it will shown 2 same pending item)
- Approved both
Current Result:
System allowed to approved same Security Question Code
Expected Result:
Maker User cannot create duplicate code. Once user try to create new same Security Code system should throw error message stated "<Security Code has been used. Please use another Security Code.>"
Thank you
History
#1 Updated by Alwi Husada over 11 years ago
- Assignee changed from Alwi Husada to Ting Wei Gan
#2 Updated by Tan Lee Yong over 11 years ago
I think the Security Code should be unique in DB. Can we set it as unique? If it is unique, then duplicated code will not be allowed to insert.
#3 Updated by Ting Wei Gan over 11 years ago
- Assignee changed from Ting Wei Gan to Alwi Husada
#4 Updated by Alwi Husada over 11 years ago
- Status changed from New - Begin Life Cycle to Internal Testing
- Assignee changed from Alwi Husada to Lizahwati Basirun
- % Done changed from 0 to 100
Set Security Code to be uniqe in DB.
#5 Updated by Lizahwati Basirun over 11 years ago
- Status changed from Internal Testing to Development / Work In Progress
- % Done changed from 100 to 90
Hi Alwi,
Here the testing result.
- IBAM053 - User is able to input Security Question Code using special character. - FAILED. System still accept the special character.
- IBAM054 - User can create same Security Question Code and checker can approve both same code - PASSED
Kindly fixed on the IBAM053.
Thanks.
#6 Updated by Alwi Husada over 11 years ago
- Status changed from Development / Work In Progress to Internal Testing
- % Done changed from 90 to 100
fixed , added alphaNumeric validation for Security question code
#7 Updated by Lizahwati Basirun over 11 years ago
- Status changed from Internal Testing to Pending Customer Feedback
Fixed and sucessfully re-tested. Pending for customer feedback.
#8 Updated by Tan Lee Yong about 11 years ago
- Project changed from Phase 2 - SIT Phase to IBAM
- Category set to IBAM - Maintenance - COP
#9 Updated by Norhaidah Md Dasuki about 11 years ago
- Category changed from IBAM - Maintenance - COP to IBAM>IBAM: Content
- Status changed from Pending Customer Feedback to Closed - End of life cycle
- Assignee changed from Lizahwati Basirun to Norhaidah Md Dasuki
27062013(Ruzaimah) - retest - change to modified date. - unsuccessful
IBAM054 - User can create same Security Question Code and checker can approve both same code - PASSED
Expected: Security Question Code shall be unique.
#10 Updated by Norhaidah Md Dasuki about 11 years ago
- Due date set to July 04, 2013
- Status changed from Closed - End of life cycle to Development / Work In Progress
- Assignee changed from Norhaidah Md Dasuki to Syahrul Anwar
- Start date changed from June 18, 2013 to July 03, 2013
- % Done changed from 100 to 0
#11 Updated by Syahrul Anwar about 11 years ago
- Status changed from Development / Work In Progress to Internal Testing
- Assignee changed from Syahrul Anwar to Norhaidah Md Dasuki
- % Done changed from 0 to 100
- Estimated time set to 2.00
already test.. can't reproduce issue cause already fix it
#12 Updated by Norhaidah Md Dasuki about 11 years ago
- Status changed from Internal Testing to Pending Customer Feedback
During new creation, before approval, system will allowed to create product type with same product code which is still not exist in DB. During approval process, once 1st transaction has been approved, the other transaction with same product code will be rejected with error message <<Security Code has been used. Please use another Security Code.>
#13 Updated by Norhaidah Md Dasuki about 11 years ago
- Status changed from Pending Customer Feedback to Closed - End of life cycle
10/3/13 [Ruzaimah] - retest and closed