Divisadero no longer maintains this pre-google-emulator one 2021-11-02T09:31:27.79Z+00:00 ... Sure @dinigo, I'll try using the official emulator. Thanks ^^ 2021-11-02T10:05:19.07Z+00:00 ... Currently there are only implementations in Node.js, Go, and PHP, but see Issue #5 about the Python implementation. I suggest, whatever implementation you use, to follow the Functions Framework ... More on stackoverflow.com

One option is to use a web framework in Cloud Functions, like Express or Flask. See the official doc here . If your backend exposes many endpoints to a frontend application, you might find it easier to use Cloud Run. You'd write an application in your favorite server-side web framework (Python/Flask, Node/Express, etc). You'd run that application on your local machine for testing, without using anything specific to Google Cloud. Then you'd deploy it to the cloud with gcloud run deploy --source . I recently worked on a project where the number of Cloud Functions had grown over time. We managed for a while by adding a framework. But in the end we migrated to Cloud Run to make management of all the endpoints easier, to simplify local development, and to standardize things like authentication. Now we use Cloud Functions only to react to events like database updates. For us, that is the sweet spot for Cloud Functions. We feel that Cloud Run is great at exposing a large API surface to clients. More on reddit.com

I found this library: functions-framework on GoogleCloudPlatform/functions-framework-python github repository. More on stackoverflow.com

Hey there, As others have pointed out, the point of Function Framework is to give you a local execution environment that mimics a production environment, without having to write the boilerplate for running an HTTP server nor having to write mocks and manual unmarshalling for things like CloudEvent messages. It's especially useful when you're working within a larger code base, where you have multiple teams of engineers writing lots of different functions. Having a single abstraction for handling how functions are tested, without each team or engineer writing their own harness, allows for a consistent (and less buggy) experience across the organization. Additionally, when working across many teams with many engineers, it's often desirable to test locally without having to have each engineer need a staging environment for each and every function that is run, which in turn let's you write fully hermetic tests . Internally at Google, our testing systems are heavily restricted from reaching out to production services during tests, specifically to avoid issues like "I just ran this RPC that deleted every user in the live database." We've come to find that even if you have a staging environment, it's incredibly easy to misconfigure your tests to run against a production environment, thus local testing frameworks and hermetic testing. As you have already noted, you definitely don't need to use Function Framework for your tests as it's mostly just convenience wrappers. You can achieve all of the above your self, without the framework. If you want to manually write the boilerplate for your language, that's entirely possible as you have noted. You can also just test directly on the real system -- this is a common pattern in the world of open source :) Hope this helps! More on reddit.com