Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Our processors are now almost completely covered with tests, regarding their functionality.
However, we don't test whether their configuration forms work as expected, but especially for the "Aggregated fields" processor this would be interesting (even though we probably cannot verify the AJAX magic, we can at least test the no-JS fallback).
We should therefore either add configuring and using the processors to the existing integration test, or create a new one for it.
Comments
Comment #1
vurt CreditAttribution: vurt commentedI will have a try on this...
Comment #2
borisson_Comment #3
borisson_I have added these at DrupalCamp Ghent, they're in the master branch now.
Tests didn't pass on the run travis did when I pushed this to master but it looks like this is a problem with travis rather than my code (https://travis-ci.org/nickveenhof/search-api-sandbox/jobs/40378461).
Currently these tests are not very efficient, I'll try to add some more efficiency to the tests today.
Comment #4
borisson_I have removed some of the unneeded assertions in these tests. Travis still doesn't pass but I don't understand why Travis' mysql server goes away while trying to run tests.
Comment #5
drunken monkeyOK, thanks! It also works fine for me locally, so it's really just a Travis thing.
I'll look over it in the course of #2242361: Coding standards clean up.