github.com/kubeshop/testkube@v1.17.23/docs/docs/articles/getting-test-suites-results.md (about)

     1  # Getting Results
     2  
     3  To get recent results, call the `testsuites executions` subcommand:
     4  
     5  ```sh
     6  testkube get tse
     7  ```
     8  
     9  ```sh title="Expected output:"
    10  
    11    ID                       | TEST SUITE NAME                | EXECUTION NAME                        | STATUS  | STEPS | LABELS        
    12  ---------------------------+--------------------------------+---------------------------------------+---------+-------+---------------
    13    63d401e5fed6933f342ccc67 | executor-maven-smoke-tests     | ts-executor-maven-smoke-tests-680     | failed  |     3 | app=testkube  
    14    63d401a9fed6933f342ccc61 | executor-artillery-smoke-tests | ts-executor-artillery-smoke-tests-682 | passed  |     2 | app=testkube  
    15    63d3fed9fed6933f342ccc5b | executor-jmeter-smoke-tests    | ts-executor-jmeter-smoke-tests-500    | passed  |     2 | app=testkube  
    16    63d3fd35fed6933f342ccc51 | executor-postman-smoke-tests   | ts-executor-postman-smoke-tests-671   | passed  |     4 | app=testkube  
    17    63d3fb91fed6933f342ccc4b | executor-container-smoke-tests | ts-executor-container-smoke-tests-683 | failed  |     2 | app=testkube
    18  
    19  ```
    20  
    21  ## **Getting a Single Test Suite Execution**
    22  
    23  With the test suite execution ID, you can get single test suite results:
    24  
    25  ```sh
    26  testkube get tse 61e1136165e59a3183465125
    27  ```
    28  
    29  ```sh title="Expected output:"
    30  Id:       63d3cd05c6768fc8b574e2e8
    31  Name:     ts-testsuite-parallel-19
    32  Status:   passed
    33  Duration: 22.138s
    34  
    35  Labels:   
    36    STATUSES               | STEP                           | IDS                            | ERRORS      
    37  -------------------------+--------------------------------+--------------------------------+-------------
    38    passed, passed, passed | run:testkube/cli-test,         | 63d3cd05c6768fc8b574e2e9,      | "", "", ""  
    39                           | run:testkube/demo-test, delay  | 63d3cd05c6768fc8b574e2ea, ""   |             
    40                           | 1000ms                         |                                |             
    41    passed                 | delay 5000ms                   | ""                             | ""          
    42  
    43  
    44  Use the following command to get test suite execution details:
    45  $ kubectl testkube get tse 61e1136165e59a3183465125
    46  ```
    47  
    48  Test Suite steps that are running workflows based on `Test` Custom Resources have a Test Execution ID. You can get the details of each in a separate command:
    49  
    50  ```sh 
    51  kubectl testkube get execution 63d3cd05c6768fc8b574e2e9
    52  
    53  ID:         63d3cd05c6768fc8b574e2e9
    54  Name:       testsuite-parallel-cli-test-46
    55  Number:            46
    56  Test name:         cli-test
    57  Type:              cli/test
    58  Status:            passed
    59  Start time:        2023-01-27 13:09:25.54 +0000 UTC
    60  End time:          2023-01-27 13:09:42.432 +0000 UTC
    61  Duration:          00:00:16
    62  
    63  
    64  TODO
    65  
    66  → Create TODO
    67    POST http://34.74.127.60:8080/todos [201 Created, 296B, 100ms]
    68    ✓  Status code is 201 CREATED
    69    ┌
    70    │ 'creating', 'http://34.74.127.60:8080/todos/50'
    71    └
    72    ✓  Check if todo item created successfully
    73    GET http://34.74.127.60:8080/todos/50 [200 OK, 291B, 8ms]
    74  
    75  → Complete TODO item
    76    ┌
    77    │ 'completing', 'http://34.74.127.60:8080/todos/50'
    78    └
    79    PATCH http://34.74.127.60:8080/todos/50 [200 OK, 290B, 8ms]
    80  
    81  → Delete TODO item
    82    ┌
    83    │ 'deleting', 'http://34.74.127.60:8080/todos/50'
    84    └
    85    DELETE http://34.74.127.60:8080/todos/50 [204 No Content, 113B, 7ms]
    86    ✓  Status code is 204 no content
    87  
    88  ┌─────────────────────────┬───────────────────┬──────────────────┐
    89  │                         │          executed │           failed │
    90  ├─────────────────────────┼───────────────────┼──────────────────┤
    91  │              iterations │                 1 │                0 │
    92  ├─────────────────────────┼───────────────────┼──────────────────┤
    93  │                requests │                 4 │                0 │
    94  ├─────────────────────────┼───────────────────┼──────────────────┤
    95  │            test-scripts │                 5 │                0 │
    96  ├─────────────────────────┼───────────────────┼──────────────────┤
    97  │      prerequest-scripts │                 6 │                0 │
    98  ├─────────────────────────┼───────────────────┼──────────────────┤
    99  │              assertions │                 3 │                0 │
   100  ├─────────────────────────┴───────────────────┴──────────────────┤
   101  │ total run duration: 283ms                                      │
   102  ├────────────────────────────────────────────────────────────────┤
   103  │ total data received: 353B (approx)                             │
   104  ├────────────────────────────────────────────────────────────────┤
   105  │ average response time: 30ms [min: 7ms, max: 100ms, s.d.: 39ms] │
   106  └────────────────────────────────────────────────────────────────┘
   107  
   108  ```
   109  
   110  ### Getting a Test Suite Status of a Given Test Suite from Test Suite CRD
   111  
   112  To get the Test Suite CRD status of a particular test suite, pass the test suite name as a parameter:
   113  
   114  ```sh
   115  kubectl testkube get testsuites test-suite-example --crd-only
   116  ```
   117  
   118  Output:
   119  
   120  ```yaml title="Expected output:"
   121  apiVersion: tests.testkube.io/v3
   122  kind: TestSuite
   123  metadata:
   124    name: test-suite-example
   125    namespace: testkube
   126  spec:
   127    steps:
   128    - stopOnFailure: false
   129      execute:
   130      - test: testkube-dashboard
   131      - delay: 1s
   132      - test: testkube-homepage
   133  
   134  status:
   135    latestExecution:
   136      id: 63b7551cb2a16c73e8cfa1bf
   137      startTime: 2023-01-05T22:54:20Z
   138      endTime: 2023-01-05T22:54:29Z
   139      status: failed
   140  ```