---
number: 7348
title: Migrate vdom/VdomAsymmetricUpdates test from Siesta to Playwright
author: KURO-1125
state: MERGED
createdAt: '2025-10-04T09:53:24Z'
updatedAt: '2025-10-04T14:11:54Z'
closedAt: '2025-10-04T13:46:13Z'
mergedAt: '2025-10-04T13:46:13Z'
head: migrate-vdom-asymmetric-updates
base: dev
url: 'https://github.com/neomjs/neo/pull/7348'
---
Migrates the Siesta test for `vdom/VdomAsymmetricUpdates.mjs` to Playwright using the AI native workflow.

- Create test/playwright/unit/vdom/VdomAsymmetricUpdates.spec.mjs
- Translate all Siesta assertions to Playwright expect syntax
- Create proper ticket following project strategy
- All tests pass successfully with npm test
- Generated using AI native workflow

Closes #7291 

Please make sure to read the Contributing Guidelines:
https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [x] Feature
- [ ] Code style update
- [x] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch, _not_ the `main` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)

If adding a **new feature**, the PR's description includes:

- [x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**

This migration is part of the ongoing effort to convert Siesta tests to Playwright. The AI native workflow ensured proper adherence to project conventions and complete test coverage for VDOM asymmetric update operations.


## Comments

### `@tobiu` commented on 2025-10-04T13:51:38Z

thx! merged in. btw, here is some context what this item was about:
https://github.com/neomjs/neo/blob/dev/learn/blog/v10-deep-dive-vdom-revolution.md

---

### `@KURO-1125` commented on 2025-10-04T13:57:43Z

Awesome, thanks for merging!
I'll check out that blog post to understand the VDOM revolution context better. 
Appreciate the learning resource!


---

### `@tobiu` commented on 2025-10-04T14:11:54Z

very simplified: drop a toolbar and 1 of its 10 child buttons into the same update cycle.

in theory, you could ask gemini: "use the ai knowledge db and tell me about asymmetric vdom updates!"

if it does not work, open a new ticket please :)

---

