The scenario
Model the data behind e-commerce checkout requirements and their automated Selenium regression tests, from requirement through page objects to test results.
What is in this drawing
Read the decisions behind it.
01
Native erd tables with FK references mirror the automation pyramid and page object model.
02
All relationships modeled as many-mandatory to one-mandatory for clean referential integrity.
03
Separate TestRun and TestResult allow historical execution tracking without mutating test definitions.
Use when building a repository for requirements traceability and automated regression test reporting.
More like this