Create scaffolding for testdata
Background
We need scaffolding for new testdata.
Implementation
Suggestions
-
Create new ella-testdata repo -
Move testdata from current repo to new repo -
Add scripts (in testdata repo) for uploading pgdumps -
Add utility scripts to fetch data from new repo -
ops/testdata/fetch-testdata.py
-
clones new repo -
can update existing repo -
can fetch based on SHA, tag, branch -
shallow clone by default, but can do full clone
-
-
ops/testdata/reset-testdata.py
-
loads via local files -
loads via pgdump pulled from digitalocean by commit hash and dataset name -
load local pg dump -
save local copies of pg dumps -
upload pgdumps to digitalocean
-
-
make fetch-testdata
- wrapper for script
-
-
Redirect all references to old testdata
Some script to download and populate test database, and to upload a new version of the test data. The test data should consist of: We should not overwrite the existing test data, as this is used in both old e2e tests and integration tests. We might however think that we wish to get rid of the existing testdata in the long run, so this should be probably be kept completely separate. (END OF SCOPE) When that is done we are ready to populate the database in the following order: Then we start preparing analyses. I have everything more or less ready to run samples through anno (+anno-targets where required).Old summary
$ATTACHMENT_STORAGE
, /ella/src/vardb/testdata/attachments/)$ANALYSES_PATH
)
PASTE LOGS HERE