fix(actions): fix e2e UI test

[pedrobonamin]

Description

Adds missing env variable for e2e ui actions
You can see tests passing here

What to review

Testing

Notes for release

n/a

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2025 5:57pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2025 5:57pm

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
e2e-studio	⬜️ Ignored (Inspect)			Jun 17, 2025 5:57pm
studio-workshop	⬜️ Ignored (Inspect)			Jun 17, 2025 5:57pm
test-next-studio	⬜️ Ignored (Inspect)			Jun 17, 2025 5:57pm
page-building-studio	⬜️ Skipped (Inspect)			Jun 17, 2025 5:57pm

[github-actions]

⚡️ Editor Performance Report

Updated Tue, 17 Jun 2025 19:26:29 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	21.3 efps (47ms)	21.7 efps (46ms)	-1ms (-2.1%)	✅
article (body)	25.2 efps (40ms)	23.4 efps (43ms)	+3ms (+7.7%)	✅
article (string inside object)	23.3 efps (43ms)	23.8 efps (42ms)	-1ms (-2.3%)	✅
article (string inside array)	20.2 efps (50ms)	18.9 efps (53ms)	+4ms (+7.1%)	✅
recipe (name)	41.7 efps (24ms)	43.5 efps (23ms)	-1ms (-4.2%)	✅
recipe (description)	47.6 efps (21ms)	50.0 efps (20ms)	-1ms (-4.8%)	✅
recipe (instructions)	99.9+ efps (10ms)	99.9+ efps (10ms)	+0ms (-/-%)	✅
synthetic (title)	17.5 efps (57ms)	17.9 efps (56ms)	-1ms (-1.8%)	✅
synthetic (string inside object)	17.4 efps (58ms)	17.5 efps (57ms)	-1ms (-0.9%)	✅

efps — editor "frames per second". The number of updates assumed to be possible within a second.

Derived from input latency. efps = 1000 / input_latency

Detailed information

🏠 Reference result

The performance result of sanity@latest

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	47ms	61ms	88ms	319ms	640ms	12.4s
article (body)	40ms	47ms	83ms	310ms	1234ms	11.0s
article (string inside object)	43ms	46ms	53ms	172ms	323ms	7.7s
article (string inside array)	50ms	55ms	62ms	208ms	497ms	8.3s
recipe (name)	24ms	26ms	32ms	43ms	5ms	7.8s
recipe (description)	21ms	22ms	23ms	35ms	0ms	5.0s
recipe (instructions)	10ms	13ms	31ms	40ms	0ms	5.0s
synthetic (title)	57ms	61ms	73ms	324ms	1293ms	14.3s
synthetic (string inside object)	58ms	62ms	74ms	362ms	1323ms	9.3s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	46ms	51ms	67ms	284ms	455ms	11.7s
article (body)	43ms	61ms	105ms	355ms	1069ms	11.6s
article (string inside object)	42ms	49ms	53ms	100ms	287ms	7.5s
article (string inside array)	53ms	56ms	63ms	343ms	621ms	8.4s
recipe (name)	23ms	25ms	28ms	37ms	0ms	7.5s
recipe (description)	20ms	22ms	25ms	43ms	0ms	5.0s
recipe (instructions)	10ms	13ms	25ms	36ms	18ms	5.5s
synthetic (title)	56ms	61ms	112ms	297ms	1470ms	13.2s
synthetic (string inside object)	57ms	60ms	77ms	322ms	1105ms	8.9s

📚 Glossary

column definitions

• benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
• latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
• p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
• p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
• p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
• blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
• test duration — how long the test run took to complete.

[github-actions]

🧪 E2E Preview environment

🔑 Environment Variables for Local Testing

This is the preview URL for the E2E tests: https://e2e-studio-ikpgn4z5p.sanity.dev

To run the E2E tests locally, you can use the following environment variables, then run pnpm test:e2e --ui to open the Playwright test runner.

💬 Remember to build the project first with pnpm build:e2e.

  SANITY_E2E_PROJECT_ID=ittbm412
  SANITY_E2E_BASE_URL=https://e2e-studio-ikpgn4z5p.sanity.dev
  SANITY_E2E_DATASET="update depending the project you want to test (pr-9718-chromium-15714656788 || pr-9718-firefox-15714656788 )"
  SANITY_E2E_DATASET_CHROMIUM=pr-9718-chromium-15714656788
  SANITY_E2E_DATASET_FIREFOX=pr-9718-firefox-15714656788

[github-actions]

No changes to documentation

[github-actions]

📊 Playwright Test Report

Download Full E2E Report

This report contains test results, including videos of failing tests.

[stipsan]

Thanks! 💖

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	43.83%	59886 / 136604
🔵	Statements	43.83%	59886 / 136604
🔵	Functions	48.59%	2998 / 6169
🔵	Branches	79.43%	11132 / 14014

File Coverage

No changed files found.

Generated in workflow #36913 for commit 511baae by the Vitest Coverage Report Action