test: e2e supports easy tagging of tests and running of tags

[jordanl17]

Description

What to review

Testing

Notes for release

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
page-building-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2025 5:09pm
performance-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2025 5:09pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2025 5:09pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Mar 28, 2025 5:09pm
test-next-studio	⬜️ Ignored (Inspect)			Mar 28, 2025 5:09pm

[github-actions]

No changes to documentation

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	43.27%	56324 / 130157
🔵	Statements	43.27%	56324 / 130157
🔵	Functions	47.27%	2786 / 5893
🔵	Branches	79.65%	10494 / 13174

File Coverage

No changed files found.

Generated in workflow #32978 for commit 8974318 by the Vitest Coverage Report Action

[github-actions]

⚡️ Editor Performance Report

Updated Fri, 28 Mar 2025 17:18:59 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	26.3 efps (38ms)	25.0 efps (40ms)	+2ms (+5.3%)	✅
article (body)	72.5 efps (14ms)	72.5 efps (14ms)	+0ms (-/-%)	✅
article (string inside object)	24.1 efps (42ms)	24.4 efps (41ms)	-1ms (-1.2%)	✅
article (string inside array)	23.8 efps (42ms)	21.3 efps (47ms)	+5ms (+11.9%)	✅
recipe (name)	45.5 efps (22ms)	43.5 efps (23ms)	+1ms (+4.5%)	✅
recipe (description)	47.6 efps (21ms)	47.6 efps (21ms)	+0ms (-/-%)	✅
recipe (instructions)	99.9+ efps (6ms)	99.9+ efps (6ms)	+0ms (-/-%)	✅
synthetic (title)	18.5 efps (54ms)	18.2 efps (55ms)	+1ms (+1.9%)	✅
synthetic (string inside object)	19.4 efps (52ms)	17.2 efps (58ms)	+7ms (+12.6%)	✅

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)	38ms	41ms	45ms	62ms	50ms	10.6s
article (body)	14ms	16ms	18ms	62ms	73ms	4.9s
article (string inside object)	42ms	48ms	68ms	132ms	420ms	7.7s
article (string inside array)	42ms	44ms	49ms	138ms	308ms	7.1s
recipe (name)	22ms	24ms	29ms	47ms	6ms	7.8s
recipe (description)	21ms	22ms	23ms	24ms	0ms	4.8s
recipe (instructions)	6ms	7ms	8ms	8ms	0ms	3.1s
synthetic (title)	54ms	58ms	64ms	358ms	1167ms	12.8s
synthetic (string inside object)	52ms	54ms	60ms	200ms	828ms	8.1s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	40ms	42ms	44ms	63ms	61ms	9.7s
article (body)	14ms	16ms	22ms	138ms	185ms	5.3s
article (string inside object)	41ms	45ms	52ms	235ms	339ms	7.7s
article (string inside array)	47ms	50ms	55ms	250ms	546ms	7.9s
recipe (name)	23ms	25ms	28ms	44ms	1ms	8.0s
recipe (description)	21ms	24ms	28ms	42ms	0ms	5.0s
recipe (instructions)	6ms	8ms	10ms	33ms	0ms	3.4s
synthetic (title)	55ms	60ms	72ms	208ms	1272ms	14.4s
synthetic (string inside object)	58ms	60ms	65ms	275ms	1176ms	8.6s

📚 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]

📊 Playwright Test Report

Download Full E2E Report

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