Create a prototype test plan

[dbutenhof]

Summary

0.7.0 broke several things, and we were sloppy about testing. 0.7.1 fixed JSON output with an api_key, but not CSV output. We need to be more disciplined about pre-release testing.

Details

I've considered trying to build a formal manual test plan for some time; a few recent issues brought that back to mind, and I thought I'd make a try to start something.

I began with a few bullet items and thought I'd send that out for review, when the idea struck me to feed my bullet list and some general instructions into Cursor and see what it came up with.

This is the result. I haven't even reviewed it in great detail, but at a glance most of this seems plausible, if not complete. At least, it seems like a place to start; and I like the idea of "enshrining" this in our documentation. Although, ideally, we'll migrate this into our CI, extending or replacing our e2e tests.

Test Plan

• yes, we should test the test plan!

Related Issues

Related to all issues, closes none!

---

• "I certify that all code in this PR is my own, except as noted below."

Use of AI

• Includes code generated or substantially modified by an AI agent
• Includes tests generated or substantially modified by an AI agent

NOTE: the Generated-by or Assisted-by trailers should be used in git commit messages when code or tests were generated or substantially modified by an AI agent, as described in the project's DEVELOPING.md file.

---

git log

commit 9ff2878
Author: David Butenhof dbutenho@redhat.com
Date: Wed Jul 22 16:37:02 2026 -0400

Create a prototype test plan

Signed-off-by: David Butenhof <dbutenho@redhat.com>

---

Signed-off-by: David Butenhof dbutenho@redhat.com