Package org.evomaster.client.java.controller.api.dto

Class ActionResponseDto

java.lang.Object

org.evomaster.client.java.controller.api.dto.ActionResponseDto

public class ActionResponseDto
extends Object

handling response of actions which are executed in driver side

Field Summary

Fields

Modifier and Type	Field	Description
List<String>	assertionScript	code for assertions currently, the assertion generation is processed on driver side based on response instance returned after the endpoint is invoked.
CustomizedCallResultCode	customizedCallResultCode	representing a result categorized by user's specification
String	error500Msg	with rpc, we need to return generated scripts and assertions then instead of only return msg, we return this dto with error msg
RPCExceptionInfoDto	exceptionInfoDto	representing exception info if it occurs
ExpandRPCInfoDto	expandInfo	for RPC problem, its schema or mock object might be expanded during the search
Integer	index	The index of this action which was executed in this test.
String	jsonResponse	an original response with json format
ParamDto	rpcResponse	a response from an RPC action.
List<String>	testScript	code for processing the action in generated test scripts, the action could be involved by either 1) executeRPCAction (a method in SutHandler) or 2) client.endpoint(args).

Constructor Summary

Constructors

Constructor	Description
ActionResponseDto()

Method Summary

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details

index

public Integer index

The index of this action which was executed in this test.

rpcResponse

public ParamDto rpcResponse

a response from an RPC action. note that this info is only used for RPC problem

jsonResponse

public String jsonResponse

an original response with json format

testScript

public List<String> testScript

code for processing the action in generated test scripts, the action could be involved by either 1) executeRPCAction (a method in SutHandler) or 2) client.endpoint(args). For 1), we could process it from core side, while for 2), now it is handled from driver side. this attribute is to enable 2) generation.

assertionScript

public List<String> assertionScript

code for assertions currently, the assertion generation is processed on driver side based on response instance returned after the endpoint is invoked. then this attribute contains a list of generated scripts for assertions on the response if it is not `void`

exceptionInfoDto

public RPCExceptionInfoDto exceptionInfoDto

representing exception info if it occurs

customizedCallResultCode

public CustomizedCallResultCode customizedCallResultCode

representing a result categorized by user's specification

error500Msg

public String error500Msg

with rpc, we need to return generated scripts and assertions then instead of only return msg, we return this dto with error msg

expandInfo

public ExpandRPCInfoDto expandInfo

for RPC problem, its schema or mock object might be expanded during the search

Constructor Details

ActionResponseDto

public ActionResponseDto()