refactor(int): integration tests rewrite - wip

Author: kirstywilliams

integration_test/.env.example

@@ -0,0 +1,7 @@
+REGION=us-central1
+PROJECT_ID=
+DATABASE_URL=
+STORAGE_BUCKET=
+NODE_VERSION=18
+FIREBASE_ADMIN=^10.0.0
+GOOGLE_APPLICATION_CREDENTIALS=

integration_test/.gitignore

@@ -0,0 +1,70 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+firebase-debug.log*
+firebase-debug.*.log*
+
+# Firebase cache
+.firebase/
+
+# Firebase config
+
+# Uncomment this if you'd like others to create their own Firebase project.
+# For a team working on the same Firebase project(s), it is recommended to leave
+# it commented so all members can deploy to the same project(s) in .firebaserc.
+# .firebaserc
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (http://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# Firebase/GCP config
+.firebaserc
+serviceAccount.json

integration_test/README.md

@@ -1,22 +1,32 @@
-## How to Use
+# Integration Test Suite
 
-**_ATTENTION_**: Running this test will wipe the contents of the Firebase project(s) you run it against. Make sure you use disposable Firebase project(s)!
+## How to use
 
-Run the integration test as follows:
+### Prerequisites
 
-```bash
-./run_tests.sh <project_id> [<project_id2>]
-```
+Tests use locally installed firebase to invoke commands for deploying function.
+The test also requires that you have gcloud CLI installed and authenticated
+(`gcloud auth login`).
+
+Tests are deployed with a unique identifier, which enables the teardown of its own resources, without affecting other test runs.
 
-Test runs cycles of testing, once for Node.js 14 and another for Node.js 16.
+1. Add a service account at root serviceAccount.json
+2. Add a .env `cp .env.example .env`
 
-Test uses locally installed firebase to invoke commands for deploying function. The test also requires that you have
-gcloud CLI installed and authenticated (`gcloud auth login`).
+### Running setup and tests
 
-Integration test is triggered by invoking HTTP function integrationTest which in turns invokes each function trigger
-by issuing actions necessary to trigger it (e.g. write to storage bucket).
+This will deploy functions with unique names, set up environment for running the
+jest files, and run the jest test suite.
+
+```bash
+yarn start
+```
 
-### Debugging
+## TODO
 
-The status and result of each test is stored in RTDB of the project used for testing. You can also inspect Cloud Logging
-for more clues.
+[x] Deploy functions with unique name
+[x] Update existing tests to use jest (v1 and v2)
+[] Add missing coverage for v1 and v2 (WIP)
+[] Ensure proper teardown of resources (only those for current test run)
+[] Python runtime support
+[] Capture test outcome for use by CI