MPT-18371 mark helpdesk chat tests as flaky

[jentyk]

Closes MPT-18371

• Mark all tests in tests/e2e/helpdesk/chats/test_async_chats.py as flaky by adding module-level pytest.mark.flaky marker
• Mark all tests in tests/e2e/helpdesk/chats/test_sync_chats.py as flaky by adding module-level pytest.mark.flaky marker

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 3844f536-44ad-45d7-882a-6540ba89e7fd

📥 Commits

Reviewing files that changed from the base of the PR and between a2d90ec and b0004b4.

📒 Files selected for processing (2)

• tests/e2e/helpdesk/chats/test_async_chats.py
• tests/e2e/helpdesk/chats/test_sync_chats.py

---

📝 Walkthrough

Walkthrough

Module-level flaky markers are added to two test files in the e2e helpdesk chats test suite. These changes designate all tests in each module as flaky using pytest's mark.flaky mechanism, requiring no modifications to existing test logic or assertions.

Changes

Cohort / File(s)	Summary
Test Flaky Markers tests/e2e/helpdesk/chats/test_async_chats.py, tests/e2e/helpdesk/chats/test_sync_chats.py	Add module-level pytestmark = [pytest.mark.flaky] to mark all tests in each module as flaky for pytest handling.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Jira Issue Key In Title	✅ Passed	The PR title contains exactly one Jira issue key in the correct format MPT-18371.
Test Coverage Required	✅ Passed	The PR exclusively modifies test files within the tests/ folder by adding pytest flaky markers. No production code files in the mpt_api_client/ directory are modified.
Single Commit Required	✅ Passed	The PR contains exactly one commit (b0004b4) that adds pytest.mark.flaky marker to both test files.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can scan for known vulnerabilities in your dependencies using OSV Scanner.

OSV Scanner will automatically detect and report security vulnerabilities in your project's dependencies. No additional configuration is required.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud