Forums

caching the session as weve been having some crashing issues that seem to be keeping the session open, so current thought process was to cache the session which will allow me to exit it later if need be. Unless theres a kill all session kinda command i dont know of 

@Jason Porath  I found quite fine running running unit and functional tests on test projects right on production server. It is quite easy to construct any context with ftrack_api and release it after tests finished. In worst case you will got a bunch of test entities on test project that no one cares. so feel free to: @pytest.fixture def session():     return ftrack_api.Session()   @pytest.fixture def context(request, session😞     context = session.create('Folder', {'parent_id': ..., 'project_id': ..., 'name': ...})     def finalizer():         session.rollback()         session.delete(context)         session.commit()     request.addfinalizer(finalizer)     return context The better approach is to running tests on staging ftrack server that should have relative fresh database snapshot from production, that is much more complex. 

Hi Peter, what's your use case? Just caching objects (or some other server state) locally or something else?

@Toby Angwin @kristin you should be in now. Sorry for the delay !