Files
Charon/docs/issues/manual_test_smtp_mock_flakiness_fix.md
akanealw eec8c28fb3
Some checks are pending
Go Benchmark / Performance Regression Check (push) Waiting to run
Cerberus Integration / Cerberus Security Stack Integration (push) Waiting to run
Upload Coverage to Codecov / Backend Codecov Upload (push) Waiting to run
Upload Coverage to Codecov / Frontend Codecov Upload (push) Waiting to run
CodeQL - Analyze / CodeQL analysis (go) (push) Waiting to run
CodeQL - Analyze / CodeQL analysis (javascript-typescript) (push) Waiting to run
CrowdSec Integration / CrowdSec Bouncer Integration (push) Waiting to run
Docker Build, Publish & Test / build-and-push (push) Waiting to run
Docker Build, Publish & Test / Security Scan PR Image (push) Blocked by required conditions
Quality Checks / Auth Route Protection Contract (push) Waiting to run
Quality Checks / Codecov Trigger/Comment Parity Guard (push) Waiting to run
Quality Checks / Backend (Go) (push) Waiting to run
Quality Checks / Frontend (React) (push) Waiting to run
Rate Limit integration / Rate Limiting Integration (push) Waiting to run
Security Scan (PR) / Trivy Binary Scan (push) Waiting to run
Supply Chain Verification (PR) / Verify Supply Chain (push) Waiting to run
WAF integration / Coraza WAF Integration (push) Waiting to run
changed perms
2026-04-22 18:19:14 +00:00

1.8 KiB
Executable File

title, status, priority, assignee, labels
title status priority assignee labels
Manual Test Plan - SMTP Mock Server Flakiness Fix Open High QA testing, backend, reliability

Test Objective

Confirm the SMTP mock server flakiness fix improves mail test reliability without changing production mail behavior.

Scope

  • In scope: test reliability for SMTP mock server flows used by backend mail tests.
  • Out of scope: production SMTP sending behavior and user-facing mail features.

Prerequisites

  • Charon repository is up to date.
  • Backend test environment is available.
  • Ability to run backend tests repeatedly.

Manual Scenarios

1) Target flaky test repeated run

  • Run TestMailService_TestConnection_StartTLSSuccessWithAuth repeatedly (at least 20 times).
  • Record pass/fail count and any intermittent errors.

2) Mail service targeted subset run

  • Run mail service connection and send test subset once.
  • Confirm no new intermittent failures appear in related tests.

3) Race-focused verification

  • Run targeted mail service tests with race detection enabled.
  • Confirm no race warnings or hangs occur.

4) Cleanup/shutdown stability check

  • Repeat targeted runs and watch for stuck test processes or timeout behavior.
  • Confirm test execution exits cleanly each run.

Expected Results

  • Repeated target test runs complete with zero flaky failures.
  • Related mail service test subset remains stable.
  • No race detector findings for targeted scenarios.
  • No hangs during test cleanup/shutdown.

Regression Checks (No Production Impact)

  • Confirm only test reliability behavior changed; no production mail behavior changes are required.
  • Confirm no production endpoints, settings, or user-facing mail flows are affected.
  • Confirm standard backend test workflow still completes successfully after this fix.