The engine_helpers tox test fails

[Elliria]

AutoKey is a Xorg application and will not function in a Wayland session. Do you use Xorg (X11) or Wayland?

Xorg

Has this issue already been reported?

• I have searched through the existing issues.

Is this a question rather than an issue?

• This is not a question.

What type of issue is this?

None

Choose one or more terms that describe this issue:

• autokey triggers
• autokey-gtk
• autokey-qt
• beta
• bug
• critical
• development
• documentation
• enhancement
• installation/configuration
• phrase expansion
• scripting
• technical debt
• user interface

Other terms that describe this issue if not provided above:

testing

Which Linux distribution did you use?

Kubuntu 22.04 LTS

Which AutoKey GUI did you use?

None

Which AutoKey version did you use?

AutoKey 0.96.0 in development.

How did you install AutoKey?

Cloned from GitHub development branch.

Can you briefly describe the issue?

The tox -- tests/engine_helpers.py test fails with an exited with code 5 error.

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

1. Open a terminal window in a directory you'd like to put a cloned directory of AutoKey into.
2. Clone the AutoKey develop branch:

   git clone --branch develop --single-branch https://github.com/autokey/autokey.git
   

3. Change to the directory you just created:

   cd autokey
   

4. Run a tox test on the engine_helpers.py file:

   tox -- tests/engine_helpers.py
   

What should have happened?

All tests should pass.

What actually happened?

The test failed with exit code 5:

$ tox -- tests/engine_helpers.py
GLOB sdist-make: /home/elliria/Desktop/autokey/setup.py
test inst-nodeps: /home/elliria/Desktop/autokey/.tox/.tmp/package/1/autokey-0.96.0b9.zip
test installed: autokey @ file:///home/elliria/Desktop/autokey/.tox/.tmp/package/1/autokey-0.96.0b9.zip,coverage==7.2.5,dbus-python==1.3.2,exceptiongroup==1.1.1,iniconfig==2.0.0,packaging==23.1,pluggy==1.0.0,pycairo==1.23.0,PyGObject==3.44.1,PyHamcrest==2.0.4,pyinotify==0.9.6,PyQt5==5.15.9,PyQt5-Qt5==5.15.2,PyQt5-sip==12.12.1,pytest==7.3.1,pytest-cov==4.0.0,pytest-xvfb==2.0.0,python-xlib==0.33,PyVirtualDisplay==3.0,six==1.16.0,tomli==2.0.1
test run-test-pre: PYTHONHASHSEED='1382385798'
test run-test: commands[0] | pytest --no-cov tests/engine_helpers.py
=================================================================== test session starts ====================================================================
platform linux -- Python 3.10.6, pytest-7.3.1, pluggy-1.0.0
cachedir: .tox/test/.pytest_cache
rootdir: /home/elliria/Desktop/autokey
configfile: setup.cfg
plugins: cov-4.0.0, xvfb-2.0.0
collected 0 items                                                                                                                                          

================================================================== no tests ran in 0.09s ===================================================================
ERROR: InvocationError for command /home/elliria/Desktop/autokey/.tox/test/bin/pytest --no-cov tests/engine_helpers.py (exited with code 5)
_________________________________________________________________________ summary __________________________________________________________________________
ERROR:   test: commands failed

Do you have screenshots?

No response

Can you provide the output of the AutoKey command?

No response

Anything else?

The comments on this GitHub page might be useful in sorting this out.

[josephj11]

This and the otiher issue you just filed seem like they fit under installation/Configuration - for developers.

If the code in your other issue can't even find the engine module, how is code to test it going to work. Sounds like the same problem with different symptoms.

[Elliria]

I wasn't comfortable choosing installation/configuration because AutoKey works, so I don't think this is about configuring an installation. It's the test of a specific file that's failing.

Also, this is a separate issue that's unrelated to the other tox issue I posted at the same time. Each of the tox tests in these two issues are being deliberately run on specific individual files. Several others passed.