... | ... | @@ -14,8 +14,8 @@ |
|
|
|
|
|
Combining that list of issues with some of the existing/desirable characteristics, we might give a list of positive goals/features:
|
|
|
|
|
|
* <span dir="">Sample data-set(s) should provide broad coverage for different subsystems, locales, and scales (sizes).</span>
|
|
|
* <span dir="">Sample data-set(s) should be readily/easily available for use by evaluators/demo’ers, trainers/learners, developers/testers, and (E2E) automated-test-systems.</span>
|
|
|
* Sample data-set(s) should be maintainable. <span dir="">The workflow for patching sample-data and seeing it in a working site should be simple/short.</span> When a change is required in the data-model, it should be straight-forward to discover+revise corresponding sample data-set(s).
|
|
|
* <span dir="">Sample data-set(s) should be reproducible (for consistency in tutorials, E2E, etc) - but they should be allowed to use controlled-randomization</span> (to generate large sets; and to allow primitive fuzz-testing).
|
|
|
* <span dir="">Sample data-set(s) should be available for different deployments/environments (Drupal/WordPress/Backdrop/Standalone; </span>[<span dir="">localhost/VM/VPS/Aegir</span>](http://localhost/VM/VPS/Aegir)<span dir="">; etc).</span> |
|
|
\ No newline at end of file |
|
|
* **Coverage**: <span dir="">Sample data-set(s) should provide broad coverage for different subsystems (CiviContribute/CiviEvent/etc), locales (language/region/currency/etc), and scales (sizes).</span>
|
|
|
* **Accessibility (By Audience/Role)**: <span dir="">Sample data-set(s) should be readily/easily available for use by evaluators/demo’ers, trainers/learners, developers/testers, and (E2E) automated-test-systems.</span>
|
|
|
* **Reproducibility**: <span dir="">Sample data-set(s) should be reproducible (for consistency in tutorials, E2E, etc) - but they should be allowed to use controlled-randomization</span> (to generate large sets; and to allow primitive fuzz-testing).
|
|
|
* **Maintainability**: Sample data-set(s) should be maintainable. <span dir="">The workflow for patching sample-data and seeing it in a working site should be simple/short.</span> When a change is required in the data-model, it should be straight-forward to discover+revise corresponding sample data-set(s).
|
|
|
* **Accessibility (By Technology)**: <span dir="">Sample data-set(s) should be available for different deployments/environments/technologies (Drupal/WordPress/Backdrop/Standalone; </span>[<span dir="">localhost/VM/VPS/Aegir</span>](http://localhost/VM/VPS/Aegir)<span dir="">; etc).</span> |
|
|
\ No newline at end of file |