Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test failures with python 3.11+ #364

Open
shish opened this issue Mar 27, 2024 · 0 comments
Open

Test failures with python 3.11+ #364

shish opened this issue Mar 27, 2024 · 0 comments

Comments

@shish
Copy link
Contributor

shish commented Mar 27, 2024

I'm using TestSlide version: f22c183

Given: no changes

When I run: make

I expected this to happen: tests pass

But, instead this happened:

  1) mock_constructor(), patching mechanism, original class attribute access: can call class methods
    1) TypeError: Target.regular_class_method() missing 1 required positional argument: 'cls'
      File "testslide/runner.py", line 837, in run
        self._run_example(example)
      File "testslide/runner.py", line 821, in _run_example
        ).run()
      File "testslide/__init__.py", line 534, in run
        self._sync_run_all_hooks_and_example(context_data)
      File "testslide/__init__.py", line 506, in _sync_run_all_hooks_and_example
        aggregated_exceptions.raise_correct_exception()
      File "testslide/__init__.py", line 275, in raise_correct_exception
        raise self.exceptions[0]
      File "testslide/__init__.py", line 259, in catch
        yield
      File "testslide/__init__.py", line 497, in _sync_run_all_hooks_and_example
        self._fail_if_coroutine_function(self.example.code, context_data)
      File "testslide/__init__.py", line 465, in _fail_if_coroutine_function
        return func(*args, **kwargs)
      File "tests/mock_constructor_testslide.py", line 214, in can_call_class_methods
        self.assertEqual(getattr(original_target_class, name)(), name)
shish added a commit that referenced this issue Mar 27, 2024
The first attempt was landed too soon and reverted - turns out that 3.11+ actually have real breakages that we need to fix before we can call them supported
shish added a commit that referenced this issue Mar 27, 2024
The first attempt was landed too soon and reverted - turns out that 3.11+ actually have real breakages that we need to fix before we can call them supported
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant