InconclusiveDetailArgs

data class InconclusiveDetailArgs(val abortedByUser: Output<Boolean>? = null, val hasErrorLogs: Output<Boolean>? = null, val infrastructureFailure: Output<Boolean>? = null) : ConvertibleToJava<InconclusiveDetailArgs>

Details for an outcome with an INCONCLUSIVE outcome summary.

Constructors

Link copied to clipboard
fun InconclusiveDetailArgs(abortedByUser: Output<Boolean>? = null, hasErrorLogs: Output<Boolean>? = null, infrastructureFailure: Output<Boolean>? = null)

Functions

Link copied to clipboard
open override fun toJava(): InconclusiveDetailArgs

Properties

Link copied to clipboard
val abortedByUser: Output<Boolean>? = null

If the end user aborted the test execution before a pass or fail could be determined. For example, the user pressed ctrl-c which sent a kill signal to the test runner while the test was running.

Link copied to clipboard
val hasErrorLogs: Output<Boolean>? = null

If results are being provided to the user in certain cases of infrastructure failures

Link copied to clipboard
val infrastructureFailure: Output<Boolean>? = null

If the test runner could not determine success or failure because the test depends on a component other than the system under test which failed. For example, a mobile test requires provisioning a device where the test executes, and that provisioning can fail.