Tag Archives: #mariadb
TAF’s reproducibility story just gained its most important upgrade: every test case now produces a fully resolved, auto‑generated user properties file.
This file captures exactly what the run used — not what the user intended, not what was passed in, but the final, authoritative configuration TAF executed. It removes ambiguity, eliminates hidden dependencies, and makes every test case a fully self‑describing artifact.
This feature builds directly on the work introduced in the previous blog, where TAF gained support for embedding database configuration inside user properties.
If you missed that post, you can read it here:
TAF 4.0 Database Configuration Handling
With embedded configuration in place, TAF can now take the next step:
auto‑generating a complete user properties file for every run.
…