User Login Testing

[coltd76]

Test Results of User Login Test Cases here: https://github.com/btswann11/CSE550/blob/main/test-plans/user-login.md
Use #47 (comment) as example

[coltd76]

I know it's early in the code but ran the user login tests now to highlight what requirements we still need to update. can update this doc with each test run

User Login Test Results.md

[btswann11]

Feature improvement: The login page/user agreement is only available in English. The flow should be updated as below:

Choose language -> User agreement -> Username selection -> using app

[btswann11]

Test 1a: User Declines Pre-login Warning Screen

This test covers requirements: NFR5, FR14

Steps:

1. Navigate to the web application's root URL.- PASS
2. Verify that a warning screen is immediately displayed before any login or input is available.- PASS
3. Confirm the screen contains a message not to share sensitive information.- PASS
4. Confirm the screen asks for age confirmation (18+).- FAIL: a comment has been left in the PR to include this, so we will allow it
5. Select "Decline" on the user agreement or age confirmation.- PASS
6. Verify that a message is displayed stating: "You must accept the user agreement and be 18 years or older."- FAIL: a comment has been left on the PR to include this
7. Confirm that the user is not allowed to use the app and cannot proceed further.- PASS
8. Attempting to interact with the app should not allow access; the only way to proceed is to refresh the webpage and accept the agreement.- PASS

Overall result: PASS- Some wording needs to be updated but these have already been addressed via PR comments

[btswann11]

Test 1b: User Accepts Pre-login Warning Screen

This test covers requirements: NFR5, FR14

Steps:

1. Navigate to the web application's root URL.- PASS
2. Verify that a warning screen is immediately displayed before any login or input is available.- PASS
3. Confirm the screen contains a message not to share sensitive information.- PASS
4. Confirm the screen asks for age confirmation (18+).- FAIL: same as test 1a
5. Select "Accept" on the user agreement and age confirmation.- PASS
6. Verify that the user is allowed to move forward to the username/language setup.- PASS

Overall result: PASS- similar to 1a there are some wording changes to make that have already been addressed

[btswann11]

Test 2a: Username Uniqueness and Validation

This test covers requirement: FR1

Steps:

1. Proceed to the user setup page and accept the popup.- PASS
2. Enter a username that is already in use (e.g., "testuser1").- PASS
3. Open a separate browser and repeat steps 1 and 2- PASS
4. Verify that a warning appears stating the username is already in use.- FAIL: duplicate username can be made
5. Enter a new, unique username (e.g., "newuser123").
6. Select a native language from the dropdown.
7. Submit the form.
8. Verify that the user is successfully taken to the chat interface, confirming the setup is accepted.

Overall result: FAIL- multiple users with the same name can be made. Doesnt seem to make a difference whether its the same or a different language selected. Attempts have been made to try and trigger the notification but using a new tab, new browser, or incognito makes no difference. Bug ticket made here: #52

[btswann11]

Test 2b: Username Field Validation (Empty and Invalid Input)

This test covers requirement: FR1

Steps:

1. Proceed to the user setup page.- PASS
2. Leave the username field empty and try to proceed.- PASS
3. Verify that an error message appears indicating the field is required.- PASS
4. Enter a username with invalid characters (e.g., "!!!" or spaces).- PASS: Exclamations are valid characters but spaces are not if they are the only characters in the username
5. Verify that the system rejects the input with a relevant message.- FAIL: a relevant message is not displayed, but the user cannot proceed without choosing a valid username
6. Enter a valid username to confirm validation success. PASS

Overall result: PASS- having punctuation in the name is not part of the requirements and it makes sense to allow for it. Spaces may be debatable but it does not let you proceed with a blank name. A low priority bug ticket can be made to account for a message not being displayed when the username chosen is all spaces

[btswann11]

TEST OMIT: this is a repeat of test 1b. There is no requirement to have a persistent message display to not share sensitive information. Inclusion may lead to disruption and an ugly UI when the user has already accepted the initial notice

Test 3: Sensitive Info Warning Is Always Displayed

This test covers requirement: FR14

Steps:

1. From a new browser session, access the website.
2. On the pre-login screen, confirm a warning is shown stating not to share personal or sensitive information.
3. Complete the setup and enter the chat interface.
4. Verify that the same warning is also repeated or displayed in a persistent notice, banner, or tooltip in the chat UI.

[btswann11]

Test 4: Prevent Unauthorized Session Access

This test covers requirement: FR15

Steps:

1. Open the web app in one browser window, complete setup, and enter a chat session.- PASS
2. Copy the session/chat URL.- PASS
3. Open an incognito/private window and paste the same URL.- PASS
4. Verify that the session does not open directly without completing the setup.- PASS
5. Confirm that the user is redirected to the pre-login warning screen or setup page instead.- PASS

Overall result: PASS

[btswann11]

Test Results:

• Test Cases Planned: 6
• Test Cases Executed: 5
• Test Cases Passed: 4
• Test Cases Failed: 1