Added checks for missing mock usage (#44). This change introduces new checks to a PyLint plugin for use with Databricks, specifically targeting the usage of mock objects in Python code. Two new checks, R8921 and R8922, have been developed to ensure the proper assignment and utilization of mock objects. R8921 checks for instances where a mock object is not assigned to a variable, suggesting an assignment to enable assertions. R8922 checks for situations where a mock object is used after creation, recommending an assertion, return value, or side effect for correct usage. To disable these checks on specific lines, users can add comments # pylint: disable=mock-no-assign or # pylint: disable=mock-no-usage. The commit also includes documentation and examples to guide users in implementing and disabling these checks, enhancing the overall quality and reliability of the code.
R8921andR8922, have been developed to ensure the proper assignment and utilization of mock objects.R8921checks for instances where a mock object is not assigned to a variable, suggesting an assignment to enable assertions.R8922checks for situations where a mock object is used after creation, recommending an assertion, return value, or side effect for correct usage. To disable these checks on specific lines, users can add comments# pylint: disable=mock-no-assignor# pylint: disable=mock-no-usage. The commit also includes documentation and examples to guide users in implementing and disabling these checks, enhancing the overall quality and reliability of the code.