To Mock or Not to Mock
Applications depend on data to function, and in the modern world that data is usually stored somewhere up in the nebulous concept known as the "cloud" but is actually a computer processing your requests and spitting back data. During the development of an application decisions about how to supply the required data and service those requests for more must be made. Here is a non-exhaustive list of options: Real live production Actual Data. That poor lil computer in the cloud did nothing to deserve being pummeled with malformed and/or repeated requests for the same data during live testing. Let alone tortured with automated testing on every commit. Be a considerate developer. Local Representative fake Data This is a good starting point. It has the unfortunate side effect of having to be manually updated, maintained, and carefully constructed with every edge case. Local Cached data captured from live session. Few downsides, requires vigilant maintenance and api level checks and...