prescottprue/test-generator-react-firebase

Test project for generator-react-firebase

test-generator-react-firebase

Table of Contents

1. Before Starting
2. Getting Started
3. Gotchas
4. Config Files
5. Application Structure
6. Development
   1. Routing
7. Testing
8. Configuration
9. Production
10. Deployment

Requirements

• node ^14.15.0
• npm ^6.0.0

Before Starting

1. Make sure you have firebase-tools installed an you are logged in (firebase login)
2. Create a project within the Firebase Console (or have one prepared to use)
3. Confirm billing is enabled for your project
4. Confirm Firebase Hosting API is enabled for your project

Getting Started

1. Install app and functions dependencies: npm i && npm i --prefix functions

2. Create a .env file which has GCLOUD_PROJECT set within it, for example:

   GCLOUD_PROJECT="some-project"
   
   

3. Start Development server: yarn start

While developing, you will probably rely mostly on yarn start; however, there are additional scripts at your disposal:

yarn <script>	Description
start	Serves your app at localhost:3000 with automatic refreshing and hot module replacement
start:dist	Builds the application to ./build then serves at localhost:3000 using firebase hosting emulator
start:emulate	Same as start, but pointed to database emulators (make sure to call emulators first to boot up emulators)
build	Builds the application to ./build
emulators	Starts database and pubsub emulators for use with start:emulate
emulators:hosting	Starts database and hosting emulators (used in verify workflow by Cypress)
test	Runs unit tests with Jest. See testing
test:watch	Runs test in watch mode to re-run tests when changed
test:ui:run	Runs UI tests with Cypress. See testing
test:ui	Opens UI tests runner (Cypress Dashboard). See testing
test:ui:emulate	Same as test:ui but with tests pointed at emulators
lint	Lints the project for potential errors
lint:fix	Lints the project and fixes all correctable errors

Husky is used to enable prepush hook capability. The prepush script currently runs eslint, which will keep you from pushing if there is any lint within your code. If you would like to disable this, remove the prepush script from the package.json.

Gotchas

• Preview Channels are only for hosting - functions changes will not be included (functions will point to your default project)
• UI Tests run in verify workflow use emulators (including functions)

Config Files

There are multiple configuration files:

• Firebase Project Configuration - .firebaserc
• Project Configuration - config (file names match branch and environment names)
• Local Project Configuration Override - .env
• Local Cloud Functions Configuration - functions/.runtimeconfig.json

More details in the Application Structure Section

Application Structure

The application structure presented in this boilerplate is fractal, where functionality is grouped primarily by feature rather than file type. Please note, however, that this structure is only meant to serve as a guide, it is by no means prescriptive. That said, it aims to represent generally accepted guidelines and patterns for building scalable applications.

├── .github                      # All Github configuration
│   ├── workflows                # Github Actions CI Workflows
│   │  ├── deploy.yml            # Deploy workflow (deploys when pushing to specific branches)
│   │  └── verify.yml            # Paths for application routes
│   └── PULL_REQUEST_TEMPLATE.md # Main HTML page container for app
├── bin                          # Scripts used by npm scripts and CI config
├── config                       # Configuration files (loaded by node-config)
├── cypress                      # UI Integration Tests
├── functions                    # Cloud Functions
│   ├── src                      # Cloud Functions Source code (each folder represents a function)
│   ├── .runtimeconfig.json      # Cloud Functions local configuration
│   └── index.js                 # Mount point of Cloud Functions (loads functions by name)
├── public                       # All build-related configuration
│   ├── firebase-messaging-sw.js # Service worker for Firebase Cloud Messaging
│   └── index.html               # Main HTML page container for app
├── src                          # Application source code
│   ├── components               # Global Reusable Presentational Components
│   ├── constants                # Project constants such as firebase paths and form names
│   │  ├── firebasePaths.js      # Paths within Firebase (i.e. Collections + Sub-Collections)
│   │  └── paths.js              # Paths for application routes
│   ├── containers               # Global Reusable Container Components
│   ├── layouts                  # Components that dictate major page structure
│   │   └── CoreLayout           # Global application layout in which routes are rendered
│   ├── routes                   # Main route definitions and async split points
│   │   ├── index.js             # Bootstrap main application routes
│   │   └── Home                 # Fractal route
│   │       ├── index.js         # Route definitions and async split points
│   │       ├── components       # Presentational React Components
│   │       └── routes/**        # Fractal sub-routes (** optional)
│   └── utils                    # General Utilities (used throughout application)
│       ├── form.js              # Utilities for forms (validation)
│       └── router.js            # Utilities for routing such as those that redirect back to home if not logged in
├── .env                         # Local Environment settings (automatically loaded up by npm scripts)
├── .eslintignore                # ESLint ignore file
├── .eslintrc.js                 # ESLint configuration
├── .firebaserc                  # Firebase Project configuration settings (including ci settings)
├── database.rules.json          # Rules for Firebase Real Time Database
├── firebase.json                # Firebase Service settings (Hosting, Functions, etc)
├── firestore.indexes.json       # Indexes for Cloud Firestore
├── firestore.rules              # Rules for Cloud Firestore
└── storage.rules                # Rules for Cloud Storage For Firebase

Routing

We use react-router-dom route matching (<route>/index.js) to define units of logic within our application. The application routes are defined within src/routes/index.js, which loads route settings which live in each route's index.js. The component with the suffix Page is the top level component of each route (i.e. HomePage is the top level component for Home route).

There are two types of routes definitions:

Sync Routes

The most simple way to define a route is a simple object with path and component:

src/routes/Home/index.js

import HomePage from "./components/HomePage";

// Sync route definition
export default {
  path: "/",
  component: HomePage,
};

Async Routes

Routes can also be seperated into their own bundles which are only loaded when visiting that route, which helps decrease the size of your main application bundle. Routes that are loaded asynchronously are defined using loadable function which uses React.lazy and React.Suspense:

src/routes/NotFound/index.js

import loadable from "utils/components";

// Async route definition
export default {
  path: "*",
  component: loadable(() =>
    import(/* webpackChunkName: 'NotFound' */ "./components/NotFoundPage")
  ),
};

With this setting, the name of the file (called a "chunk") is defined as part of the code as well as a loading spinner showing while the bundle file is loading.

More about how routing works is available in the react-router-dom docs.

Testing

Component Tests

To add a unit test, create a .spec.js or .test.js file anywhere inside of src. Jest will automatically find these files and generate snapshots to the __snapshots folder.

UI Tests

Cypress is used to write and run UI tests which live in the cypress folder. cypress-firebase is used to generate a custom auth token for the test user and to communicate with Firebase databases with admin privileges.

Tests Setup

1. Run yarn test:ui:emulate
2. Visit "Runs" tab of Cypress Test Runner
3. Setup a Project for recording (will save setting to cypress.json)
4. Save Record key as CYPRESS_KEY secret within CI settings

Running Hosted Tests

1. Visit the Firebase Console
2. Select your project
3. Navigate to Project Settings (gear icon button at the top left of the page).
4. Navigate to "Service Accounts" tab
5. Click "Generate New Private Key"
6. Save the service account file to the root of the repo under serviceAccount.json

Running Tests

The following npm scripts can be used to run tests:

• Run using Cypress run: yarn test:ui:run
• Open Test Runner UI (cypress open): yarn test:ui

To run tests against emulators:

1. Start database emulators: yarn emulators
2. Start React app pointed at emulators: yarn start:emulate
3. Open Cypress test runner with test utils pointed at emulators: yarn test:ui:emulate

To Run tests in CI add the following environment variables within your CI provider:

• SERVICE_ACCOUNT - Used to create custom auth tokens for test user login
• TEST_UID - UID of the user used for testing

Deployment

Build code before deployment by running yarn build. There are multiple options below for types of deployment, if you are unsure, checkout the Firebase section.

Before starting make sure to install Firebase Command Line Tool: npm i -g firebase-tools

CI Deploy (recommended)

Note: Config for this is located within .github/workflows

firebase-ci has been added to simplify the CI deployment process. All that is required is providing authentication with Firebase:

1. Login: firebase login:ci to generate an authentication token (will be used to give CI rights to deploy on your behalf)
2. Set FIREBASE_TOKEN environment variable within CI environment
3. Run a build on CI

If you would like to deploy to different Firebase instances for different branches (i.e. prod), change ci settings within .firebaserc.

For more options on CI settings checkout the firebase-ci docs

Manual deploy

1. Run firebase:login
2. Initialize project with firebase init then answer:
   • What file should be used for Database Rules? -> database.rules.json
   • What do you want to use as your public directory? -> build
   • Configure as a single-page app (rewrite all urls to /index.html)? -> Yes
   • What Firebase project do you want to associate as default? -> your Firebase project name
3. Build Project: yarn build
4. Confirm Firebase config by running locally: yarn emulators:hosting
5. Deploy to Firebase (everything including Hosting and Functions): firebase deploy

NOTE: You can use yarn emulators:hosting to test how your application will work when deployed to Firebase, but make sure you run yarn build first.

FAQ

1. Why node 14 instead of a newer version?

Cloud Functions runtime runs on 14, which is why that is what is used for the CI build version.