TL;DR Gutenberg’s JavaScript unit and integration tests now use Vitest, bringing better support for modern JavaScript modules and real-browser component testing. Tests explicitly import Vitest APIs. Filenames select Node, jsdom, or Browser Mode according to what each test needs. @wordpress/scripts 36.0.0 makes Vitest the default for test-unit-js. Projects install and configure their own test runner. […]
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Comment on Call for Testing: Responsive Styling by Kedar Joyner | 0 | 8.89 | 05-08-2026 |
| 2 | Guidelines for Syncing Code From Gutenberg Into WordPress Develop | 0 | 7 | 30-06-2026 |
| 3 | VirtualBrowser: VirtualBrowser vs Cloud Browsers and Browser Automation Alternatives | 0 | 17.33 | 23-09-2026 |
| 4 | Call for testing: DataForm editor inspector | 0 | 6.97 | 17-09-2026 |
| 5 | tryke: Rust-Based, Jest-Style Test Runner | 0 | 50 | 07-05-2026 |
| 6 | Вышел Meta Test 2.0 | 0 | 10.42 | 17-09-2026 |
| 7 | Как мы создали новый тестовый фреймворк, адаптируемый к росту проектов | 0 | 6.14 | 11-04-2026 |
| 8 | Comment on Call for Testing: Gutenberg 4.7 by seiko12 | 0 | 11.09 | 15-08-2026 |
| 9 | Параметризация Pytest: когда файловая коллекция становится тест-кейсами | 0 | 11.85 | 21-03-2026 |
| 10 | What’s new in Gutenberg 23.5? (July 1, 2026) | 0 | 5 | 01-07-2026 |