Marketplace/Fake Data: Difference between revisions

Marketplace/Fake Data (view source)

Revision as of 20:35, 15 April 2015

195 bytes removed , 15 April 2015

rewrite to catch up with apps being deployed on -dev

Ashort

44

edits

@@ Line 1: / Line 1: @@
+== Overview ==
 Tools and libraries for generating data are needed to exercise every part of our code without unnecessary storing/sharing of data from production.
-== User stories ==
+[[Marketplace/Fake_Data/App_Types|App Types]] lists the kinds of apps being generated.
-=== New developers ===
+=== Docs ===
-A new developer follows the instructions on https://zamboni.readthedocs.org/ to create a new development configuration. He creates an admin user account and runs a command that creates a variety of apps, some of them owned by his new account, some not.
+For generating apps from a spec file see docs for [http://zamboni.readthedocs.org/en/latest/topics/install-zamboni/installation.html#loading-test-apps Loading Test Apps].
+For editing fake app descriptions, see [http://zamboni.readthedocs.org/en/latest/topics/fake-app-spec.html Fake App Spec].
-=== Existing developers ===
+== Engineering Considerations ==
-A Zamboni developer needs to create apps in a specific state with specific properties, and so runs a command with flags/options specifying what's needed.
+* app generation code currently doesn't generate video.
+* generation of apps for feed is done separately from rest of app specification.
-=== marketplace-dev deployment ===
+* no current way to specify particular locales/regions.
-When Zamboni is deployed in a non-production role, a variety of different apps are created with status and data appropriate for every use case that QA needs to test.
+* no current way to specify content ratings.
+* we might want to add an admin page for uploading a spec file so QA can generate specific apps they need easily.
-== Next Steps ==
-. save altdev data set because we know it exhibits {{Bugzilla|1101581}} that has been elusive on -dev.
-# ashort starts writing the Complete Dev JSON file, but don't finish it. Then kraj can keep going with it.
-# Once we have this Complete Dev JSON file, we can put it on altdev for full QA.
 == Bugs ==