WhoDB for QA testers

WhoDB helps you prepare a known database state and inspect the records behind a test result. Use it to answer a specific question: did this application action create or change the records the test expects?

Start with a reproducible fixture#

Use a disposable database with the same schema as the application under test. Load a known CSV or Excel fixture through Import, or run the application's normal seed process. Preview field mapping and sample values before committing an import.

Choose the import mode deliberately. Append can skip existing primary keys, while upsert updates matching keys where supported. Relational overwrite can clear referencing tables as well as the selected table. For a repeatable test setup, keep a way to recreate the whole fixture. See Importing data.

Mock data is useful for testing pagination, missing values, and general layouts. Use explicit fixtures when the test depends on a particular relationship or business state.

Check the scenario's records#

Run the application action, then use Filter to look up its identifier in Data. Inspect the fields that should have changed and any related rows. For example, an order submission might need both an order record and the expected item records.

Keep a verification query in Scratchpad. Check positive and negative cases: the expected record exists, an unrelated record remains unchanged, and a rejected request created no unintended record.

Turn the finding into a repeatable test#

Keep setup files and assertions in the test repository. Record the fixture version and the action that produced the result. A screenshot can make a defect easier to understand, but the setup and query let another person reproduce it.

Use CLI & MCP for terminal checks and Prepare and inspect test data for the full development workflow.