[almighty] a snapshot of data - evolving in time

[Karanbir Singh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi,

in order to execute our e2e testing ( ref:
https://github.com/almighty/almighty-ui/issues/147 ) - we need to be
able to bringup the service on demand, but the db cant be blank.

what data can we pre-load into the db for the tests to be productive ?

how can we keep this data store updated ( so we dont hit migration
issues etc when core comes up ) ?

Ideally a sql dump checked into the e2e tests code repo itself would
be used. But could we come up with a process that keeps this sql updated
 ?

the same data would / could be used for the per-PR service bringup
instances.

regards,

- -- 
Karanbir Singh, Project Lead, The CentOS Project, London, UK
Red Hat Ext. 8274455 | DID: 0044 207 009 4455
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJX/RUUAAoJEI3Oi2Mx7xbtYEMIALo0OFGlm4s5FAfdS93UH0o8
Sve365cWE3/RoAIJc7qYr42nEmpCzfWjSU6sCPMyYRJb+C+qbZvZoTuYeQ5Hdc+A
SnxiWPH9rfv6MY64aCyeoXjMhz9u76c8RXadLiJNk8gF6XglMNUIaTjM1DbuMNtn
eCMr4K/IbuT9V9hL0v7xXN6Cdz0fRpdsrmgun2c1mm6qTno5+NicEduzsnw/ezDz
GVYWbY88ji2GY29vURBlqhordasv5C4RvdTS7HKdqa3drk9NrmWFZ2KsCXmD9qm3
bIxUeh1U1jdBQcZNmnTdPM3DYVhn74eHPH0QM1royAOzCuLopMkAS+LvN/v1JW0=
=QWdT
-----END PGP SIGNATURE-----