Feature request: a backend for third-parties to test their keyring usage.

As far as I can see, there's no backend (either in keyring, keyring.alt or PyPI) which is designed for running as a test backend to check that calls to keyring are correct. Mocks could be used, but given backends are somewhat deployment specific anyway, having a test backend would avoid every project having their own mocks.

Would such a test backend be acceptable to the main keyring codebase? Naturally it would never be used unless requested, and would be documented as not to be used for anything else than testing (e.g. would be in memory only, so would not work as a keychain), or is keychain sufficiently frozen as to require this to be a third party backend?

Review the existing keyring backends and the related keyring.alt and PyPI options before deciding whether this belongs in the main codebase. The proposed outcome is an explicitly opt-in, in-memory backend for third-party tests, documented as testing-only, or a clear decision to keep it external.

Written by the indexing model from the issue text.