I was unaware serialisers cached attribute at the model level, how interesting.
Depending on what you want to test depends on how you should deal with it, if you don’t care about receiving fresh data either of your earlier solutions are fine. But you should consider if you want your update to “bust the cache” and return fresh data. Cheers Jon Rowe --------------------------- [email protected] jonrowe.co.uk On 24 April 2019 at 06:28, Surya wrote: > Although I'm not aware of your setup nor do I know what exactly you're trying > to achieve. > > However, the failing spec does state the fact that you're not updating it > bursting your cache. What are the odds you not coming across this issue in > production? As you wouldn't have a null store in prod, and if it continues to > give you old address then I believe spec was broken for good reason. > > Sent from phone, please ignore brevity. -- You received this message because you are subscribed to the Google Groups "rspec" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rspec/dejalu-217-6799f603-4dc3-400f-baf2-ab4fac66a9f2%40jonrowe.co.uk. For more options, visit https://groups.google.com/d/optout.
