Problem/Motivation

I can never remember the names of the variables when I want to run the repeat test class job. However, GitLab now has a better feature for this: job inputs.

These are predefined settings that you can require and describe in the UI, instead of having to remember or copy-and-paste variable names into a form.

Steps to reproduce

Proposed resolution

Swap the variables for inputs.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3616180

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

longwave created an issue. See original summary.

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Active » Needs review

Now the job should prompt you for inputs, but if you leave the test class blank, it will fall back to the test-only method: run the tests that you changed in the MR.

This MR was largely written by Claude Code.

longwave opened merge request !16661

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Needs review » Needs work

Apparently I do not have access to start the job.

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Needs work » Needs review

Oh, it was only that GitLab had logged me out again.

smustgrave’s picture

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

Pipeline seems to run fine, if this better helps use run repeats for random failure tickets all for it.

mstrelan’s picture

mstrelan commented
Status: Reviewed & tested by the community » Needs work

Tested this with the suggested class and 5 repeats and confirm its both easier to understand and works as expected, see https://git.drupalcode.org/project/drupal/-/jobs/11484423

Can we test making a change to one or more test classes so we can check that this works with empty inputs? Either as a separate MR or as a commit to this MR that we revert afterwards?

I also tried with a preceding backslash, which is what PhpStorm gives you by default when you copy a reference to the class, and it was rejected by the regex. I think we should allow either.

One other nit: if we're providing an example I think we should use something that's efficient and likely not to be removed, e.g. if we move away from ckeditor5. Perhaps `\Drupal\Tests\UnitTestCaseTest` would be ideal.