} catch (DataStoreException e) {
            assertEquals(errorMessage, e.getMessage());
            assertNull(e.getCause());
        } catch (Exception e) {
            fail("Should have caught DataStoreException specifically");
        }
    }

    @Test
    public void test_throwAndCatchWithCause() {
        // Test throwing and catching the exception with cause
        final String errorMessage = "Data store write error";

            param("env.JDK11", javaHome(OpenJdk11, Os.LINUX))
            param("env.JDK17", javaHome(OpenJdk17, Os.LINUX))
            // Keep 21 and 25 for tests requiring it specifically: https://github.com/gradle/gradle/pull/35410#discussion_r2460835304
            param("env.JDK21", javaHome(OpenJdk21, Os.LINUX))
            param("env.JDK25", javaHome(OpenJdk25, Os.LINUX))

import org.opensearch.common.settings.Settings;
import org.opensearch.common.settings.Settings.Builder;
import org.opensearch.transport.client.Client;

/**
 * OpenSearch client implementation specifically for crawler operations.
 * Extends FesenClient to provide search engine connectivity for the crawler components.
 */
public class CrawlerEngineClient extends FesenClient {

    /**

Gradle is an international open-source project with contributors from around the world. English is the primary language for code, comments, documentation, and communication, but there are variations in English spelling and terminology, specifically American English vs. British English.

Inconsistency in spelling conventions can lead to several issues:

    @Test
    public void test_register_arrayList() {
        RenderData data = new RenderData();

        BsUser entity1 = new BsUser();
        entity1.setName("user1");

        // Test ArrayList specifically (not just List interface)
        ArrayList<BsUser> arrayList = new ArrayList<>();
        arrayList.add(entity1);

        RenderDataUtil.register(data, "arrayList", arrayList);

                    // Sort the array in place by type, then member
                    // Note that Firefox is fine with a sort function returning any positive or negative number, but Chrome
                    // requires 1 or -1 specifically and ignores higher or lower values.  This sort ought to remain consistent
                    // with the sort used by AbstractAcceptedApiChangesMaintenanceTask.
                    result.acceptedApiChanges.sort((a, b) => {