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

Implement tests for CalendarViewModel #27

Closed
othbcq opened this issue Oct 13, 2024 · 1 comment
Closed

Implement tests for CalendarViewModel #27

othbcq opened this issue Oct 13, 2024 · 1 comment
Assignees

Comments

@othbcq
Copy link
Contributor

othbcq commented Oct 13, 2024

Description:

The CalendarViewModel currently lacks sufficient unit tests to verify its core functionalities. Implement comprehensive unit tests to ensure the model behaves as expected, particularly around event filtering, sorting, and handling recurring and multi-day events.

Tasks:

  • Write unit tests for filtering and sorting events.
  • Test the handling of recurring events, ensuring they are properly processed and displayed.
  • Test multi-day event handling to confirm accurate representation across consecutive days.
  • Ensure edge cases are covered (e.g., events spanning the start or end of the testing period).
@othbcq
Copy link
Contributor Author

othbcq commented Oct 16, 2024

Closing this issue to combine with #39

After reviewing both tasks, I’ve decided to combine this issue with issue #39 to streamline the development process. Since both issues relate to the CalendarViewModel and the Calendar feature, it makes sense to address them together. By merging the two, I’ll be able to manage everything in one pull request instead of two, ensuring a more efficient and cohesive update for the calendar functionality.

@othbcq othbcq closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2024
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

When branches are created from issues, their pull requests are automatically linked.

1 participant