bug: Application context fails to load after upgrade to springboot 3.x about dgs-framework HOT 4 CLOSED

Hi @AshaBPatil, I'm not able to reproduce this with the current version of the framework running springboot 3.2 as the dgs application boots successfully. I noticed error message mentions testClass = com.chegg.acds.answer.service.datafetcher.AnswerFieldDataFetcherTest, it appears this is failing in a test context?

from dgs-framework.

yes this is happening only in the test environment , this is the test code :
@ExtendWith(MockitoExtension.class)
@SpringBootTest(
classes = {
DgsAutoConfiguration.class,
AnswerFieldDataFetcher.class,
GraphQLRuntimeWiring.class,
DgsExtendedScalarsAutoConfiguration.class
},
properties = {})
public class AnswerFieldDataFetcherTest {
@Autowired DgsQueryExecutor dgsQueryExecutor;
@MockBean AnswerService answerService;
@MockBean Executor answerAsyncExecutor;
HttpHeaders httpHeaders;
@MockBean CompletableFuture completableFuture;

@beforeeach
public void init() {
openMocks(this);
httpHeaders =
new HttpHeaders(
new LinkedMultiValueMap<>() {
{
put(X_CHEGG_USER_UUID.getKey(), Collections.singletonList(USER_UUID.toString()));
}
});
}

@test
@DisplayName("Get ec answer field for question with exception")
public void testEcAnswersWithException() throws ExecutionException, InterruptedException {
doThrow(new RuntimeException()).when(answerAsyncExecutor).execute(any(Runnable.class));

Map<String, Object> variables = getVariables(QUESTION_UUID.toString());
ExecutionResult result =
    dgsQueryExecutor.execute(GET_EC_ANSWER_FIELD_QUERY, variables, null, httpHeaders);
assertTrue(result.getErrors().size() > 0);
assertEquals(
    result.getErrors().get(0).getMessage(),
    String.format(
        "%s: %s",
        InternalServerError.class.getCanonicalName(),
        String.format(UNABLE_TO_GET_EC_ANSWER_BY_QUESTION, QUESTION_UUID)));

}
}

from dgs-framework.

Confirming this did compile and run in spring 2.x and no longer in 3.x. The issue is that ScheduledExecutorService is a dependency of dgsQueryExecutor and the issue arises when mocking it's superclass Executor.
ScheduledExecutorService extends Executor with additional functionality. Can you try swapping Executor for ScheduledExecutorService for your mock?

from dgs-framework.

this worked for me thank you

from dgs-framework.