MPT-19124 remove module scope from fixtures

[jentyk]

Closes MPT-19124

• Changed e2e pytest fixtures to use function scope instead of module scope
  • Affected fixtures: mpt_vendor, async_mpt_vendor, mpt_ops, async_mpt_ops, mpt_client, and async_mpt_client
  • Each test function now receives a fresh instance of these fixtures instead of sharing a single instance across the entire test module
  • Client configuration logic via MPTClient.from_config and AsyncMPTClient.from_config remains unchanged

[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: ea727103-7d77-4214-8cd1-42a7d270b31f

📥 Commits

Reviewing files that changed from the base of the PR and between 7bd1fff and 43d6bfd.

📒 Files selected for processing (1)

• tests/e2e/conftest.py

---

📝 Walkthrough

Walkthrough

Six pytest fixtures in the end-to-end test configuration had their scope changed from module-level to function-level (default). The internal client construction logic remains unchanged; only fixture setup and teardown frequency is affected.

Changes

Cohort / File(s)	Summary
E2E Fixture Scope Adjustment tests/e2e/conftest.py	Six fixtures (mpt_vendor, async_mpt_vendor, mpt_ops, async_mpt_ops, mpt_client, async_mpt_client) changed from module scope to function scope by removing the scope="module" decorator parameter.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• MPT-14898 E2E for catalog units of measure #146: Modifies dependent fixture scopes (mpt_ops/async_mpt_ops) that are required by new test cases introduced in that PR.
• MPT-19124 remove fixture scope #264: Also modifies the same pytest fixtures in tests/e2e/conftest.py by adjusting their fixture scopes.
• MPT-19124 speed up tests #262: Changes scope configuration for the same six fixtures in tests/e2e/conftest.py but in a different direction (to session level).

🚥 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 MPT-19124 in the correct MPT-XXXX format.
Test Coverage Required	✅ Passed	PR modifies only test file (tests/e2e/conftest.py) with no production code changes in mpt_api_client/
Single Commit Required	✅ Passed	The PR contains exactly one commit (43d6bfd: fix(e2e): remove module scope from fixtures) as verified by comparing the current branch against the main branch, meeting the requirement for a single commit and keeping git history clean.

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

---

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

[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