... | ... | @@ -7,7 +7,7 @@ |
|
|
* **<span dir="">D8/D9</span>**<span dir="">: If you use D8/D9, the default installation flow bypasses the install screen - it is highly unlikely that an evaluator/tester will discover that sample data is available.</span>
|
|
|
* **<span dir="">Extension Entities</span>**<span dir="">: There is no consistent approach to sample data for extensions (say, CiviVolunteer or Mosaico).</span>
|
|
|
* **<span dir="">Reproducibility/E2E</span>**<span dir="">: With RNG, a small change can bubble out to make a larger change in the overall sample data-set. It is therefore unreliable to use sample-data for E2E testing.</span>
|
|
|
* **<span dir="">POV/Tuning</span>**<span dir="">: Different evaluators/testers may have different interests (wrt #records, choice of subsystems, complexity of configurations). The use of a singular sample data-set makes it difficult to attune to all those interests.</span>
|
|
|
* **<span dir="">POV/Tuning</span>**<span dir="">: Different evaluators/testers may have different interests (wrt #records, choice of locales+subsystems, minimal-vs-maximal use of config options). The use of a singular sample data-set makes it difficult to attune to all those interests.</span>
|
|
|
* **<span dir="">Naive Adopter Cleanup</span>**<span dir="">: A naive adopter may load samples as a way to learn/explore. While learning, they start to add their own data on top. Later, they realize that they have created a confusing mix of data - which must be cleaned or migrated. There is no clear on/off (hide/show; import/delete).</span>
|
|
|
|
|
|
## Goals
|
... | ... | |