Kenneth W. Bingham

case study · Java 21 · Spring Boot · PostgreSQL · Selenium · open source

QA in a box: test the real system, then leave no trace.

TestThisPuppy tests a running web application and its real database in one command: the network path, the API, every form, wrong input, SQL injection, race conditions and whole user workflows. Then it puts the database back exactly as it found it. It rebuilds a test harness I first wrote and used at Axis41, Finicity and InComm.

The problem

Most automated tests either mock the database, which tests the mock and not the system, or run against a shared database and leave test rows behind for the next person to trip over. Neither tells you whether the real application, on a real database, behaves when someone types something wrong or something hostile.

Why it is hard

What it does

The proof

Technologies and skills

How it was built: about two hours, from my prompts

This is a featured AI-assisted build. I directed it; Claude wrote and ran the code. The times come from the file system and the git history, measured, not estimated. They are wall-clock time with me directing, including every round of changes.

The AI and tools

The prompts I gave, in order

Exactly as I typed them, with spelling tidied. Most came in while the AI was already working; it finished the step in hand, then took up the next.

  1. "I want to rebuild TestThisPuppy with a tester that sends HTTP requests, opens the database, fills it with dummy data, runs the tests and sends the results, and have it integrated with Selenium and WebDriver, where it scans the page, finds all the elements and populates them. Then when it's complete it cleans up the database as if it was never there. This way, real database testing on the code base."
  2. Asked three questions, I chose: write it as a mix (the AI builds the plumbing, I write three core parts as practice drills), Java 21 with Maven, and PostgreSQL.
  3. "https://github.com/kenbin64/testthispuppy.git"
  4. "Just use Latin words to fill the forms and data. Create a filler word CSV file."
  5. "It can connect to the actual database with credentials, or create an internal DB just for testing."
  6. "Have a happy path option, a wrong input type test, and test your try-catches to throw errors."
  7. "Also test for SQL injection, using the internal database only, for safety."
  8. "Test ping and source route to check the database connection, test forms in the UI, test backend controllers and objects, test race conditions, regression tests and unit tests."
  9. "Do we have Tomcat?" Then: "That's right, Spring Boot has it."
  10. "I also AI-assisted to analyze logs and stack traces."
  11. "Also include complete documentation."
  12. "Workflows."
  13. "Ways to create macros and automated tests using WebDriver."
  14. "Able to do hundreds of tests, all automated."
  15. "Your QA in a box."
  16. "Yes, let's put it in GitHub and on butterflyfx.us, my portfolio page."
  17. "I am going to do a featured AI-assisted program. Say how long it took to build and add the prompts I used to create it."
  18. "And the AI and tools used, VS Code, etc."

What the prompts do not show is the checking. Every claim on this page was run before it was written down, and when a check found a problem (a test that passed for the wrong reason, a safety notice that could be skipped, a regression test that needed proof it could fail), it was fixed before moving on.

What it does not claim

4real bugs found, first run
143/143checks in one run
54unit and error-path tests
0rows left behind