It seems that $cachedResource write actions are not properly hooking into Protractor's knowledge of when requests are complete. This means that, sometimes, for integration tests, actions that result in a $cachedResource write are resolving before the write is actually complete.
It seems that $cachedResource write actions are not properly hooking into Protractor's knowledge of when requests are complete. This means that, sometimes, for integration tests, actions that result in a $cachedResource write are resolving before the write is actually complete.