tree: 170c03aae4153028170e32f44a642f89c5b84a8a [path history] [tgz]
  1. .gitattributes
  2. .gitignore
  3. BUILD
  5. app/
  7. server.go
  8. wct.conf.js


Installing Node.js

The minimum nodejs version supported is 6.x+

# Debian experimental
sudo apt-get install nodejs-legacy

# OS X with Homebrew
brew install node

All other platforms: download from

Installing Bazel

Follow the instructions here to get and install Bazel.

Local UI, Production Data

This is a quick and easy way to test your local changes against real data. Unfortunately, you can't sign in, so testing certain features will require you to use the “test data” technique described below.

Installing go

This is required for running the script below.

# Debian/Ubuntu
sudo apt-get install golang

# OS X with Homebrew
brew install go

All other platforms: download from

Then add go to your path:


Running the server

To test the local UI against


Then visit http://localhost:8081

Local UI, Test Data

One-time setup:

  1. Build Gerrit
  2. Set up a local test site. Docs here and here.

When your project is set up and works using the classic UI, run a test server that serves PolyGerrit:

bazel build polygerrit && \
java -jar bazel-bin/polygerrit.war daemon --polygerrit-dev \
-d ../gerrit_testsite --console-log --show-stack-trace

Running Tests

One-time setup:

# Debian/Ubuntu
sudo apt-get install npm

# OS X with Homebrew
brew install npm

# All platforms (including those above)
sudo npm install -g web-component-tester

Note: it may be necessary to add the options --unsafe-perm=true --allow-root to the npm install command to avoid file permission errors.

Run all web tests:


If you need to pass additional arguments to wct:

WCT_ARGS='-p --some-flag="foo bar"' ./polygerrit-ui/app/

For interactively working on a single test file, do the following:


Then visit http://localhost:8081/elements/foo/bar_test.html

To run Chrome tests in headless mode:

WCT_HEADLESS_MODE=1 ./polygerrit-ui/app/

Toolchain requirements for headless mode:

  • Chrome: 59+
  • web-component-tester: v6.5.0+

Style guide

We follow the Google JavaScript Style Guide with a few exceptions. When in doubt, remain consistent with the code around you.