Skip to main content

test_cases

Overview

Nametest_cases
TypeResource
Idfirebase.toolresults.test_cases

Fields

NameDatatypeDescription
elapsedTimeobjectA Duration represents a signed, fixed-length span of time represented as a count of seconds and fractions of seconds at nanosecond resolution. It is independent of any calendar and concepts like "day" or "month". It is related to Timestamp in that the difference between two Timestamp values is a Duration and it can be added or subtracted from a Timestamp. Range is approximately +-10,000 years.
startTimeobjectA Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear. The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
endTimeobjectA Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear. The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
statusstringThe status of the test case. Required.
testCaseIdstringA unique identifier within a Step for this Test Case.
testCaseReferenceobjectA reference to a test case. Test case references are canonically ordered lexicographically by these three factors: First, by test_suite_name. Second, by class_name. * Third, by name.
skippedMessagestringWhy the test case was skipped. Present only for skipped test case
stackTracesarrayThe stack trace details if the test case failed or encountered an error. The maximum size of the stack traces is 100KiB, beyond which the stack track will be truncated. Zero if the test case passed.
toolOutputsarrayReferences to opaque files of any format output by the tool execution. @OutputOnly

Methods

NameAccessible byRequired ParamsDescription
projects_histories_executions_steps_testCases_getSELECTexecutionId, historyId, projectId, stepId, testCaseIdGets details of a Test Case for a Step. Experimental test cases API. Still in active development. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write to project - INVALID_ARGUMENT - if the request is malformed - NOT_FOUND - if the containing Test Case does not exist
projects_histories_executions_steps_testCases_listSELECTexecutionId, historyId, projectId, stepIdLists Test Cases attached to a Step. Experimental test cases API. Still in active development. May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to write to project - INVALID_ARGUMENT - if the request is malformed - NOT_FOUND - if the containing Step does not exist