Do I need to hardcode my own GPG keys for new UserGPGKey class?

Background

I'm developing a UserGPGKey class to expose this library to GitHub's REST API endpoints for GPG keys. The UserGPG class is moduled similar to the already-existing UserKey class. The necessiary modifcations have been made to NamedUser and AuthenticatedUser in order to access GPG keys after authentication.

Problem

In the tests of UserKey, AuthenticatedUser, and NamedUser tests, there is information provived on some SSH keys which from my understanding comes from @jacquev6. Here are screenshots from the codebase showcasing what I am refering to:

tests/UserKey.py

tests/AuthenticatedUser.py

tests/NamedUser.py

What I'd like to know is if I'd need something similar and hardcode information from my own GPG key(s) into the testing code for UserGPGKey?

If possible, I'd like to avoid doing this for privacy reasons.
Thanks in advance for reading this rather lengthy issue! 😅

Start by reviewing tests/UserKey.py, tests/AuthenticatedUser.py, and tests/NamedUser.py to understand the existing key fixtures and access patterns. Then compare those patterns with the proposed UserGPGKey class and its NamedUser and AuthenticatedUser changes; done should include appropriate tests without requiring the contributor's private GPG key data.