Problem/Motivation

This is one of the slowest remaining functional tests, and the job it runs in finishes after all the other functional javascript jobs.

Steps to reproduce

If you look at https://git.drupalcode.org/project/drupal/-/jobs/565430 - you will see that JsonApiRegressionTest is now the penultimate test to finish (the first list of tests is shown in the order they finish). On test runs of HEAD, it's the last test to finish.

Proposed resolution

Split the tests dealing with PATCH requests out to their own test class.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3412029

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

catch created an issue. See original summary.

catch opened merge request !6006

catch’s picture

catch
he/him
Primary language English
commented
Issue summary: View changes
catch’s picture

catch
he/him
Primary language English
commented
Issue summary: View changes
Status: Active » Needs review
smustgrave’s picture

smustgrave commented
Status: Needs review » Reviewed & tested by the community

Nothing appears lost from the split.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Status: Reviewed & tested by the community » Fixed

Given how our tests are it'd be cool to implement something similar to paratests parallel method running instead of doing this. But this is simple for now.

Committed and pushed 02f4022504 to 11.x and 635cd75543 to 10.2.x. Thanks!

Backported to 10.2.x because this is test only.

  • alexpott committed 635cd755 on 10.2.x 
    Issue #3412029 by catch: Split up JsonApiRegressionTest

(cherry picked...

  • alexpott committed 02f40225 on 11.x 
    Issue #3412029 by catch: Split up JsonApiRegressionTest

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.