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

add Christina to fixtures list #2062

Merged
merged 7 commits into from Apr 24, 2024
Merged

add Christina to fixtures list #2062

merged 7 commits into from Apr 24, 2024

Conversation

kristinacyin
Copy link
Contributor

Ticket

Resolves #2052

Changes

  • Change 1
  • Change 2

Context for reviewers

Setup

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

  • Met the acceptance criteria, or will meet them in a subsequent PR
  • Created/modified automated tests
  • Added at least 2 developers as PR reviewers (only 1 will need to approve)
  • Messaged on Slack or in standup to notify the team that a PR is ready for review
  • Changes to “how we do things” are documented in READMEs and or onboarding guide
  • If any model was updated to modify/add/delete columns, makemigrations was ran and the associated migrations file has been commited.

Ensured code standards are met (Original Developer)

  • All new functions and methods are commented using plain language
  • Did dependency updates in Pipfile also get changed in requirements.txt?
  • Interactions with external systems are wrapped in try/except
  • Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

  • New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
  • Checked keyboard navigability
  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
  • Add at least 1 designer as PR reviewer

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

  • Pulled this branch locally and tested it
  • Reviewed this code and left comments
  • Checked that all code is adequately covered by tests
  • Made it clear which comments need to be addressed before this work is merged
  • If any model was updated to modify/add/delete columns, makemigrations was ran and the associated migrations file has been commited.

Ensured code standards are met (Code reviewer)

  • All new functions and methods are commented using plain language
  • Interactions with external systems are wrapped in try/except
  • Error handling exists for unusual or missing values
  • (Rarely needed) Did dependency updates in Pipfile also get changed in requirements.txt?

Validated user-facing changes as a developer

  • New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing

  • Checked keyboard navigability

  • Meets all designs and user flows provided by design/product

  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

  • Tested with multiple browsers, the suggestion is to use ones that the developer didn't (check off which ones were used)

    • Chrome
    • Microsoft Edge
    • FireFox
    • Safari
  • (Rarely needed) Tested as both an analyst and applicant user

Note: Multiple code reviewers can share the checklists above, a second reviewers should not make a duplicate checklist

As a designer reviewer, I have

Verified that the changes match the design intention

  • Checked that the design translated visually
  • Checked behavior
  • Checked different states (empty, one, some, error)
  • Checked for landmarks, page heading structure, and links
  • Tried to break the intended flow

Validated user-facing changes as a designer

  • Checked keyboard navigability

  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

  • Tested with multiple browsers (check off which ones were used)

    • Chrome
    • Microsoft Edge
    • FireFox
    • Safari
  • (Rarely needed) Tested as both an analyst and applicant user

Screenshots

@kristinacyin kristinacyin removed the request for review from abroddrick April 22, 2024 16:15
zandercymatics
zandercymatics previously approved these changes Apr 24, 2024
Copy link
Contributor

@zandercymatics zandercymatics left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zandercymatics zandercymatics dismissed their stale review April 24, 2024 16:08

Merge conflicts

Copy link
Contributor

@zandercymatics zandercymatics left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code-wise this looks great. However, it looks like there is a merge conflict that you'd need to resolve before merging this. Once thats resolved, I can take a quick look over and approve!

Let me know if you need any help on it

@zandercymatics zandercymatics self-assigned this Apr 24, 2024
Copy link

🥳 Successfully deployed to developer sandbox ky.

1 similar comment
Copy link

🥳 Successfully deployed to developer sandbox ky.

Copy link

🥳 Successfully deployed to developer sandbox ky.

Copy link

🥳 Successfully deployed to developer sandbox ky.

Copy link
Contributor

@therealslimhsiehdy therealslimhsiehdy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM -- did a cross comparison with the one Alysia made for Riley recently and looks great!

Quick question: Would Christina want to change the Analyst email to christina.burnett+1@cisa.dhs.gov, or does @gwe...send to the same email? (Asking bc I'm not sure if it sends to the same mailbox, which may be easier sometimes for testing)

@therealslimhsiehdy therealslimhsiehdy self-assigned this Apr 24, 2024
@kristinacyin
Copy link
Contributor Author

LGTM -- did a cross comparison with the one Alysia made for Riley recently and looks great!

Quick question: Would Christina want to change the Analyst email to christina.burnett+1@cisa.dhs.gov, or does @gwe...send to the same email? (Asking bc I'm not sure if it sends to the same mailbox, which may be easier sometimes for testing)

For some reason the +1 didn't work for her, so we're using the @gwe.cisa.dhs.gov email instead. It doesn't send to the same inbox as the @cisa.dhs.gov one unfortunately

@kristinacyin kristinacyin merged commit bc77ad7 into main Apr 24, 2024
9 of 10 checks passed
@kristinacyin kristinacyin deleted the ky/add-christina-fixtures branch April 24, 2024 20:37
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.

Add Christina to fixtures
3 participants