Google Cloud Native is in preview. Google Cloud Classic is fully supported.
google-native.toolresults/v1beta3.getStep
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Gets a Step. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to read project - INVALID_ARGUMENT - if the request is malformed - NOT_FOUND - if the Step does not exist
Using getStep
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getStep(args: GetStepArgs, opts?: InvokeOptions): Promise<GetStepResult>
function getStepOutput(args: GetStepOutputArgs, opts?: InvokeOptions): Output<GetStepResult>
def get_step(execution_id: Optional[str] = None,
history_id: Optional[str] = None,
project: Optional[str] = None,
step_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetStepResult
def get_step_output(execution_id: Optional[pulumi.Input[str]] = None,
history_id: Optional[pulumi.Input[str]] = None,
project: Optional[pulumi.Input[str]] = None,
step_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetStepResult]
func LookupStep(ctx *Context, args *LookupStepArgs, opts ...InvokeOption) (*LookupStepResult, error)
func LookupStepOutput(ctx *Context, args *LookupStepOutputArgs, opts ...InvokeOption) LookupStepResultOutput
> Note: This function is named LookupStep
in the Go SDK.
public static class GetStep
{
public static Task<GetStepResult> InvokeAsync(GetStepArgs args, InvokeOptions? opts = null)
public static Output<GetStepResult> Invoke(GetStepInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetStepResult> getStep(GetStepArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:toolresults/v1beta3:getStep
arguments:
# arguments dictionary
The following arguments are supported:
- Execution
Id string - History
Id string - Step
Id string - Project string
- Execution
Id string - History
Id string - Step
Id string - Project string
- execution
Id String - history
Id String - step
Id String - project String
- execution
Id string - history
Id string - step
Id string - project string
- execution_
id str - history_
id str - step_
id str - project str
- execution
Id String - history
Id String - step
Id String - project String
getStep Result
The following output properties are available:
- Completion
Time Pulumi.Google Native. Tool Results. V1Beta3. Outputs. Timestamp Response - The time when the step status was set to complete. This value will be set automatically when state transitions to COMPLETE. - In response: set if the execution state is COMPLETE. - In create/update request: never set
- Creation
Time Pulumi.Google Native. Tool Results. V1Beta3. Outputs. Timestamp Response - The time when the step was created. - In response: always set - In create/update request: never set
- Description string
- A description of this tool For example: mvn clean package -D skipTests=true - In response: present if set by create/update request - In create/update request: optional
- Device
Usage Pulumi.Duration Google Native. Tool Results. V1Beta3. Outputs. Duration Response - How much the device resource is used to perform the test. This is the device usage used for billing purpose, which is different from the run_duration, for example, infrastructure failure won't be charged for device usage. PRECONDITION_FAILED will be returned if one attempts to set a device_usage on a step which already has this field set. - In response: present if previously set. - In create request: optional - In update request: optional
- Dimension
Value List<Pulumi.Google Native. Tool Results. V1Beta3. Outputs. Step Dimension Value Entry Response> - If the execution containing this step has any dimension_definition set, then this field allows the child to specify the values of the dimensions. The keys must exactly match the dimension_definition of the execution. For example, if the execution has
dimension_definition = ['attempt', 'device']
then a step must define values for those dimensions, eg.dimension_value = ['attempt': '1', 'device': 'Nexus 6']
If a step does not participate in one dimension of the matrix, the value for that dimension should be empty string. For example, if one of the tests is executed by a runner which does not support retries, the step could havedimension_value = ['attempt': '', 'device': 'Nexus 6']
If the step does not participate in any dimensions of the matrix, it may leave dimension_value unset. A PRECONDITION_FAILED will be returned if any of the keys do not exist in the dimension_definition of the execution. A PRECONDITION_FAILED will be returned if another step in this execution already has the same name and dimension_value, but differs on other data fields, for example, step field is different. A PRECONDITION_FAILED will be returned if dimension_value is set, and there is a dimension_definition in the execution which is not specified as one of the keys. - In response: present if set by create - In create request: optional - In update request: never set - Has
Images bool - Whether any of the outputs of this step are images whose thumbnails can be fetched with ListThumbnails. - In response: always set - In create/update request: never set
- Labels
List<Pulumi.
Google Native. Tool Results. V1Beta3. Outputs. Step Labels Entry Response> - Arbitrary user-supplied key/value pairs that are associated with the step. Users are responsible for managing the key namespace such that keys don't accidentally collide. An INVALID_ARGUMENT will be returned if the number of labels exceeds 100 or if the length of any of the keys or values exceeds 100 characters. - In response: always set - In create request: optional - In update request: optional; any new key/value pair will be added to the map, and any new value for an existing key will update that key's value
- Multi
Step Pulumi.Google Native. Tool Results. V1Beta3. Outputs. Multi Step Response - Details when multiple steps are run with the same configuration as a group. These details can be used identify which group this step is part of. It also identifies the groups 'primary step' which indexes all the group members. - In response: present if previously set. - In create request: optional, set iff this step was performed more than once. - In update request: optional
- Name string
- A short human-readable name to display in the UI. Maximum of 100 characters. For example: Clean build A PRECONDITION_FAILED will be returned upon creating a new step if it shares its name and dimension_value with an existing step. If two steps represent a similar action, but have different dimension values, they should share the same name. For instance, if the same set of tests is run on two different platforms, the two steps should have the same name. - In response: always set - In create request: always set - In update request: never set
- Outcome
Pulumi.
Google Native. Tool Results. V1Beta3. Outputs. Outcome Response - Classification of the result, for example into SUCCESS or FAILURE - In response: present if set by create/update request - In create/update request: optional
- Run
Duration Pulumi.Google Native. Tool Results. V1Beta3. Outputs. Duration Response - How long it took for this step to run. If unset, this is set to the difference between creation_time and completion_time when the step is set to the COMPLETE state. In some cases, it is appropriate to set this value separately: For instance, if a step is created, but the operation it represents is queued for a few minutes before it executes, it would be appropriate not to include the time spent queued in its run_duration. PRECONDITION_FAILED will be returned if one attempts to set a run_duration on a step which already has this field set. - In response: present if previously set; always present on COMPLETE step - In create request: optional - In update request: optional
- State string
- The initial state is IN_PROGRESS. The only legal state transitions are * IN_PROGRESS -> COMPLETE A PRECONDITION_FAILED will be returned if an invalid transition is requested. It is valid to create Step with a state set to COMPLETE. The state can only be set to COMPLETE once. A PRECONDITION_FAILED will be returned if the state is set to COMPLETE multiple times. - In response: always set - In create/update request: optional
- Step
Id string - A unique identifier within a Execution for this Step. Returns INVALID_ARGUMENT if this field is set or overwritten by the caller. - In response: always set - In create/update request: never set
- Test
Execution Pulumi.Step Google Native. Tool Results. V1Beta3. Outputs. Test Execution Step Response - An execution of a test runner.
- Tool
Execution Pulumi.Step Google Native. Tool Results. V1Beta3. Outputs. Tool Execution Step Response - An execution of a tool (used for steps we don't explicitly support).
- Completion
Time TimestampResponse - The time when the step status was set to complete. This value will be set automatically when state transitions to COMPLETE. - In response: set if the execution state is COMPLETE. - In create/update request: never set
- Creation
Time TimestampResponse - The time when the step was created. - In response: always set - In create/update request: never set
- Description string
- A description of this tool For example: mvn clean package -D skipTests=true - In response: present if set by create/update request - In create/update request: optional
- Device
Usage DurationDuration Response - How much the device resource is used to perform the test. This is the device usage used for billing purpose, which is different from the run_duration, for example, infrastructure failure won't be charged for device usage. PRECONDITION_FAILED will be returned if one attempts to set a device_usage on a step which already has this field set. - In response: present if previously set. - In create request: optional - In update request: optional
- Dimension
Value []StepDimension Value Entry Response - If the execution containing this step has any dimension_definition set, then this field allows the child to specify the values of the dimensions. The keys must exactly match the dimension_definition of the execution. For example, if the execution has
dimension_definition = ['attempt', 'device']
then a step must define values for those dimensions, eg.dimension_value = ['attempt': '1', 'device': 'Nexus 6']
If a step does not participate in one dimension of the matrix, the value for that dimension should be empty string. For example, if one of the tests is executed by a runner which does not support retries, the step could havedimension_value = ['attempt': '', 'device': 'Nexus 6']
If the step does not participate in any dimensions of the matrix, it may leave dimension_value unset. A PRECONDITION_FAILED will be returned if any of the keys do not exist in the dimension_definition of the execution. A PRECONDITION_FAILED will be returned if another step in this execution already has the same name and dimension_value, but differs on other data fields, for example, step field is different. A PRECONDITION_FAILED will be returned if dimension_value is set, and there is a dimension_definition in the execution which is not specified as one of the keys. - In response: present if set by create - In create request: optional - In update request: never set - Has
Images bool - Whether any of the outputs of this step are images whose thumbnails can be fetched with ListThumbnails. - In response: always set - In create/update request: never set
- Labels
[]Step
Labels Entry Response - Arbitrary user-supplied key/value pairs that are associated with the step. Users are responsible for managing the key namespace such that keys don't accidentally collide. An INVALID_ARGUMENT will be returned if the number of labels exceeds 100 or if the length of any of the keys or values exceeds 100 characters. - In response: always set - In create request: optional - In update request: optional; any new key/value pair will be added to the map, and any new value for an existing key will update that key's value
- Multi
Step MultiStep Response - Details when multiple steps are run with the same configuration as a group. These details can be used identify which group this step is part of. It also identifies the groups 'primary step' which indexes all the group members. - In response: present if previously set. - In create request: optional, set iff this step was performed more than once. - In update request: optional
- Name string
- A short human-readable name to display in the UI. Maximum of 100 characters. For example: Clean build A PRECONDITION_FAILED will be returned upon creating a new step if it shares its name and dimension_value with an existing step. If two steps represent a similar action, but have different dimension values, they should share the same name. For instance, if the same set of tests is run on two different platforms, the two steps should have the same name. - In response: always set - In create request: always set - In update request: never set
- Outcome
Outcome
Response - Classification of the result, for example into SUCCESS or FAILURE - In response: present if set by create/update request - In create/update request: optional
- Run
Duration DurationResponse - How long it took for this step to run. If unset, this is set to the difference between creation_time and completion_time when the step is set to the COMPLETE state. In some cases, it is appropriate to set this value separately: For instance, if a step is created, but the operation it represents is queued for a few minutes before it executes, it would be appropriate not to include the time spent queued in its run_duration. PRECONDITION_FAILED will be returned if one attempts to set a run_duration on a step which already has this field set. - In response: present if previously set; always present on COMPLETE step - In create request: optional - In update request: optional
- State string
- The initial state is IN_PROGRESS. The only legal state transitions are * IN_PROGRESS -> COMPLETE A PRECONDITION_FAILED will be returned if an invalid transition is requested. It is valid to create Step with a state set to COMPLETE. The state can only be set to COMPLETE once. A PRECONDITION_FAILED will be returned if the state is set to COMPLETE multiple times. - In response: always set - In create/update request: optional
- Step
Id string - A unique identifier within a Execution for this Step. Returns INVALID_ARGUMENT if this field is set or overwritten by the caller. - In response: always set - In create/update request: never set
- Test
Execution TestStep Execution Step Response - An execution of a test runner.
- Tool
Execution ToolStep Execution Step Response - An execution of a tool (used for steps we don't explicitly support).
- completion
Time TimestampResponse - The time when the step status was set to complete. This value will be set automatically when state transitions to COMPLETE. - In response: set if the execution state is COMPLETE. - In create/update request: never set
- creation
Time TimestampResponse - The time when the step was created. - In response: always set - In create/update request: never set
- description String
- A description of this tool For example: mvn clean package -D skipTests=true - In response: present if set by create/update request - In create/update request: optional
- device
Usage DurationDuration Response - How much the device resource is used to perform the test. This is the device usage used for billing purpose, which is different from the run_duration, for example, infrastructure failure won't be charged for device usage. PRECONDITION_FAILED will be returned if one attempts to set a device_usage on a step which already has this field set. - In response: present if previously set. - In create request: optional - In update request: optional
- dimension
Value List<StepDimension Value Entry Response> - If the execution containing this step has any dimension_definition set, then this field allows the child to specify the values of the dimensions. The keys must exactly match the dimension_definition of the execution. For example, if the execution has
dimension_definition = ['attempt', 'device']
then a step must define values for those dimensions, eg.dimension_value = ['attempt': '1', 'device': 'Nexus 6']
If a step does not participate in one dimension of the matrix, the value for that dimension should be empty string. For example, if one of the tests is executed by a runner which does not support retries, the step could havedimension_value = ['attempt': '', 'device': 'Nexus 6']
If the step does not participate in any dimensions of the matrix, it may leave dimension_value unset. A PRECONDITION_FAILED will be returned if any of the keys do not exist in the dimension_definition of the execution. A PRECONDITION_FAILED will be returned if another step in this execution already has the same name and dimension_value, but differs on other data fields, for example, step field is different. A PRECONDITION_FAILED will be returned if dimension_value is set, and there is a dimension_definition in the execution which is not specified as one of the keys. - In response: present if set by create - In create request: optional - In update request: never set - has
Images Boolean - Whether any of the outputs of this step are images whose thumbnails can be fetched with ListThumbnails. - In response: always set - In create/update request: never set
- labels
List<Step
Labels Entry Response> - Arbitrary user-supplied key/value pairs that are associated with the step. Users are responsible for managing the key namespace such that keys don't accidentally collide. An INVALID_ARGUMENT will be returned if the number of labels exceeds 100 or if the length of any of the keys or values exceeds 100 characters. - In response: always set - In create request: optional - In update request: optional; any new key/value pair will be added to the map, and any new value for an existing key will update that key's value
- multi
Step MultiStep Response - Details when multiple steps are run with the same configuration as a group. These details can be used identify which group this step is part of. It also identifies the groups 'primary step' which indexes all the group members. - In response: present if previously set. - In create request: optional, set iff this step was performed more than once. - In update request: optional
- name String
- A short human-readable name to display in the UI. Maximum of 100 characters. For example: Clean build A PRECONDITION_FAILED will be returned upon creating a new step if it shares its name and dimension_value with an existing step. If two steps represent a similar action, but have different dimension values, they should share the same name. For instance, if the same set of tests is run on two different platforms, the two steps should have the same name. - In response: always set - In create request: always set - In update request: never set
- outcome
Outcome
Response - Classification of the result, for example into SUCCESS or FAILURE - In response: present if set by create/update request - In create/update request: optional
- run
Duration DurationResponse - How long it took for this step to run. If unset, this is set to the difference between creation_time and completion_time when the step is set to the COMPLETE state. In some cases, it is appropriate to set this value separately: For instance, if a step is created, but the operation it represents is queued for a few minutes before it executes, it would be appropriate not to include the time spent queued in its run_duration. PRECONDITION_FAILED will be returned if one attempts to set a run_duration on a step which already has this field set. - In response: present if previously set; always present on COMPLETE step - In create request: optional - In update request: optional
- state String
- The initial state is IN_PROGRESS. The only legal state transitions are * IN_PROGRESS -> COMPLETE A PRECONDITION_FAILED will be returned if an invalid transition is requested. It is valid to create Step with a state set to COMPLETE. The state can only be set to COMPLETE once. A PRECONDITION_FAILED will be returned if the state is set to COMPLETE multiple times. - In response: always set - In create/update request: optional
- step
Id String - A unique identifier within a Execution for this Step. Returns INVALID_ARGUMENT if this field is set or overwritten by the caller. - In response: always set - In create/update request: never set
- test
Execution TestStep Execution Step Response - An execution of a test runner.
- tool
Execution ToolStep Execution Step Response - An execution of a tool (used for steps we don't explicitly support).
- completion
Time TimestampResponse - The time when the step status was set to complete. This value will be set automatically when state transitions to COMPLETE. - In response: set if the execution state is COMPLETE. - In create/update request: never set
- creation
Time TimestampResponse - The time when the step was created. - In response: always set - In create/update request: never set
- description string
- A description of this tool For example: mvn clean package -D skipTests=true - In response: present if set by create/update request - In create/update request: optional
- device
Usage DurationDuration Response - How much the device resource is used to perform the test. This is the device usage used for billing purpose, which is different from the run_duration, for example, infrastructure failure won't be charged for device usage. PRECONDITION_FAILED will be returned if one attempts to set a device_usage on a step which already has this field set. - In response: present if previously set. - In create request: optional - In update request: optional
- dimension
Value StepDimension Value Entry Response[] - If the execution containing this step has any dimension_definition set, then this field allows the child to specify the values of the dimensions. The keys must exactly match the dimension_definition of the execution. For example, if the execution has
dimension_definition = ['attempt', 'device']
then a step must define values for those dimensions, eg.dimension_value = ['attempt': '1', 'device': 'Nexus 6']
If a step does not participate in one dimension of the matrix, the value for that dimension should be empty string. For example, if one of the tests is executed by a runner which does not support retries, the step could havedimension_value = ['attempt': '', 'device': 'Nexus 6']
If the step does not participate in any dimensions of the matrix, it may leave dimension_value unset. A PRECONDITION_FAILED will be returned if any of the keys do not exist in the dimension_definition of the execution. A PRECONDITION_FAILED will be returned if another step in this execution already has the same name and dimension_value, but differs on other data fields, for example, step field is different. A PRECONDITION_FAILED will be returned if dimension_value is set, and there is a dimension_definition in the execution which is not specified as one of the keys. - In response: present if set by create - In create request: optional - In update request: never set - has
Images boolean - Whether any of the outputs of this step are images whose thumbnails can be fetched with ListThumbnails. - In response: always set - In create/update request: never set
- labels
Step
Labels Entry Response[] - Arbitrary user-supplied key/value pairs that are associated with the step. Users are responsible for managing the key namespace such that keys don't accidentally collide. An INVALID_ARGUMENT will be returned if the number of labels exceeds 100 or if the length of any of the keys or values exceeds 100 characters. - In response: always set - In create request: optional - In update request: optional; any new key/value pair will be added to the map, and any new value for an existing key will update that key's value
- multi
Step MultiStep Response - Details when multiple steps are run with the same configuration as a group. These details can be used identify which group this step is part of. It also identifies the groups 'primary step' which indexes all the group members. - In response: present if previously set. - In create request: optional, set iff this step was performed more than once. - In update request: optional
- name string
- A short human-readable name to display in the UI. Maximum of 100 characters. For example: Clean build A PRECONDITION_FAILED will be returned upon creating a new step if it shares its name and dimension_value with an existing step. If two steps represent a similar action, but have different dimension values, they should share the same name. For instance, if the same set of tests is run on two different platforms, the two steps should have the same name. - In response: always set - In create request: always set - In update request: never set
- outcome
Outcome
Response - Classification of the result, for example into SUCCESS or FAILURE - In response: present if set by create/update request - In create/update request: optional
- run
Duration DurationResponse - How long it took for this step to run. If unset, this is set to the difference between creation_time and completion_time when the step is set to the COMPLETE state. In some cases, it is appropriate to set this value separately: For instance, if a step is created, but the operation it represents is queued for a few minutes before it executes, it would be appropriate not to include the time spent queued in its run_duration. PRECONDITION_FAILED will be returned if one attempts to set a run_duration on a step which already has this field set. - In response: present if previously set; always present on COMPLETE step - In create request: optional - In update request: optional
- state string
- The initial state is IN_PROGRESS. The only legal state transitions are * IN_PROGRESS -> COMPLETE A PRECONDITION_FAILED will be returned if an invalid transition is requested. It is valid to create Step with a state set to COMPLETE. The state can only be set to COMPLETE once. A PRECONDITION_FAILED will be returned if the state is set to COMPLETE multiple times. - In response: always set - In create/update request: optional
- step
Id string - A unique identifier within a Execution for this Step. Returns INVALID_ARGUMENT if this field is set or overwritten by the caller. - In response: always set - In create/update request: never set
- test
Execution TestStep Execution Step Response - An execution of a test runner.
- tool
Execution ToolStep Execution Step Response - An execution of a tool (used for steps we don't explicitly support).
- completion_
time TimestampResponse - The time when the step status was set to complete. This value will be set automatically when state transitions to COMPLETE. - In response: set if the execution state is COMPLETE. - In create/update request: never set
- creation_
time TimestampResponse - The time when the step was created. - In response: always set - In create/update request: never set
- description str
- A description of this tool For example: mvn clean package -D skipTests=true - In response: present if set by create/update request - In create/update request: optional
- device_
usage_ Durationduration Response - How much the device resource is used to perform the test. This is the device usage used for billing purpose, which is different from the run_duration, for example, infrastructure failure won't be charged for device usage. PRECONDITION_FAILED will be returned if one attempts to set a device_usage on a step which already has this field set. - In response: present if previously set. - In create request: optional - In update request: optional
- dimension_
value Sequence[StepDimension Value Entry Response] - If the execution containing this step has any dimension_definition set, then this field allows the child to specify the values of the dimensions. The keys must exactly match the dimension_definition of the execution. For example, if the execution has
dimension_definition = ['attempt', 'device']
then a step must define values for those dimensions, eg.dimension_value = ['attempt': '1', 'device': 'Nexus 6']
If a step does not participate in one dimension of the matrix, the value for that dimension should be empty string. For example, if one of the tests is executed by a runner which does not support retries, the step could havedimension_value = ['attempt': '', 'device': 'Nexus 6']
If the step does not participate in any dimensions of the matrix, it may leave dimension_value unset. A PRECONDITION_FAILED will be returned if any of the keys do not exist in the dimension_definition of the execution. A PRECONDITION_FAILED will be returned if another step in this execution already has the same name and dimension_value, but differs on other data fields, for example, step field is different. A PRECONDITION_FAILED will be returned if dimension_value is set, and there is a dimension_definition in the execution which is not specified as one of the keys. - In response: present if set by create - In create request: optional - In update request: never set - has_
images bool - Whether any of the outputs of this step are images whose thumbnails can be fetched with ListThumbnails. - In response: always set - In create/update request: never set
- labels
Sequence[Step
Labels Entry Response] - Arbitrary user-supplied key/value pairs that are associated with the step. Users are responsible for managing the key namespace such that keys don't accidentally collide. An INVALID_ARGUMENT will be returned if the number of labels exceeds 100 or if the length of any of the keys or values exceeds 100 characters. - In response: always set - In create request: optional - In update request: optional; any new key/value pair will be added to the map, and any new value for an existing key will update that key's value
- multi_
step MultiStep Response - Details when multiple steps are run with the same configuration as a group. These details can be used identify which group this step is part of. It also identifies the groups 'primary step' which indexes all the group members. - In response: present if previously set. - In create request: optional, set iff this step was performed more than once. - In update request: optional
- name str
- A short human-readable name to display in the UI. Maximum of 100 characters. For example: Clean build A PRECONDITION_FAILED will be returned upon creating a new step if it shares its name and dimension_value with an existing step. If two steps represent a similar action, but have different dimension values, they should share the same name. For instance, if the same set of tests is run on two different platforms, the two steps should have the same name. - In response: always set - In create request: always set - In update request: never set
- outcome
Outcome
Response - Classification of the result, for example into SUCCESS or FAILURE - In response: present if set by create/update request - In create/update request: optional
- run_
duration DurationResponse - How long it took for this step to run. If unset, this is set to the difference between creation_time and completion_time when the step is set to the COMPLETE state. In some cases, it is appropriate to set this value separately: For instance, if a step is created, but the operation it represents is queued for a few minutes before it executes, it would be appropriate not to include the time spent queued in its run_duration. PRECONDITION_FAILED will be returned if one attempts to set a run_duration on a step which already has this field set. - In response: present if previously set; always present on COMPLETE step - In create request: optional - In update request: optional
- state str
- The initial state is IN_PROGRESS. The only legal state transitions are * IN_PROGRESS -> COMPLETE A PRECONDITION_FAILED will be returned if an invalid transition is requested. It is valid to create Step with a state set to COMPLETE. The state can only be set to COMPLETE once. A PRECONDITION_FAILED will be returned if the state is set to COMPLETE multiple times. - In response: always set - In create/update request: optional
- step_
id str - A unique identifier within a Execution for this Step. Returns INVALID_ARGUMENT if this field is set or overwritten by the caller. - In response: always set - In create/update request: never set
- test_
execution_ Teststep Execution Step Response - An execution of a test runner.
- tool_
execution_ Toolstep Execution Step Response - An execution of a tool (used for steps we don't explicitly support).
- completion
Time Property Map - The time when the step status was set to complete. This value will be set automatically when state transitions to COMPLETE. - In response: set if the execution state is COMPLETE. - In create/update request: never set
- creation
Time Property Map - The time when the step was created. - In response: always set - In create/update request: never set
- description String
- A description of this tool For example: mvn clean package -D skipTests=true - In response: present if set by create/update request - In create/update request: optional
- device
Usage Property MapDuration - How much the device resource is used to perform the test. This is the device usage used for billing purpose, which is different from the run_duration, for example, infrastructure failure won't be charged for device usage. PRECONDITION_FAILED will be returned if one attempts to set a device_usage on a step which already has this field set. - In response: present if previously set. - In create request: optional - In update request: optional
- dimension
Value List<Property Map> - If the execution containing this step has any dimension_definition set, then this field allows the child to specify the values of the dimensions. The keys must exactly match the dimension_definition of the execution. For example, if the execution has
dimension_definition = ['attempt', 'device']
then a step must define values for those dimensions, eg.dimension_value = ['attempt': '1', 'device': 'Nexus 6']
If a step does not participate in one dimension of the matrix, the value for that dimension should be empty string. For example, if one of the tests is executed by a runner which does not support retries, the step could havedimension_value = ['attempt': '', 'device': 'Nexus 6']
If the step does not participate in any dimensions of the matrix, it may leave dimension_value unset. A PRECONDITION_FAILED will be returned if any of the keys do not exist in the dimension_definition of the execution. A PRECONDITION_FAILED will be returned if another step in this execution already has the same name and dimension_value, but differs on other data fields, for example, step field is different. A PRECONDITION_FAILED will be returned if dimension_value is set, and there is a dimension_definition in the execution which is not specified as one of the keys. - In response: present if set by create - In create request: optional - In update request: never set - has
Images Boolean - Whether any of the outputs of this step are images whose thumbnails can be fetched with ListThumbnails. - In response: always set - In create/update request: never set
- labels List<Property Map>
- Arbitrary user-supplied key/value pairs that are associated with the step. Users are responsible for managing the key namespace such that keys don't accidentally collide. An INVALID_ARGUMENT will be returned if the number of labels exceeds 100 or if the length of any of the keys or values exceeds 100 characters. - In response: always set - In create request: optional - In update request: optional; any new key/value pair will be added to the map, and any new value for an existing key will update that key's value
- multi
Step Property Map - Details when multiple steps are run with the same configuration as a group. These details can be used identify which group this step is part of. It also identifies the groups 'primary step' which indexes all the group members. - In response: present if previously set. - In create request: optional, set iff this step was performed more than once. - In update request: optional
- name String
- A short human-readable name to display in the UI. Maximum of 100 characters. For example: Clean build A PRECONDITION_FAILED will be returned upon creating a new step if it shares its name and dimension_value with an existing step. If two steps represent a similar action, but have different dimension values, they should share the same name. For instance, if the same set of tests is run on two different platforms, the two steps should have the same name. - In response: always set - In create request: always set - In update request: never set
- outcome Property Map
- Classification of the result, for example into SUCCESS or FAILURE - In response: present if set by create/update request - In create/update request: optional
- run
Duration Property Map - How long it took for this step to run. If unset, this is set to the difference between creation_time and completion_time when the step is set to the COMPLETE state. In some cases, it is appropriate to set this value separately: For instance, if a step is created, but the operation it represents is queued for a few minutes before it executes, it would be appropriate not to include the time spent queued in its run_duration. PRECONDITION_FAILED will be returned if one attempts to set a run_duration on a step which already has this field set. - In response: present if previously set; always present on COMPLETE step - In create request: optional - In update request: optional
- state String
- The initial state is IN_PROGRESS. The only legal state transitions are * IN_PROGRESS -> COMPLETE A PRECONDITION_FAILED will be returned if an invalid transition is requested. It is valid to create Step with a state set to COMPLETE. The state can only be set to COMPLETE once. A PRECONDITION_FAILED will be returned if the state is set to COMPLETE multiple times. - In response: always set - In create/update request: optional
- step
Id String - A unique identifier within a Execution for this Step. Returns INVALID_ARGUMENT if this field is set or overwritten by the caller. - In response: always set - In create/update request: never set
- test
Execution Property MapStep - An execution of a test runner.
- tool
Execution Property MapStep - An execution of a tool (used for steps we don't explicitly support).
Supporting Types
AnyResponse
- Type
Url string - A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the schemehttp
,https
, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided,https
is assumed. * An HTTP GET on the URL must yield a google.protobuf.Type value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other thanhttp
,https
(or the empty scheme) might be used with implementation specific semantics. - Value string
- Must be a valid serialized protocol buffer of the above specified type.
- Type
Url string - A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the schemehttp
,https
, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided,https
is assumed. * An HTTP GET on the URL must yield a google.protobuf.Type value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other thanhttp
,https
(or the empty scheme) might be used with implementation specific semantics. - Value string
- Must be a valid serialized protocol buffer of the above specified type.
- type
Url String - A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the schemehttp
,https
, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided,https
is assumed. * An HTTP GET on the URL must yield a google.protobuf.Type value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other thanhttp
,https
(or the empty scheme) might be used with implementation specific semantics. - value String
- Must be a valid serialized protocol buffer of the above specified type.
- type
Url string - A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the schemehttp
,https
, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided,https
is assumed. * An HTTP GET on the URL must yield a google.protobuf.Type value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other thanhttp
,https
(or the empty scheme) might be used with implementation specific semantics. - value string
- Must be a valid serialized protocol buffer of the above specified type.
- type_
url str - A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the schemehttp
,https
, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided,https
is assumed. * An HTTP GET on the URL must yield a google.protobuf.Type value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other thanhttp
,https
(or the empty scheme) might be used with implementation specific semantics. - value str
- Must be a valid serialized protocol buffer of the above specified type.
- type
Url String - A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in
path/google.protobuf.Duration
). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the schemehttp
,https
, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided,https
is assumed. * An HTTP GET on the URL must yield a google.protobuf.Type value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. Schemes other thanhttp
,https
(or the empty scheme) might be used with implementation specific semantics. - value String
- Must be a valid serialized protocol buffer of the above specified type.
DurationResponse
- Nanos int
- Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0
seconds
field and a positive or negativenanos
field. For durations of one second or more, a non-zero value for thenanos
field must be of the same sign as theseconds
field. Must be from -999,999,999 to +999,999,999 inclusive. - Seconds string
- Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
- Nanos int
- Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0
seconds
field and a positive or negativenanos
field. For durations of one second or more, a non-zero value for thenanos
field must be of the same sign as theseconds
field. Must be from -999,999,999 to +999,999,999 inclusive. - Seconds string
- Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
- nanos Integer
- Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0
seconds
field and a positive or negativenanos
field. For durations of one second or more, a non-zero value for thenanos
field must be of the same sign as theseconds
field. Must be from -999,999,999 to +999,999,999 inclusive. - seconds String
- Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
- nanos number
- Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0
seconds
field and a positive or negativenanos
field. For durations of one second or more, a non-zero value for thenanos
field must be of the same sign as theseconds
field. Must be from -999,999,999 to +999,999,999 inclusive. - seconds string
- Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
- nanos int
- Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0
seconds
field and a positive or negativenanos
field. For durations of one second or more, a non-zero value for thenanos
field must be of the same sign as theseconds
field. Must be from -999,999,999 to +999,999,999 inclusive. - seconds str
- Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
- nanos Number
- Signed fractions of a second at nanosecond resolution of the span of time. Durations less than one second are represented with a 0
seconds
field and a positive or negativenanos
field. For durations of one second or more, a non-zero value for thenanos
field must be of the same sign as theseconds
field. Must be from -999,999,999 to +999,999,999 inclusive. - seconds String
- Signed seconds of the span of time. Must be from -315,576,000,000 to +315,576,000,000 inclusive. Note: these bounds are computed from: 60 sec/min * 60 min/hr * 24 hr/day * 365.25 days/year * 10000 years
FailureDetailResponse
- Crashed bool
- If the failure was severe because the system (app) under test crashed.
- Device
Out boolOf Memory - If the device ran out of memory during a test, causing the test to crash.
- Failed
Roboscript bool - If the Roboscript failed to complete successfully, e.g., because a Roboscript action or assertion failed or a Roboscript action could not be matched during the entire crawl.
- Not
Installed bool - If an app is not installed and thus no test can be run with the app. This might be caused by trying to run a test on an unsupported platform.
- Other
Native boolCrash - If a native process (including any other than the app) crashed.
- Timed
Out bool - If the test overran some time limit, and that is why it failed.
- Unable
To boolCrawl - If the robo was unable to crawl the app; perhaps because the app did not start.
- Crashed bool
- If the failure was severe because the system (app) under test crashed.
- Device
Out boolOf Memory - If the device ran out of memory during a test, causing the test to crash.
- Failed
Roboscript bool - If the Roboscript failed to complete successfully, e.g., because a Roboscript action or assertion failed or a Roboscript action could not be matched during the entire crawl.
- Not
Installed bool - If an app is not installed and thus no test can be run with the app. This might be caused by trying to run a test on an unsupported platform.
- Other
Native boolCrash - If a native process (including any other than the app) crashed.
- Timed
Out bool - If the test overran some time limit, and that is why it failed.
- Unable
To boolCrawl - If the robo was unable to crawl the app; perhaps because the app did not start.
- crashed Boolean
- If the failure was severe because the system (app) under test crashed.
- device
Out BooleanOf Memory - If the device ran out of memory during a test, causing the test to crash.
- failed
Roboscript Boolean - If the Roboscript failed to complete successfully, e.g., because a Roboscript action or assertion failed or a Roboscript action could not be matched during the entire crawl.
- not
Installed Boolean - If an app is not installed and thus no test can be run with the app. This might be caused by trying to run a test on an unsupported platform.
- other
Native BooleanCrash - If a native process (including any other than the app) crashed.
- timed
Out Boolean - If the test overran some time limit, and that is why it failed.
- unable
To BooleanCrawl - If the robo was unable to crawl the app; perhaps because the app did not start.
- crashed boolean
- If the failure was severe because the system (app) under test crashed.
- device
Out booleanOf Memory - If the device ran out of memory during a test, causing the test to crash.
- failed
Roboscript boolean - If the Roboscript failed to complete successfully, e.g., because a Roboscript action or assertion failed or a Roboscript action could not be matched during the entire crawl.
- not
Installed boolean - If an app is not installed and thus no test can be run with the app. This might be caused by trying to run a test on an unsupported platform.
- other
Native booleanCrash - If a native process (including any other than the app) crashed.
- timed
Out boolean - If the test overran some time limit, and that is why it failed.
- unable
To booleanCrawl - If the robo was unable to crawl the app; perhaps because the app did not start.
- crashed bool
- If the failure was severe because the system (app) under test crashed.
- device_
out_ boolof_ memory - If the device ran out of memory during a test, causing the test to crash.
- failed_
roboscript bool - If the Roboscript failed to complete successfully, e.g., because a Roboscript action or assertion failed or a Roboscript action could not be matched during the entire crawl.
- not_
installed bool - If an app is not installed and thus no test can be run with the app. This might be caused by trying to run a test on an unsupported platform.
- other_
native_ boolcrash - If a native process (including any other than the app) crashed.
- timed_
out bool - If the test overran some time limit, and that is why it failed.
- unable_
to_ boolcrawl - If the robo was unable to crawl the app; perhaps because the app did not start.
- crashed Boolean
- If the failure was severe because the system (app) under test crashed.
- device
Out BooleanOf Memory - If the device ran out of memory during a test, causing the test to crash.
- failed
Roboscript Boolean - If the Roboscript failed to complete successfully, e.g., because a Roboscript action or assertion failed or a Roboscript action could not be matched during the entire crawl.
- not
Installed Boolean - If an app is not installed and thus no test can be run with the app. This might be caused by trying to run a test on an unsupported platform.
- other
Native BooleanCrash - If a native process (including any other than the app) crashed.
- timed
Out Boolean - If the test overran some time limit, and that is why it failed.
- unable
To BooleanCrawl - If the robo was unable to crawl the app; perhaps because the app did not start.
FileReferenceResponse
- File
Uri string - The URI of a file stored in Google Cloud Storage. For example: http://storage.googleapis.com/mybucket/path/to/test.xml or in gsutil format: gs://mybucket/path/to/test.xml with version-specific info, gs://mybucket/path/to/test.xml#1360383693690000 An INVALID_ARGUMENT error will be returned if the URI format is not supported. - In response: always set - In create/update request: always set
- File
Uri string - The URI of a file stored in Google Cloud Storage. For example: http://storage.googleapis.com/mybucket/path/to/test.xml or in gsutil format: gs://mybucket/path/to/test.xml with version-specific info, gs://mybucket/path/to/test.xml#1360383693690000 An INVALID_ARGUMENT error will be returned if the URI format is not supported. - In response: always set - In create/update request: always set
- file
Uri String - The URI of a file stored in Google Cloud Storage. For example: http://storage.googleapis.com/mybucket/path/to/test.xml or in gsutil format: gs://mybucket/path/to/test.xml with version-specific info, gs://mybucket/path/to/test.xml#1360383693690000 An INVALID_ARGUMENT error will be returned if the URI format is not supported. - In response: always set - In create/update request: always set
- file
Uri string - The URI of a file stored in Google Cloud Storage. For example: http://storage.googleapis.com/mybucket/path/to/test.xml or in gsutil format: gs://mybucket/path/to/test.xml with version-specific info, gs://mybucket/path/to/test.xml#1360383693690000 An INVALID_ARGUMENT error will be returned if the URI format is not supported. - In response: always set - In create/update request: always set
- file_
uri str - The URI of a file stored in Google Cloud Storage. For example: http://storage.googleapis.com/mybucket/path/to/test.xml or in gsutil format: gs://mybucket/path/to/test.xml with version-specific info, gs://mybucket/path/to/test.xml#1360383693690000 An INVALID_ARGUMENT error will be returned if the URI format is not supported. - In response: always set - In create/update request: always set
- file
Uri String - The URI of a file stored in Google Cloud Storage. For example: http://storage.googleapis.com/mybucket/path/to/test.xml or in gsutil format: gs://mybucket/path/to/test.xml with version-specific info, gs://mybucket/path/to/test.xml#1360383693690000 An INVALID_ARGUMENT error will be returned if the URI format is not supported. - In response: always set - In create/update request: always set
InconclusiveDetailResponse
- Aborted
By boolUser - 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.
- Has
Error boolLogs - If results are being provided to the user in certain cases of infrastructure failures
- Infrastructure
Failure bool - 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.
- Aborted
By boolUser - 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.
- Has
Error boolLogs - If results are being provided to the user in certain cases of infrastructure failures
- Infrastructure
Failure bool - 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.
- aborted
By BooleanUser - 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.
- has
Error BooleanLogs - If results are being provided to the user in certain cases of infrastructure failures
- infrastructure
Failure Boolean - 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.
- aborted
By booleanUser - 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.
- has
Error booleanLogs - If results are being provided to the user in certain cases of infrastructure failures
- infrastructure
Failure boolean - 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.
- aborted_
by_ booluser - 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.
- has_
error_ boollogs - If results are being provided to the user in certain cases of infrastructure failures
- infrastructure_
failure bool - 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.
- aborted
By BooleanUser - 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.
- has
Error BooleanLogs - If results are being provided to the user in certain cases of infrastructure failures
- infrastructure
Failure Boolean - 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.
IndividualOutcomeResponse
- Multistep
Number int - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- Outcome
Summary string - Run
Duration Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Duration Response - How long it took for this step to run.
- Step
Id string
- Multistep
Number int - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- Outcome
Summary string - Run
Duration DurationResponse - How long it took for this step to run.
- Step
Id string
- multistep
Number Integer - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- outcome
Summary String - run
Duration DurationResponse - How long it took for this step to run.
- step
Id String
- multistep
Number number - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- outcome
Summary string - run
Duration DurationResponse - How long it took for this step to run.
- step
Id string
- multistep_
number int - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- outcome_
summary str - run_
duration DurationResponse - How long it took for this step to run.
- step_
id str
- multistep
Number Number - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- outcome
Summary String - run
Duration Property Map - How long it took for this step to run.
- step
Id String
MultiStepResponse
- Multistep
Number int - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- Primary
Step Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Primary Step Response - Present if it is a primary (original) step.
- Primary
Step stringId - Step Id of the primary (original) step, which might be this step.
- Multistep
Number int - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- Primary
Step PrimaryStep Response - Present if it is a primary (original) step.
- Primary
Step stringId - Step Id of the primary (original) step, which might be this step.
- multistep
Number Integer - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- primary
Step PrimaryStep Response - Present if it is a primary (original) step.
- primary
Step StringId - Step Id of the primary (original) step, which might be this step.
- multistep
Number number - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- primary
Step PrimaryStep Response - Present if it is a primary (original) step.
- primary
Step stringId - Step Id of the primary (original) step, which might be this step.
- multistep_
number int - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- primary_
step PrimaryStep Response - Present if it is a primary (original) step.
- primary_
step_ strid - Step Id of the primary (original) step, which might be this step.
- multistep
Number Number - Unique int given to each step. Ranges from 0(inclusive) to total number of steps(exclusive). The primary step is 0.
- primary
Step Property Map - Present if it is a primary (original) step.
- primary
Step StringId - Step Id of the primary (original) step, which might be this step.
OutcomeResponse
- Failure
Detail Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Failure Detail Response - More information about a FAILURE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not FAILURE. Optional
- Inconclusive
Detail Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Inconclusive Detail Response - More information about an INCONCLUSIVE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not INCONCLUSIVE. Optional
- Skipped
Detail Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Skipped Detail Response - More information about a SKIPPED outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SKIPPED. Optional
- Success
Detail Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Success Detail Response - More information about a SUCCESS outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SUCCESS. Optional
- Summary string
- The simplest way to interpret a result. Required
- Failure
Detail FailureDetail Response - More information about a FAILURE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not FAILURE. Optional
- Inconclusive
Detail InconclusiveDetail Response - More information about an INCONCLUSIVE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not INCONCLUSIVE. Optional
- Skipped
Detail SkippedDetail Response - More information about a SKIPPED outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SKIPPED. Optional
- Success
Detail SuccessDetail Response - More information about a SUCCESS outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SUCCESS. Optional
- Summary string
- The simplest way to interpret a result. Required
- failure
Detail FailureDetail Response - More information about a FAILURE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not FAILURE. Optional
- inconclusive
Detail InconclusiveDetail Response - More information about an INCONCLUSIVE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not INCONCLUSIVE. Optional
- skipped
Detail SkippedDetail Response - More information about a SKIPPED outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SKIPPED. Optional
- success
Detail SuccessDetail Response - More information about a SUCCESS outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SUCCESS. Optional
- summary String
- The simplest way to interpret a result. Required
- failure
Detail FailureDetail Response - More information about a FAILURE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not FAILURE. Optional
- inconclusive
Detail InconclusiveDetail Response - More information about an INCONCLUSIVE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not INCONCLUSIVE. Optional
- skipped
Detail SkippedDetail Response - More information about a SKIPPED outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SKIPPED. Optional
- success
Detail SuccessDetail Response - More information about a SUCCESS outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SUCCESS. Optional
- summary string
- The simplest way to interpret a result. Required
- failure_
detail FailureDetail Response - More information about a FAILURE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not FAILURE. Optional
- inconclusive_
detail InconclusiveDetail Response - More information about an INCONCLUSIVE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not INCONCLUSIVE. Optional
- skipped_
detail SkippedDetail Response - More information about a SKIPPED outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SKIPPED. Optional
- success_
detail SuccessDetail Response - More information about a SUCCESS outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SUCCESS. Optional
- summary str
- The simplest way to interpret a result. Required
- failure
Detail Property Map - More information about a FAILURE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not FAILURE. Optional
- inconclusive
Detail Property Map - More information about an INCONCLUSIVE outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not INCONCLUSIVE. Optional
- skipped
Detail Property Map - More information about a SKIPPED outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SKIPPED. Optional
- success
Detail Property Map - More information about a SUCCESS outcome. Returns INVALID_ARGUMENT if this field is set but the summary is not SUCCESS. Optional
- summary String
- The simplest way to interpret a result. Required
PrimaryStepResponse
- Individual
Outcome List<Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Individual Outcome Response> - Step Id and outcome of each individual step.
- Roll
Up string - Rollup test status of multiple steps that were run with the same configuration as a group.
- Individual
Outcome []IndividualOutcome Response - Step Id and outcome of each individual step.
- Roll
Up string - Rollup test status of multiple steps that were run with the same configuration as a group.
- individual
Outcome List<IndividualOutcome Response> - Step Id and outcome of each individual step.
- roll
Up String - Rollup test status of multiple steps that were run with the same configuration as a group.
- individual
Outcome IndividualOutcome Response[] - Step Id and outcome of each individual step.
- roll
Up string - Rollup test status of multiple steps that were run with the same configuration as a group.
- individual_
outcome Sequence[IndividualOutcome Response] - Step Id and outcome of each individual step.
- roll_
up str - Rollup test status of multiple steps that were run with the same configuration as a group.
- individual
Outcome List<Property Map> - Step Id and outcome of each individual step.
- roll
Up String - Rollup test status of multiple steps that were run with the same configuration as a group.
SkippedDetailResponse
- Incompatible
App boolVersion - If the App doesn't support the specific API level.
- Incompatible
Architecture bool - If the App doesn't run on the specific architecture, for example, x86.
- Incompatible
Device bool - If the requested OS version doesn't run on the specific device model.
- Incompatible
App boolVersion - If the App doesn't support the specific API level.
- Incompatible
Architecture bool - If the App doesn't run on the specific architecture, for example, x86.
- Incompatible
Device bool - If the requested OS version doesn't run on the specific device model.
- incompatible
App BooleanVersion - If the App doesn't support the specific API level.
- incompatible
Architecture Boolean - If the App doesn't run on the specific architecture, for example, x86.
- incompatible
Device Boolean - If the requested OS version doesn't run on the specific device model.
- incompatible
App booleanVersion - If the App doesn't support the specific API level.
- incompatible
Architecture boolean - If the App doesn't run on the specific architecture, for example, x86.
- incompatible
Device boolean - If the requested OS version doesn't run on the specific device model.
- incompatible_
app_ boolversion - If the App doesn't support the specific API level.
- incompatible_
architecture bool - If the App doesn't run on the specific architecture, for example, x86.
- incompatible_
device bool - If the requested OS version doesn't run on the specific device model.
- incompatible
App BooleanVersion - If the App doesn't support the specific API level.
- incompatible
Architecture Boolean - If the App doesn't run on the specific architecture, for example, x86.
- incompatible
Device Boolean - If the requested OS version doesn't run on the specific device model.
StackTraceResponse
- Exception string
- The stack trace message. Required
- Exception string
- The stack trace message. Required
- exception String
- The stack trace message. Required
- exception string
- The stack trace message. Required
- exception str
- The stack trace message. Required
- exception String
- The stack trace message. Required
StepDimensionValueEntryResponse
StepLabelsEntryResponse
SuccessDetailResponse
- Other
Native boolCrash - If a native process other than the app crashed.
- Other
Native boolCrash - If a native process other than the app crashed.
- other
Native BooleanCrash - If a native process other than the app crashed.
- other
Native booleanCrash - If a native process other than the app crashed.
- other_
native_ boolcrash - If a native process other than the app crashed.
- other
Native BooleanCrash - If a native process other than the app crashed.
TestCaseReferenceResponse
- Class
Name string - The name of the class.
- Name string
- The name of the test case. Required.
- Test
Suite stringName - The name of the test suite to which this test case belongs.
- Class
Name string - The name of the class.
- Name string
- The name of the test case. Required.
- Test
Suite stringName - The name of the test suite to which this test case belongs.
- class
Name String - The name of the class.
- name String
- The name of the test case. Required.
- test
Suite StringName - The name of the test suite to which this test case belongs.
- class
Name string - The name of the class.
- name string
- The name of the test case. Required.
- test
Suite stringName - The name of the test suite to which this test case belongs.
- class_
name str - The name of the class.
- name str
- The name of the test case. Required.
- test_
suite_ strname - The name of the test suite to which this test case belongs.
- class
Name String - The name of the class.
- name String
- The name of the test case. Required.
- test
Suite StringName - The name of the test suite to which this test case belongs.
TestExecutionStepResponse
- Test
Issues List<Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Test Issue Response> - Issues observed during the test execution. For example, if the mobile app under test crashed during the test, the error message and the stack trace content can be recorded here to assist debugging. - In response: present if set by create or update - In create/update request: optional
- Test
Suite List<Pulumi.Overviews Google Native. Tool Results. V1Beta3. Inputs. Test Suite Overview Response> - List of test suite overview contents. This could be parsed from xUnit XML log by server, or uploaded directly by user. This references should only be called when test suites are fully parsed or uploaded. The maximum allowed number of test suite overviews per step is 1000. - In response: always set - In create request: optional - In update request: never (use publishXunitXmlFiles custom method instead)
- Test
Timing Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Test Timing Response - The timing break down of the test execution. - In response: present if set by create or update - In create/update request: optional
- Tool
Execution Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Tool Execution Response - Represents the execution of the test runner. The exit code of this tool will be used to determine if the test passed. - In response: always set - In create/update request: optional
- Test
Issues []TestIssue Response - Issues observed during the test execution. For example, if the mobile app under test crashed during the test, the error message and the stack trace content can be recorded here to assist debugging. - In response: present if set by create or update - In create/update request: optional
- Test
Suite []TestOverviews Suite Overview Response - List of test suite overview contents. This could be parsed from xUnit XML log by server, or uploaded directly by user. This references should only be called when test suites are fully parsed or uploaded. The maximum allowed number of test suite overviews per step is 1000. - In response: always set - In create request: optional - In update request: never (use publishXunitXmlFiles custom method instead)
- Test
Timing TestTiming Response - The timing break down of the test execution. - In response: present if set by create or update - In create/update request: optional
- Tool
Execution ToolExecution Response - Represents the execution of the test runner. The exit code of this tool will be used to determine if the test passed. - In response: always set - In create/update request: optional
- test
Issues List<TestIssue Response> - Issues observed during the test execution. For example, if the mobile app under test crashed during the test, the error message and the stack trace content can be recorded here to assist debugging. - In response: present if set by create or update - In create/update request: optional
- test
Suite List<TestOverviews Suite Overview Response> - List of test suite overview contents. This could be parsed from xUnit XML log by server, or uploaded directly by user. This references should only be called when test suites are fully parsed or uploaded. The maximum allowed number of test suite overviews per step is 1000. - In response: always set - In create request: optional - In update request: never (use publishXunitXmlFiles custom method instead)
- test
Timing TestTiming Response - The timing break down of the test execution. - In response: present if set by create or update - In create/update request: optional
- tool
Execution ToolExecution Response - Represents the execution of the test runner. The exit code of this tool will be used to determine if the test passed. - In response: always set - In create/update request: optional
- test
Issues TestIssue Response[] - Issues observed during the test execution. For example, if the mobile app under test crashed during the test, the error message and the stack trace content can be recorded here to assist debugging. - In response: present if set by create or update - In create/update request: optional
- test
Suite TestOverviews Suite Overview Response[] - List of test suite overview contents. This could be parsed from xUnit XML log by server, or uploaded directly by user. This references should only be called when test suites are fully parsed or uploaded. The maximum allowed number of test suite overviews per step is 1000. - In response: always set - In create request: optional - In update request: never (use publishXunitXmlFiles custom method instead)
- test
Timing TestTiming Response - The timing break down of the test execution. - In response: present if set by create or update - In create/update request: optional
- tool
Execution ToolExecution Response - Represents the execution of the test runner. The exit code of this tool will be used to determine if the test passed. - In response: always set - In create/update request: optional
- test_
issues Sequence[TestIssue Response] - Issues observed during the test execution. For example, if the mobile app under test crashed during the test, the error message and the stack trace content can be recorded here to assist debugging. - In response: present if set by create or update - In create/update request: optional
- test_
suite_ Sequence[Testoverviews Suite Overview Response] - List of test suite overview contents. This could be parsed from xUnit XML log by server, or uploaded directly by user. This references should only be called when test suites are fully parsed or uploaded. The maximum allowed number of test suite overviews per step is 1000. - In response: always set - In create request: optional - In update request: never (use publishXunitXmlFiles custom method instead)
- test_
timing TestTiming Response - The timing break down of the test execution. - In response: present if set by create or update - In create/update request: optional
- tool_
execution ToolExecution Response - Represents the execution of the test runner. The exit code of this tool will be used to determine if the test passed. - In response: always set - In create/update request: optional
- test
Issues List<Property Map> - Issues observed during the test execution. For example, if the mobile app under test crashed during the test, the error message and the stack trace content can be recorded here to assist debugging. - In response: present if set by create or update - In create/update request: optional
- test
Suite List<Property Map>Overviews - List of test suite overview contents. This could be parsed from xUnit XML log by server, or uploaded directly by user. This references should only be called when test suites are fully parsed or uploaded. The maximum allowed number of test suite overviews per step is 1000. - In response: always set - In create request: optional - In update request: never (use publishXunitXmlFiles custom method instead)
- test
Timing Property Map - The timing break down of the test execution. - In response: present if set by create or update - In create/update request: optional
- tool
Execution Property Map - Represents the execution of the test runner. The exit code of this tool will be used to determine if the test passed. - In response: always set - In create/update request: optional
TestIssueResponse
- Category string
- Category of issue. Required.
- Error
Message string - A brief human-readable message describing the issue. Required.
- Severity string
- Severity of issue. Required.
- Stack
Trace Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Stack Trace Response - Deprecated in favor of stack trace fields inside specific warnings.
- Type string
- Type of issue. Required.
- Warning
Pulumi.
Google Native. Tool Results. V1Beta3. Inputs. Any Response - Warning message with additional details of the issue. Should always be a message from com.google.devtools.toolresults.v1.warnings
- Category string
- Category of issue. Required.
- Error
Message string - A brief human-readable message describing the issue. Required.
- Severity string
- Severity of issue. Required.
- Stack
Trace StackTrace Response - Deprecated in favor of stack trace fields inside specific warnings.
- Type string
- Type of issue. Required.
- Warning
Any
Response - Warning message with additional details of the issue. Should always be a message from com.google.devtools.toolresults.v1.warnings
- category String
- Category of issue. Required.
- error
Message String - A brief human-readable message describing the issue. Required.
- severity String
- Severity of issue. Required.
- stack
Trace StackTrace Response - Deprecated in favor of stack trace fields inside specific warnings.
- type String
- Type of issue. Required.
- warning
Any
Response - Warning message with additional details of the issue. Should always be a message from com.google.devtools.toolresults.v1.warnings
- category string
- Category of issue. Required.
- error
Message string - A brief human-readable message describing the issue. Required.
- severity string
- Severity of issue. Required.
- stack
Trace StackTrace Response - Deprecated in favor of stack trace fields inside specific warnings.
- type string
- Type of issue. Required.
- warning
Any
Response - Warning message with additional details of the issue. Should always be a message from com.google.devtools.toolresults.v1.warnings
- category str
- Category of issue. Required.
- error_
message str - A brief human-readable message describing the issue. Required.
- severity str
- Severity of issue. Required.
- stack_
trace StackTrace Response - Deprecated in favor of stack trace fields inside specific warnings.
- type str
- Type of issue. Required.
- warning
Any
Response - Warning message with additional details of the issue. Should always be a message from com.google.devtools.toolresults.v1.warnings
- category String
- Category of issue. Required.
- error
Message String - A brief human-readable message describing the issue. Required.
- severity String
- Severity of issue. Required.
- stack
Trace Property Map - Deprecated in favor of stack trace fields inside specific warnings.
- type String
- Type of issue. Required.
- warning Property Map
- Warning message with additional details of the issue. Should always be a message from com.google.devtools.toolresults.v1.warnings
TestSuiteOverviewResponse
- Elapsed
Time Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Duration Response - Elapsed time of test suite.
- Error
Count int - Number of test cases in error, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- Failure
Count int - Number of failed test cases, typically set by the service by parsing the xml_source. May also be set by the user. - In create/response: always set - In update request: never
- Flaky
Count int - Number of flaky test cases, set by the service by rolling up flaky test attempts. Present only for rollup test suite overview at environment level. A step cannot have flaky test cases.
- Name string
- The name of the test suite. - In create/response: always set - In update request: never
- Skipped
Count int - Number of test cases not run, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- Total
Count int - Number of test cases, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- Xml
Source Pulumi.Google Native. Tool Results. V1Beta3. Inputs. File Reference Response - If this test suite was parsed from XML, this is the URI where the original XML file is stored. Note: Multiple test suites can share the same xml_source Returns INVALID_ARGUMENT if the uri format is not supported. - In create/response: optional - In update request: never
- Elapsed
Time DurationResponse - Elapsed time of test suite.
- Error
Count int - Number of test cases in error, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- Failure
Count int - Number of failed test cases, typically set by the service by parsing the xml_source. May also be set by the user. - In create/response: always set - In update request: never
- Flaky
Count int - Number of flaky test cases, set by the service by rolling up flaky test attempts. Present only for rollup test suite overview at environment level. A step cannot have flaky test cases.
- Name string
- The name of the test suite. - In create/response: always set - In update request: never
- Skipped
Count int - Number of test cases not run, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- Total
Count int - Number of test cases, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- Xml
Source FileReference Response - If this test suite was parsed from XML, this is the URI where the original XML file is stored. Note: Multiple test suites can share the same xml_source Returns INVALID_ARGUMENT if the uri format is not supported. - In create/response: optional - In update request: never
- elapsed
Time DurationResponse - Elapsed time of test suite.
- error
Count Integer - Number of test cases in error, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- failure
Count Integer - Number of failed test cases, typically set by the service by parsing the xml_source. May also be set by the user. - In create/response: always set - In update request: never
- flaky
Count Integer - Number of flaky test cases, set by the service by rolling up flaky test attempts. Present only for rollup test suite overview at environment level. A step cannot have flaky test cases.
- name String
- The name of the test suite. - In create/response: always set - In update request: never
- skipped
Count Integer - Number of test cases not run, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- total
Count Integer - Number of test cases, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- xml
Source FileReference Response - If this test suite was parsed from XML, this is the URI where the original XML file is stored. Note: Multiple test suites can share the same xml_source Returns INVALID_ARGUMENT if the uri format is not supported. - In create/response: optional - In update request: never
- elapsed
Time DurationResponse - Elapsed time of test suite.
- error
Count number - Number of test cases in error, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- failure
Count number - Number of failed test cases, typically set by the service by parsing the xml_source. May also be set by the user. - In create/response: always set - In update request: never
- flaky
Count number - Number of flaky test cases, set by the service by rolling up flaky test attempts. Present only for rollup test suite overview at environment level. A step cannot have flaky test cases.
- name string
- The name of the test suite. - In create/response: always set - In update request: never
- skipped
Count number - Number of test cases not run, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- total
Count number - Number of test cases, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- xml
Source FileReference Response - If this test suite was parsed from XML, this is the URI where the original XML file is stored. Note: Multiple test suites can share the same xml_source Returns INVALID_ARGUMENT if the uri format is not supported. - In create/response: optional - In update request: never
- elapsed_
time DurationResponse - Elapsed time of test suite.
- error_
count int - Number of test cases in error, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- failure_
count int - Number of failed test cases, typically set by the service by parsing the xml_source. May also be set by the user. - In create/response: always set - In update request: never
- flaky_
count int - Number of flaky test cases, set by the service by rolling up flaky test attempts. Present only for rollup test suite overview at environment level. A step cannot have flaky test cases.
- name str
- The name of the test suite. - In create/response: always set - In update request: never
- skipped_
count int - Number of test cases not run, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- total_
count int - Number of test cases, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- xml_
source FileReference Response - If this test suite was parsed from XML, this is the URI where the original XML file is stored. Note: Multiple test suites can share the same xml_source Returns INVALID_ARGUMENT if the uri format is not supported. - In create/response: optional - In update request: never
- elapsed
Time Property Map - Elapsed time of test suite.
- error
Count Number - Number of test cases in error, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- failure
Count Number - Number of failed test cases, typically set by the service by parsing the xml_source. May also be set by the user. - In create/response: always set - In update request: never
- flaky
Count Number - Number of flaky test cases, set by the service by rolling up flaky test attempts. Present only for rollup test suite overview at environment level. A step cannot have flaky test cases.
- name String
- The name of the test suite. - In create/response: always set - In update request: never
- skipped
Count Number - Number of test cases not run, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- total
Count Number - Number of test cases, typically set by the service by parsing the xml_source. - In create/response: always set - In update request: never
- xml
Source Property Map - If this test suite was parsed from XML, this is the URI where the original XML file is stored. Note: Multiple test suites can share the same xml_source Returns INVALID_ARGUMENT if the uri format is not supported. - In create/response: optional - In update request: never
TestTimingResponse
- Test
Process Pulumi.Duration Google Native. Tool Results. V1Beta3. Inputs. Duration Response - How long it took to run the test process. - In response: present if previously set. - In create/update request: optional
- Test
Process DurationDuration Response - How long it took to run the test process. - In response: present if previously set. - In create/update request: optional
- test
Process DurationDuration Response - How long it took to run the test process. - In response: present if previously set. - In create/update request: optional
- test
Process DurationDuration Response - How long it took to run the test process. - In response: present if previously set. - In create/update request: optional
- test_
process_ Durationduration Response - How long it took to run the test process. - In response: present if previously set. - In create/update request: optional
- test
Process Property MapDuration - How long it took to run the test process. - In response: present if previously set. - In create/update request: optional
TimestampResponse
- Nanos int
- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.
- Seconds string
- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
- Nanos int
- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.
- Seconds string
- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
- nanos Integer
- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.
- seconds String
- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
- nanos number
- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.
- seconds string
- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
- nanos int
- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.
- seconds str
- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
- nanos Number
- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.
- seconds String
- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
ToolExecutionResponse
- Command
Line List<string>Arguments - The full tokenized command line including the program name (equivalent to argv in a C program). - In response: present if set by create request - In create request: optional - In update request: never set
- Exit
Code Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Tool Exit Code Response - Tool execution exit code. This field will be set once the tool has exited. - In response: present if set by create/update request - In create request: optional - In update request: optional, a FAILED_PRECONDITION error will be returned if an exit_code is already set.
- Tool
Logs List<Pulumi.Google Native. Tool Results. V1Beta3. Inputs. File Reference Response> - References to any plain text logs output the tool execution. This field can be set before the tool has exited in order to be able to have access to a live view of the logs while the tool is running. The maximum allowed number of tool logs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- Tool
Outputs List<Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Tool Output Reference Response> - References to opaque files of any format output by the tool execution. The maximum allowed number of tool outputs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- Command
Line []stringArguments - The full tokenized command line including the program name (equivalent to argv in a C program). - In response: present if set by create request - In create request: optional - In update request: never set
- Exit
Code ToolExit Code Response - Tool execution exit code. This field will be set once the tool has exited. - In response: present if set by create/update request - In create request: optional - In update request: optional, a FAILED_PRECONDITION error will be returned if an exit_code is already set.
- Tool
Logs []FileReference Response - References to any plain text logs output the tool execution. This field can be set before the tool has exited in order to be able to have access to a live view of the logs while the tool is running. The maximum allowed number of tool logs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- Tool
Outputs []ToolOutput Reference Response - References to opaque files of any format output by the tool execution. The maximum allowed number of tool outputs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- command
Line List<String>Arguments - The full tokenized command line including the program name (equivalent to argv in a C program). - In response: present if set by create request - In create request: optional - In update request: never set
- exit
Code ToolExit Code Response - Tool execution exit code. This field will be set once the tool has exited. - In response: present if set by create/update request - In create request: optional - In update request: optional, a FAILED_PRECONDITION error will be returned if an exit_code is already set.
- tool
Logs List<FileReference Response> - References to any plain text logs output the tool execution. This field can be set before the tool has exited in order to be able to have access to a live view of the logs while the tool is running. The maximum allowed number of tool logs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- tool
Outputs List<ToolOutput Reference Response> - References to opaque files of any format output by the tool execution. The maximum allowed number of tool outputs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- command
Line string[]Arguments - The full tokenized command line including the program name (equivalent to argv in a C program). - In response: present if set by create request - In create request: optional - In update request: never set
- exit
Code ToolExit Code Response - Tool execution exit code. This field will be set once the tool has exited. - In response: present if set by create/update request - In create request: optional - In update request: optional, a FAILED_PRECONDITION error will be returned if an exit_code is already set.
- tool
Logs FileReference Response[] - References to any plain text logs output the tool execution. This field can be set before the tool has exited in order to be able to have access to a live view of the logs while the tool is running. The maximum allowed number of tool logs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- tool
Outputs ToolOutput Reference Response[] - References to opaque files of any format output by the tool execution. The maximum allowed number of tool outputs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- command_
line_ Sequence[str]arguments - The full tokenized command line including the program name (equivalent to argv in a C program). - In response: present if set by create request - In create request: optional - In update request: never set
- exit_
code ToolExit Code Response - Tool execution exit code. This field will be set once the tool has exited. - In response: present if set by create/update request - In create request: optional - In update request: optional, a FAILED_PRECONDITION error will be returned if an exit_code is already set.
- tool_
logs Sequence[FileReference Response] - References to any plain text logs output the tool execution. This field can be set before the tool has exited in order to be able to have access to a live view of the logs while the tool is running. The maximum allowed number of tool logs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- tool_
outputs Sequence[ToolOutput Reference Response] - References to opaque files of any format output by the tool execution. The maximum allowed number of tool outputs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- command
Line List<String>Arguments - The full tokenized command line including the program name (equivalent to argv in a C program). - In response: present if set by create request - In create request: optional - In update request: never set
- exit
Code Property Map - Tool execution exit code. This field will be set once the tool has exited. - In response: present if set by create/update request - In create request: optional - In update request: optional, a FAILED_PRECONDITION error will be returned if an exit_code is already set.
- tool
Logs List<Property Map> - References to any plain text logs output the tool execution. This field can be set before the tool has exited in order to be able to have access to a live view of the logs while the tool is running. The maximum allowed number of tool logs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
- tool
Outputs List<Property Map> - References to opaque files of any format output by the tool execution. The maximum allowed number of tool outputs per step is 1000. - In response: present if set by create/update request - In create request: optional - In update request: optional, any value provided will be appended to the existing list
ToolExecutionStepResponse
- Tool
Execution Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Tool Execution Response - A Tool execution. - In response: present if set by create/update request - In create/update request: optional
- Tool
Execution ToolExecution Response - A Tool execution. - In response: present if set by create/update request - In create/update request: optional
- tool
Execution ToolExecution Response - A Tool execution. - In response: present if set by create/update request - In create/update request: optional
- tool
Execution ToolExecution Response - A Tool execution. - In response: present if set by create/update request - In create/update request: optional
- tool_
execution ToolExecution Response - A Tool execution. - In response: present if set by create/update request - In create/update request: optional
- tool
Execution Property Map - A Tool execution. - In response: present if set by create/update request - In create/update request: optional
ToolExitCodeResponse
- Number int
- Tool execution exit code. A value of 0 means that the execution was successful. - In response: always set - In create/update request: always set
- Number int
- Tool execution exit code. A value of 0 means that the execution was successful. - In response: always set - In create/update request: always set
- number Integer
- Tool execution exit code. A value of 0 means that the execution was successful. - In response: always set - In create/update request: always set
- number number
- Tool execution exit code. A value of 0 means that the execution was successful. - In response: always set - In create/update request: always set
- number int
- Tool execution exit code. A value of 0 means that the execution was successful. - In response: always set - In create/update request: always set
- number Number
- Tool execution exit code. A value of 0 means that the execution was successful. - In response: always set - In create/update request: always set
ToolOutputReferenceResponse
- Creation
Time Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Timestamp Response - The creation time of the file. - In response: present if set by create/update request - In create/update request: optional
- Output
Pulumi.
Google Native. Tool Results. V1Beta3. Inputs. File Reference Response - A FileReference to an output file. - In response: always set - In create/update request: always set
- Test
Case Pulumi.Google Native. Tool Results. V1Beta3. Inputs. Test Case Reference Response - The test case to which this output file belongs. - In response: present if set by create/update request - In create/update request: optional
- Creation
Time TimestampResponse - The creation time of the file. - In response: present if set by create/update request - In create/update request: optional
- Output
File
Reference Response - A FileReference to an output file. - In response: always set - In create/update request: always set
- Test
Case TestCase Reference Response - The test case to which this output file belongs. - In response: present if set by create/update request - In create/update request: optional
- creation
Time TimestampResponse - The creation time of the file. - In response: present if set by create/update request - In create/update request: optional
- output
File
Reference Response - A FileReference to an output file. - In response: always set - In create/update request: always set
- test
Case TestCase Reference Response - The test case to which this output file belongs. - In response: present if set by create/update request - In create/update request: optional
- creation
Time TimestampResponse - The creation time of the file. - In response: present if set by create/update request - In create/update request: optional
- output
File
Reference Response - A FileReference to an output file. - In response: always set - In create/update request: always set
- test
Case TestCase Reference Response - The test case to which this output file belongs. - In response: present if set by create/update request - In create/update request: optional
- creation_
time TimestampResponse - The creation time of the file. - In response: present if set by create/update request - In create/update request: optional
- output
File
Reference Response - A FileReference to an output file. - In response: always set - In create/update request: always set
- test_
case TestCase Reference Response - The test case to which this output file belongs. - In response: present if set by create/update request - In create/update request: optional
- creation
Time Property Map - The creation time of the file. - In response: present if set by create/update request - In create/update request: optional
- output Property Map
- A FileReference to an output file. - In response: always set - In create/update request: always set
- test
Case Property Map - The test case to which this output file belongs. - In response: present if set by create/update request - In create/update request: optional
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.