| commit | 8274e392beb25add2f0e8c5a7e9930d17b0c6fff | [log] [tgz] |
|---|---|---|
| author | Eduardo Yap <eduardoyap@google.com> | Fri Jan 16 22:33:16 2026 +0000 |
| committer | SkCQ <skcq-be@skia-corp.google.com.iam.gserviceaccount.com> | Mon Jan 19 13:48:20 2026 -0800 |
| tree | 5dd4a0d10f3aaf15fc1095f1bb1b6cce859c15ea | |
| parent | a57c339a798c97f86cdb9fa0abb52dc5c4ff16eb [diff] |
feat: Puppeteer test integration for plot-summary-sk selection This commit enhances the puppeteer tests for and to utilize the range selection feature of the component. - Updates explore-multi-sk_po and explore-simple-sk_po to include plot-summary-sk_po. - Adds a new puppeteer test suite for explore-multi-sk to verify the integration with plot-summary-sk. - The new test ensures that selecting a range in plot-summary-sk updates the main graph's begin and end times in the URL. - Refactors plot-summary-sk_po to include a method that uses ratios for selection, making tests more robust against different screen sizes. - Adds a function to ensure the chart is fully rendered and the API is ready before interactions. - Updates existing tests to use the new method. This integration allows users to intuitively zoom into specific time ranges on the main graphs by selecting a range on the plot summary. Screencast: https://screencast.googleplex.com/cast/NTI5MDI4NjU5ODA2MjA4MHw0YjQwZWYyNi0yMA Bug: 457464705 Change-Id: I5b0434564fb9f1a39700f4a2babdfb102b20d3a6 Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/1143099 Reviewed-by: Sergei Rudenkov <sergeirudenkov@google.com> Commit-Queue: Eduardo Yap <eduardoyap@google.com>
This repo contains infrastructure code for Skia.
The infrastructure code is generally built to run on x86 linux. Running on other platforms may be possible but is not officially supported and success will vary depending on the command.
The main source code repository is a Git repository hosted at https://skia.googlesource.com/buildbot.git. It is possible to check out this repository directly with git clone or via go get.
Using git clone allows you to work in whatever directory you want. You will still need to set GOPATH in order to build some apps (recommended to put this in a cache dir). E.g.:
$ cd ${WORKDIR}
$ git clone https://skia.googlesource.com/buildbot.git
$ export GOPATH=${HOME}/.cache/gopath/$(basename ${WORKDIR})
$ mkdir $GOPATH
$ cd buildbot
Almost all applications are built with Bazel, and bazelisk is the recommended tool to ensure you have the right version of bazel installed:
go install github.com/bazelbuild/bazelisk@latest go install github.com/bazelbuild/buildtools/buildifier@latest go install github.com/kisielk/errcheck@latest go install golang.org/x/tools/cmd/goimports@latest go install github.com/mikefarah/yq/v4@latest go install go.chromium.org/luci/client/cmd/...@latest
export PATH=$PATH:$(go env GOPATH)/bin
You will need Node.js and npm installed to run web infrastructure tests and linters. We recommend using nvm to manage Node versions.
After installing Node.js, run the following command to install repository dependencies (including linter tools):
npm install
sudo apt-get install jq
bazelisk build --config=mayberemote //...
This step might be an optional step, but some test requires these enviornment variables.
Runs
./scripts/run_emulators/run_emulators start
The following are example of environment variables.
Emulators started. Set environment variables as follows: export DATASTORE_EMULATOR_HOST=localhost:8891 export BIGTABLE_EMULATOR_HOST=localhost:8892 export PUBSUB_EMULATOR_HOST=localhost:8893 export FIRESTORE_EMULATOR_HOST=localhost:8894 export COCKROACHDB_EMULATOR_HOST=localhost:8895
And stores these environment variables to ~/.bashrc file.
bazelisk test --config=mayberemote //...
To update generated code run the following in any directory:
go generate ./...
Install Cloud SDK.
Use this command to run the presubmit tests:
./run_unittests --small