What exactly gets written to Google Cloud Storage during PHP Unit Tests?

[cloudscape-germany]

Describe the problem/question

What gets written there? We are very sensitive when it comes to write data to non-EU cloud providers. Is there an alternative to not use public cloud for running unit tests?

Did you use the FAQ section?

• Yes, I have read the FAQ and I found no solution/answer there.

What you did?

1. running php unit tests
2. system complains about not having Public Cloud at Google Cloud Storage

What happens

No response

What should happen

No use of Public Cloud at all, at any stages of development, test and production.

Additional information

No response

Server address

No response

Server OS

No response

Webserver

No response

PrivateBin version

No response

Browser and version

No response

Local operating system and version

No response

Issue reproducibility

No, I cannot reproduce it on https://privatebin.net.

[Ribas160]

PrivateBin doesn't write data to Google Cloud Storage while running PHP unit tests. However, running tests related to Google Cloud Storage requires the google/cloud-storage package to be installed.
You can install it by running composer require google/cloud-storage or use the privatebin/unit-testing Docker image, which contains everything needed to run PHP or JavaScript unit tests.

P.S. The issue of excluding google/cloud-storage from the list of required packages for running unit tests was discussed in #1641

[rugk]

To clarify: I guess you can also run the unit tests in an air gapped environmental, the package being installed is just required, so the test gets correctly interpreted. The calls itself should all be mocked. It's just a unit test nothing further like an integration test, after all.