Autocomplete on taxonomy term name

Does the information that is passed to the DB backend look correct? Then yes, please move it to the Search API queue, DB backend component, and we'll try to come up with a test there.

This adds infrastructure for testing autocomplete, plus two assertions for simple autocompletion cases.
For me, both of them pass. If they do for you, too, please try to add a failing assertion based on your specific scenario. (If necessary, you can of course also change the index (in the test code, not the export) or other config, or add more items.)

Damn, that #$*@ @group gets me every single time …

Oh, didn't know about that annotation … Great work, Drupal testing infrastructure!
(Hm, though it remains to be seen whether this will make it download the module or skip the test …)

However, forgot to say before that I'm not sure anyways whether we should commit this patch at this point. The Autocomplete module is far from stable, I'll still surely change lots of things (e.g., most class/interface names), and I'm not sure breaking the Search API tests each time is a good idea. (It would at least ensure we keep our integration up-to-date, but it's still less than ideal, I'd say. Even if both modules are maintained by the same person.)

Yes, seems that's the problem. Then let's just go with the patch in #8.

However, I actually thought you wanted to use the test to show what doesn't work? (Even if the test bot fails in any case, we can use it locally for verifying/debugging.) Would be great if you could try to come up with a failing test based on the patch.

Also, see my notes about committing this in #10 – what's your opinion on that?

This test doesn't use a lot of internals of what the autocomplete module does, so committing it now doesn't seem like a bad idea.

It's not really about internals. The SearchApiAutocompleteSearchInterface class name, e.g., will definitely be changed.
Hm, so maybe just remove the type hint there for now? (Patch attached, interdiff compared to #8.)
However, the method signature itself might also change, and with the discrepancy between dev version and the version used by the d.o test bot, it might be tricky to adapt to that without causing test fails in the mean time.
Furthermore, now that we know this is working, I'd say it's pretty unlikely to break unless we actually change that method. In which case we can also just run the tests manually, if we want to verify we didn't break anything.

But all of that considered, if you still think we should add it, then let's do it. (With or without type hint, your choice.) We'll survive if the test bot chokes at some point on this for a day or two.

The patch here seems to be failing though, so let's fix that before commit.

It's working fine for me. What failures do you get?
(The test bot failing, as discussed, is just a fault in the test bot regarding new module dependencies. It should be fixed once we commit the patch – at least we'll have to hope that.)

Ah, OK, no problem.
Committed. Let's hope for the best. ;)

Hm, should we then mark this as "Fixed" or move it back to "Active" for your original problem?

Didn't pass after all, for some reason, had to disable it again for now. Maybe after we've made another release for the Search API? (Which we probably should do soon in any case.)

Let's try again.
(Just realize I should have probably removed it from the changelog after disabling the test. But well, no big deal.)

Ah, wait, seems we forgot to actually depend on the Search API Autocomplete module in the test module! Maybe that'll solve it?

Apparently not.
But I now committed that dependency, maybe that helps. Otherwise, let's wait for the next release (1.2), then try again and if it still doesn't work go complain in the Drupal CI issue queue.
Perhaps it won't work as long as the Autocomplete module doesn't have a stable release?