{"push_id":789622886,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"93009c2d6bbae721daa566bb3d6b87c5a9da4981","before":"f3c5411d2dfa680d6ea2d0227feb89b98ca680a5","commits":[{"sha":"93009c2d6bbae721daa566bb3d6b87c5a9da4981","author":{"email":"a949d6a97b3d779ed8f5913240b7ad1401001d41@physics.ox.ac.uk","name":"Tim Staley"},"message":"Basic tests for rest API, some restructuring.\n\nUse of blueprint makes for cleaner definition of API vs 'rest of app config',\nplus should allow for side-by-side use of multi-version APIs.\n\nFigured out how to use the same session initialization for both basic\ndatabase tests and Flask API tests, just needs careful reconfiguration\nof the scoped_session-bound sessionmaker.\n\nAll good. However this is a good example of where the UnitTest API has\nreally reached its limit. We want module-level and maybe even\nonce-per-test-run level fixtures\n(i.e. a transaction enclosed database connection with fresh tables -\nexpensive to create for every test-case). These require globals,\nand thus are approximately impossible to share between test-modules.\nTime for something new - drumroll for pytest!","distinct":true,"url":"https://api.github.com/repos/timstaley/voeventcache/commits/93009c2d6bbae721daa566bb3d6b87c5a9da4981"}]}