Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
There is some complex logic that occurs when the Acquia Search module is disabled. We should define the expected behaviors and add tests for them.
Comment | File | Size | Author |
---|---|---|---|
#2 | disable-tests-1791642-2.patch | 5.94 KB | cpliakas |
#1 | disable-tests-1791642-1.patch | 2.57 KB | cpliakas |
Comments
Comment #1
cpliakas CreditAttribution: cpliakas commentedFirst use case, marking as needs work because there are others.
Comment #2
cpliakas CreditAttribution: cpliakas commentedAdded the different use cases I could think of. The bot will fail because testDisableModuleCase2() has two use cases that I think should be addressed but aren't yet. Will file a separate issue where we can discuss the use cases, and will set this as postponed pending that discussion.
Comment #4
cpliakas CreditAttribution: cpliakas commentedTests failed as expected. Marking as "postponed" pending discussion at #1791824: Discuss use cases when disabling Acquia Search and what the default environment should fall back to.
Comment #6
Dane Powell CreditAttribution: Dane Powell at Acquia commentedThis branch of Acquia Connector is no longer supported, per the version policy on the project homepage. As such, I'm tentatively closing this issue.
If this issue still applies to a supported branch (currently 7.x-3.x, 8.x-1.x, or 8.x-2.x), please reopen and select the new target version. Thanks!