Win10,Chrome - Sign In -Unable to sign in with valid email as field is case sensitive #2621
Labels
Applause C5
Applause testing for new QA environment
HTD
P0: Critical path blocker
Blocking testing or the launch critical path, drop everything to investigate & fix
Milestone
View your issue at Applause Testing Services - https://platform.applause.com/products/27563/testcycles/357144/issues/5503186
---- ACTION DETAILS ----
Action Performed:
Pre:
The cache is cleared
Expected Result:
User successfully signed in
Actual Result:
Error message pops up: Wrong username or password
if user Enters same email with a capital letter - Aleut15@gmail and tap Sign in. Then signing in goes as expected.
. Apparently, the email field is not case sensitive on Sign in, even though capitalization on Sign Up page was ignored as expected
Additional Info:
Error Code/Message:
---- ENVIRONMENT ----
Antivirus:Kaspersky,Language:English,Operating System:Windows,Web Browser:Chrome,Desktop Accessories:Webcam,Desktop Accessories:Microphone,Desktop Accessories:Headset,Operating System Version:10,Operating System Major Version:Windows 10
---- APPLAUSE PROPERTIES ----
Applause Issue/Bug ID: 5503186
Title: Win10,Chrome - Sign In -Unable to sign in with valid email as field is case sensitive
Status: New
Type: Functional
Frequency: Every Time
Severity: High
Product (Build): Global Health (Global Health.QA URL)
Test Cycle: Global Health - QA Test Cycle - 3/23/2022
---- 1 Community Reproductions ----
Greeshma K on 2022-03-23 22:06:35.0
macOS - Monterey 12.X - Monterey 12.0.1 - English - Safari
Attachments:
Screen_Shot_2022-03-23_at_6.05.35_PM.png : https://utest-dl.s3.amazonaws.com/5503186/bugReproduction/2117699/Screen_Shot_2022-03-23_at_6.05.35_PM.png?AWSAccessKeyId=AKIAJ2UIWMJ2OMC3UCQQ&Expires=1963836460&Signature=8OmTTh3wSw0InrqymTMW0Z6A4AY%3D
---- APPLAUSE ATTACHMENT(S) ----
Bug5503186_SignIn.mp4 : https://utest-dl.s3.amazonaws.com/6414/27563/357144/5503186/bugAttachment/Bug5503186_SignIn.mp4?AWSAccessKeyId=AKIAJ2UIWMJ2OMC3UCQQ&Expires=1963836460&Signature=XcOUPxWy7dCvbJzdlU4eLYb1t2E%3D
The text was updated successfully, but these errors were encountered: