Consecutive requests with CLI do not use

[diazjf]

When performing consecutive (one-after-another) requests using the CLI, post response variables are not captured.

Example

Collection: doggy_daycare_collection.zip

1. We run the Create Dog request as follows:

fern@fern-zenbook:~/Collections/Doggy_DayCare/Doggy Daycare$ bru run Dogs/Create\ Dog.yml --env Local
Dogs/Create Dog (201 Created) - 30 ms

📊 Execution Summary
┌───────────────┬──────────────┐
│ Metric        │    Result    │
├───────────────┼──────────────┤
│ Status        │    ✓ PASS    │
├───────────────┼──────────────┤
│ Requests      │ 1 (1 Passed) │
├───────────────┼──────────────┤
│ Tests         │     0/0      │
├───────────────┼──────────────┤
│ Assertions    │     0/0      │
├───────────────┼──────────────┤
│ Duration (ms) │      30      │
└───────────────┴──────────────┘

2. Run the Get Dog request as follows:

bru run Dogs/Get\ Dog.yml --env Local
Dogs/Get Dog (404 Not Found) - 15 ms
Tests
   ✕ should return 200 OK
      expected 404 to equal 200
   ✕ should return correct content type
      expected 'text/plain; charset=utf-8' to include 'application/json'
   ✕ should have valid dog fields
      expected 'dog not found\n' to have property 'name'
Assertions
   ✕ res.status: eq 200
      expected 404 to equal 200
   ✕ res.body.id: eq {{newDogId}}
      expected undefined to equal '{{newDogId}}'

📊 Execution Summary
┌───────────────┬──────────────┐
│ Metric        │    Result    │
├───────────────┼──────────────┤
│ Status        │    ✗ FAIL    │
├───────────────┼──────────────┤
│ Requests      │ 1 (1 Failed) │
├───────────────┼──────────────┤
│ Tests         │     0/3      │
├───────────────┼──────────────┤
│ Assertions    │     0/2      │
├───────────────┼──────────────┤
│ Duration (ms) │      15      │
└───────────────┴──────────────┘

We see the Get Dog request fail because {{newDogId}} is never set in Create Dog event hough it is part of the post script.

Other Questions

1. Is it possible to see the response using the Bruno CLI?
2. Do sequences (1,2,...) need to be set manually?

[diazjf]

If I run all tests in a sequence then they pass meaning that variables do persist.

fern@fern-zenbook:~/Collections/Doggy_DayCare/Doggy Daycare$ bru run Dogs/ --env Local
Dogs/Get All Dogs (200 OK) - 28 ms
Dogs/Create Dog (201 Created) - 12 ms
Dogs/Update Dog (500 Internal Server Error) - 3 ms
Dogs/Delete Dog (204 No Content) - 2 ms
Dogs/Get Dog (200 OK) - 1 ms
Tests
   ✓ should return 200 OK
   ✓ should return correct content type
   ✓ should have valid dog fields
Assertions
   ✓ res.status: eq 200
   ✓ res.body.id: eq {{newDogId}}

📊 Execution Summary
┌───────────────┬──────────────┐
│ Metric        │    Result    │
├───────────────┼──────────────┤
│ Status        │    ✓ PASS    │
├───────────────┼──────────────┤
│ Requests      │ 5 (5 Passed) │
├───────────────┼──────────────┤
│ Tests         │     3/3      │
├───────────────┼──────────────┤
│ Assertions    │     2/2      │
├───────────────┼──────────────┤
│ Duration (ms) │      46      │
└───────────────┴──────────────┘

My question is, is the CLI mainly used just to validate tests/assertions since responses are not provided?

[diazjf]

Additionally GraphQL queries seem to fail:

fern@fern-zenbook:~/Collections/Doggy_DayCare/Doggy Daycare$ bru run --output results.json --env Local
Dogs/Get All Dogs (200 OK) - 28 ms
Dogs/Create Dog (201 Created) - 39 ms
Dogs/Update Dog (500 Internal Server Error) - 2 ms
Dogs/Delete Dog (204 No Content) - 2 ms
Dogs/Get Dog (200 OK) - 1 ms
Tests
   ✓ should return 200 OK
   ✓ should return correct content type
   ✓ should have valid dog fields
Assertions
   ✓ res.status: eq 200
   ✓ res.body.id: eq {{newDogId}}
Attendance/CheckIn (201 Created) - 12 ms
Attendance/Attendance Stream (400 Bad Request) - 2 ms
Feed/Create Post (Unsupported protocol localhost:)
Feed/Get Feed (Unsupported protocol localhost:)
Social/Social Graph (200 OK) - 2 ms
Social/List Friends (200 OK) - 1 ms

📊 Execution Summary
┌───────────────┬─────────────────────────┐
│ Metric        │         Result          │
├───────────────┼─────────────────────────┤
│ Status        │         ✗ FAIL          │
├───────────────┼─────────────────────────┤
│ Requests      │ 11 (9 Passed, 2 Failed) │
├───────────────┼─────────────────────────┤
│ Tests         │           3/3           │
├───────────────┼─────────────────────────┤
│ Assertions    │           2/2           │
├───────────────┼─────────────────────────┤
│ Duration (ms) │           89            │
└───────────────┴─────────────────────────┘
Wrote json results to results.json

[diazjf]

Note: This behavior is expected since the CLI does not retain the set variables for single calls. However, if the application is run in a sequence then the set variables are retained.

Additional Note: Choosing not to include the Collection in this tutorial since it may fail based off the variables set using in examples which are uuids generated by the micro-service.