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

Class SutInfoDto

java.lang.Object

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

public class SutInfoDto
extends Object

Nested Class Summary

Nested Classes

Modifier and Type	Class and Description
static class	SutInfoDto.OutputFormat

Field Summary

Fields

Modifier and Type	Field and Description
String	baseUrlOfSUT The base URL of the running SUT (if any).
BootTimeInfoDto	bootTimeInfoDto info collected during SUT boot-time
SutInfoDto.OutputFormat	defaultOutputFormat When generating test cases for this SUT, specify the default preferred output format (eg JUnit 4 in Java)
List<String>	errorMsg there might exist some errors which could be ignored for the moment in order to make evomaster still process test generations.
GraphQLProblemDto	graphQLProblem If the SUT is a GraphQL API, here there will be the info on how to interact with it
List<AuthenticationDto>	infoForAuthentication There is no way a testing system can guess passwords, even if given full access to the database storing them (ie, reversing hash values).
Boolean	isSutRunning Whether the SUT is running or not
RestProblemDto	restProblem If the SUT is a RESTful API, here there will be the info on how to interact with it
RPCProblemDto	rpcProblem If the SUT is a PRC-based service, here there will be the info on how to interact with it
DbSchemaDto	sqlSchemaDto If the application is using a SQL database, then we need to know its schema to be able to do operations on it.
UnitsInfoDto	unitsInfoDto Information about the "units" in the SUT.

Constructor Summary

Constructors

Constructor and Description
SutInfoDto()

Method Summary

Methods inherited from class java.lang.Object

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

Field Detail

restProblem

public RestProblemDto restProblem

If the SUT is a RESTful API, here there will be the info on how to interact with it

graphQLProblem

public GraphQLProblemDto graphQLProblem

If the SUT is a GraphQL API, here there will be the info on how to interact with it

rpcProblem

public RPCProblemDto rpcProblem

If the SUT is a PRC-based service, here there will be the info on how to interact with it

isSutRunning

public Boolean isSutRunning

Whether the SUT is running or not

defaultOutputFormat

public SutInfoDto.OutputFormat defaultOutputFormat

When generating test cases for this SUT, specify the default preferred output format (eg JUnit 4 in Java)

baseUrlOfSUT

public String baseUrlOfSUT

The base URL of the running SUT (if any). E.g., "http://localhost:8080" It should only contain the protocol and the hostname/port

infoForAuthentication

public List<AuthenticationDto> infoForAuthentication

There is no way a testing system can guess passwords, even if given full access to the database storing them (ie, reversing hash values). As such, the SUT might need to provide a set of valid credentials

sqlSchemaDto

public DbSchemaDto sqlSchemaDto

If the application is using a SQL database, then we need to know its schema to be able to do operations on it.

unitsInfoDto

public UnitsInfoDto unitsInfoDto

Information about the "units" in the SUT.

bootTimeInfoDto

public BootTimeInfoDto bootTimeInfoDto

info collected during SUT boot-time

errorMsg

public List<String> errorMsg

there might exist some errors which could be ignored for the moment in order to make evomaster still process test generations. however, such error should be handled propertly in the future. to better view such errors, might show them on the core side

Constructor Detail

SutInfoDto

public SutInfoDto()