1<html><body>
2<style>
3
4body, h1, h2, h3, div, span, p, pre, a {
5  margin: 0;
6  padding: 0;
7  border: 0;
8  font-weight: inherit;
9  font-style: inherit;
10  font-size: 100%;
11  font-family: inherit;
12  vertical-align: baseline;
13}
14
15body {
16  font-size: 13px;
17  padding: 1em;
18}
19
20h1 {
21  font-size: 26px;
22  margin-bottom: 1em;
23}
24
25h2 {
26  font-size: 24px;
27  margin-bottom: 1em;
28}
29
30h3 {
31  font-size: 20px;
32  margin-bottom: 1em;
33  margin-top: 1em;
34}
35
36pre, code {
37  line-height: 1.5;
38  font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
39}
40
41pre {
42  margin-top: 0.5em;
43}
44
45h1, h2, h3, p {
46  font-family: Arial, sans serif;
47}
48
49h1, h2, h3 {
50  border-bottom: solid #CCC 1px;
51}
52
53.toc_element {
54  margin-top: 0.5em;
55}
56
57.firstline {
58  margin-left: 2 em;
59}
60
61.method  {
62  margin-top: 1em;
63  border: solid 1px #CCC;
64  padding: 1em;
65  background: #EEE;
66}
67
68.details {
69  font-weight: bold;
70  font-size: 14px;
71}
72
73</style>
74
75<h1><a href="toolresults_v1beta3.html">Cloud Tool Results API</a> . <a href="toolresults_v1beta3.projects.html">projects</a> . <a href="toolresults_v1beta3.projects.histories.html">histories</a> . <a href="toolresults_v1beta3.projects.histories.executions.html">executions</a> . <a href="toolresults_v1beta3.projects.histories.executions.steps.html">steps</a> . <a href="toolresults_v1beta3.projects.histories.executions.steps.testCases.html">testCases</a></h1>
76<h2>Instance Methods</h2>
77<p class="toc_element">
78  <code><a href="#get">get(projectId, historyId, executionId, stepId, testCaseId)</a></code></p>
79<p class="firstline">Gets details of a Test Case for a Step. Experimental test cases API. Still in active development.</p>
80<p class="toc_element">
81  <code><a href="#list">list(projectId, historyId, executionId, stepId, pageSize=None, pageToken=None)</a></code></p>
82<p class="firstline">Lists Test Cases attached to a Step. Experimental test cases API. Still in active development.</p>
83<p class="toc_element">
84  <code><a href="#list_next">list_next(previous_request, previous_response)</a></code></p>
85<p class="firstline">Retrieves the next page of results.</p>
86<h3>Method Details</h3>
87<div class="method">
88    <code class="details" id="get">get(projectId, historyId, executionId, stepId, testCaseId)</code>
89  <pre>Gets details of a Test Case for a Step. Experimental test cases API. Still in active development.
90
91May return any of the following canonical error codes:
92
93- 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
94
95Args:
96  projectId: string, A Project id.
97
98Required. (required)
99  historyId: string, A History id.
100
101Required. (required)
102  executionId: string, A Execution id
103
104Required. (required)
105  stepId: string, A Step id. Note: This step must include a TestExecutionStep.
106
107Required. (required)
108  testCaseId: string, A Test Case id.
109
110Required. (required)
111
112Returns:
113  An object of the form:
114
115    {
116    "status": "A String", # The status of the test case.
117        #
118        # Required.
119    "testCaseReference": { # A reference to a test case. # Test case reference, e.g. name, class name and test suite name.
120        #
121        # Required.
122        #
123        # Test case references are canonically ordered lexicographically by these three factors: * First, by test_suite_name. * Second, by class_name. * Third, by name.
124      "className": "A String", # The name of the class.
125      "testSuiteName": "A String", # The name of the test suite to which this test case belongs.
126      "name": "A String", # The name of the test case.
127          #
128          # Required.
129    },
130    "testCaseId": "A String", # A unique identifier within a Step for this Test Case.
131    "toolOutputs": [ # References to opaque files of any format output by the tool execution.
132      { # A reference to a ToolExecution output file.
133        "testCase": { # A reference to a test case. # The test case to which this output file belongs.
134            #
135            # - In response: present if set by create/update request - In create/update request: optional
136            #
137            # Test case references are canonically ordered lexicographically by these three factors: * First, by test_suite_name. * Second, by class_name. * Third, by name.
138          "className": "A String", # The name of the class.
139          "testSuiteName": "A String", # The name of the test suite to which this test case belongs.
140          "name": "A String", # The name of the test case.
141              #
142              # Required.
143        },
144        "output": { # A reference to a file. # A FileReference to an output file.
145            #
146            # - In response: always set - In create/update request: always set
147          "fileUri": "A String", # The URI of a file stored in Google Cloud Storage.
148              #
149              # 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
150              #
151              # An INVALID_ARGUMENT error will be returned if the URI format is not supported.
152              #
153              # - In response: always set - In create/update request: always set
154        },
155        "creationTime": { # A 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. # The creation time of the file.
156            #
157            # - In response: present if set by create/update request - In create/update request: optional
158            #
159            # 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](https://developers.google.com/time/smear).
160            #
161            # 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](https://www.ietf.org/rfc/rfc3339.txt) date strings.
162            #
163            # # Examples
164            #
165            # Example 1: Compute Timestamp from POSIX `time()`.
166            #
167            # Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);
168            #
169            # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
170            #
171            # struct timeval tv; gettimeofday(&tv, NULL);
172            #
173            # Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);
174            #
175            # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
176            #
177            # FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
178            #
179            # // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
180            #
181            # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
182            #
183            # long millis = System.currentTimeMillis();
184            #
185            # Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();
186            #
187            #
188            #
189            # Example 5: Compute Timestamp from current time in Python.
190            #
191            # timestamp = Timestamp() timestamp.GetCurrentTime()
192            #
193            # # JSON Mapping
194            #
195            # In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
196            #
197            # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
198            #
199            # In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format.
200          "nanos": 42, # 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.
201          "seconds": "A 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.
202        },
203      },
204    ],
205    "startTime": { # A 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. # The start time of the test case.
206        #
207        # Optional.
208        #
209        # 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](https://developers.google.com/time/smear).
210        #
211        # 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](https://www.ietf.org/rfc/rfc3339.txt) date strings.
212        #
213        # # Examples
214        #
215        # Example 1: Compute Timestamp from POSIX `time()`.
216        #
217        # Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);
218        #
219        # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
220        #
221        # struct timeval tv; gettimeofday(&tv, NULL);
222        #
223        # Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);
224        #
225        # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
226        #
227        # FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
228        #
229        # // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
230        #
231        # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
232        #
233        # long millis = System.currentTimeMillis();
234        #
235        # Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();
236        #
237        #
238        #
239        # Example 5: Compute Timestamp from current time in Python.
240        #
241        # timestamp = Timestamp() timestamp.GetCurrentTime()
242        #
243        # # JSON Mapping
244        #
245        # In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
246        #
247        # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
248        #
249        # In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format.
250      "nanos": 42, # 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.
251      "seconds": "A 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.
252    },
253    "skippedMessage": "A String", # Why the test case was skipped.
254        #
255        # Present only for skipped test case
256    "stackTraces": [ # The stack trace details if the test case failed or encountered an error.
257        #
258        # The maximum size of the stack traces is 100KiB, beyond which the stack track will be truncated.
259        #
260        # Zero if the test case passed.
261      { # A stacktrace.
262        "exception": "A String", # The stack trace message.
263            #
264            # Required
265      },
266    ],
267    "endTime": { # A 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. # The end time of the test case.
268        #
269        # Optional.
270        #
271        # 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](https://developers.google.com/time/smear).
272        #
273        # 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](https://www.ietf.org/rfc/rfc3339.txt) date strings.
274        #
275        # # Examples
276        #
277        # Example 1: Compute Timestamp from POSIX `time()`.
278        #
279        # Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);
280        #
281        # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
282        #
283        # struct timeval tv; gettimeofday(&tv, NULL);
284        #
285        # Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);
286        #
287        # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
288        #
289        # FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
290        #
291        # // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
292        #
293        # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
294        #
295        # long millis = System.currentTimeMillis();
296        #
297        # Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();
298        #
299        #
300        #
301        # Example 5: Compute Timestamp from current time in Python.
302        #
303        # timestamp = Timestamp() timestamp.GetCurrentTime()
304        #
305        # # JSON Mapping
306        #
307        # In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
308        #
309        # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
310        #
311        # In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format.
312      "nanos": 42, # 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.
313      "seconds": "A 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.
314    },
315  }</pre>
316</div>
317
318<div class="method">
319    <code class="details" id="list">list(projectId, historyId, executionId, stepId, pageSize=None, pageToken=None)</code>
320  <pre>Lists Test Cases attached to a Step. Experimental test cases API. Still in active development.
321
322May return any of the following canonical error codes:
323
324- 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
325
326Args:
327  projectId: string, A Project id.
328
329Required. (required)
330  historyId: string, A History id.
331
332Required. (required)
333  executionId: string, A Execution id
334
335Required. (required)
336  stepId: string, A Step id. Note: This step must include a TestExecutionStep.
337
338Required. (required)
339  pageSize: integer, The maximum number of TestCases to fetch.
340
341Default value: 100. The server will use this default if the field is not set or has a value of 0.
342
343Optional.
344  pageToken: string, A continuation token to resume the query at the next item.
345
346Optional.
347
348Returns:
349  An object of the form:
350
351    { # Response message for StepService.ListTestCases.
352    "nextPageToken": "A String",
353    "testCases": [ # List of test cases.
354      {
355        "status": "A String", # The status of the test case.
356            #
357            # Required.
358        "testCaseReference": { # A reference to a test case. # Test case reference, e.g. name, class name and test suite name.
359            #
360            # Required.
361            #
362            # Test case references are canonically ordered lexicographically by these three factors: * First, by test_suite_name. * Second, by class_name. * Third, by name.
363          "className": "A String", # The name of the class.
364          "testSuiteName": "A String", # The name of the test suite to which this test case belongs.
365          "name": "A String", # The name of the test case.
366              #
367              # Required.
368        },
369        "testCaseId": "A String", # A unique identifier within a Step for this Test Case.
370        "toolOutputs": [ # References to opaque files of any format output by the tool execution.
371          { # A reference to a ToolExecution output file.
372            "testCase": { # A reference to a test case. # The test case to which this output file belongs.
373                #
374                # - In response: present if set by create/update request - In create/update request: optional
375                #
376                # Test case references are canonically ordered lexicographically by these three factors: * First, by test_suite_name. * Second, by class_name. * Third, by name.
377              "className": "A String", # The name of the class.
378              "testSuiteName": "A String", # The name of the test suite to which this test case belongs.
379              "name": "A String", # The name of the test case.
380                  #
381                  # Required.
382            },
383            "output": { # A reference to a file. # A FileReference to an output file.
384                #
385                # - In response: always set - In create/update request: always set
386              "fileUri": "A String", # The URI of a file stored in Google Cloud Storage.
387                  #
388                  # 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
389                  #
390                  # An INVALID_ARGUMENT error will be returned if the URI format is not supported.
391                  #
392                  # - In response: always set - In create/update request: always set
393            },
394            "creationTime": { # A 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. # The creation time of the file.
395                #
396                # - In response: present if set by create/update request - In create/update request: optional
397                #
398                # 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](https://developers.google.com/time/smear).
399                #
400                # 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](https://www.ietf.org/rfc/rfc3339.txt) date strings.
401                #
402                # # Examples
403                #
404                # Example 1: Compute Timestamp from POSIX `time()`.
405                #
406                # Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);
407                #
408                # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
409                #
410                # struct timeval tv; gettimeofday(&tv, NULL);
411                #
412                # Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);
413                #
414                # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
415                #
416                # FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
417                #
418                # // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
419                #
420                # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
421                #
422                # long millis = System.currentTimeMillis();
423                #
424                # Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();
425                #
426                #
427                #
428                # Example 5: Compute Timestamp from current time in Python.
429                #
430                # timestamp = Timestamp() timestamp.GetCurrentTime()
431                #
432                # # JSON Mapping
433                #
434                # In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
435                #
436                # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
437                #
438                # In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format.
439              "nanos": 42, # 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.
440              "seconds": "A 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.
441            },
442          },
443        ],
444        "startTime": { # A 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. # The start time of the test case.
445            #
446            # Optional.
447            #
448            # 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](https://developers.google.com/time/smear).
449            #
450            # 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](https://www.ietf.org/rfc/rfc3339.txt) date strings.
451            #
452            # # Examples
453            #
454            # Example 1: Compute Timestamp from POSIX `time()`.
455            #
456            # Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);
457            #
458            # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
459            #
460            # struct timeval tv; gettimeofday(&tv, NULL);
461            #
462            # Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);
463            #
464            # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
465            #
466            # FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
467            #
468            # // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
469            #
470            # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
471            #
472            # long millis = System.currentTimeMillis();
473            #
474            # Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();
475            #
476            #
477            #
478            # Example 5: Compute Timestamp from current time in Python.
479            #
480            # timestamp = Timestamp() timestamp.GetCurrentTime()
481            #
482            # # JSON Mapping
483            #
484            # In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
485            #
486            # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
487            #
488            # In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format.
489          "nanos": 42, # 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.
490          "seconds": "A 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.
491        },
492        "skippedMessage": "A String", # Why the test case was skipped.
493            #
494            # Present only for skipped test case
495        "stackTraces": [ # The stack trace details if the test case failed or encountered an error.
496            #
497            # The maximum size of the stack traces is 100KiB, beyond which the stack track will be truncated.
498            #
499            # Zero if the test case passed.
500          { # A stacktrace.
501            "exception": "A String", # The stack trace message.
502                #
503                # Required
504          },
505        ],
506        "endTime": { # A 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. # The end time of the test case.
507            #
508            # Optional.
509            #
510            # 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](https://developers.google.com/time/smear).
511            #
512            # 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](https://www.ietf.org/rfc/rfc3339.txt) date strings.
513            #
514            # # Examples
515            #
516            # Example 1: Compute Timestamp from POSIX `time()`.
517            #
518            # Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);
519            #
520            # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
521            #
522            # struct timeval tv; gettimeofday(&tv, NULL);
523            #
524            # Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);
525            #
526            # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
527            #
528            # FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
529            #
530            # // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
531            #
532            # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
533            #
534            # long millis = System.currentTimeMillis();
535            #
536            # Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();
537            #
538            #
539            #
540            # Example 5: Compute Timestamp from current time in Python.
541            #
542            # timestamp = Timestamp() timestamp.GetCurrentTime()
543            #
544            # # JSON Mapping
545            #
546            # In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
547            #
548            # For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
549            #
550            # In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format.
551          "nanos": 42, # 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.
552          "seconds": "A 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.
553        },
554      },
555    ],
556  }</pre>
557</div>
558
559<div class="method">
560    <code class="details" id="list_next">list_next(previous_request, previous_response)</code>
561  <pre>Retrieves the next page of results.
562
563Args:
564  previous_request: The request for the previous page. (required)
565  previous_response: The response from the request for the previous page. (required)
566
567Returns:
568  A request object that you can call 'execute()' on to request the next
569  page. Returns None if there are no more items in the collection.
570    </pre>
571</div>
572
573</body></html>