Some of the production code was updated in the previous commit.

…vey-events

These scenarios are covered in other tests so I'm fine with not trying to make them work.

…vey-events

This commit sets up the logging infrastructure, including tests.

Since Firestore is introduced, some tests in the app module may be broken, and will be fixed in the next commit.

This commit soes not handle actual upload to firestore yet, because firebase auth is not yet properly configured.

…loguploader/LogUploadWorkerTest.kt

This new controller provides functionality to retrieve the current signed in user and also sign in user anonymously, and can be called from anywhere. This decouples authentication from a firestore-only use case.

The implementation relies on an AuthenticationListener to switch out the real and fake authentication controllers for testing purposes.

This commit has not included the Auth module in app module test files(Fragment/Acticity tests), hence these will fail to build with a dagger error. This is fixed in the subsequent commit.

…ional-response-upload

Now that we can successfully mock firebase auth, we can test for upload, cache and sync scenarios.

This is to allow the fake version of firebase

To be more descriptive of its purpose.

Lower the versions of Firestore and Auth.

The previously included versions were not compatible with older libraries currently in use within the project.

I also added a dontwarn to proguard for FirestoreChannel

Switch out logger for controller which should swap debug vs real event loggers

…ional-response-upload

I have been unable to mock firebase for this test class since it is supposed to verify the real controller is returned, and not a mock.

This test cannot pass due to the version of robolectric.

There is a conflict between Firestore's SQLite database connection and Robolectric's shadow implementation of SQLite. Firestore is trying to access an illegal connection pointer (pointer 52), which indicates a problem with the database connection.

…ional-response-upload

Allow real auth in tests for firestore

…ional-response-upload

This is to swap out the real factory in tests

Ensure the production controller is always created in prod

And remove the test file exemption to ensure the bindings stay intentional as the modules change over time.

Removed the factory pattern and converted the class to a singleton

I renamed it because the methods encapsulated here are required to be called by implementations of the interface.

We can bind the same implementation instances to both listener types in Dagger (such that the debug-only module provides an implementation for DebugFirestoreEventLogger that can be used by the debug-only view models).

…ional-response-upload

Instead of Injecting the real logger's factory, injecting the interface allows for swapping out the implementation with a fake for testing purposes.

…ional-response-upload

Updated firestore dependency

…ional-response-upload

The comment on timeout possibility and creating a sealed class for fakeauthenticationwrapperimp have not been addressed in this commit.

…ional-response-upload

This is important so that we can verify uploads and also test appcheck

- refactor FakeAuthState from sealed to enum class
- refactor auth timeout to constant
- fix remove uploaded logs logic
- fix firebase authwrapper test set up and naming
- refactor event log viewmodel list mapping