[meta] Add messages to assertions in a loop in sped up tests

Created on 26 August 2024, 5 months ago

Problem/Motivation

Recent commits to speed up the tests has changed some test to use a loop instead of a dataprovider without also adding messages to the assertions. The messages are needed to identify which case is failing.

So far, these have been checked. Are there others?

  1. 📌 Speed up ContentModerationStateTest Fixed
  2. 📌 Speed up RevisionRevertFormTest Fixed
  3. 📌 Speed up UpdateSemverTestSecurityAvailabilityTrait Fixed
  4. 📌 Speed up UpdateSemverTestSecurityCoverageTest Fixed
  5. 📌 Speed up UpdateContribTest Fixed
  6. 📌 Speed up JSON:API ResourceTestBase Fixed
  7. 📌 Speed up BigPipeRegressionTest Fixed
  8. 📌 Speed up WorkspacesContentModerationStateTest Fixed
  9. 📌 Speed up DemoUmamiProfileTest Fixed
  10. 📌 Speed up PageCacheTest Fixed
  11. 📌 Speed up ElementsTest Active
  12. 📌 Speed up ExposedFormTest Fixed

Steps to reproduce

Proposed resolution

Check all recent speed up tests for removal of a dataprovider. For those, add messages to the assertions in the loop.

Remaining tasks

Of the 12 in the proposed resolution, the following need follow up work. Add a child issue for the following, after the issue is committed.

  1. 📌 Speed up ContentModerationStateTest Fixed
  2. 📌 Speed up RevisionRevertFormTest Fixed
  3. 📌 Speed up UpdateSemverTestSecurityAvailabilityTrait Fixed
  4. 📌 Speed up UpdateSemverTestSecurityCoverageTest Fixed
  5. 📌 Speed up UpdateContribTest Fixed

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

11.0 🔥

Component
PHPUnit 

Last updated 4 minutes ago

Created by

🇳🇿New Zealand quietone

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

Comments & Activities

Production build 0.71.5 2024