Skip to content

Conversation

@ShivaGupta-14
Copy link
Contributor

@ShivaGupta-14 ShivaGupta-14 commented Jan 21, 2026

Description

  • Use test.each to keep similar tests clean, readable, and DRY

  • Reorganize existing tests into proper describe blocks

  • Add tests for Keyboard Navigation (ArrowUp, ArrowDown, boundary stops)

  • Add tests for Hotkey Shortcuts ('a', 'c', 'd', 'f', 'p', 'r', 's', 't')

  • Add tests for complete/delete hotkeys when dialog is already open

  • Add test for hotkeys disabled when input is focused

  • Add tests for Hotkeys Enable/Disable on Hover

  • Update MultiSelectFilter mock to use aria-expanded for behavior testing

  • Remove unnecessary mock override in overdue filter test

  • Contributes: Add frontend test suites/cases for src/components/HomeComponents/Tasks #300

Checklist

  • Ran npx prettier --write . (for formatting)
  • Ran gofmt -w . (for Go backend)
  • Ran npm test (for JS/TS testing)
  • Added unit tests, if applicable
  • Verified all tests pass
  • Updated documentation, if needed

Additional Notes

Before:

Screenshot 2026-01-22 at 1 33 20 AM

After:

Screenshot 2026-01-22 at 1 34 18 AM

Note

This is Part 1 of 3 for comprehensive Tasks.tsx test coverage.

  • PR 1: Keyboard navigation and hotkey tests

Will open the remaining PRs after completing review of this pr.

- Reorganize existing tests into proper describe blocks
- Add tests for Keyboard Navigation (ArrowUp, ArrowDown, boundary stops)
- Add tests for Hotkey Shortcuts ('a', 'c', 'd', 'f', 'p', 'r', 's', 't')
- Add tests for complete/delete hotkeys when dialog is already open
- Add test for hotkeys disabled when input is focused
- Add tests for Hotkeys Enable/Disable on Hover
- Update MultiSelectFilter mock to use aria-expanded for behavior testing
- Remove unnecessary mock override in overdue filter test
@github-actions
Copy link

Thank you for opening this PR!

Before a maintainer takes a look, it would be really helpful if you could walk through your changes using GitHub's review tools.

Please take a moment to:

  • Check the "Files changed" tab
  • Leave comments on any lines for functions, comments, etc. that are important, non-obvious, or may need attention
  • Clarify decisions you made or areas you might be unsure about and/or any future updates being considered.
  • Finally, submit all the comments!

More information on how to conduct a self review:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request

This helps make the review process smoother and gives us a clearer understanding of your thought process.

Once you've added your self-review, we'll continue from our side. Thank you!

@its-me-abhishek
Copy link
Collaborator

its-me-abhishek commented Jan 23, 2026

Hey @ShivaGupta-14, thanks for the PR! This one is similar to #356, and similar to earlier discussion, with all the tests and changes it’s a bit heavy to review in one go. Might be better to break it down and open PRs per sub-component smaller diffs will make reviews smoother.

About Part 1 of 3 (and upcoming parts), feel free to open up a separate issue or a tracker for these, and breakdown these further as required.

EDIT: For ex: Just add describe('Keyboard Navigation' in one PR, and so on

@its-me-abhishek
Copy link
Collaborator

Closing for now

@ShivaGupta-14
Copy link
Contributor Author

ShivaGupta-14 commented Jan 24, 2026

Hi @its-me-abhishek!
this PR actually contains ~200 lines of new changes, the rest are due to refactoring the tests into proper describe blocks, that’s why i included both in a single PR

as you suggested, I have now created a tracker issue #433 and open further smaller PRs for easier review :)

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