nextcloud / nextcloud/mail

JMAP UI and Integration Testing

Open
#12,612 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Summary

Add protocol selection to account setup UI and implement integration tests against Stalwart JMAP server.

Problem

Without UI for protocol selection, users cannot create JMAP accounts. Without integration tests,
JMAP support cannot be reliably maintained.

Solution

  • Add protocol selector (IMAP / JMAP) to account creation form
  • Display protocol in account info
  • Route validation based on selected protocol
  • Set up Stalwart JMAP server in CI
  • Implement comprehensive integration tests

Implementation

Frontend changes:

  • Add protocol selector in account creation (Vue component)
  • Default to IMAP for backwards compatibility
  • Store protocol selection with account
  • Display protocol in account list and settings

CI changes:

  • Add Stalwart docker service to CI pipeline (similar to Dovecot)
  • Configure test accounts and mailboxes
  • Implement integration test suite

Integration tests cover:

  • Account creation for both IMAP and JMAP
  • Mailbox sync
  • Message fetching
  • Flag operations
  • Move/copy/delete operations
  • Error cases

Documentation:

  • Update README with JMAP support notes
  • Document limitations and out-of-scope features
  • Create follow-up tracking issue for future enhancements

Affected Components

  • Frontend: account creation and settings components
  • CI: workflow configuration
  • Documentation: README and related docs
  • New: integration test suite under tests/Integration/

Acceptance Criteria

  • Protocol selector visible in account creation
  • IMAP and JMAP accounts can be created
  • Protocol is stored and displayed
  • Integration tests pass for both protocols
  • CI runs tests reliably
  • Documentation updated
  • Follow-up tracking issue created

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing account creation and settings Vue components, then inspect the Dovecot-like CI service configuration and the new tests/Integration/ area. Verify both IMAP and JMAP account flows, mailbox and message operations, and error cases for both protocols. Done means the CI tests pass reliably, the README documents support and limitations, and a follow-up tracking issue exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript
Domain
ci-cd, documentation, frontend, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.