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

Restructure relevant JMAP tests to cover CalDavEventAttendanceRepository #1545

Open
HoussemNasri opened this issue Feb 17, 2025 · 0 comments · May be fixed by #1554
Open

Restructure relevant JMAP tests to cover CalDavEventAttendanceRepository #1545

HoussemNasri opened this issue Feb 17, 2025 · 0 comments · May be fixed by #1554
Assignees

Comments

@HoussemNasri
Copy link
Member

HoussemNasri commented Feb 17, 2025

Why?

Because for CalDav we need to enable OpenPaas integration and not all tests are applicable for both Standalone and CalDav implementations.

How?

Create:

  • DavMemoryLinagoraCalendarEventAcceptMethodTest
  • DavMemoryLinagoraCalendarEventRejectMethodTest
  • DavMemoryLinagoraCalendarEventMaybeMethodTest,
  • DavMemoryLinagoraCalendarEventAttendanceGetMethodTest

that launches an OpenPaas and CalDav server along the TMail server to run the integration tests on.

The implementation is based on DAVClient, which does not utilize storage. Therefore, tests with the Distributed Server are not necessary.

Tests specific to the Standalone or CalDav implementations should be placed in a dedicated contract test class.

We need to create a new user for each test to achieve isolation. This would require that we generate email invitations dynamically.

DoD

  • Tests for CalDavEventAttendanceRepository should run on a real/dockerized OpenPaas server.
  • ~100% test coverage of CalDavEventAttendanceRepository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant