re-enable async processing in index trigger tests

Author: dennisvang

src/test/java/org/fairdatateam/fairdatapoint/acceptance/index/admin/List_Trigger_POST.java

@@ -34,11 +34,13 @@
 import org.junit.jupiter.api.DisplayName;
 import org.junit.jupiter.api.Test;
 import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.boot.test.context.TestConfiguration;
 import org.springframework.core.ParameterizedTypeReference;
 import org.springframework.http.HttpHeaders;
 import org.springframework.http.HttpStatus;
 import org.springframework.http.RequestEntity;
 import org.springframework.http.ResponseEntity;
+import org.springframework.scheduling.annotation.EnableAsync;
 
 import java.net.URI;
 import java.util.List;
@@ -202,4 +204,16 @@ public void res404_triggerOne() {
         assertThat("One AdminTrigger event is created", events.size(), is(equalTo(1)));
         assertThat("Records correct client URL", events.get(0).getAdminTrigger().getClientUrl(), is(equalTo(entry.getClientUrl())));
     }
+
+    /**
+     * Enables asynchronous request processing.
+     * This reproduces the exception handling behaviour of the production config,
+     * which causes RDF parsing exceptions to be ignored by the ExceptionControllerAdvice,
+     * because they occur in worker threads.
+     * The parsing exceptions should be reflected in the resulting IndexEntryState instead.
+     */
+    @TestConfiguration
+    @EnableAsync
+    public static class AsyncConfig {
+    }
 }