eWallet_MobileApp_OTP validity is for 3 minutes only however the OTP had not expired even after 5 minutes and the transaction went through when the User tried with the old OTP # 54

[ArjunLokanath]

As per the Table 2 under UC4 it is said that the OTP Pin is valid only for 3 minutes however when the same OTP was used even after 5 minutes, the User was able to proceed completing the registration and no error message was prompted to stop the User from completing the registration process

[ArjunLokanath]

As per May from APAC Venture this defect is pending investigation from ABL side

[JasonABL]

Currently system param configured 30 mins in dev environment.

[ArjunLokanath]

Hi Jason,

The test conducted is as per the details mentioned in the Functional Specs, Hence it will still be considered as a defect if the FS has not been updated accordingly (30 minutes), Thanks

Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870

On Tue, Nov 15, 2016 at 12:17 PM, JasonABL notifications@github.com wrote:

Currently system param configured 30 mins in dev environment.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/54#issuecomment-260543377, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_mclebtrLYR5UzYwt_jg3NTDAtSaks5q-TJtgaJpZM4KxEhf .

[JasonABL]

Hi Arjun,

Understood the document stated default value as 3. But it's dev environment, the value have changed for testing purpose. Have updated back the value to 3. Please try again, thanks.

[ArjunLokanath]

I tried to retest this many times but unable to test this accurately even in the Dev environment because the OTP is being generated only after around 10 minutes time hence the OTP i enter is invalid already,

Objective of the test i exactly after 3 minutes which we are unable to achieve at the moment.

Dear Bavani,

Please take note as this issue is occurring in the Dev environment as well, Thanks

Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870

On Wed, Nov 16, 2016 at 11:20 AM, JasonABL notifications@github.com wrote:

Hi Arjun,

Understood the document stated default value as 3. But it's dev environment, the value have changed for testing purpose. Have updated back the value to 3. Please try again, thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/54#issuecomment-260842822, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_vrB92xGene5S08gT8mDRTr7qGqUks5q-naCgaJpZM4KxEhf .

[ArjunLokanath]

Hi Arjun,

If the OTP is expired means the OTP time validation is correct. The delay of receiving OTP is not within our control. May check with Mobility One why this is happening. Thanks.

Regards,

Jason

From: Arjun Lokanath [mailto:arjun.lokanath@appsync.sg] Sent: Thursday, 17 November 2016 4:46 PM To: TNGSB/eWallet reply@reply.github.com; Jason Pang jason@ablglobal.com; Bavani Shanmugam bavani@touchngo.com.my Cc: TNGSB/eWallet eWallet@noreply.github.com; Author author@noreply.github.com Subject: Re: [TNGSB/eWallet] eWallet_MobileApp_OTP validity is for 3 minutes only however the OTP had not expired even after 5 minutes and the transaction went through when the User tried with the old OTP # 54 (#54)

I tried to retest this many times but unable to test this accurately even in the Dev environment because the OTP is being generated only after around 10 minutes time hence the OTP i enter is invalid already,

Objective of the test i exactly after 3 minutes which we are unable to achieve at the moment.

Dear Bavani,

Please take note as this issue is occurring in the Dev environment as well, Thanks

Best Regards,

Arjun Lokanath

Test Manager, AppSync

Malaysia HP: 01135443870

On Wed, Nov 16, 2016 at 11:20 AM, JasonABL <notifications@github.com mailto:notifications@github.com > wrote:

Hi Arjun,

Understood the document stated default value as 3. But it's dev environment, the value have changed for testing purpose. Have updated back the value to 3. Please try again, thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/54#issuecomment-260842822 , or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_vrB92xGene5S08gT8mDRTr7qGqUks5q-naCgaJpZM4KxEhf . https://github.com/notifications/beacon/AWCs_ptZiWk5nAUyEU0xt9TgnwAwsIpzks5q-naCgaJpZM4KxEhf.gif

[ArjunLokanath]

Yes I am aware Jason, However the test is not only on the OTP expiry but also on the time validation meaning I want to check if it consider at 5 minutes or not which was the previous setting, But not able to test this as I am receiving only around 10 minutes or so, Hope this clarifies.. Thanks

Hi Bavani,

Can please help to check onwards with Mobility One why there is a big delay in User receiving the OTP's, Thanks

Best Regards, Arjun Lokanath Test Manager, AppSync Malaysia HP: 01135443870

On Thu, Nov 17, 2016 at 5:25 PM, Jason Pang jason@ablglobal.com wrote:

Hi Arjun,

If the OTP is expired means the OTP time validation is correct. The delay of receiving OTP is not within our control. May check with Mobility One why this is happening. Thanks.

Regards,

Jason

From: Arjun Lokanath [mailto:arjun.lokanath@appsync.sg] Sent: Thursday, 17 November 2016 4:46 PM To: TNGSB/eWallet <reply+0160acfe778da0722f86c8b3217390 a06198f3420d29a3c892cf000000011443928292a169ce0b44c40c@reply.github.com>; Jason Pang jason@ablglobal.com; Bavani Shanmugam <bavani@touchngo.com.my

Cc: TNGSB/eWallet eWallet@noreply.github.com; Author < author@noreply.github.com> Subject: Re: [TNGSB/eWallet] eWallet_MobileApp_OTP validity is for 3 minutes only however the OTP had not expired even after 5 minutes and the transaction went through when the User tried with the old OTP # 54 (#54)

I tried to retest this many times but unable to test this accurately even in the Dev environment because the OTP is being generated only after around 10 minutes time hence the OTP i enter is invalid already,

Objective of the test i exactly after 3 minutes which we are unable to achieve at the moment.

Dear Bavani,

Please take note as this issue is occurring in the Dev environment as well, Thanks

Best Regards,

Arjun Lokanath

Test Manager, AppSync

Malaysia HP: 01135443870

On Wed, Nov 16, 2016 at 11:20 AM, JasonABL notifications@github.com wrote:

Hi Arjun,

Understood the document stated default value as 3. But it's dev environment, the value have changed for testing purpose. Have updated back the value to 3. Please try again, thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/54#issuecomment-260842822, or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_vrB92xGene5S08gT8mDRTr7qGqUks5q-naCgaJpZM4KxEhf .

[ArjunLokanath]

Hi Arjun,

Okay, noted. =D

Thanks.

Regards,

Jason

From: Arjun Lokanath [mailto:arjun.lokanath@appsync.sg] Sent: Thursday, 17 November 2016 5:34 PM To: Jason Pang jason@ablglobal.com Cc: TNGSB/eWallet reply@reply.github.com; Bavani Shanmugam bavani@touchngo.com.my; TNGSB/eWallet eWallet@noreply.github.com; Author author@noreply.github.com Subject: Re: [TNGSB/eWallet] eWallet_MobileApp_OTP validity is for 3 minutes only however the OTP had not expired even after 5 minutes and the transaction went through when the User tried with the old OTP # 54 (#54)

Yes I am aware Jason, However the test is not only on the OTP expiry but also on the time validation meaning I want to check if it consider at 5 minutes or not which was the previous setting, But not able to test this as I am receiving only around 10 minutes or so, Hope this clarifies.. Thanks

Hi Bavani,

Can please help to check onwards with Mobility One why there is a big delay in User receiving the OTP's, Thanks

Best Regards,

Arjun Lokanath

Test Manager, AppSync

Malaysia HP: 01135443870

On Thu, Nov 17, 2016 at 5:25 PM, Jason Pang <jason@ablglobal.com mailto:jason@ablglobal.com > wrote:

Hi Arjun,

If the OTP is expired means the OTP time validation is correct. The delay of receiving OTP is not within our control. May check with Mobility One why this is happening. Thanks.

Regards,

Jason

From: Arjun Lokanath [mailto:arjun.lokanath@appsync.sg mailto:arjun.lokanath@appsync.sg ] Sent: Thursday, 17 November 2016 4:46 PM To: TNGSB/eWallet <reply@reply.github.com mailto:reply%2B0160acfe778da0722f86c8b3217390a06198f3420d29a3c892cf000000011443928292a169ce0b44c40c@reply.github.com >; Jason Pang <jason@ablglobal.com mailto:jason@ablglobal.com >; Bavani Shanmugam <bavani@touchngo.com.my mailto:bavani@touchngo.com.my > Cc: TNGSB/eWallet <eWallet@noreply.github.com mailto:eWallet@noreply.github.com >; Author <author@noreply.github.com mailto:author@noreply.github.com > Subject: Re: [TNGSB/eWallet] eWallet_MobileApp_OTP validity is for 3 minutes only however the OTP had not expired even after 5 minutes and the transaction went through when the User tried with the old OTP # 54 (#54)

I tried to retest this many times but unable to test this accurately even in the Dev environment because the OTP is being generated only after around 10 minutes time hence the OTP i enter is invalid already,

Objective of the test i exactly after 3 minutes which we are unable to achieve at the moment.

Dear Bavani,

Please take note as this issue is occurring in the Dev environment as well, Thanks

Best Regards,

Arjun Lokanath

Test Manager, AppSync

Malaysia HP: 01135443870

On Wed, Nov 16, 2016 at 11:20 AM, JasonABL <notifications@github.com mailto:notifications@github.com > wrote:

Hi Arjun,

Understood the document stated default value as 3. But it's dev environment, the value have changed for testing purpose. Have updated back the value to 3. Please try again, thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TNGSB/eWallet/issues/54#issuecomment-260842822 , or mute the thread https://github.com/notifications/unsubscribe-auth/AWCs_vrB92xGene5S08gT8mDRTr7qGqUks5q-naCgaJpZM4KxEhf . https://github.com/notifications/beacon/AWCs_ptZiWk5nAUyEU0xt9TgnwAwsIpzks5q-naCgaJpZM4KxEhf.gif

[markshermanp]

<Zharfan 2.12.16> Retest OK. Closed.