pytest-anki is a pytest plugin that allows developers to write tests for their Anki add-ons.
At its core lies the anki_session fixture that provides add-on authors with the ability to create and control headless Anki sessions to test their add-ons in:
from pytest_anki import AnkiSession
def test_addon_registers_deck(anki_session: AnkiSession):
my_addon = anki_session.load_addon("my_addon")
with anki_session.load_profile()
with anki_session.deck_installed(deck_path) as deck_id:
assert deck_id in my_addon.deck_idsanki_session comes with a comprehensive API that allows developers to programmatically manipulate Anki, set up and reproduce specific configurations, simulate user interactions, and much more.
The goal is to provide add-on authors with a one-stop-shop for their functional testing needs, while also enabling them to QA their add-ons against a battery of different Anki versions, catching incompatibilities as they arise.
Important: The plugin is currently undergoing a major rewrite and expansion of its feature-set, so the documentation below is very sparse at the moment. I am working on bringing the docs up to speed, but until then, please feel free to check out the inline documentation and also take a look at the plug-in's tests for a number of hopefully helpful examples.
pytest-anki has only been confirmed to work on Linux so far.
pytest-anki requires Python 3.8+.
$ pip install pytest-ankior
$ poetry add --dev pytest-ankiIn your tests add:
from pytest_anki import AnkiSession # for type checking and completions
@pytest.mark.forked
def test_my_addon(anki_session: AnkiSession):
# add some tests in hereThe anki_session fixture yields an AnkiSession object that gives you access to the following attributes, among others:
app {AnkiApp} -- Anki QApplication instance
mw {AnkiQt} -- Anki QMainWindow instance
user {str} -- User profile name (e.g. "User 1")
base {str} -- Path to Anki base directory
Additionally, the fixture provides a number of helpful methods and context managers, e.g. for initializing an Anki profile:
@pytest.mark.forked
def test_my_addon(anki_session: AnkiSession):
with anki_session.profile_loaded():
assert anki_session.collectionYou can customize the Anki session context by passing arguments to the anki_session fixture using pytest's indirect parametrization, e.g.
import pytest
@pytest.mark.forked
@pytest.mark.parametrize("anki_session", [dict(load_profile=True)], indirect=True)
def test_my_addon(anki_session: AnkiSession):
# profile / collection already pre-loaded!
assert anki_session.collectionRunning your test in an Anki environment is expensive and introduces an additional layer of confounding factors. If you can mock your Anki runtime dependencies away, then that should always be your first tool of choice.
Where anki_session comes in handy is further towards the upper levels of the test pyramid, i.e. functional tests, end-to-end tests, and UI tests. Additionally the plugin can provide you with a convenient way to automate testing for incompatibilities with Anki and other add-ons.
You might have noticed that most of the examples above use a @pytest.mark.forked decorator. This is because, while the plugin does attempt to tear down Anki sessions as cleanly as possible on exit, this process is never quite perfect, especially for add-ons that monkey-patch Anki.
With unforked test runs, factors like that can lead to unexpected behavior, or worse still, your tests crashing. Forking a new subprocess for each test bypasses these limitations, and therefore my advice would be to mark any anki_session tests as forked by default.
To do this in batch for an entire test module, you can use the following pytest hook:
def pytest_collection_modifyitems(items):
for item in items:
item.add_marker("forked")Future versions of pytest-anki will possibly do this by default.
pytest-anki is designed to work well with continuous integration systems such as GitHub actions. For an example see pytest-anki's own GitHub workflows.
Especially if you run your tests headlessly with xvfb, you might run into cases where pytest will sometimes appear to hang. Oftentimes this is due to blocking non-dismissable prompts that your add-on code might invoke in some scenarios. If you suspect that might be the case, my advice would be to temporarily bypass xvfb locally via pytest --no-xvfb to show the UI and manually debug the issue.
Contributions are welcome! To set up pytest-anki for development, please first make sure you have Python 3.8+ and poetry installed, then run the following steps:
$ git clone https://github.com/glutanimate/pytest-anki.git
$ cd pytest-anki
# Either set up a new Python virtual environment at this stage
# (e.g. using pyenv), or let poetry create the venv for you
$ make install
Before submitting any changes, please make sure that pytest-anki's checks and tests pass:
make check
make lint
make testThis project uses black, isort and autoflake to enforce a consistent code style. To auto-format your code you can use:
make formatpytest-anki is
Copyright © 2019-2021 Aristotelis P. (Glutanimate) and contributors
Copyright © 2017-2019 Michal Krassowski
Copyright © 2017-2021 Ankitects Pty Ltd and contributors
All credits for the original idea for creating a context manager to test Anki add-ons with go to Michal. pytest-anki would not exist without his anki_testing project.
I would also like to extend a heartfelt thanks to AMBOSS for their major part in supporting the development of this plugin! Most of the recent feature additions leading up to v1.0.0 of the plugin were implemented as part of my work on the AMBOSS add-on.
pytest-anki is free and open-source software. Its source-code is released under the GNU AGPLv3 license, extended by a number of additional terms. For more information please see the license file that accompanies this program.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. Please see the license file for more details.
