pytest

A ZeroDivisionError in pytest usually arises from dividing by zero during a test, often within custom test logic or fixtures. To fix it, carefully inspect the traceback to pinpoint the faulty calculation and ensure the denominator is never zero by adding conditional checks or using appropriate error handling techniques to prevent the division. Provide a default value or use `pytest.skip` if a zero denominator renders the test meaningless.

The "ModuleNotFoundError" in pytest usually indicates that a required Python package or module isn't installed or isn't in the Python path being used by pytest. To fix this, ensure that all necessary packages are installed, ideally using `pip install <package_name>`, and verify that your PYTHONPATH environment variable or pytest configuration correctly points to the location of the missing module if it's a custom one. You may need to activate the correct virtual environment if the module is installed there.

AssertionError in pytest usually indicates that a test's expected outcome doesn't match the actual result, signifying a failed assertion. To fix it, carefully examine the traceback to identify the specific assertion that failed and then adjust either the expected value or the code under test to ensure they align, or alternatively use `pytest.approx` to allow for small numerical differences. Debugging the test or the tested function is crucial to pinpoint the root cause of the discrepancy.

The "UncaughtCharmError" in pytest, often occurring in pdb or traceback displays, typically arises from incorrect handling of terminal size or encoding changes during exception processing. To fix this, ensure that the `CHARM_DEBUG` environment variable is not set (or is set to an empty string) and that pytest's terminal output configurations are compatible with the execution environment; try running pytest with the `--no-header` flag to simplify terminal interactions.

This error usually arises when accessing a non-existent attribute or method of an object within your pytest code (e.g., trying to read a nonexistent option added via pytest_addoption). Inspect the traceback to identify the problematic attribute and object. Ensure the attribute is correctly defined on the object or that the method is available; double-check for typos and correct option names passed to pytest_addoption.

UnicodeEncodeError in pytest often arises when the test output (including captured stdout/stderr, or parametrization values) contains characters that cannot be encoded using the default terminal encoding (like ASCII). Force pytest to use UTF-8 encoding by setting the `PYTHONIOENCODING=utf-8` environment variable before running pytest, or configure your system to use UTF-8 as the default encoding to ensure consistent encoding across environments.