fixture 'aiohttp_client' not found

[eLvErDe]

Hello,

I'm not able to run the unittest and I don't understand why. Here is what happens:

==================================== ERRORS ====================================
______________________ ERROR at setup of test_get_payload ______________________
file /tmp/aiohttp-jwt-0.1.1/tests/test_middleware.py, line 13
  async def test_get_payload(create_app, aiohttp_client, fake_payload, token):
      async def handler(request):
          assert request.get('payload') == fake_payload
          return web.json_response({'status': 'ok'})
      routes = (('/foo', handler),)
      client = await aiohttp_client(create_app(routes))
      response = await client.get('/foo', headers={
          'Authorization': 'Bearer {}'.format(token.decode('utf-8')),
      })
      assert response.status == 200
E       fixture 'aiohttp_client' not found
>       available fixtures: cache, capfd, caplog, capsys, capturelog, cov, create_app, doctest_namespace, event_loop, event_loop_process_pool, fake_payload, fast, loop, monkeypatch, pytestconfig, raw_test_server, record_xml_property, recwarn, secret, shorttmpdir, test_client, test_server, tmpdir, tmpdir_factory, token, unused_port, unused_tcp_port, unused_tcp_port_factory
>       use 'pytest --fixtures [testpath]' for help on them.

Thanks in advance for your support

[hzlmn]

Hello, it is because this fixture available only in aiohttp >= 3.0. Previously it was named test_client. Seems like you ran tests against older version of aiohttp.

[eLvErDe]

Yes absolutely, 2.2.x.
Is there any way to detect this ?

[hzlmn]

I guess, you can create proxy fixture like

@pytest.fixture
def aiohttp_client(test_client):
    return test_client

and add it to conftest file.
But i am wondering why do you want to run tests on older version? Also note that middleware works only with aiohttp >= 2.3.5

[eLvErDe]

Well, basically I started rewriting some APIs at work using aiohttp and the easiest way for me to deploy libraries among executors machines is to create Debian package for them.
It's a standard practise to run unit tests at the end of the package building. We're using aiohttp 2.2.3 and I don't want to update this at the moment.

According to my first tests today, your middleware is working just fine with this version, but I'd feel relaxed if I could see all unittests running fine ;)

[hzlmn]

Okay, I got your point. Could you please tell how did you build .deb package? I actually tested it locally with aiohttp 2.2.3 and with latests pytest-aiohttp it works fine.

[hzlmn]

Closing due to inactivity. Feel free to reopen it if necessary.