Repository navigation
Move processFunctionLogs functions into a library #1240
Description
Activity
I suggest following the existing pattern and putting this inside the CloudFunctionsDeployTrait or creating a new trait to encapsulate utilities for async testing. When the first example was merged, we discussed that being a useful follow-up as part of the 2nd or 3rd usage to make sure we understood the needed logic.
I've noticed several (and counting) of our Cloud Functions samples'
DeployTests define aprocessFunctionLogsfunction.Since these functions are largely similar (if not the same) across all these files, we should move this logic to a shared library (e.g.
php-tools) or a single location within the repo (maybe the root-leveltestingdirectory?).