Set budgets rather than exact numbers of asset size assertions

Created on 18 April 2024, 7 months ago
Updated 3 May 2024, 7 months ago

Problem/Motivation

To make backports between 11.x and 10.x easier (see 📌 Refactor (if feasible) uses of the jQuery animate function to use Vanilla/native Fixed ), we can use assertLessThan() instead of assertSame() for CSS/JS assert sizes in performance tests.

If we set appropriate assertions for both 11.x and 10.3.x, that will save having to update the performance tests on every small change to CSS or JavaScript, while still requiring new library additions to increase the budget, and hopefully still pick up any aggregation bugs.

Actual performance/size improvements should explicitly lower the budgets on both branches.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Fixed

Version

10.3

Component
PHPUnit 

Last updated about 10 hours ago

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024