Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add click to entire user row. #126

Merged
merged 3 commits into from
Nov 15, 2023
Merged

Conversation

Chakravarthy7102
Copy link
Contributor

@Chakravarthy7102 Chakravarthy7102 commented Nov 15, 2023

Summary of change

Adds click action to user row.

Problem Statement

(A few sentences about why this change is being made)

Summary of solution

(Overview of how the problem is solved by this PR)

Related issues

  • Link to issue1 here
  • Link to issue1 here

Test Plan

Tested on all primary browsers for:

  • Chrome
    • Desktop
    • Mobile
    • Tablet
  • Safari
    • Desktop
    • Mobile
    • Tablet
  • Firefox
    • Desktop
    • Mobile
    • Tablet
  • (Optional) Tested on Safari 12 (Physical or emulator)
    • iPad
    • iPhone
  • (Optional) Tested on physical mobile and tablet device for:
    • Android
    • iOS (including iPadOS)

Feature tests:

  • Search
    • Search with anything that results in an empty state in the UI (Should show an empty state explaining that there were no results)
    • Search with an empty string (Dashboard should not allow this)
    • Email search
      • Serach for "e" with email tag and then delete the tag (Should show one user initially then show all with pagination enabled)
      • Search for "test" with the email tag (Expect 14 results)
      • Search with "g" for email tag (Expect 3 results)
      • Search with "g" and "p" for email tag (Expect 3 results)
      • Search with "g" and "t" for email tag, then delete "t" (Expect 17 results initially, then 3)
      • Search with "@" for email tag (Expect 0 results (This is because at the time of adding this case we would only check for the start of the email or the domain and not any character inside the full email))
      • Search for "[email protected]" with email tag (Expect 1 result)
      • Search for "[email protected]" with email tag (Expect 3 results)
      • Search for "gmail" with email tag (Expect 3 results)
      • Search for "ABC" with email tag (Expect 0 results)
      • Search for "a" with email tag (Expect 0 results (This is because at the time of adding this we only check if the email starts with the query and not contains))
      • Search for "team" with email tag (Expect 0 results)
      • Search for "782" with email tag (Expect 1 result)
    • Phone search
      • Search for "1" with phone tag (Expect 3 results)
      • Search for "+1" with phone tag (Expect 3 results)
      • Search for "91" with phone tag (Expect 1 result)
      • Search for "291" with phone tag (Expect 0 results)
      • Search for "+12" with phone tag (Expect 2 results)
      • Search for "5" with phone tag (Expect 0 results)
      • Search for "1(" with phone tag (Expect 0 results (This is because we render phone numbers with brackets so users may end up searching with that))
    • Provider search
      • Search for "g" with provider tag (Expect 5 results)
      • Search for "gi" with provider tag (Expect 2 results)
      • Search for "t" with provider tag (Expect 0 results)
      • Search for "google" with provider tag (Expect 3 results)
    • Combination testing
      • Search with "g" for email tag and "g" for provider tag (Expect 1 result)
      • Search for "github" with provider tag and "782" with email tag (Expect 1 result)
      • Search for "github" and "google" with provider tag (Expect 5 results)
      • Search for "j" and "g" with email tag (Expect 6 results)
      • Search for "1" and "91" with phone tag (Expect 4 results)
      • Search with "google" for provider tag and "1" for phone tag (Expect 0 results)
      • Search for "g" with email tag and "1" with phone tag (Expect 0 results)
      • Search for "k" with provider and "a", "g", "b" (in that order) for email (Expect 0 resutls)
  • General UI testing
    • Test that emty state renders fine (no overflow, no UI glitches, responsiveness etc)
    • Test that the list renders fine (no overflow, no UI glitches, responsiveness etc)
    • Test that pagination is visiable and usable (There should be at least 2 pages worth of users)
    • Test that the list only shows 10 users at a time
    • Test that for users with no accounts linked the auth method i nthe list is correct
    • Test that for users with multiple login methods, the auth method shows correctly
    • Test that search is visible if the feature is enabled
  • Multi tenant testing
    • Create one tenant (tenant1), and add 3 users to them. In the dashboard, when you switch to that tenant, it should list those users.
    • Create a user in tenant1 and using backend sdk's(Go, Python, Node) associate the user to a different tenant and select that tenant on the dashboard from the tenants dropdown, it should show that user in the list

Documentation changes

(If relevant, please create a PR in our docs repo, or create a checklist here highlighting the necessary changes)

Checklist for important updates

  • Changelog has been updated
  • Changes to the version if needed
    • In package.json
    • In package-lock.json
    • In src/version.ts
  • Had run npm run build
  • Had installed and ran the pre-commit hook

Remaining TODOs for this PR

  • Item1
  • Item2

@rishabhpoddar rishabhpoddar merged commit bd916ae into master Nov 15, 2023
3 checks passed
@rishabhpoddar rishabhpoddar deleted the fix/handle-row-click branch November 15, 2023 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants