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

Class AdditionalInfoDto

java.lang.Object

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

public class AdditionalInfoDto
extends Object

Field Summary

Fields

Modifier and Type	Field and Description
List<ExternalServiceInfoDto>	employedDefaultWM a list of external service info which is direct to default WM
List<ExternalServiceInfoDto>	externalServices To keep track of all external service calls used under SUT.
Set<String>	headers In REST APIs, it can happen that some HTTP headers do not appear in the schema if they are indirectly accessed via objects like WebRequest.
List<HostnameResolutionInfoDto>	hostnameResolutionInfoDtos
String	lastExecutedStatement Keep track of the last executed statement done in the SUT.
Set<String>	parsedDtoNames The name of all DTO that have been parsed (eg, with GSON and Jackson).
Set<String>	queryParameters In REST APIs, it can happen that some query parameters do not appear in the schema if they are indirectly accessed via objects like WebRequest.
Boolean	rawAccessOfHttpBodyPayload Check if the business logic of the SUT (and not a third-party library) is accessing the raw bytes of HTTP body payload (if any) directly
Map<String,List<StringSpecializationInfoDto>>	stringSpecializations Information for taint analysis.

Constructor Summary

Constructors

Constructor and Description
AdditionalInfoDto()

Method Summary

Methods inherited from class java.lang.Object

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

Field Detail

queryParameters

public Set<String> queryParameters

In REST APIs, it can happen that some query parameters do not appear in the schema if they are indirectly accessed via objects like WebRequest. But we can track at runtime when such kind of objects are used to access the query parameters

headers

public Set<String> headers

In REST APIs, it can happen that some HTTP headers do not appear in the schema if they are indirectly accessed via objects like WebRequest. But we can track at runtime when such kind of objects are used to access the query parameters

stringSpecializations

public Map<String,List<StringSpecializationInfoDto>> stringSpecializations

Information for taint analysis. When some string inputs are recognized of a specific type (eg, they are used as integers or dates), we keep track of it. The key in this map is the value of the tainted input. The associated list is its possible specializations (which usually will be at most 1).

lastExecutedStatement

public String lastExecutedStatement

Keep track of the last executed statement done in the SUT. But not in the third-party libraries, just the business logic of the SUT. The statement is represented with a descriptive unique id, like the class name and line number.

rawAccessOfHttpBodyPayload

public Boolean rawAccessOfHttpBodyPayload

Check if the business logic of the SUT (and not a third-party library) is accessing the raw bytes of HTTP body payload (if any) directly

parsedDtoNames

public Set<String> parsedDtoNames

The name of all DTO that have been parsed (eg, with GSON and Jackson). Note: the actual content of schema is queried separately.

externalServices

public List<ExternalServiceInfoDto> externalServices

To keep track of all external service calls used under SUT.

employedDefaultWM

public List<ExternalServiceInfoDto> employedDefaultWM

a list of external service info which is direct to default WM

hostnameResolutionInfoDtos

public List<HostnameResolutionInfoDto> hostnameResolutionInfoDtos

Constructor Detail

AdditionalInfoDto

public AdditionalInfoDto()