Keeping in sync with schema changes is indeed a concern.  the _out 
dictionary that is produced by the format_app function is limited to the 
properties needed for EDW interoperation.   I'd like
to test that it can interpret what it GET's from encoded and can strip 
it to EDW essentials.

Originally this test was app-independent, and tested just the expanded 
file json.   When I
realized I'd also need to handle emedded (in Elasticsearch-free test 
environment) it
grew.   Since it is now app-dependent, perhaps there's a better way than 
static json file to
test this function.

I had thought to have script test schema version, but decided to defer 
that when I
encountered a schema version=2...

   Kate


On 10/10/13 2:14 PM, Laurence Rowe wrote:
>
> In src/encoded/tests/data/edw_file/format_app_file_in.1.json:
>
> > @@ -0,0 +1,562 @@
> > +{
>
> Could this test dataset perhaps be cut down to only the properties 
> your script requires? I'm a little concerned about keeping it in sync 
> going forwards.
>
> —
> Reply to this email directly or view it on GitHub 
> <https://github.com/ENCODE-DCC/encoded/pull/19/files#r6901067>.
>