Space-separated words use implicit AND. Press / to focus the search bar. Operators &&||!! activate advanced mode; without them, legacy tag expressions (@a and @b or not @c) are also supported.
Status:
Happy Paths:
Duration ≥:seconds
Dependencies:
Details:lines
Scenario Timeline 🛈
Listing feedback for an order should return the feedback
1.7s
Retrieving an existing inventory item should return the item
1.6s
Ingredient usage should aggregate across multiple recipes
1.5s
Order summaries should contain ingested order data
1.2s
An outbox message should transition to failed after exhausting retries
1.2s
Consuming recipe cost event should trigger downstream processing
1.1s
Creating an order should emit a structured log entry
1.0s
A valid order should be created and an event published
926ms
Audit logs should be filterable by entity id
865ms
Listing usage by ingredient should return matching records
589ms
Listing waste by recipe should return matching records
556ms
The OpenApi endpoint should return a valid specification
547ms
Recording usage with missing ingredient name should return bad request
495ms
Recording an order timing should return the created record
489ms
The Scalar UI endpoint should return a valid page
435ms
Exceeding the rate limit should return too many requests
427ms
Cancelling an already cancelled reservation should return a conflict response
411ms
Listing reviews by recipe should return matching reviews
400ms
All menu items should be marked unavailable when the supplier service is down
360ms
The AsyncApi endpoint should return a valid specification
346ms
Creating an order should produce an audit log entry and events
345ms
Toppings should include raspberries when the feature flag is enabled
321ms
Listing orders with a small page size should limit results
285ms
An order at the maximum items per order should be accepted
267ms
Goat milk endpoint should return fresh goat milk when feature is enabled
264ms
The menu endpoint should return all menu items with availability status
261ms
Submitting a recipe review should return the created review
252ms
Menu responses should be cached and returned even when supplier becomes unavailable
247ms
Requesting the second page should return different orders
237ms
An order should progress through all status transitions to completion
221ms
Health check should report degraded when the cow service is unavailable
219ms
Health check should report degraded when a downstream service returns a non-success status
215ms
Goat milk endpoint should return not found when feature is disabled
212ms
Health check should report degraded when multiple downstream services are unavailable
202ms
Creating an order should produce a retrievable audit log entry
200ms
Pancake recipe summary should return correct data
171ms
Creating an order should write an outbox message that gets processed
162ms
The health check response should include description and data for each entry
162ms
Listing notes by recipe should return matching notes
161ms
Retrieving an existing staff member should return the member
159ms
Popular recipes should return recipe types ordered by frequency
158ms
Toppings should exclude raspberries when the feature flag is disabled
158ms
Sending a request with an unsupported content type should return an unsupported media type response
155ms
Submitting the same order with different idempotency keys should return different confirmations
153ms
Recording an equipment reading should return the created record
147ms
Updating a non-existent note should return not found
145ms
Updating an existing topping should return the updated topping
144ms
Listing timings by station should return matching records
142ms
Listing orders should return a paginated response
135ms
Listing all inventory items should return all items
133ms
An order exceeding the maximum items per order should be rejected
133ms
Muffins endpoint called with an invalid field should return a bad request response
133ms
Waffles endpoint is called with invalid ingredients should return a bad request response
132ms
Updating customer preferences should return the updated preferences
128ms
Requesting goat milk when the goat service is unavailable should return a bad gateway response
126ms
Listing readings by equipment should return matching records
119ms
Getting usage summary should return aggregated data
114ms
Ingredient shipments should be recorded when delivered via eventgrid webhook
114ms
A valid waffle request should return a fresh batch
114ms
A created order should be retrievable by its ID
110ms
Different muffin recipes should produce the expected batch
108ms
Batch completions should contain data ingested via pubsub consumer
107ms
Retrieving non-existent customer preferences should return not found
104ms
Deleting an inventory item should return no content
100ms
Retrieving an existing reservation should return the reservation
100ms
Order status for non-existent order should return not found
98ms
Consuming an order served event should trigger downstream processing
96ms
Getting the timing summary should return aggregated data
96ms
Retrieving an existing note by id should return the note
95ms
Adding a new topping should return the created topping
93ms
Deleting a staff member should return no content
90ms
A valid status transition should update the order
88ms
Updating an inventory item should return the updated item
88ms
Creating an order when the kitchen service returns an error should still create the order
86ms
A request with a correlation id should return the same id in the response
78ms
Consuming customer feedback event should trigger downstream processing
77ms
Equipment alerts should contain data ingested via Event Hub consumer
76ms
Ordering a non-existent daily special should return not found
76ms
Listing orders when none exist should return an empty page
75ms
Updating an existing note should return the updated note
73ms
Audit logs should be filterable by entity type
72ms
Streaming order updates should return the current status
70ms
Deleting a reservation should return no content
67ms
Deleting a waste record should return no content
63ms
A waffle request with more toppings than allowed should return a bad request response
63ms
Retrieving a non-existent review should return not found
62ms
An invalid status transition should return a conflict response
61ms
Recipe reports should contain ingested recipe data
61ms
Order status via gRPC should return order details
60ms
Retrieving non-existent feedback should return not found
60ms
Update toppings endpoint is called with invalid or dangerous input
57ms
Updating the status of a non-existent order should return not found
54ms
An invalid status transition should return a conflict response
53ms
Audit logs should be returned in descending timestamp order
50ms
A valid pancake request should return a fresh batch
48ms
An invalid status transition should return a conflict response
48ms
Deleting a reading should remove it from the list
47ms
A valid apple cinnamon muffin request should return a fresh batch
43ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
42ms
Creating a reservation should return the confirmed reservation
42ms
The toppings endpoint should return all available toppings
39ms
An invalid status transition should return a conflict response
39ms
Cancelling a reservation should return the cancelled reservation
38ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
34ms
Retrieving existing customer preferences should return the preferences
34ms
Orders endpoint is called with invalid fields should return a bad request response
34ms
An invalid status transition should return a conflict response
34ms
A valid status transition should update the order
34ms
An invalid status transition should return a conflict response
34ms
Retrieving existing review by id should return the review
33ms
Deleting a non-existent topping should return not found
33ms
Update toppings endpoint is called with invalid or dangerous input
32ms
Order summaries should return an empty list when no orders exist
32ms
Retrieving existing feedback by id should return the feedback
31ms
The health check endpoint should return a healthy status with dependency details
31ms
An invalid status transition should return a conflict response
30ms
The daily specials endpoint should return all available specials
30ms
Ordering a daily special beyond the threshold should return a conflict response
30ms
Requesting goat milk when the goat service returns an invalid response should return a bad gateway response
30ms
Waffles endpoint is called with invalid ingredients should return a bad request response
29ms
Filtering audit logs by a non-existent entity type should return an empty collection
28ms
A request with a correlation id should forward it to the supplier service
27ms
Deleting an existing topping should return no content
26ms
A valid status transition should update the order
26ms
Daily specials order endpoint is called with invalid fields should return a bad request response
26ms
Submitting feedback should return the created feedback
26ms
A pancake request with more toppings than allowed should return a bad request response
25ms
Recording ingredient usage should return the created record
25ms
A valid status transition should update the order
24ms
Recording waste with zero quantity should return bad request
24ms
Saving customer preferences should return the saved preferences
23ms
Different muffin recipes should produce the expected batch
22ms
Recording ingredient waste should return the created record
22ms
Remaining quantity should decrease after each order
22ms
Submitting the same order with the same idempotency key should return the same confirmation
22ms
Orders endpoint is called with invalid fields should return a bad request response
21ms
Recording a timing with zero prep seconds should return bad request
21ms
Requesting milk when the cow service returns an invalid response should return a bad gateway response
21ms
Order status update endpoint is called with invalid fields should return a bad request response
21ms
Sending a request with an unsupported content type should return an unsupported media type response
21ms
A valid daily special order should return a confirmation
20ms
The heartbeat endpoint should return a running message
20ms
Creating a chef note should return the created note
20ms
Recording a reading with zero value should return bad request
19ms
Creating a note with missing note text should return bad request
18ms
Toppings endpoint is called with invalid or dangerous input
18ms
Toppings endpoint is called with invalid or dangerous input
18ms
Streaming updates for non-existent order should return not found
17ms
Retrieving a non-existent order should return not found
17ms
Recording a reading with missing metric should return bad request
17ms
Muffins endpoint called with an invalid field should return a bad request response
17ms
Sending a request with an unsupported content type should return an unsupported media type response
16ms
Different muffin recipes should produce the expected batch
15ms
Adding a new staff member should return the created member
15ms
Waffles endpoint is called with invalid ingredients should return a bad request response
15ms
Retrieving a non-existent note should return not found
14ms
Saving customer preferences with missing customer name should return bad request
14ms
Submitting a review with an invalid rating should return bad request
13ms
Unknown recipe type should return zero batches
13ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
13ms
A request without a correlation id should have one generated in the response
13ms
Waffles endpoint is called with invalid ingredients should return a bad request response
12ms
Waffle recipe summary should return correct data
12ms
Adding a new inventory item should return the created item
11ms
Recording waste with missing reason should return bad request
11ms
Waffles endpoint is called with invalid ingredients should return a bad request response
11ms
Submitting feedback with missing customer name should return bad request
11ms
Requesting milk when the cow service is unavailable should return a bad gateway response
10ms
Recording a timing with missing station should return bad request
10ms
Adding a staff member with an invalid role should return a bad request response
10ms
Update toppings endpoint is called with invalid or dangerous input
10ms
Muffins endpoint called with an invalid field should return a bad request response
10ms
A request with a correlation id should forward it to the cow service
9ms
Requesting milk when the cow service times out should return a bad gateway response
9ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
9ms
Muffins endpoint called with an invalid field should return a bad request response
9ms
Recording waste with missing ingredient name should return bad request
9ms
Creating a note with missing recipe name should return bad request
9ms
Toppings endpoint is called with invalid or dangerous input
9ms
Submitting a review with missing recipe name should return bad request
8ms
Submitting feedback with invalid rating should return bad request
8ms
Recording usage with zero quantity should return bad request
8ms
Orders endpoint is called with invalid fields should return a bad request response
8ms
Daily specials order endpoint is called with invalid fields should return a bad request response
8ms
Waffles endpoint is called with invalid ingredients should return a bad request response
7ms
Orders endpoint is called with invalid fields should return a bad request response
7ms
Waffles endpoint is called with invalid ingredients should return a bad request response
7ms
Sending a request with an unsupported content type should return an unsupported media type response
7ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
7ms
Retrieving a non-existent inventory item should return not found
7ms
A valid goat milk request should return fresh goat milk
7ms
Update toppings endpoint is called with invalid or dangerous input
6ms
Orders endpoint is called with invalid fields should return a bad request response
5ms
Sending a request with an unsupported content type should return an unsupported media type response
5ms
Toppings endpoint is called with invalid or dangerous input
5ms
Update toppings endpoint is called with invalid or dangerous input
5ms
Waffles endpoint is called with invalid ingredients should return a bad request response
5ms
Updating a non-existent topping should return not found
5ms
Update toppings endpoint is called with invalid or dangerous input
5ms
Muffins endpoint called with an invalid field should return a bad request response
5ms
Muffins endpoint called with an invalid field should return a bad request response
4ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
4ms
Toppings endpoint is called with invalid or dangerous input
4ms
Sending a request with an unsupported content type should return an unsupported media type response
4ms
Toppings endpoint is called with invalid or dangerous input
4ms
Apple Cinnamon Muffins Creation
/muffins - Creating apple cinnamon muffins with baking profiles and toppings
A valid apple cinnamon muffin request should return a fresh batch Happy Path43ms🔗Steps✓Givena valid apple cinnamon muffin recipe with all ingredients(9ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Whenthe muffins are prepared(12ms)
✓Thenthe muffin response should contain a valid batch with all ingredients(12ms)
✓Muffin steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Muffin steps response ingredients should contain 'Milk'(0ms)
✓Muffin steps response ingredients should contain 'Eggs'(0ms)
✓Muffin steps response ingredients should contain 'Flour'(0ms)
✓Muffin steps response ingredients should contain GrannySmithApples(0ms)
✓Muffin steps response ingredients should contain CeylonCinnamon(0ms)
✓Muffin steps response toppings should have count 1(0ms)
✓Muffin steps response baking temperature should be DefaultTemperature(0ms)
✓Muffin steps response baking duration should be DefaultDuration(0ms)
✓Andthe cow service should have received a milk request for the muffins(6ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ](0ms)
Diagrams
Details:lines
Different muffin recipes should produce the expected batch 3/3 passed147ms🔗
Steps✓Givena muffin recipe "Classic" with the following ingredients:(4ms)
Flour
Apples
Cinnamon
Plain Flour
Granny Smith
Ceylon
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Andwith baking at 180 degrees for 25 minutes in a "Standard" pan(0ms)
✓Andthe following muffin toppings:(0ms)
Name
Amount
Streusel
Light
Icing Glaze
Drizzle
✓Whenthe muffins are prepared(6ms)
✓Thenthe muffin batch should have 5 ingredients(0ms)
✓Muffin steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Muffin steps response ingredients should have count '5'(0ms)
✓Andthe muffin response should include 2 toppings(0ms)
✓Muffin steps response toppings should have count '2'(0ms)
✓Andthe muffin response should include baking information(0ms)
✓Muffin steps response baking temperature should be greater than 0(0ms)
Steps✓Givena muffin recipe "Rustic Wholesome" with the following ingredients:(6ms)
Flour
Apples
Cinnamon
Whole Wheat
Honeycrisp
Cassia
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Andwith baking at 175 degrees for 30 minutes in a "Cast Iron" pan(1ms)
✓Andthe following muffin toppings:(0ms)
Name
Amount
Brown Sugar Crumb
Heavy
Maple Drizzle
Light
✓Whenthe muffins are prepared(5ms)
✓Thenthe muffin batch should have 5 ingredients(2ms)
✓Muffin steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Muffin steps response ingredients should have count '5'(0ms)
✓Andthe muffin response should include 2 toppings(0ms)
✓Muffin steps response toppings should have count '2'(0ms)
✓Andthe muffin response should include baking information(0ms)
✓Muffin steps response baking temperature should be greater than 0(0ms)
Steps✓Givena muffin recipe "Spiced Deluxe" with the following ingredients:(23ms)
Flour
Apples
Cinnamon
Almond
Pink Lady
Saigon
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Andwith baking at 190 degrees for 20 minutes in a "Silicone" pan(1ms)
✓Andthe following muffin toppings:(5ms)
Name
Amount
Cinnamon Sugar
Heavy
Cream Cheese Swirl
Thick
✓Whenthe muffins are prepared(43ms)
✓Thenthe muffin batch should have 5 ingredients(8ms)
✓Muffin steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Muffin steps response ingredients should have count '5'(0ms)
✓Andthe muffin response should include 2 toppings(1ms)
✓Muffin steps response toppings should have count '2'(0ms)
✓Andthe muffin response should include baking information(3ms)
✓Muffin steps response baking temperature should be greater than 0(0ms)
Diagrams
Details:lines
Muffins endpoint called with an invalid field should return a bad request response 6/6 passed180ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Apples
Apples is required
'Apples' is required.
Bad Request
Passed
9ms
2
Cinnamon
<script>alert('xss')</script>
XSS in cinnamon
Cinnamon contains potentially dangerous content.
Bad Request
Passed
133ms
3
Cinnamon
Cinnamon is required
'Cinnamon' is required.
Bad Request
Passed
4ms
4
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
17ms
5
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
5ms
6
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
10ms
Steps
✓Givena valid muffin request with "Apples" set to ""(3ms)
✓Whenthe invalid muffin request is submitted(3ms)
✓Thenthe muffin response should contain error "'Apples' is required." with status "Bad Request"(1ms)
✓Response body should contain ''Apples' is required.'(0ms)
✓Muffin steps response message status code should be BadRequest(0ms)
Steps
✓Givena valid muffin request with "Cinnamon" set to "<script>alert('xss')</script>"(25ms)
✓Whenthe invalid muffin request is submitted(98ms)
✓Thenthe muffin response should contain error "Cinnamon contains potentially dangerous content." with status "Bad Request"(5ms)
✓Response body should contain 'Cinnamon contains potentially dangerous content.'(0ms)
✓Muffin steps response message status code should be BadRequest(0ms)
Steps
✓Givena valid muffin request with "Cinnamon" set to ""(0ms)
✓Whenthe invalid muffin request is submitted(2ms)
✓Thenthe muffin response should contain error "'Cinnamon' is required." with status "Bad Request"(0ms)
✓Response body should contain ''Cinnamon' is required.'(0ms)
✓Muffin steps response message status code should be BadRequest(0ms)
Steps
✓Givena valid muffin request with "Eggs" set to ""(0ms)
✓Whenthe invalid muffin request is submitted(3ms)
✓Thenthe muffin response should contain error "'Eggs' is required." with status "Bad Request"(12ms)
✓Response body should contain ''Eggs' is required.'(0ms)
✓Muffin steps response message status code should be BadRequest(0ms)
Steps
✓Givena valid muffin request with "Flour" set to ""(0ms)
✓Whenthe invalid muffin request is submitted(2ms)
✓Thenthe muffin response should contain error "'Flour' is required." with status "Bad Request"(0ms)
✓Response body should contain ''Flour' is required.'(0ms)
✓Muffin steps response message status code should be BadRequest(0ms)
Steps
✓Givena valid muffin request with "Milk" set to ""(3ms)
✓Whenthe invalid muffin request is submitted(4ms)
✓Thenthe muffin response should contain error "'Milk' is required." with status "Bad Request"(0ms)
✓Response body should contain ''Milk' is required.'(0ms)
✓Muffin steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Audit Log Filtering
/audit-logs - Filtering audit logs by entity type and entity ID
Audit logs should be filterable by entity id 865ms🔗Steps✓Givena pancake batch has been created(370ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order has been created for the batch(414ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response order id should not be empty(0ms)
✓Whenaudit logs are requested filtered by entity id(70ms)
✓Thenthe audit log response should contain the specific order entry(5ms)
✓Audit log response status code should be OK(0ms)
✓Audit logs should contain [ l => l.EntityId == 'aed6327f-e0ba-49ac-a6bb-56866b99ae33' ](0ms)
Diagrams
Details:lines
Audit logs should be filterable by entity type 72ms🔗Steps✓Givena pancake batch has been created(31ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order has been created for the batch(15ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response order id should not be empty(0ms)
✓Whenaudit logs are requested filtered by entity type(15ms)
✓Thenthe audit log response should only contain order entries(7ms)
✓Audit log response status code should be OK(0ms)
✓Audit logs should only contain [ l => l.EntityType == AuditLogDefaults.OrderEntityType ](0ms)
Diagrams
Details:lines
Audit logs should be returned in descending timestamp order 50ms🔗Steps✓Givena pancake batch has been created(19ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order has been created for the batch(12ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response order id should not be empty(0ms)
✓Whenaudit logs are requested filtered by entity type(5ms)
✓Thenthe audit logs should be ordered by timestamp descending(11ms)
✓Audit logs should not be null or empty(0ms)
✓Audit logs should be in descending order [ l => l.Timestamp ](0ms)
Diagrams
Details:lines
Filtering audit logs by a non-existent entity type should return an empty collection 28ms🔗Steps
✓Whenaudit logs are requested filtered by a non-existent entity type(15ms)
✓Thenthe audit log response should be an empty collection(11ms)
✓Audit log response status code should be OK(0ms)
✓Audit logs from different time range should be empty(0ms)
Diagrams
Details:lines
Audit Log Retrieval
/audit-logs - Retrieving audit log entries for order operations
Creating an order should produce a retrievable audit log entry Happy Path200ms🔗Steps✓Givena pancake batch has been created(14ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order has been created for the batch(10ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response order id should not be empty(0ms)
✓Whenthe audit logs are retrieved(123ms)
✓Thenthe audit log response should contain the order creation entry(22ms)
✓Audit steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Audit steps response should contain [ a => a.Action == AuditLogDefaults.CreatedAction && a.EntityType == AuditLogDefaults.OrderEntityType && a.Details.Contains('TestCustomer_3003254498391496470') ](0ms)
✓Andthe cow service should have received a milk request(3ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ](0ms)
✓Andthe kitchen service should have received a preparation request(1ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ](0ms)
Diagrams
Details:lines
Breakfast Order
/orders - Creating and managing breakfast orders with event publishing
Creating an order publishes events and notifies the kitchenA valid order should be created and an event published Happy Path926ms🔗Steps✓Givena pancake batch has been created(11ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Anda valid order request for the created batch(0ms)
✓Whenthe breakfast order is placed(9ms)
✓Thenthe order response should contain a complete order(0ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response customer name should be 'TestCustomer_7643611584290268907'(0ms)
✓Order steps response items should have count 1(0ms)
✓Andan order created event should have been published(900ms)
✓Event store should not be null(0ms)
✓Andthe kitchen service should have received a preparation request(0ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ](0ms)
Diagrams
Details:lines
Creating an order produces audit and recipe logsCreating an order should produce an audit log entry and events 345ms🔗Steps✓Givena pancake batch has been created(10ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Anda valid order request for the created batch(0ms)
✓Whenthe breakfast order is placed(9ms)
✓Thenthe order response should contain a complete order(0ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response customer name should be 'TestCustomer_6447564057217514397'(0ms)
✓Order steps response items should have count 1(0ms)
✓Andan order created event should have been published(307ms)
✓Event store should not be null(0ms)
✓Anda recipe log should have been published to kafka(14ms)
✓Kafka store should not be null(0ms)
Diagrams
Details:lines
Creating an order writes an outbox message for reliable deliveryCreating an order should write an outbox message that gets processed 162ms🔗Steps✓Givena pancake batch has been created(15ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Anda valid order request for the created batch(1ms)
✓Whenthe breakfast order is placed(17ms)
✓Thenthe order response should contain a complete order(5ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response customer name should be 'TestCustomer_6937937718522117583'(0ms)
✓Order steps response items should have count 1(0ms)
✓Andan outbox message should have been written for the order created event(74ms)
✓Outbox messages should contain [ m => m.EventType == 'OrderCreatedEvent', $"an outbox message should exist for event type '{eventType}'" ](0ms)
✓Andthe outbox message should have been processed(42ms)
Diagrams
Details:lines
Chef Notes Management
/chef-notes - Creating, retrieving, and updating chef notes (MongoDB)
Creating a chef note should return the created note Happy Path20ms🔗Steps
✓Givena valid chef note request(2ms)
✓Whenthe note is submitted(4ms)
✓Thenthe response should contain the created note(11ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response recipe name should be 'Recipe-be544c9c26a44576a5fd7d3cba7c9b26'(0ms)
✓Post steps response note text should be "Remember to fold the batter gently to keep it fluffy."(0ms)
✓Post steps response category should be "Technique"(0ms)
✓Post steps response note id should not be null or empty(0ms)
Diagrams
Details:lines
Creating a note with missing note text should return bad request 18ms🔗Steps
✓Givena note request with missing note text(6ms)
✓Whenthe note is submitted(5ms)
✓Thenthe note response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Creating a note with missing recipe name should return bad request 9ms🔗Steps
✓Givena note request with a missing recipe name(1ms)
✓Whenthe note is submitted(1ms)
✓Thenthe note response should indicate bad request(4ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Listing notes by recipe should return matching notes 161ms🔗Steps✓Givena chef note exists(75ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe notes are listed by recipe(61ms)
✓Thenthe list response should contain the note(13ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ n => n.NoteId == '7abd6d60-c0a1-4424-bf13-a72caaa70e08' ](0ms)
Diagrams
Details:lines
Retrieving a non-existent note should return not found 14ms🔗Steps
✓Whena non-existent note is retrieved(12ms)
✓Thenthe get response should indicate not found(1ms)
✓Get steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Retrieving an existing note by id should return the note 95ms🔗Steps✓Givena chef note exists(11ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe note is retrieved by id(72ms)
✓Thenthe get response should contain the note(5ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response note id should be 'aacbfe04-b5cf-456d-b37e-0b9cbbb57beb'(0ms)
✓Get steps response recipe name should be 'Recipe-bc65512658de495c8eb7dc2cba2748c8'(0ms)
Diagrams
Details:lines
Updating a non-existent note should return not found 145ms🔗Steps
✓Whena non-existent note is updated(142ms)
✓Thenthe note update response should indicate not found(1ms)
✓Patch steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Updating an existing note should return the updated note 73ms🔗Steps✓Givena chef note exists(2ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe note is updated(45ms)
✓Thenthe update response should contain the modified note(24ms)
✓Patch steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response note id should be 'feeef16c-fd05-45de-aa0a-5b2f0ffab485'(0ms)
✓Patch steps response note text should be "Updated: Use unsalted butter for better flavour control."(0ms)
✓Patch steps response category should be "Ingredients"(0ms)
✓Patch steps response updated at should not be null(0ms)
Diagrams
Details:lines
Complete Order Lifecycle
/orders - Complete order lifecycle from creation through to completion
An order should progress through all status transitions to completion Happy Path221ms🔗Steps✓Givena pancake batch has been created(14ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Anda breakfast order has been placed for the batch(54ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe order progresses through all statuses to completed(47ms)
✓Patch steps response message status code should be OK(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Thenthe completed order should be retrievable with all details(57ms)
✓Get order steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get order steps response order id should be '5fa5add7-6662-4ef4-99bf-60d57db01441'(0ms)
✓Get order steps response status should be Completed(0ms)
✓Get order steps response customer name should be 'LifecycleTestCustomer_942288103579178619'(0ms)
✓Andan audit log entry should exist for the order(34ms)
✓Audit steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Audit steps response should contain [ a => a.Action == AuditLogDefaults.CreatedAction && a.EntityType == AuditLogDefaults.OrderEntityType && a.Details.Contains('LifecycleTestCustomer_942288103579178619') ](0ms)
✓Andthe cow service should have received a milk request(1ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ](0ms)
✓Andthe kitchen service should have received a preparation request(1ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ](0ms)
Diagrams
Details:lines
Correlation Id
Cross-cutting - X-Correlation-Id header propagation across API responses
Provided correlation IDs are echoed backA request with a correlation id should return the same id in the response Happy Path78ms🔗Steps
✓Givena request with a known correlation id(7ms)
✓Whenthe request is sent to the menu endpoint(57ms)
✓Thenthe response should contain the same correlation id(3ms)
✓Response contains correlation id header should be true(0ms)
✓First correlation id header value should be '1e349f3e-6944-442a-bbf5-a140db013131'(0ms)
Diagrams
Details:lines
Missing correlation IDs are generated automaticallyA request without a correlation id should have one generated in the response 13ms🔗Steps
✓Whena request without a correlation id is sent to the menu endpoint(4ms)
✓Thenthe response should contain a generated correlation id(3ms)
✓Response contains correlation id header should be true(0ms)
✓First correlation id header value should not be null or empty(0ms)
Customer preferences support CRUD operationsSaving customer preferences should return the saved preferences Happy Path23ms🔗Steps
✓Givena valid customer preference request(3ms)
✓Whenthe customer preferences are saved(12ms)
✓Thenthe preference response should contain the saved preferences(5ms)
✓Put steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Put steps response preferred milk type should be "Oat"(0ms)
✓Put steps response favourite item should be "Blueberry Pancakes"(0ms)
Diagrams
Details:lines
Retrieving existing customer preferences should return the preferences 34ms🔗Steps✓Givencustomer preferences exist(4ms)
✓Put steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe customer preferences are retrieved(22ms)
✓Thenthe preference get response should contain the preferences(5ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response customer id should be '191f8b5d7655429489b7b9886735c061'(0ms)
✓Get steps response preferred milk type should be "Oat"(0ms)
✓Get steps response likes extra toppings should be true(0ms)
Diagrams
Details:lines
Non-existent preferences cannot be retrievedRetrieving non-existent customer preferences should return not found 104ms🔗Steps
✓Whennon-existent customer preferences are retrieved(96ms)
✓Thenthe preference get response should indicate not found(1ms)
✓Get steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Preference requests must pass validationSaving customer preferences with missing customer name should return bad request 14ms🔗Steps
✓Givena customer preference request with missing customer name(5ms)
✓Whenthe customer preferences are saved(4ms)
✓Thenthe preference response should indicate bad request(1ms)
✓Put steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Customer preferences support CRUD operationsUpdating customer preferences should return the updated preferences 128ms🔗Steps✓Givencustomer preferences exist(105ms)
✓Put steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe customer preferences are updated(14ms)
✓Thenthe preference update response should contain the updated values(7ms)
✓Put steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Put steps response preferred milk type should be "Almond"(0ms)
✓Put steps response favourite item should be "Belgian Waffles"(0ms)
Diagrams
Details:lines
Daily Specials Idempotency
/daily-specials/orders - Idempotent order creation using Idempotency-Key header
Submitting the same order with different idempotency keys should return different confirmations 153ms🔗Steps
✓Giventhe cinnamon swirl order count is reset(36ms)
✓Andan order request for the same special(2ms)
✓Whenthe order is submitted with two different idempotency keys(108ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Thenthe responses should have different confirmation ids(1ms)
✓First confirmation id should not be 'accfe792-18d8-4c96-a61e-cfcdf9dd9b29'(0ms)
Diagrams
Details:lines
Submitting the same order with the same idempotency key should return the same confirmation 22ms🔗Steps
✓Giventhe cinnamon swirl order count is reset(36ms)
✓Andan order request with an idempotency key(2ms)
✓Whenthe order is submitted twice with the same idempotency key(13ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Thenboth responses should return the same confirmation id(1ms)
✓First confirmation id should be '79233e77-f000-44a7-aa41-386c5916eb32'(0ms)
Diagrams
Details:lines
Daily Specials Not Found
/daily-specials/orders - Ordering a non-existent daily special
Ordering a non-existent daily special should return not found 76ms🔗Steps
✓Givena daily special order request for a non-existent special(4ms)
✓Whenthe daily special order is submitted(57ms)
✓Thenthe daily special response should indicate not found(7ms)
✓Post steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Daily Specials Ordering
/daily-specials - Ordering daily specials with threshold limits
Valid daily special orders are fulfilledA valid daily special order should return a confirmation Happy Path20ms🔗Steps
✓Giventhe cinnamon swirl order count is reset(1ms)
✓Anda valid daily special order request for cinnamon swirl(4ms)
✓Whenthe daily special order is submitted(3ms)
✓Thenthe daily special order response should contain a valid confirmation(4ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response special id should be CinnamonSwirlId(0ms)
✓Post steps response order confirmation id should not be empty(0ms)
Diagrams
Details:lines
Orders are rejected when the daily limit is reachedOrdering a daily special beyond the threshold should return a conflict response IgnoreIfExternalSut30ms🔗Steps
✓Giventhe matcha waffles order count is reset(3ms)
✓Andthe matcha waffles special has been ordered up to the configured limit(6ms)
✓Post steps response message status code should be Created(0ms)
✓Whenanother order is placed for the matcha waffles special(11ms)
✓Thenthe response should indicate the daily special is sold out(7ms)
✓Post steps response message status code should be Conflict(0ms)
Diagrams
Details:lines
Remaining quantity decreases with each orderRemaining quantity should decrease after each order IgnoreIfExternalSut22ms🔗Steps
✓Giventhe lemon ricotta order count is reset(4ms)
✓Anda daily special order for lemon ricotta of quantity one is placed(5ms)
✓Post steps response message status code should be Created(0ms)
✓Whenthe available daily specials are requested(1ms)
✓Thenthe lemon ricotta special should have one fewer remaining(9ms)
✓Response content is valid json should be true(0ms)
✓Lemon ricotta remaining quantity should be MaxOrdersPerSpecial - 1(0ms)
Diagrams
Details:lines
Valid daily special orders are fulfilledThe daily specials endpoint should return all available specials 30ms🔗Steps
✓Whenthe available daily specials are requested(17ms)
✓Thenthe daily specials response should contain all expected specials(11ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response should have count ExpectedSpecialsCount(0ms)
Diagrams
Details:lines
Daily Specials Validation
/daily-specials/orders - Input validation for daily special orders
Daily specials order endpoint is called with invalid fields should return a bad request response 2/2 passed34ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Quantity
0
Quantity must be > zero
Quantity must be greater than zero.
Bad Request
Passed
26ms
2
SpecialId
SpecialId is required
'Special Id' is required.
Bad Request
Passed
8ms
Steps
✓Givena valid daily special order request with "Quantity" set to "0"(4ms)
✓Whenthe invalid daily special order request is submitted(10ms)
✓Thenthe daily special response should contain error "Quantity must be greater than zero." with status "Bad Request"(7ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Quantity must be greater than zero.') ](0ms)
Steps
✓Givena valid daily special order request with "SpecialId" set to ""(0ms)
✓Whenthe invalid daily special order request is submitted(2ms)
✓Thenthe daily special response should contain error "'Special Id' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Special Id' is required.') ](0ms)
Diagrams
Details:lines
Degraded Health Check
/health - Health check endpoint reporting degraded status when downstream services are unavailable
Health check should report degraded when multiple downstream services are unavailable SkipUnlessFakesControllable202ms🔗Steps
✓Giventhe cow service is configured to be unreachable(2ms)
✓Andthe supplier service is configured to be unreachable(1ms)
✓Whenthe health check endpoint is called(186ms)
✓Thenthe health check response should indicate a degraded status(3ms)
✓Health response status code should be OK(0ms)
✓Health check result status should be Degraded(0ms)
✓Andthe cow service dependency should report degraded(2ms)
✓Health check result results should contain key CowService(0ms)
✓Cow service health status should be Degraded(0ms)
✓Andthe supplier service dependency should report degraded(2ms)
✓Health check result results should contain key SupplierService(0ms)
✓Supplier service health status should be Degraded(0ms)
Diagrams
Details:lines
Health check should report degraded when the cow service is unavailable SkipUnlessFakesControllable219ms🔗Steps
✓Giventhe cow service is configured to be unreachable(0ms)
✓Whenthe health check endpoint is called(211ms)
✓Thenthe health check response should indicate a degraded status(0ms)
✓Health response status code should be OK(0ms)
✓Health check result status should be Degraded(0ms)
✓Andthe cow service dependency should report degraded(0ms)
✓Health check result results should contain key CowService(0ms)
✓Cow service health status should be Degraded(0ms)
Diagrams
Details:lines
Downstream Error Health Check
/health - Health check reports degraded when a downstream service returns a non-success HTTP status
Health check should report degraded when a downstream service returns a non-success status SkipUnlessFakesControllable215ms🔗Steps
✓Giventhe kitchen service health check is configured to use a failing endpoint(178ms)
✓Whenthe health check endpoint is called(27ms)
✓Thenthe health check response should indicate a degraded status(0ms)
✓Health response status code should be OK(0ms)
✓Health check result status should be Degraded(0ms)
✓Andthe kitchen service dependency should report degraded with a status code description(5ms)
✓Health check result results should contain key KitchenService(0ms)
✓Kitchen service health status should be Degraded(0ms)
✓Kitchen service health description should contain "503"(0ms)
Diagrams
Details:lines
Equipment Alerts
/graphql - Querying equipment alerts populated by Event Hub consumption
Equipment alerts should contain data ingested via Event Hub consumer Happy Path76ms🔗Steps✓Givena pancake batch has been created(17ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Whenthe equipment alerts are queried via graphql(18ms)
✓Thenthe graphql response should contain the equipment alert record(32ms)
✓Graph ql steps response message status code should be OK(0ms)
/equipment-readings - Recording and monitoring kitchen equipment readings (ClickHouse)
Recording an equipment reading should return the created record Happy Path147ms🔗Steps
✓Givena valid equipment reading request(3ms)
✓Whenthe equipment reading is recorded(107ms)
✓Thenthe reading response should contain the created record(24ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response equipment id should be 'Oven-5f81d0099129458d9280f7e33675eab5'(0ms)
✓Post steps response value should be '5m'(0ms)
✓Post steps response reading id should not be null or empty(0ms)
Diagrams
Details:lines
Deleting a reading should remove it from the list 47ms🔗Steps✓Givenan equipment reading record has been created(8ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe reading is deleted(26ms)
✓Thenthe reading delete response should indicate no content(1ms)
✓Delete steps response message status code should be NoContent(0ms)
✓Andthe reading should no longer be listed(8ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should not contain [ r => r.ReadingId == '715de419-87b8-473d-b48d-8a149b98ed82' ](0ms)
Diagrams
Details:lines
Listing readings by equipment should return matching records 119ms🔗Steps✓Givenan equipment reading record has been created(38ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe readings are listed by equipment(58ms)
✓Thenthe reading list response should contain the record(18ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ r => r.ReadingId == '6555adb5-3760-4367-89e4-cfd6080e452d' ](0ms)
Diagrams
Details:lines
Recording a reading with missing metric should return bad request 17ms🔗Steps
✓Givenan equipment reading request with a missing metric(1ms)
✓Whenthe equipment reading is recorded(7ms)
✓Thenthe reading post response should indicate bad request(5ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Recording a reading with zero value should return bad request 19ms🔗Steps
✓Givenan equipment reading request with zero value(2ms)
✓Whenthe equipment reading is recorded(15ms)
✓Thenthe reading post response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Feedback Management
/feedback - Submitting and retrieving customer feedback
Feedback can be submitted and retrievedSubmitting feedback should return the created feedback Happy Path26ms🔗Steps
✓Givena valid feedback request(0ms)
✓Whenthe feedback is submitted(16ms)
✓Thenthe feedback response should contain the created feedback(5ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response customer name should be 'CustomerName'(0ms)
✓Post steps response rating should be 4(0ms)
Diagrams
Details:lines
Listing feedback for an order should return the feedback 1.7s🔗Steps✓Givena feedback entry exists(1.2s)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe feedback is retrieved by order id(518ms)
✓Thenthe feedback list response should contain the feedback(12ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ f => f.FeedbackId == '1619ab39-0a72-4970-a82b-e4ef1e25a846' ](0ms)
Diagrams
Details:lines
Retrieving existing feedback by id should return the feedback 31ms🔗Steps✓Givena feedback entry exists(4ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe feedback is retrieved by id(14ms)
✓Thenthe feedback get response should contain the feedback(10ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response feedback id should be 'aff54994-384e-45c6-b100-636da89c1e94'(0ms)
✓Get steps response customer name should be 'CustomerName'(0ms)
✓Get steps response rating should be 4(0ms)
Diagrams
Details:lines
Non-existent feedback cannot be retrievedRetrieving non-existent feedback should return not found 60ms🔗Steps
✓Whena non-existent feedback is retrieved(51ms)
✓Thenthe feedback get response should indicate not found(7ms)
✓Get steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Feedback requests must pass validationSubmitting feedback with invalid rating should return bad request 8ms🔗Steps
✓Givena feedback request with an invalid rating(2ms)
✓Whenthe feedback is submitted(4ms)
✓Thenthe feedback response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Submitting feedback with missing customer name should return bad request 11ms🔗Steps
✓Givena feedback request with missing customer name(3ms)
✓Whenthe feedback is submitted(4ms)
✓Thenthe feedback response should indicate bad request(1ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Goat Milk Downstream Failure
/goat-milk - Handling downstream Goat Service failures
Requesting goat milk when the goat service is unavailable should return a bad gateway response SkipUnlessFakesControllable126ms🔗Steps
✓Giventhe goat service will return service unavailable(4ms)
✓Whengoat milk is requested(106ms)
✓Thenthe goat milk response should indicate a bad gateway(10ms)
✓Goat milk steps response message status code should be BadGateway(0ms)
✓Goat milk error response body should contain GoatServiceUnavailableTitle(0ms)
Diagrams
Details:lines
Requesting goat milk when the goat service returns an invalid response should return a bad gateway response SkipUnlessFakesControllable30ms🔗Steps
✓Giventhe goat service will return an invalid response(10ms)
✓Whengoat milk is requested(16ms)
✓Thenthe goat milk response should indicate a bad gateway(0ms)
✓Goat milk steps response message status code should be BadGateway(0ms)
✓Goat milk error response body should contain GoatServiceUnavailableTitle(0ms)
Diagrams
Details:lines
Goat Milk Feature Flag
/goat-milk - Goat milk availability controlled by feature flag
Goat milk is available when the feature flag is enabledGoat milk endpoint should return fresh goat milk when feature is enabled IgnoreIfExternalSut264ms🔗Steps
✓Giventhe goat milk feature flag is enabled(172ms)
✓Whengoat milk is requested(57ms)
✓Thenthe goat milk response should contain fresh goat milk(32ms)
✓Goat milk steps response message status code should be OK(0ms)
✓Goat milk steps goat milk response goat milk should be FreshGoatMilk(0ms)
Diagrams
Details:lines
Goat milk is hidden when the feature flag is disabledGoat milk endpoint should return not found when feature is disabled IgnoreIfExternalSut212ms🔗Steps
✓Giventhe goat milk feature flag is disabled(174ms)
✓Whengoat milk is requested(27ms)
✓Thenthe goat milk response should indicate feature disabled(3ms)
✓Goat milk steps response message status code should be NotFound(0ms)
✓Goat milk feature disabled response body should contain FeatureDisabled(0ms)
Diagrams
Details:lines
Goat Milk Sourcing
/goat-milk - Retrieving goat milk from the Goat Service
A valid goat milk request should return fresh goat milk Happy Path7ms🔗Steps
✓Whengoat milk is requested(3ms)
✓Thenthe goat milk response should contain fresh goat milk(0ms)
✓Goat milk steps response message status code should be OK(0ms)
✓Goat milk steps goat milk response goat milk should be FreshGoatMilk(0ms)
Diagrams
Details:lines
Header Propagation
/milk; /menu - X-Correlation-Id header propagation to downstream services
A request with a correlation id should forward it to the cow service Happy PathSkipUnlessFakesControllable9ms🔗Steps
✓Givena request with a known correlation id(0ms)
✓Whenmilk is requested with the correlation id(5ms)
✓Thenthe cow service should have received the correlation id(1ms)
✓Requests should not be empty(0ms)
✓Request headers should contain key CorrelationId(0ms)
✓Request headers[ custom headers correlation id] should be 'a777c4ba-f3b5-4b36-af73-85a5ae142b60'(0ms)
Diagrams
Details:lines
A request with a correlation id should forward it to the supplier service SkipUnlessFakesControllable27ms🔗Steps
✓Givena request with a known correlation id(0ms)
✓Andthe menu cache is cleared(13ms)
✓Whenthe menu is requested with the correlation id(6ms)
✓Thenthe supplier service should have received the correlation id(3ms)
✓Requests should not be empty(0ms)
✓Request headers should contain key CorrelationId(0ms)
✓Request headers[ custom headers correlation id] should be '202118c9-987f-4df0-ada9-a32491eebba9'(0ms)
Diagrams
Details:lines
Health Check
/health - Health check endpoint with dependency status for monitoring
The health check endpoint should return a healthy status with dependency details Happy Path31ms🔗Steps
✓Whenthe health check endpoint is called(7ms)
✓Thenthe health check response should indicate healthy with all dependencies(18ms)
✓Health response status code should be OK(0ms)
✓Health check result should not be null(0ms)
✓Health check result status should be Healthy(0ms)
✓Health check result results should contain key CowService(0ms)
✓Health check result results should contain key GoatService(0ms)
✓Health check result results should contain key SupplierService(0ms)
✓Health check result results should contain key KitchenService(0ms)
✓Health check result results should contain key CosmosDb(0ms)
✓Health check result results should contain key Kafka(0ms)
Diagrams
Details:lines
Health Check Detail
/health - Health check response includes detailed entry descriptions and data
The health check response should include description and data for each entry 162ms🔗Steps
✓Whenthe health check endpoint is called(124ms)
✓Thenthe health check response should contain detailed entries(33ms)
✓Health response status code should be OK(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check entry status should not be null or empty $"'{entry.Key}' should have a status"(0ms)
✓Health check result results should contain key 'CowService'(0ms)
✓Health check description should not be null or empty $"'{checkName}' should have a description"(0ms)
✓Health check result results should contain key 'GoatService'(0ms)
✓Health check description should not be null or empty $"'{checkName}' should have a description"(0ms)
✓Health check result results should contain key 'SupplierService'(0ms)
✓Health check description should not be null or empty $"'{checkName}' should have a description"(0ms)
✓Health check result results should contain key 'KitchenService'(0ms)
✓Health check description should not be null or empty $"'{checkName}' should have a description"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
✓Health check entry data should not be null $"'{entry.Key}' should have a data object"(0ms)
Diagrams
Details:lines
Heartbeat
/heartbeat - Heartbeat endpoint confirming the service is running
The heartbeat endpoint should return a running message Happy Path20ms🔗Steps
✓Whenthe heartbeat endpoint is called(7ms)
✓Thenthe heartbeat response should indicate the service is running(7ms)
✓Heartbeat response status code should be OK(0ms)
✓Result should not be null(0ms)
✓Result status should be HeartbeatStatus(0ms)
Diagrams
Details:lines
Ingredient Usage Analytics
/ingredient-usage - Recording and summarising ingredient usage (BigQuery)
Recording ingredient usage should return the created record Happy Path25ms🔗Steps
✓Givena valid ingredient usage request(3ms)
✓Whenthe ingredient usage is recorded(7ms)
✓Thenthe usage response should contain the created record(11ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response ingredient name should be 'Flour-bcfbbe2fd5634bd58d9982b71a738284'(0ms)
✓Post steps response quantity used should be '5m'(0ms)
✓Post steps response usage id should not be null or empty(0ms)
Diagrams
Details:lines
Getting usage summary should return aggregated data 114ms🔗Steps✓Givenan ingredient usage record has been created(7ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe usage summary is requested(93ms)
✓Thenthe summary should contain aggregated data(10ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps summary response should contain [ s => s.IngredientName == 'Flour-d75d667875a84e18a8b480d7f46e4ec9' ](0ms)
Diagrams
Details:lines
Listing usage by ingredient should return matching records 589ms🔗Steps✓Givenan ingredient usage record has been created(60ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe usage is listed by ingredient name(504ms)
✓Thenthe usage list response should contain the record(20ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ u => u.IngredientName == 'Flour-d9ee22e7f57f443592d3381a365a949c' ](0ms)
Diagrams
Details:lines
Recording usage with missing ingredient name should return bad request 495ms🔗Steps
✓Givenan ingredient usage request with a missing ingredient name(40ms)
✓Whenthe ingredient usage is recorded(399ms)
✓Thenthe usage post response should indicate bad request(4ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Recording usage with zero quantity should return bad request 8ms🔗Steps
✓Givenan ingredient usage request with zero quantity(4ms)
✓Whenthe ingredient usage is recorded(1ms)
✓Thenthe usage post response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Ingredient Waste Tracking
/ingredient-waste - Recording and managing ingredient waste (BigQuery)
Recording ingredient waste should return the created record Happy Path22ms🔗Steps
✓Givena valid ingredient waste request(0ms)
✓Whenthe waste is recorded(13ms)
✓Thenthe waste response should contain the created record(5ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response ingredient name should not be null or empty(0ms)
✓Post steps response quantity wasted should be '5m'(0ms)
✓Post steps response waste id should not be null or empty(0ms)
✓Post steps response reason should be "Expired before use"(0ms)
Diagrams
Details:lines
Deleting a waste record should return no content 63ms🔗Steps✓Givenan ingredient waste record has been created(17ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe waste record is deleted(43ms)
✓Thenthe delete response should indicate no content(1ms)
✓Delete steps response message status code should be NoContent(0ms)
Diagrams
Details:lines
Listing waste by recipe should return matching records 556ms🔗Steps✓Givenan ingredient waste record has been created(55ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe waste is listed by recipe(476ms)
✓Thenthe waste list response should contain the record(19ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ w => w.WasteId == '4544d809-3a77-4d39-807a-0fe25ce03b0c' ](0ms)
Diagrams
Details:lines
Recording waste with missing ingredient name should return bad request 9ms🔗Steps
✓Givena waste request with a missing ingredient name(1ms)
✓Whenthe waste is recorded(5ms)
✓Thenthe waste post response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Recording waste with missing reason should return bad request 11ms🔗Steps
✓Givena waste request with a missing reason(1ms)
✓Whenthe waste is recorded(7ms)
✓Thenthe waste post response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Recording waste with zero quantity should return bad request 24ms🔗Steps
✓Givena waste request with zero quantity(4ms)
✓Whenthe waste is recorded(15ms)
✓Thenthe waste post response should indicate bad request(1ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Inventory Management
/inventory - Managing ingredient inventory with full CRUD operations
Inventory items support full CRUD operationsAdding a new inventory item should return the created item Happy Path11ms🔗Steps
✓Givena valid inventory item request(0ms)
✓Whenthe inventory item is submitted(5ms)
✓Thenthe inventory response should contain the created item(4ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response name should be 'Name'(0ms)
✓Post steps response category should be "Dry Goods"(0ms)
Diagrams
Details:lines
Deleting an inventory item should return no content 100ms🔗Steps✓Givenan inventory item exists(8ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe inventory item is deleted(87ms)
✓Thenthe inventory delete response should indicate no content(2ms)
✓Delete steps response message status code should be NoContent(0ms)
Diagrams
Details:lines
Listing all inventory items should return all items 133ms🔗Steps✓Givenan inventory item exists(28ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenall inventory items are requested(92ms)
✓Thenthe inventory list response should contain the item(11ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ i => i.Id == '2' ](0ms)
Diagrams
Details:lines
Non-existent inventory items cannot be retrievedRetrieving a non-existent inventory item should return not found 7ms🔗Steps
✓Whena non-existent inventory item is retrieved(4ms)
✓Thenthe inventory get response should indicate not found(1ms)
✓Get steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Inventory items support full CRUD operationsRetrieving an existing inventory item should return the item 1.6s🔗Steps✓Givenan inventory item exists(843ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe inventory item is retrieved by id(699ms)
✓Thenthe inventory get response should contain the item(23ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response id should be '1'(0ms)
✓Get steps response name should be 'Name'(0ms)
Diagrams
Details:lines
Updating an inventory item should return the updated item 88ms🔗Steps✓Givenan inventory item exists(18ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe inventory item is updated(62ms)
✓Thenthe inventory update response should contain the updated values(5ms)
✓Put steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Put steps response category should be "Updated Category"(0ms)
Diagrams
Details:lines
Kitchen Service Failure
/orders - Creating orders when the Kitchen Service returns an error
Creating an order when the kitchen service returns an error should still create the order SkipUnlessFakesControllable86ms🔗Steps✓Givena pancake batch has been created(14ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Anda valid order request for the created batch(1ms)
✓Andthe kitchen service is configured to return busy(1ms)
✓Whenthe breakfast order is placed(50ms)
✓Thenthe order should still be created successfully despite the kitchen failure(6ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response order id should not be empty(0ms)
Diagrams
Details:lines
Menu Availability
/menu - Checking menu item availability from ingredient sources
The menu endpoint should return all menu items with availability status Happy PathMenuAvailability261ms🔗Steps
✓Whenthe menu is requested(53ms)
✓Thenthe menu response should contain all menu items(14ms)
✓Menu steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Menu steps response should contain [ m => m.Name == MenuDefaults.ClassicPancakes ](0ms)
✓Menu steps response should contain [ m => m.Name == MenuDefaults.BelgianWaffles ](0ms)
✓Menu steps response should contain [ m => m.Name == MenuDefaults.GoatMilkPancakes ](0ms)
Diagrams
Details:lines
Menu Caching
/menu - Menu response caching behaviour
Menu responses should be cached and returned even when supplier becomes unavailable SkipUnlessFakesControllableMenuCaching247ms🔗Steps✓Giventhe menu has been requested and cached(65ms)
✓Menu steps response message status code should be OK(0ms)
✓Andthe supplier service is then made unavailable(4ms)
✓Whenthe menu is requested again(12ms)
✓Thenthe menu response should still return available items(5ms)
✓Steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Steps response should contain [ m => m.IsAvailable ](0ms)
Diagrams
Details:lines
Menu Downstream Failure
/menu - Menu behaviour when Supplier Service is unavailable
All menu items should be marked unavailable when the supplier service is down SkipUnlessFakesControllableMenuDownstreamFailure360ms🔗Steps
✓Giventhe supplier service will return service unavailable(27ms)
✓Whenthe menu is requested(57ms)
✓Thenthe menu response should mark all items as unavailable(15ms)
✓Menu steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Menu steps response should only contain [ m => m.IsAvailable == false ](0ms)
Diagrams
Details:lines
Milk Downstream Failure
/milk - Handling downstream Cow Service failures
Requesting milk when the cow service is unavailable should return a bad gateway response SkipUnlessFakesControllable10ms🔗Steps
✓Giventhe cow service will return service unavailable(1ms)
✓Whenmilk is requested(4ms)
✓Thenthe milk response should indicate a bad gateway(0ms)
✓Milk steps response message status code should be BadGateway(0ms)
✓Milk error response body should contain CowServiceUnavailableTitle(0ms)
Diagrams
Details:lines
Requesting milk when the cow service returns an invalid response should return a bad gateway response SkipUnlessFakesControllable21ms🔗Steps
✓Giventhe cow service will return an invalid response(1ms)
✓Whenmilk is requested(6ms)
✓Thenthe milk response should indicate a bad gateway(4ms)
✓Milk steps response message status code should be BadGateway(0ms)
✓Milk error response body should contain CowServiceUnavailableTitle(0ms)
Diagrams
Details:lines
Requesting milk when the cow service times out should return a bad gateway response SkipUnlessFakesControllable9ms🔗Steps
✓Giventhe cow service will return a timeout(0ms)
✓Whenmilk is requested(6ms)
✓Thenthe milk response should indicate a bad gateway(0ms)
✓Milk steps response message status code should be BadGateway(0ms)
✓Milk error response body should contain CowServiceUnavailableTitle(0ms)
Diagrams
Details:lines
Order Cross Field Validation
/orders - Cross-field validation with configurable item limits
An order at the maximum items per order should be accepted IgnoreIfExternalSut267ms🔗Steps
✓Giventhe maximum items per order is configured to two(157ms)
✓Anda pancake batch has been created(57ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order request with two items(1ms)
✓Whenthe order is submitted(44ms)
✓Thenthe response should indicate success(2ms)
✓Order steps response message status code should be Created(0ms)
Diagrams
Details:lines
An order exceeding the maximum items per order should be rejected IgnoreIfExternalSut133ms🔗Steps
✓Giventhe maximum items per order is configured to two(157ms)
✓Anda pancake batch has been created(57ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order request with three items(1ms)
✓Whenthe order is submitted(16ms)
✓Thenthe response should indicate a validation error(1ms)
✓Order steps response message status code should be BadRequest(0ms)
✓Andthe error message should reference the item limit(3ms)
✓Order validation error response body should contain "Items"(0ms)
Diagrams
Details:lines
Order Pagination
/orders - Paginated listing of breakfast orders
Listing orders should return a paginated response Happy Path135ms🔗Steps✓Givenmultiple orders have been created(73ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response message status code should be Created(0ms)
✓Order steps response message status code should be Created(0ms)
✓Whenorders are listed with default pagination(50ms)
✓Thenthe paginated response should contain the orders(8ms)
✓List steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓List steps response items should have count greater than or equal to '2'(0ms)
✓Andthe paginated response should have correct page metadata(0ms)
✓Response content is valid json should be true(0ms)
✓List steps response page should be greater than or equal to 1(0ms)
✓List steps response total count should be greater than or equal to '2'(0ms)
Diagrams
Details:lines
Listing orders when none exist should return an empty page IgnoreIfNeedsDirectDbAccessIgnoreUnlessInMemoryDb75ms🔗Steps
✓Whenorders are listed with default pagination(67ms)
✓Thenthe paginated response should be empty(5ms)
✓List steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
Diagrams
Details:lines
Listing orders with a small page size should limit results 285ms🔗Steps✓Givenmultiple orders have been created(244ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response message status code should be Created(0ms)
✓Order steps response message status code should be Created(0ms)
✓Whenorders are listed with page 1 and page size 1(38ms)
✓Thenthe paginated response should have correct page metadata(0ms)
✓Response content is valid json should be true(0ms)
✓List steps response page should be greater than or equal to 1(0ms)
✓List steps response total count should be greater than or equal to '2'(0ms)
Diagrams
Details:lines
Requesting the second page should return different orders 237ms🔗Steps✓Givenmultiple orders have been created(81ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response message status code should be Created(0ms)
✓Order steps response message status code should be Created(0ms)
✓Whenorders are listed with page 2 and page size 1(139ms)
✓Thenthe paginated response should have correct page metadata(9ms)
✓Response content is valid json should be true(0ms)
✓List steps response page should be greater than or equal to 1(0ms)
✓List steps response total count should be greater than or equal to '2'(0ms)
Diagrams
Details:lines
Order Rate Limiting
/orders - Rate limiting on order creation
Exceeding the rate limit should return too many requests IgnoreIfExternalSut427ms🔗Steps
✓Giventhe rate limit is configured to allow one request per window(157ms)
✓Anda pancake batch has been created(189ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Anda valid order request(1ms)
✓Whenthe order is submitted twice in rapid succession(65ms)
✓Thenthe first request should succeed(6ms)
✓First response status code should be Created(0ms)
✓Andthe second request should be rate limited(1ms)
✓Second response status code should be TooManyRequests(0ms)
Diagrams
Details:lines
Order Retrieval
/orders - Retrieving orders by ID
Existing orders can be retrievedA created order should be retrievable by its ID Happy PathIgnoreIfNeedsEventInfrastructure110ms🔗Steps✓Givenan order has been created(90ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe order is retrieved by id(9ms)
✓Thenthe order retrieval response should contain the order(6ms)
✓Get order steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get order steps response order id should be '108a1cc6-e4e0-4455-8ea6-b26cb3978ec0'(0ms)
Diagrams
Details:lines
Non-existent orders return not foundRetrieving a non-existent order should return not found 17ms🔗Steps
✓Whena non-existent order is retrieved(5ms)
✓Thenthe order retrieval response should indicate not found(1ms)
✓Get order steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Order Status Transition
/orders - Order status transitions following the order lifecycle
Valid status transitions are acceptedA valid status transition should update the order 4/4 passed174ms🔗
#
Input Parameters
Status
Duration
From Status
To Status
1
Created
Cancelled
Passed
24ms
2
Created
Preparing
Passed
26ms
3
Preparing
Ready
Passed
34ms
4
Ready
Completed
Passed
88ms
Steps✓Givenan order exists with status "Created"(18ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe order status is updated to "Cancelled"(4ms)
✓Thenthe order status should be updated successfully to "Cancelled"(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response status should be 'Cancelled'(0ms)
Steps✓Givenan order exists with status "Created"(19ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe order status is updated to "Preparing"(4ms)
✓Thenthe order status should be updated successfully to "Preparing"(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response status should be 'Preparing'(0ms)
Steps✓Givenan order exists with status "Preparing"(27ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Whenthe order status is updated to "Ready"(3ms)
✓Thenthe order status should be updated successfully to "Ready"(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response status should be 'Ready'(0ms)
Steps✓Givenan order exists with status "Ready"(55ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Whenthe order status is updated to "Completed"(10ms)
✓Thenthe order status should be updated successfully to "Completed"(20ms)
✓Patch steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response status should be 'Completed'(0ms)
Diagrams
Details:lines
Invalid status transitions are rejectedAn invalid status transition should return a conflict response 7/7 passed302ms🔗
#
Input Parameters
Status
Duration
From Status
To Status
1
Cancelled
Preparing
Passed
34ms
2
Cancelled
Ready
Passed
39ms
3
Completed
Preparing
Passed
61ms
4
Created
Completed
Passed
48ms
5
Created
Ready
Passed
30ms
6
Preparing
Cancelled
Passed
53ms
7
Ready
Preparing
Passed
34ms
Steps✓Givenan order exists with status "Cancelled"(27ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Whenthe order status is updated to "Preparing"(2ms)
✓Thenthe response should indicate an invalid state transition(0ms)
✓Patch steps response message status code should be Conflict(0ms)
Steps✓Givenan order exists with status "Cancelled"(35ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Whenthe order status is updated to "Ready"(2ms)
✓Thenthe response should indicate an invalid state transition(0ms)
✓Patch steps response message status code should be Conflict(0ms)
Steps✓Givenan order exists with status "Completed"(57ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Whenthe order status is updated to "Preparing"(2ms)
✓Thenthe response should indicate an invalid state transition(0ms)
✓Patch steps response message status code should be Conflict(0ms)
Steps✓Givenan order exists with status "Created"(35ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe order status is updated to "Completed"(4ms)
✓Thenthe response should indicate an invalid state transition(2ms)
✓Patch steps response message status code should be Conflict(0ms)
Steps✓Givenan order exists with status "Created"(26ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe order status is updated to "Ready"(2ms)
✓Thenthe response should indicate an invalid state transition(0ms)
✓Patch steps response message status code should be Conflict(0ms)
Steps✓Givenan order exists with status "Preparing"(48ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Whenthe order status is updated to "Cancelled"(1ms)
✓Thenthe response should indicate an invalid state transition(0ms)
✓Patch steps response message status code should be Conflict(0ms)
Steps✓Givenan order exists with status "Ready"(29ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Patch steps response message status code should be OK(0ms)
✓Whenthe order status is updated to "Preparing"(2ms)
✓Thenthe response should indicate an invalid state transition(0ms)
✓Patch steps response message status code should be Conflict(0ms)
Diagrams
Details:lines
Order Status Via G RPC
/grpc - Retrieving order status via gRPC
Order status via gRPC should return order details Happy Path60ms🔗Steps✓Givena pancake batch has been created(30ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order has been created for the batch(13ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response order id should not be empty(0ms)
✓Whenthe order status is requested via gRPC(11ms)
✓Thenthe gRPC response should contain the order details(3ms)
✓Grpc steps order status reply should not be null(0ms)
✓Grpc steps order status reply order id should be orderSteps.Response.OrderId.ToString()(0ms)
✓Grpc steps order status reply customer name should be 'TestCustomer_5203206899910891560'(0ms)
✓Grpc steps order status reply status should be Created(0ms)
Diagrams
Details:lines
Order status for non-existent order should return not found 98ms🔗Steps
✓Whenthe order status for a non-existent order is requested via gRPC(86ms)
✓Thenthe gRPC response should be a not found error(6ms)
✓Grpc steps rpc exception should not be null(0ms)
✓Grpc steps rpc exception status code should be NotFound(0ms)
Diagrams
Details:lines
Order Summaries
/graphql - Querying order summary reports via GraphQL
Order summaries should contain ingested order data Happy PathIgnoreIfNeedsDirectDbAccess1.2s🔗Steps
✓Givenan order has been created and ingested into the reporting database(69ms)
✓Whenthe order summaries are queried via graphql(1.1s)
✓Thenthe graphql response should contain the ingested order summary(14ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Graph ql steps order summaries should contain [ o => o.OrderId == '237721f2-388b-4d3d-bda4-f16a689b8486' && o.CustomerName == 'TestCustomer_6361274405633543047' && o.ItemCount == 3 && o.TableNumber == 7 ](0ms)
Diagrams
Details:lines
Order summaries should return an empty list when no orders exist 32ms🔗Steps
✓Whenthe order summaries are queried via graphql(18ms)
✓Thenthe graphql response should be successful(3ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Andthe order summaries list should be empty or not contain the test order(9ms)
✓Graph ql steps order summaries should not contain [ o => o.OrderId == 'f2b13e1d-5788-49c8-8ebd-c1022130d916' ](0ms)
Diagrams
Details:lines
Order Timings Analytics
/order-timings - Recording and summarising kitchen order timings (ClickHouse)
Recording an order timing should return the created record Happy Path489ms🔗Steps
✓Givena valid order timing request(36ms)
✓Whenthe order timing is recorded(430ms)
✓Thenthe timing response should contain the created record(19ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response station should be 'Griddle-e49741c5daa44762a0497c7ae34e0c50'(0ms)
✓Post steps response prep seconds should be '5m'(0ms)
✓Post steps response timing id should not be null or empty(0ms)
Diagrams
Details:lines
Getting the timing summary should return aggregated data 96ms🔗Steps✓Givenan order timing record has been created(9ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe timing summary is requested(74ms)
✓Thenthe summary should contain aggregated data for the station(10ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps summary response should contain [ s => s.Station == 'Griddle-78dfe54d0ab4442cabd0716ff33960cf' && s.TimingCount >= 1 ](0ms)
Diagrams
Details:lines
Listing timings by station should return matching records 142ms🔗Steps✓Givenan order timing record has been created(16ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe timings are listed by station(116ms)
✓Thenthe timing list response should contain the record(7ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ t => t.TimingId == '3aeead0f-fc66-4e0d-884c-bb7ac8eca9ac' ](0ms)
Diagrams
Details:lines
Recording a timing with missing station should return bad request 10ms🔗Steps
✓Givenan order timing request with a missing station(3ms)
✓Whenthe order timing is recorded(1ms)
✓Thenthe timing post response should indicate bad request(3ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Recording a timing with zero prep seconds should return bad request 21ms🔗Steps
✓Givenan order timing request with zero prep seconds(4ms)
✓Whenthe order timing is recorded(13ms)
✓Thenthe timing post response should indicate bad request(2ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Order Validation
/orders - Input validation for order creation and status updates
Order status update endpoint is called with invalid fields should return a bad request response 1/1 passed21ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Status
Status is required
'Status' is required.
Bad Request
Passed
21ms
Steps
✓Givena valid status update request with "Status" set to ""(2ms)
✓Whenthe invalid status update request is submitted(6ms)
✓Thenthe status update response should contain error "'Status' is required." with status "Bad Request"(10ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Status' is required.') ](0ms)
Diagrams
Details:lines
Orders endpoint is called with invalid fields should return a bad request response 5/5 passed78ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
CustomerName
Customer name is required
'Customer Name' is required.
Bad Request
Passed
21ms
2
Items[0].BatchId
Batch ID is required
'Batch Id' is required.
Bad Request
Passed
7ms
3
Items[0].ItemType
Item type is required
'Item Type' is required.
Bad Request
Passed
34ms
4
Items[0].Quantity
0
Quantity must be greater than zero
Quantity must be greater than zero.
Bad Request
Passed
8ms
5
Items
At least one item is required
The Items field is required.
Bad Request
Passed
5ms
Steps
✓Givena valid order request with "CustomerName" set to ""(7ms)
✓Whenthe invalid order request is submitted(4ms)
✓Thenthe order response should contain error "'Customer Name' is required." with status "Bad Request"(5ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Customer Name' is required.') ](0ms)
Steps
✓Givena valid order request with "Items[0].BatchId" set to ""(0ms)
✓Whenthe invalid order request is submitted(5ms)
✓Thenthe order response should contain error "'Batch Id' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Batch Id' is required.') ](0ms)
Steps
✓Givena valid order request with "Items[0].ItemType" set to ""(1ms)
✓Whenthe invalid order request is submitted(29ms)
✓Thenthe order response should contain error "'Item Type' is required." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Item Type' is required.') ](0ms)
Steps
✓Givena valid order request with "Items[0].Quantity" set to "0"(3ms)
✓Whenthe invalid order request is submitted(2ms)
✓Thenthe order response should contain error "Quantity must be greater than zero." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Quantity must be greater than zero.') ](0ms)
Steps
✓Givena valid order request with "Items" set to ""(0ms)
✓Whenthe invalid order request is submitted(3ms)
✓Thenthe order response should contain error "The Items field is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('The Items field is required.') ](0ms)
Diagrams
Details:lines
Outbox Retry Exhaustion
/orders - Outbox message transitions to failed after exhausting retries
An outbox message should transition to failed after exhausting retries IgnoreIfNeedsEventInfrastructure1.2s🔗Steps
✓Giventhe outbox processor is configured with a failing dispatcher(172ms)
✓Anda pending outbox message with a test-specific destination(4ms)
✓Thenthe outbox message should be in a failed state(1.0s)
Sequence Diagrams
Details:lines
Pancakes Content Negotiation
/pancakes - Content negotiation and unsupported media types
Sending a request with an unsupported content type should return an unsupported media type response 3/3 passed33ms🔗
#
Input Parameters
Status
Duration
Content Type
1
application/xml
Passed
21ms
2
text/html
Passed
4ms
3
text/plain
Passed
7ms
Steps
✓Givena pancake request with content type "application/xml"(1ms)
✓Whenthe pancakes are prepared with the given content type(6ms)
✓Thenthe response should indicate unsupported media type(4ms)
✓Response status code should be UnsupportedMediaType(0ms)
Steps
✓Givena pancake request with content type "text/html"(0ms)
✓Whenthe pancakes are prepared with the given content type(1ms)
✓Thenthe response should indicate unsupported media type(0ms)
✓Response status code should be UnsupportedMediaType(0ms)
Steps
✓Givena pancake request with content type "text/plain"(0ms)
✓Whenthe pancakes are prepared with the given content type(2ms)
✓Thenthe response should indicate unsupported media type(0ms)
✓Response status code should be UnsupportedMediaType(0ms)
Diagrams
Details:lines
Pancakes Creation
/pancakes - Creating pancakes with ingredients and optional toppings
A valid pancake request should return a fresh batch Happy Path48ms🔗Steps✓Givena valid pancake recipe with all ingredients(12ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Whenthe pancakes are prepared(13ms)
✓Thenthe pancakes response should contain a valid batch with all ingredients(6ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response ingredients should contain 'Milk'(0ms)
✓Pancake steps response ingredients should contain 'Eggs'(0ms)
✓Pancake steps response ingredients should contain 'Flour'(0ms)
✓Andthe cow service should have received a milk request(1ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ](0ms)
Diagrams
Details:lines
A pancake request with more toppings than allowed should return a bad request response IgnoreIfExternalSut25ms🔗Steps
✓Giventhe max toppings per item is the configured limit(0ms)
✓Anda valid pancake recipe with all ingredients(9ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Andthe request has more toppings than the configured limit(2ms)
✓Whenthe pancakes are prepared(3ms)
✓Thenthe pancakes response should indicate too many toppings(6ms)
✓Pancake steps response message status code should be BadRequest(0ms)
✓Pancake error response body should contain MaxToppingsExceeded(0ms)
Diagrams
Details:lines
Pancakes endpoint is called with invalid ingredients should return a bad request response 6/6 passed112ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
9ms
2
Eggs
javascript:void(0)
XSS in eggs
Eggs contains potentially dangerous content.
Bad Request
Passed
7ms
3
Flour
<img onerror=x>
XSS in flour
Flour contains potentially dangerous content.
Bad Request
Passed
4ms
4
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
34ms
5
Milk
<script>alert</script>
XSS in milk
Milk contains potentially dangerous content.
Bad Request
Passed
42ms
6
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
13ms
Steps
✓Givena valid pancake request with "Eggs" set to ""(0ms)
✓Whenthe invalid pancake request is submitted(6ms)
✓Thenthe response should contain error "'Eggs' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Eggs' is required.') ](0ms)
Steps
✓Givena valid pancake request with "Eggs" set to "javascript:void(0)"(0ms)
✓Whenthe invalid pancake request is submitted(1ms)
✓Thenthe response should contain error "Eggs contains potentially dangerous content." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Eggs contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid pancake request with "Flour" set to "<img onerror=x>"(0ms)
✓Whenthe invalid pancake request is submitted(1ms)
✓Thenthe response should contain error "Flour contains potentially dangerous content." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Flour contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid pancake request with "Flour" set to ""(0ms)
✓Whenthe invalid pancake request is submitted(2ms)
✓Thenthe response should contain error "'Flour' is required." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Flour' is required.') ](0ms)
Steps
✓Givena valid pancake request with "Milk" set to "<script>alert</script>"(11ms)
✓Whenthe invalid pancake request is submitted(8ms)
✓Thenthe response should contain error "Milk contains potentially dangerous content." with status "Bad Request"(9ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Milk contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid pancake request with "Milk" set to ""(0ms)
✓Whenthe invalid pancake request is submitted(2ms)
✓Thenthe response should contain error "'Milk' is required." with status "Bad Request"(4ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Milk' is required.') ](0ms)
Consuming recipe cost event should trigger downstream processing Happy PathIgnoreIfExternalSut1.1s🔗Steps
✓Givena recipe cost calculated event(40ms)
✓Whenthe event is published to Kafka(981ms)
✓Thenthe calculation ID should be generated(4ms)
✓Publish steps calculation id should not be Empty(0ms)
✓Andthe kitchen service should have received the preparation request(14ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ](0ms)
Diagrams
Details:lines
Recipe Reports
/graphql - Querying recipe reports and aggregations via GraphQL
Recipe reports should contain ingested recipe data Happy PathIgnoreIfNeedsDirectDbAccess61ms🔗Steps
✓Givenrecipe logs have been ingested into the reporting database(4ms)
✓Whenthe recipe reports are queried via graphql(28ms)
✓Thenthe graphql response should contain the ingested recipe reports(26ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Graph ql steps recipe reports should contain [ r => r.OrderId == '16470a1d-2f9f-4883-adaa-d100791f6b8c' && r.RecipeType == "Pancakes" && r.Ingredients.Contains("Milk") ](0ms)
Diagrams
Details:lines
Ingredient usage should aggregate across multiple recipes IgnoreIfNeedsDirectDbAccess1.5s🔗Steps
✓Givenmultiple recipe logs have been ingested with overlapping ingredients(71ms)
✓Whenthe ingredient usage is queried via graphql(1.4s)
✓Thenthe ingredient usage should reflect aggregated counts(16ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Graph ql steps ingredient usage should contain [ i => i.Ingredient == "Milk" && i.Count >= 2 ](0ms)
✓Graph ql steps ingredient usage should contain [ i => i.Ingredient == "Butter" && i.Count >= 1 ](0ms)
Diagrams
Details:lines
Popular recipes should return recipe types ordered by frequency IgnoreIfNeedsDirectDbAccess158ms🔗Steps
✓Givenmultiple recipe logs of different types have been ingested(7ms)
✓Whenthe popular recipes are queried via graphql(137ms)
✓Thenthe popular recipes should be ordered by count descending(11ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Pancakes should not be null(0ms)
✓Pancakes count should be greater than or equal to 2(0ms)
✓Graph ql steps popular recipes should contain [ r => r.RecipeType == "Waffles" && r.Count >= 1 ](0ms)
Diagrams
Details:lines
Recipe Reviews Management
/recipe-reviews - Submitting and retrieving recipe reviews (MongoDB)
Submitting a recipe review should return the created review Happy Path252ms🔗Steps
✓Givena valid recipe review request(3ms)
✓Whenthe recipe review is submitted(225ms)
✓Thenthe recipe review response should contain the created review(19ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response recipe name should be 'Recipe-fcb7aede71f44d7597f91300c7b9c638'(0ms)
✓Post steps response rating should be 5(0ms)
✓Post steps response review id should not be null or empty(0ms)
Diagrams
Details:lines
Listing reviews by recipe should return matching reviews 400ms🔗Steps✓Givena recipe review has been created(21ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe reviews are listed by recipe name(352ms)
✓Thenthe list response should contain the review(24ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps list response should contain [ r => r.ReviewId == 'c0e6438a-d544-44fa-8e5b-571d0a8b5265' ](0ms)
Diagrams
Details:lines
Retrieving a non-existent review should return not found 62ms🔗Steps
✓Whena non-existent review is retrieved(60ms)
✓Thenthe review get response should indicate not found(1ms)
✓Get steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Retrieving existing review by id should return the review 33ms🔗Steps✓Givena recipe review has been created(3ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe review is retrieved by id(8ms)
✓Thenthe get response should contain the review(20ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response review id should be '4ff79c38-98d9-4a14-ab87-3d03887cd157'(0ms)
✓Get steps response recipe name should be 'Recipe-28af40c8cb204140991184910de2f18e'(0ms)
Diagrams
Details:lines
Submitting a review with an invalid rating should return bad request 13ms🔗Steps
✓Givena recipe review request with an invalid rating(3ms)
✓Whenthe recipe review is submitted(6ms)
✓Thenthe review post response should indicate bad request(2ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Submitting a review with missing recipe name should return bad request 8ms🔗Steps
✓Givena recipe review request with a missing recipe name(1ms)
✓Whenthe recipe review is submitted(4ms)
✓Thenthe review post response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Recipe Summary Via G RPC
/grpc - Retrieving recipe summaries via gRPC
Pancake recipe summary should return correct data Happy Path171ms🔗Steps
✓Whena recipe summary is requested for "Pancakes" via gRPC(20ms)
✓Thenthe recipe summary should contain 42 total batches(3ms)
✓Grpc steps recipe summary reply total batches should be '42'(0ms)
✓Andthe recipe summary should contain ingredients "Milk, Flour, Eggs"(137ms)
✓Grpc steps recipe summary reply common ingredients should be equivalent to '[ "Milk", "Flour", "Eggs" ]'(0ms)
Diagrams
Details:lines
Waffle recipe summary should return correct data Happy Path12ms🔗Steps
✓Whena recipe summary is requested for "Waffles" via gRPC(8ms)
✓Thenthe recipe summary should contain 28 total batches(0ms)
✓Grpc steps recipe summary reply total batches should be '28'(0ms)
✓Andthe recipe summary should contain ingredients "Milk, Flour, Eggs, Butter"(1ms)
✓Grpc steps recipe summary reply common ingredients should be equivalent to '[ "Milk", "Flour", "Eggs", "Butter" ]'(0ms)
Diagrams
Details:lines
Unknown recipe type should return zero batches 13ms🔗Steps
✓Whena recipe summary is requested for "Unknown" via gRPC(2ms)
✓Thenthe recipe summary should contain 0 total batches(0ms)
✓Grpc steps recipe summary reply total batches should be '0'(0ms)
✓Andthe recipe summary should contain no ingredients(4ms)
✓Grpc steps recipe summary reply common ingredients should be empty(0ms)
Diagrams
Details:lines
Reporting Batch Completions
/graphql - Querying batch completion records populated by Pub/Sub consumption
Batch completions should contain data ingested via pubsub consumer Happy Path107ms🔗Steps✓Givena pancake batch has been created for batch completions(47ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Whenthe batch completions are queried via graphql(43ms)
✓Thenthe graphql response should contain the batch completion record(12ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Graph ql steps batch completions should contain [ r => r.BatchId == '2ebfe9f1-6c27-4999-8bf3-e8c775fb47fe' && r.RecipeType == "Pancakes" && r.Ingredients.Contains("Milk") ](0ms)
Diagrams
Details:lines
Reporting Event Grid Webhook
/webhooks/eventgrid - Ingredient shipments recorded via EventGrid webhook events
Ingredient shipments should be recorded when delivered via eventgrid webhook Happy Path114ms🔗Steps✓Givenan ingredient delivery event has been received via eventgrid webhook(83ms)
✓Response status code should be OK(0ms)
✓Whenthe ingredient shipments are queried via graphql(14ms)
✓Thenthe graphql response should contain the ingredient shipment record(11ms)
✓Graph ql steps response message status code should be OK(0ms)
/reservations - Managing table reservations with full CRUD operations and cancellation
Reservations can be created and retrievedCreating a reservation should return the confirmed reservation Happy Path42ms🔗Steps
✓Givena valid reservation request(0ms)
✓Whenthe reservation is submitted(12ms)
✓Thenthe reservation response should contain the confirmed booking(6ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response status should be "Confirmed"(0ms)
✓Post steps response customer name should be 'CustomerName'(0ms)
Diagrams
Details:lines
Reservations can be cancelled onceCancelling a reservation should return the cancelled reservation 38ms🔗Steps✓Givena reservation exists(16ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe reservation is cancelled(12ms)
✓Thenthe cancellation response should indicate the reservation is cancelled(9ms)
✓Cancel steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Cancel steps response status should be "Cancelled"(0ms)
Diagrams
Details:lines
Cancelling an already cancelled reservation should return a conflict response 411ms🔗Steps✓Givena cancelled reservation exists(329ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Cancel steps response message status code should be OK(0ms)
✓Whenthe reservation is cancelled again(69ms)
✓Thenthe cancellation response should indicate a conflict(5ms)
✓Cancel steps response message status code should be Conflict(0ms)
Diagrams
Details:lines
Reservations can be deletedDeleting a reservation should return no content 67ms🔗Steps✓Givena reservation exists(5ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe reservation is deleted(52ms)
✓Thenthe reservation delete response should indicate no content(6ms)
✓Delete response status code should be NoContent(0ms)
Diagrams
Details:lines
Reservations can be created and retrievedRetrieving an existing reservation should return the reservation 100ms🔗Steps✓Givena reservation exists(41ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe reservation is retrieved by id(28ms)
✓Thenthe reservation get response should contain the reservation(8ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response id should be '2'(0ms)
✓Get steps response customer name should be 'CustomerName'(0ms)
✓Get steps response status should be "Confirmed"(0ms)
Diagrams
Details:lines
Service Time Analysis
Order served events - Service time analysis (Kafka → ClickHouse → gRPC → Kitchen)
Consuming an order served event should trigger downstream processing Happy PathIgnoreIfExternalSut96ms🔗Steps
✓Givenan order served event(3ms)
✓Whenthe order served event is published to Kafka(57ms)
✓Thenthe order ID should be generated(7ms)
✓Publish steps order id should not be Empty(0ms)
✓Andthe kitchen service should have received the status request(15ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == $"/status/{orderId}" && r.Method == HttpMethod.Get ](0ms)
Diagrams
Details:lines
Specifications Async Api
/asyncapi/asyncapi.json - Serving the AsyncAPI specification describing event-driven messaging
The AsyncApi endpoint should return a valid specification Happy Path346ms🔗Steps
✓Whenthe asyncapi endpoint is called(292ms)
✓Thenthe response should be valid(9ms)
✓Async api response status code should be OK(0ms)
✓Async api response is valid json should be true $"response body (first 500 chars): {_asyncApiJsonString?[..Math.Min(_asyncApiJsonString.Length, 500)]}"(0ms)
✓Andthe asyncapi spec is written to disk(36ms)asyncapi.json
✓Async api json root element get property("asyncapi") should not be null(0ms)
✓Async api json root element get property("info") should not be null(0ms)
✓Async api json root element get property("default content type") should not be null(0ms)
✓Async api json root element get property("channels") should not be null(0ms)
✓Async api json root element get property("operations") should not be null(0ms)
✓Async api json root element get property("components") should not be null(0ms)
Diagrams
Details:lines
Specifications Open Api
/swagger/v1/swagger.json - Serving the OpenAPI specification describing all REST endpoints
The OpenApi endpoint should return a valid specification Happy Path547ms🔗Steps
✓Whenthe open api endpoint is called(499ms)
✓Thenthe response should be valid(7ms)
✓Swagger response status code should be OK(0ms)
✓Open api response is valid json should be true(0ms)
✓Andthe response should contain all the endpoints(27ms)
✓Paths get property( endpoints swagger pancakes path) should not be null(0ms)
✓Paths get property( endpoints swagger waffles path) should not be null(0ms)
✓Paths get property( endpoints swagger orders path) should not be null(0ms)
✓Paths get property( endpoints swagger order by id path) should not be null(0ms)
✓Paths get property( endpoints swagger toppings path) should not be null(0ms)
✓Paths get property( endpoints swagger menu path) should not be null(0ms)
✓Paths get property( endpoints swagger milk path) should not be null(0ms)
✓Paths get property( endpoints swagger eggs path) should not be null(0ms)
✓Paths get property( endpoints swagger flour path) should not be null(0ms)
✓Paths get property( endpoints swagger goat milk path) should not be null(0ms)
✓Paths get property( endpoints swagger audit logs path) should not be null(0ms)
✓Andthe openapi spec is written to disk(8ms)openapi.json
Diagrams
Details:lines
Specifications Open Api Scalar UI
/scalar/v1 - Serving the interactive API documentation UI powered by Scalar
The Scalar UI endpoint should return a valid page Happy Path435ms🔗Steps
✓Whenthe scalar ui endpoint is called(421ms)
✓Thenthe response should be a valid scalar page(5ms)
✓Scalar response status code should be OK(0ms)
✓Scalar ui response body should contain "<html"(0ms)
✓Scalar ui response body should contain "scalar"(0ms)
Diagrams
Details:lines
Staff Management
/staff - Managing kitchen staff members with full CRUD operations
Staff members support CRUD operationsAdding a new staff member should return the created member Happy Path15ms🔗Steps
✓Givena valid staff member request(2ms)
✓Whenthe staff member is submitted(7ms)
✓Thenthe staff response should contain the created member(3ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response name should be 'Name'(0ms)
✓Post steps response role should be "Chef"(0ms)
Diagrams
Details:lines
Staff requests must pass validationAdding a staff member with an invalid role should return a bad request response 10ms🔗Steps
✓Givena staff member request with an invalid role(2ms)
✓Whenthe staff member is submitted(4ms)
✓Thenthe staff response should indicate bad request(1ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Staff members support CRUD operationsDeleting a staff member should return no content 90ms🔗Steps✓Givena staff member exists(10ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe staff member is deleted(71ms)
✓Thenthe staff delete response should indicate no content(6ms)
✓Delete response status code should be NoContent(0ms)
Diagrams
Details:lines
Retrieving an existing staff member should return the member 159ms🔗Steps✓Givena staff member exists(106ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe staff member is retrieved by id(41ms)
✓Thenthe staff get response should contain the member(8ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response id should be '1'(0ms)
✓Get steps response name should be 'Name'(0ms)
✓Get steps response role should be "Chef"(0ms)
Diagrams
Details:lines
Status Update Not Found
/orders - Updating status of a non-existent order
Updating the status of a non-existent order should return not found 54ms🔗Steps
✓Whena status update is sent for a non-existent order(47ms)
✓Thenthe status update response should indicate not found(1ms)
✓Patch steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Stream Order Updates Via G RPC
/grpc - Streaming order updates via gRPC server streaming
Streaming order updates should return the current status Happy Path70ms🔗Steps✓Givena pancake batch has been created(14ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Andan order has been created for the batch(14ms)
✓Order steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Order steps response order id should not be empty(0ms)
✓Whenorder updates are streamed via gRPC(31ms)
✓Thenthe streamed response should contain the order status(5ms)
✓Grpc steps streamed replies should have count 1(0ms)
✓Grpc steps streamed replies[0] order id should be orderSteps.Response.OrderId.ToString()(0ms)
✓Grpc steps streamed replies[0] customer name should be 'TestCustomer_2173381859448366456'(0ms)
✓Grpc steps streamed replies[0] status should be Created(0ms)
Diagrams
Details:lines
Streaming updates for non-existent order should return not found 17ms🔗Steps
✓Whenorder updates for a non-existent order are streamed via gRPC(13ms)
✓Thenthe gRPC stream should return a not found error(2ms)
✓Grpc steps rpc exception should not be null(0ms)
✓Grpc steps rpc exception status code should be NotFound(0ms)
Diagrams
Details:lines
Telemetry
/orders - Structured logging and telemetry verification
Creating an order should emit a structured log entry Happy PathIgnoreIfExternalSut1.0s🔗Steps
✓Giventhe application is configured with an in-memory log capture(329ms)
✓Anda pancake batch has been created(226ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Pancake steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Pancake steps response should not be null(0ms)
✓Pancake steps response batch id should not be empty(0ms)
✓Anda valid order request(2ms)
✓Whenthe order is submitted(474ms)
✓Thena structured log entry should have been captured for order creation(7ms)
✓Log provider entries should contain [ e => e.Message.Contains("created for customer") ](0ms)
✓Log provider entries should contain [ e => e.Message.Contains(orderSteps.Request.CustomerName) ](0ms)
✓Log provider entries should contain [ e => e.Message.Contains("1 items") ](0ms)
Diagrams
Details:lines
Toppings Deletion
/toppings - Deleting toppings from the system
Existing toppings can be deletedDeleting an existing topping should return no content Happy Path26ms🔗Steps
✓Givena known topping exists(1ms)
✓Whenthe topping is deleted(17ms)
✓Thenthe delete response should indicate success(4ms)
✓Delete steps response message status code should be NoContent(0ms)
Diagrams
Details:lines
Non-existent toppings cannot be deletedDeleting a non-existent topping should return not found 33ms🔗Steps
✓Givena topping id that does not exist(0ms)
✓Whenthe topping is deleted(1ms)
✓Thenthe delete response should indicate not found(1ms)
✓Delete steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Toppings Feature Flag
/toppings - Raspberry topping availability controlled by feature flag
Raspberry topping is hidden when the feature flag is disabledToppings should exclude raspberries when the feature flag is disabled IgnoreIfExternalSut158ms🔗Steps
✓Giventhe raspberry topping feature flag is disabled(139ms)
✓Whenthe available toppings are requested(12ms)
✓Thenthe toppings response should not include raspberries(4ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response should not contain [ t => t.Name == ToppingDefaults.Raspberries ](0ms)
Diagrams
Details:lines
Raspberry topping is available when the feature flag is enabledToppings should include raspberries when the feature flag is enabled IgnoreIfExternalSut321ms🔗Steps
✓Giventhe raspberry topping feature flag is enabled(252ms)
✓Whenthe available toppings are requested(48ms)
✓Thenthe toppings response should include raspberries(13ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response should contain [ t => t.Name == ToppingDefaults.Raspberries ](0ms)
Diagrams
Details:lines
Toppings Management
/toppings - Listing available toppings and adding custom toppings
The toppings endpoint should return all available toppings Happy Path39ms🔗Steps
✓Whenthe available toppings are requested(21ms)
✓Thenthe toppings response should contain the default toppings(16ms)
✓Get steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Get steps response should have count ExpectedToppingCount(0ms)
✓Get steps response should contain [ t => t.Name == ToppingDefaults.Raspberries ](0ms)
✓Get steps response should contain [ t => t.Name == ToppingDefaults.Blueberries ](0ms)
✓Get steps response should contain [ t => t.Name == ToppingDefaults.MapleSyrup ](0ms)
✓Get steps response should contain [ t => t.Name == ToppingDefaults.WhippedCream ](0ms)
✓Get steps response should contain [ t => t.Name == ToppingDefaults.ChocolateChips ](0ms)
Diagrams
Details:lines
Adding a new topping should return the created topping 93ms🔗Steps
✓Givena valid topping request(9ms)
✓Whenthe new topping is submitted(59ms)
✓Thenthe topping response should contain the created topping(14ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Post steps response name should be Strawberries(0ms)
✓Post steps response category should be FruitCategory(0ms)
Diagrams
Details:lines
Toppings Update
/toppings - Updating existing toppings
Existing toppings can be updatedUpdating an existing topping should return the updated topping Happy Path144ms🔗Steps
✓Givena known blueberry topping exists(4ms)
✓Anda valid update topping request(1ms)
✓Whenthe topping is updated(54ms)
✓Thenthe update response should contain the updated topping(78ms)
✓Put steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Put steps response topping id should be KnownBlueberryToppingId(0ms)
✓Put steps response name should be Strawberries(0ms)
✓Put steps response category should be FruitCategory(0ms)
Diagrams
Details:lines
Update requests must pass validation and XSS checksUpdate toppings endpoint is called with invalid or dangerous input 6/6 passed118ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Category
<script>alert('xss')</script>
Script tag in category
Category contains potentially dangerous content.
Bad Request
Passed
57ms
2
Category
Category is required
'Category' is required.
Bad Request
Passed
10ms
3
Category
javascript:alert(1)
Javascript protocol
Category contains potentially dangerous content.
Bad Request
Passed
32ms
4
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
6ms
5
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
5ms
6
Name
Name is required
'Name' is required.
Bad Request
Passed
5ms
Steps
✓Givena known topping exists(0ms)
✓Anda valid update topping request with "Category" set to "<script>alert('xss')</script>"(4ms)
✓Whenthe invalid update topping request is submitted(31ms)
✓Thenthe update response should contain error "Category contains potentially dangerous content." with status "Bad Request"(18ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Category contains potentially dangerous content.') ](0ms)
Steps
✓Givena known topping exists(0ms)
✓Anda valid update topping request with "Category" set to ""(0ms)
✓Whenthe invalid update topping request is submitted(2ms)
✓Thenthe update response should contain error "'Category' is required." with status "Bad Request"(4ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Category' is required.') ](0ms)
Steps
✓Givena known topping exists(0ms)
✓Anda valid update topping request with "Category" set to "javascript:alert(1)"(0ms)
✓Whenthe invalid update topping request is submitted(3ms)
✓Thenthe update response should contain error "Category contains potentially dangerous content." with status "Bad Request"(7ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Category contains potentially dangerous content.') ](0ms)
Steps
✓Givena known topping exists(0ms)
✓Anda valid update topping request with "Name" set to "<img src=x onerror=alert(1)>"(0ms)
✓Whenthe invalid update topping request is submitted(1ms)
✓Thenthe update response should contain error "Name contains potentially dangerous content." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Name contains potentially dangerous content.') ](0ms)
Steps
✓Givena known topping exists(0ms)
✓Anda valid update topping request with "Name" set to "<script>alert('xss')</script>"(0ms)
✓Whenthe invalid update topping request is submitted(2ms)
✓Thenthe update response should contain error "Name contains potentially dangerous content." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Name contains potentially dangerous content.') ](0ms)
Steps
✓Givena known topping exists(0ms)
✓Anda valid update topping request with "Name" set to ""(0ms)
✓Whenthe invalid update topping request is submitted(1ms)
✓Thenthe update response should contain error "'Name' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Name' is required.') ](0ms)
Diagrams
Details:lines
Non-existent toppings cannot be updatedUpdating a non-existent topping should return not found 5ms🔗Steps
✓Givena topping id that does not exist(0ms)
✓Anda valid update topping request(0ms)
✓Whenthe topping is updated(1ms)
✓Thenthe update response should indicate not found(1ms)
✓Put steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Toppings XSS Validation
/toppings - XSS and input validation for toppings
Toppings endpoint is called with invalid or dangerous input 6/6 passed60ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Category
<script>alert('xss')</script>
Script tag in category
Category contains potentially dangerous content.
Bad Request
Passed
9ms
2
Category
Category is required
'Category' is required.
Bad Request
Passed
18ms
3
Category
javascript:alert(1)
Javascript protocol
Category contains potentially dangerous content.
Bad Request
Passed
4ms
4
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
18ms
5
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
4ms
6
Name
Name is required
'Name' is required.
Bad Request
Passed
5ms
Steps
✓Givena valid topping request with "Category" set to "<script>alert('xss')</script>"(0ms)
✓Whenthe invalid topping request is submitted(5ms)
✓Thenthe topping response should contain error "Category contains potentially dangerous content." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Category contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid topping request with "Category" set to ""(2ms)
✓Whenthe invalid topping request is submitted(6ms)
✓Thenthe topping response should contain error "'Category' is required." with status "Bad Request"(5ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Category' is required.') ](0ms)
Steps
✓Givena valid topping request with "Category" set to "javascript:alert(1)"(0ms)
✓Whenthe invalid topping request is submitted(1ms)
✓Thenthe topping response should contain error "Category contains potentially dangerous content." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Category contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid topping request with "Name" set to "<img src=x onerror=alert(1)>"(0ms)
✓Whenthe invalid topping request is submitted(5ms)
✓Thenthe topping response should contain error "Name contains potentially dangerous content." with status "Bad Request"(10ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Name contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid topping request with "Name" set to "<script>alert('xss')</script>"(0ms)
✓Whenthe invalid topping request is submitted(1ms)
✓Thenthe topping response should contain error "Name contains potentially dangerous content." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Name contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid topping request with "Name" set to ""(0ms)
✓Whenthe invalid topping request is submitted(2ms)
✓Thenthe topping response should contain error "'Name' is required." with status "Bad Request"(2ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Name' is required.') ](0ms)
Diagrams
Details:lines
Waffles Content Negotiation
/waffles - Content negotiation and unsupported media types
Sending a request with an unsupported content type should return an unsupported media type response 3/3 passed177ms🔗
#
Input Parameters
Status
Duration
Content Type
1
application/xml
Passed
16ms
2
text/html
Passed
155ms
3
text/plain
Passed
5ms
Steps
✓Givena waffle request with content type "application/xml"(0ms)
✓Whenthe waffles are prepared with the given content type(12ms)
✓Thenthe waffle response should indicate unsupported media type(0ms)
✓Response status code should be UnsupportedMediaType(0ms)
Steps
✓Givena waffle request with content type "text/html"(8ms)
✓Whenthe waffles are prepared with the given content type(66ms)
✓Thenthe waffle response should indicate unsupported media type(50ms)
✓Response status code should be UnsupportedMediaType(0ms)
Steps
✓Givena waffle request with content type "text/plain"(0ms)
✓Whenthe waffles are prepared with the given content type(3ms)
✓Thenthe waffle response should indicate unsupported media type(0ms)
✓Response status code should be UnsupportedMediaType(0ms)
Diagrams
Details:lines
Waffles Creation
/waffles - Creating waffles with ingredients including butter
A valid waffle request should return a fresh batch Happy Path114ms🔗Steps✓Givena valid waffle recipe with all ingredients(14ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Whenthe waffles are prepared(68ms)
✓Thenthe waffles response should contain a valid batch with all ingredients(18ms)
✓Waffle steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Waffle steps response ingredients should contain 'Milk'(0ms)
✓Waffle steps response ingredients should contain 'Eggs'(0ms)
✓Waffle steps response ingredients should contain 'Flour'(0ms)
✓Waffle steps response ingredients should contain UnsaltedButter(0ms)
✓Andthe cow service should have received a milk request(10ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ](0ms)
Diagrams
Details:lines
A waffle request with more toppings than allowed should return a bad request response IgnoreIfExternalSut63ms🔗Steps
✓Giventhe max toppings per item is the configured limit(1ms)
✓Anda valid waffle recipe with all ingredients(36ms)
✓Milk steps response message status code should be OK(0ms)
✓Eggs steps response message status code should be OK(0ms)
✓Flour steps response message status code should be OK(0ms)
✓Andthe waffle request has more toppings than the configured limit(3ms)
✓Whenthe waffles are prepared(10ms)
✓Thenthe waffles response should indicate too many toppings(3ms)
✓Waffle steps response message status code should be BadRequest(0ms)
✓Waffle error response body should contain MaxToppingsExceeded(0ms)
Diagrams
Details:lines
Waffles endpoint is called with invalid ingredients should return a bad request response 8/8 passed222ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Butter
<script>alert</script>
XSS in butter
Butter contains potentially dangerous content.
Bad Request
Passed
132ms
2
Butter
Butter is required
'Butter' is required.
Bad Request
Passed
12ms
3
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
5ms
4
Eggs
javascript:void(0)
XSS in eggs
Eggs contains potentially dangerous content.
Bad Request
Passed
29ms
5
Flour
<img onerror=x>
XSS in flour
Flour contains potentially dangerous content.
Bad Request
Passed
11ms
6
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
7ms
7
Milk
<script>alert</script>
XSS in milk
Milk contains potentially dangerous content.
Bad Request
Passed
7ms
8
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
15ms
Steps
✓Givena valid waffle request with "Butter" set to "<script>alert</script>"(22ms)
✓Whenthe invalid waffle request is submitted(75ms)
✓Thenthe waffle response should contain error "Butter contains potentially dangerous content." with status "Bad Request"(29ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Butter contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid waffle request with "Butter" set to ""(2ms)
✓Whenthe invalid waffle request is submitted(3ms)
✓Thenthe waffle response should contain error "'Butter' is required." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Butter' is required.') ](0ms)
Steps
✓Givena valid waffle request with "Eggs" set to ""(0ms)
✓Whenthe invalid waffle request is submitted(1ms)
✓Thenthe waffle response should contain error "'Eggs' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Eggs' is required.') ](0ms)
Steps
✓Givena valid waffle request with "Eggs" set to "javascript:void(0)"(2ms)
✓Whenthe invalid waffle request is submitted(20ms)
✓Thenthe waffle response should contain error "Eggs contains potentially dangerous content." with status "Bad Request"(4ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Eggs contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid waffle request with "Flour" set to "<img onerror=x>"(0ms)
✓Whenthe invalid waffle request is submitted(1ms)
✓Thenthe waffle response should contain error "Flour contains potentially dangerous content." with status "Bad Request"(4ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Flour contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid waffle request with "Flour" set to ""(0ms)
✓Whenthe invalid waffle request is submitted(1ms)
✓Thenthe waffle response should contain error "'Flour' is required." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Flour' is required.') ](0ms)
Steps
✓Givena valid waffle request with "Milk" set to "<script>alert</script>"(0ms)
✓Whenthe invalid waffle request is submitted(4ms)
✓Thenthe waffle response should contain error "Milk contains potentially dangerous content." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Milk contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid waffle request with "Milk" set to ""(3ms)
✓Whenthe invalid waffle request is submitted(5ms)
✓Thenthe waffle response should contain error "'Milk' is required." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Milk' is required.') ](0ms)