Tracking Issue: Tasks Component Test Improvements #433

Activity

1. its-me-abhishek commented on Jan 24, 2026

   

   its-me-abhishek

   on Jan 24, 2026

   Collaborator

   More actions

   Do change this to separate checklist for each component for which tests are yet to be added or updated. And the reorg tasks as well

   👍React with 👍1Reacted by Shiva Gupta
2. adiprathapa commented on Mar 19, 2026

   

   adiprathapa

   on Mar 19, 2026

   Contributor

   More actions

   Added Reports Toggle tests, opening a PR now
3. adiprathapa

   added a commit that references this issue on Mar 19, 2026

   test(Tasks): add Reports Toggle tests

   ...

   dad7e6a
4. its-me-abhishek

   added a commit that references this issue on May 24, 2026

   test(Tasks): add Reports Toggle tests (#467)

   ...

   3729006
5. Aspirant200715 commented on Nov 12, 2026

   

   Aspirant200715

   on Nov 12, 2026

   Last edited by Aspirant200715

   More actions

   Hi @its-me-abhishek,

   I've implemented unit test coverage for the Recur Editing checklist item in Tasks and opened a focused PR: #479.

   The test suite covers:

   • Saving recurrence frequencies: Verifies that valid recurrence values (weekly, monthly, etc.) are correctly persisted through editTaskOnBackend.
   • Handling none: Ensures that selecting none triggers the guard logic and prevents unnecessary API requests.
   • Cancel functionality: Verifies that clicking Cancel discards the changes and restores the original recurrence state without invoking the backend.

   All tests are passing locally, and no production code has been modified.

   Happy to address any feedback. Thanks!
6. Aspirant200715 commented on Nov 12, 2026

   

   Aspirant200715

   on Nov 12, 2026

   More actions

   Hi @its-me-abhishek,

   Following up on the Recur tests (#479), I've also implemented unit test coverage for the Annotation Editing checklist item in Tasks and opened a PR: #480 .

   The test suite covers:

   • Adding annotations: Verifies that entering an annotation and pressing Enter correctly adds it and persists it to the backend via handleSaveAnnotations / editTaskOnBackend.
   • Removing annotations: Ensures that clicking the inline removal button (✖) removes the annotation from editedAnnotations before saving.
   • Input validation: Verifies that empty or whitespace-only inputs are ignored and do not create empty annotation badges.
   • Cancel functionality: Ensures that clicking Cancel dismisses the editor without triggering unnecessary API calls.

   All 4 test cases are passing locally, and the complete Tasks test suite passes with 10 tests across 3 test files.

   Happy to address any reviews and feedback. Thanks!