Write Pytest Fixtures and Parametrized Tests for Python Applications

Write a comprehensive pytest test suite for a Python [MODULE_TYPE (e.g., service class, utility module, API client)] called [MODULE_NAME] that handles [FUNCTIONALITY_DESCRIPTION (e.g., user authentication, payment processing, data transformation)]. Module Under Test: - Key methods/functions to test: [LIST_METHODS (e.g., create_user, validate_token, calculate_total)] - External dependencies to mock: [DEPENDENCIES (e.g., database session, HTTP client, Redis cache)] - Expected exceptions: [EXCEPTION_TYPES (e.g., ValueError, NotFoundError, AuthenticationError)] Please generate the following: 1. **Fixtures (conftest.py)**: - A session-scoped fixture for [SHARED_RESOURCE (e.g., database connection, test configuration)]. - A function-scoped fixture that provides a fresh instance of [MODULE_NAME] with mocked dependencies. - A fixture that yields sample test data for [RESOURCE_NAME] and handles teardown/cleanup. - Use @pytest.fixture with appropriate scopes and autouse where justified. 2. **Parametrized Tests**: - Use @pytest.mark.parametrize to test [METHOD_NAME] with at least 5 variations: valid input, boundary values, invalid types, empty input, and edge cases. - Include IDs for each parameter set for readable test output. - Add a parametrized test that verifies correct exceptions are raised for invalid scenarios. 3. **Test Organization**: - Group tests in a class named Test[MODULE_NAME]. - Include setup/teardown methods where appropriate. - Add markers for slow tests and integration tests. - Use unittest.mock.patch or pytest-mock for dependency isolation. 4. **Assertions**: - Use specific assertions (assert x == y, not just assert x). - Verify mock call counts and arguments with assert_called_once_with. Provide the complete conftest.py and test file with comments explaining fixture scope choices.