Functional Tests: Declaration of Declaration of Drupal\Tests\recaptcha\Functional\RecaptchaJavascriptTest::setUp()

aaron.ferris → made their first commit to this issue’s fork.

I think this test is gone, im not seeing it in 8.x-3.x

You're right, I don't see it in 8.x-3.x-dev either. Is there any hint that will be in a stable release soon?

I'm attempting to put together a patch for 3.2, so that tests of my custom modules could run in composer-built CI, but I can't find a way to clone that specific release in order to build a patch of it (using instructions here: https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupa... → ). Do I need to switch to the non-stable dev branch or just not have any functional tests until the next release, or am I missing some other way to tell composer I want stable but with this one fix?

Afraid that would be a Q for the module maintainers, the MR from the previously mentioned issue would need to be merged in as well of course.

If you want to keep your Composer as minimum stable you'd need to add a new patch (or grab a patch from the latest MR that includes the return type) and include that in your composer.json - if your project is already using the patch that introduces this test then hopefully composer is already using cweagans/composer-patches?

Some good info here: https://www.drupal.org/docs/develop/using-composer/manage-dependencies →

Ah, thanks for catching that the one other patch I'm using for this module is what is adding that bad test. I missed your edit on your first comment before I made my response. I was getting very confused why there was no alignment between the composer version and the repo version. In that case, I should be able to edit that patch file to add that void declaration.

Welcome!