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 🛈
Requesting the second page should return different orders
2.2s
Equipment alerts should contain data ingested via Event Hub consumer
1.8s
Creating an order should produce a retrievable audit log entry
1.4s
An outbox message should transition to failed after exhausting retries
1.2s
Retrieving an existing staff member should return the member
1.0s
A valid order should be created and an event published
952ms
Retrieving non-existent customer preferences should return not found
839ms
Listing usage by ingredient should return matching records
726ms
Health check should report degraded when a downstream service returns a non-success status
481ms
The health check response should include description and data for each entry
412ms
Requesting milk when the cow service returns an invalid response should return a bad gateway response
412ms
All menu items should be marked unavailable when the supplier service is down
412ms
The OpenApi endpoint should return a valid specification
393ms
Creating an order should produce an audit log entry and events
375ms
Creating an order should emit a structured log entry
323ms
An order at the maximum items per order should be accepted
313ms
Goat milk endpoint should return fresh goat milk when feature is enabled
265ms
Exceeding the rate limit should return too many requests
256ms
The AsyncApi endpoint should return a valid specification
227ms
Health check should report degraded when the cow service is unavailable
217ms
The Scalar UI endpoint should return a valid page
211ms
Updating customer preferences should return the updated preferences
205ms
Cancelling an already cancelled reservation should return a conflict response
197ms
An order should progress through all status transitions to completion
190ms
Toppings should include raspberries when the feature flag is enabled
180ms
Retrieving an existing inventory item should return the item
177ms
Listing reviews by recipe should return matching reviews
157ms
An order exceeding the maximum items per order should be rejected
155ms
Goat milk endpoint should return not found when feature is disabled
155ms
Pancake recipe summary should return correct data
153ms
Muffins endpoint called with an invalid field should return a bad request response
147ms
Toppings should exclude raspberries when the feature flag is disabled
135ms
Order status via gRPC should return order details
130ms
Recording usage with missing ingredient name should return bad request
121ms
Health check should report degraded when multiple downstream services are unavailable
118ms
Creating an order should write an outbox message that gets processed
117ms
Listing orders should return a paginated response
98ms
Getting usage summary should return aggregated data
97ms
Daily specials order endpoint is called with invalid fields should return a bad request response
92ms
An invalid status transition should return a conflict response
89ms
Submitting a recipe review should return the created review
86ms
Waffles endpoint is called with invalid ingredients should return a bad request response
77ms
Audit logs should be filterable by entity id
76ms
Listing all inventory items should return all items
76ms
Audit logs should be returned in descending timestamp order
75ms
Streaming order updates should return the current status
75ms
Different muffin recipes should produce the expected batch
74ms
Popular recipes should return recipe types ordered by frequency
74ms
Updating an existing topping should return the updated topping
70ms
Waffles endpoint is called with invalid ingredients should return a bad request response
67ms
Retrieving existing customer preferences should return the preferences
66ms
Audit logs should be filterable by entity type
64ms
Retrieving a non-existent order should return not found
62ms
Toppings endpoint is called with invalid or dangerous input
62ms
Requesting milk when the cow service times out should return a bad gateway response
61ms
Listing feedback for an order should return the feedback
60ms
Order status for non-existent order should return not found
59ms
An invalid status transition should return a conflict response
53ms
An invalid status transition should return a conflict response
53ms
Listing orders with a small page size should limit results
51ms
A valid daily special order should return a confirmation
50ms
A valid status transition should update the order
50ms
An invalid status transition should return a conflict response
47ms
Deleting a staff member should return no content
45ms
A valid status transition should update the order
43ms
Different muffin recipes should produce the expected batch
43ms
An invalid status transition should return a conflict response
42ms
A valid status transition should update the order
42ms
Menu responses should be cached and returned even when supplier becomes unavailable
41ms
A created order should be retrievable by its ID
41ms
A valid waffle request should return a fresh batch
38ms
A request with a correlation id should return the same id in the response
37ms
Streaming updates for non-existent order should return not found
37ms
Submitting the same order with different idempotency keys should return different confirmations
36ms
Requesting milk when the cow service is unavailable should return a bad gateway response
36ms
Ingredient usage should aggregate across multiple recipes
34ms
Deleting an existing topping should return no content
33ms
The daily specials endpoint should return all available specials
33ms
Unknown recipe type should return zero batches
32ms
An invalid status transition should return a conflict response
32ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
32ms
Order summaries should contain ingested order data
31ms
Updating an inventory item should return the updated item
29ms
Updating the status of a non-existent order should return not found
29ms
A valid goat milk request should return fresh goat milk
29ms
A valid status transition should update the order
28ms
An invalid status transition should return a conflict response
28ms
Deleting a reservation should return no content
27ms
A request with a correlation id should forward it to the supplier service
27ms
Creating an order when the kitchen service returns an error should still create the order
27ms
Different muffin recipes should produce the expected batch
25ms
Waffles endpoint is called with invalid ingredients should return a bad request response
25ms
Retrieving a non-existent review should return not found
24ms
Submitting the same order with the same idempotency key should return the same confirmation
24ms
Retrieving an existing reservation should return the reservation
24ms
Remaining quantity should decrease after each order
24ms
Order status update endpoint is called with invalid fields should return a bad request response
22ms
Recipe reports should contain ingested recipe data
22ms
Deleting an inventory item should return no content
22ms
Retrieving non-existent feedback should return not found
21ms
A valid apple cinnamon muffin request should return a fresh batch
21ms
Filtering audit logs by a non-existent entity type should return an empty collection
21ms
Retrieving existing feedback by id should return the feedback
20ms
Toppings endpoint is called with invalid or dangerous input
20ms
Recording ingredient usage should return the created record
20ms
A valid pancake request should return a fresh batch
20ms
Waffle recipe summary should return correct data
19ms
Adding a staff member with an invalid role should return a bad request response
19ms
Toppings endpoint is called with invalid or dangerous input
18ms
A waffle request with more toppings than allowed should return a bad request response
17ms
Order summaries should return an empty list when no orders exist
17ms
Listing orders when none exist should return an empty page
16ms
A pancake request with more toppings than allowed should return a bad request response
16ms
Orders endpoint is called with invalid fields should return a bad request response
16ms
Adding a new staff member should return the created member
15ms
Update toppings endpoint is called with invalid or dangerous input
15ms
The health check endpoint should return a healthy status with dependency details
15ms
Deleting a non-existent topping should return not found
14ms
Updating a non-existent topping should return not found
14ms
Update toppings endpoint is called with invalid or dangerous input
14ms
Adding a new topping should return the created topping
14ms
Toppings endpoint is called with invalid or dangerous input
14ms
Retrieving existing review by id should return the review
14ms
Muffins endpoint called with an invalid field should return a bad request response
13ms
Recording usage with zero quantity should return bad request
13ms
Sending a request with an unsupported content type should return an unsupported media type response
13ms
Cancelling a reservation should return the cancelled reservation
12ms
Muffins endpoint called with an invalid field should return a bad request response
12ms
Ordering a non-existent daily special should return not found
12ms
The heartbeat endpoint should return a running message
11ms
Submitting a review with missing recipe name should return bad request
11ms
A request without a correlation id should have one generated in the response
11ms
Submitting feedback should return the created feedback
11ms
A request with a correlation id should forward it to the cow service
11ms
The menu endpoint should return all menu items with availability status
10ms
Submitting a review with an invalid rating should return bad request
10ms
Update toppings endpoint is called with invalid or dangerous input
10ms
Adding a new inventory item should return the created item
10ms
Ordering a daily special beyond the threshold should return a conflict response
10ms
Muffins endpoint called with an invalid field should return a bad request response
10ms
Daily specials order endpoint is called with invalid fields should return a bad request response
9ms
Toppings endpoint is called with invalid or dangerous input
9ms
Requesting goat milk when the goat service is unavailable should return a bad gateway response
9ms
Waffles endpoint is called with invalid ingredients should return a bad request response
9ms
Sending a request with an unsupported content type should return an unsupported media type response
9ms
Saving customer preferences should return the saved preferences
9ms
Orders endpoint is called with invalid fields should return a bad request response
9ms
Update toppings endpoint is called with invalid or dangerous input
8ms
Update toppings endpoint is called with invalid or dangerous input
8ms
Submitting feedback with missing customer name should return bad request
8ms
Creating a reservation should return the confirmed reservation
8ms
The toppings endpoint should return all available toppings
8ms
Update toppings endpoint is called with invalid or dangerous input
7ms
Toppings endpoint is called with invalid or dangerous input
6ms
Orders endpoint is called with invalid fields should return a bad request response
6ms
Retrieving a non-existent inventory item should return not found
6ms
Requesting goat milk when the goat service returns an invalid response should return a bad gateway response
6ms
Orders endpoint is called with invalid fields should return a bad request response
6ms
Waffles endpoint is called with invalid ingredients should return a bad request response
6ms
Submitting feedback with invalid rating should return bad request
6ms
Waffles endpoint is called with invalid ingredients should return a bad request response
5ms
Saving customer preferences with missing customer name should return bad request
5ms
Waffles endpoint is called with invalid ingredients should return a bad request response
4ms
Orders endpoint is called with invalid fields should return a bad request response
4ms
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
Sending a request with an unsupported content type should return an unsupported media type response
4ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
4ms
Sending a request with an unsupported content type should return an unsupported media type response
4ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
3ms
Waffles endpoint is called with invalid ingredients should return a bad request response
3ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
3ms
Sending a request with an unsupported content type should return an unsupported media type response
3ms
Pancakes endpoint is called with invalid ingredients should return a bad request response
3ms
Muffins endpoint called with an invalid field should return a bad request response
3ms
Sending a request with an unsupported content type should return an unsupported media type response
2ms
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 Path21ms🔗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(5ms)
✓Thenthe muffin response should contain a valid batch with all ingredients(3ms)
✓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(1ms)
✓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 passed143ms🔗
Steps✓Givena muffin recipe "Classic" with the following ingredients:(10ms)
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(28ms)
✓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:(9ms)
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(2ms)
✓Andthe following muffin toppings:(0ms)
Name
Amount
Brown Sugar Crumb
Heavy
Maple Drizzle
Light
✓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 "Spiced Deluxe" with the following ingredients:(16ms)
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(9ms)
✓Andthe following muffin toppings:(2ms)
Name
Amount
Cinnamon Sugar
Heavy
Cream Cheese Swirl
Thick
✓Whenthe muffins are prepared(23ms)
✓Thenthe muffin batch should have 5 ingredients(10ms)
✓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(1ms)
✓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 passed192ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Apples
Apples is required
'Apples' is required.
Bad Request
Passed
10ms
2
Cinnamon
<script>alert('xss')</script>
XSS in cinnamon
Cinnamon contains potentially dangerous content.
Bad Request
Passed
147ms
3
Cinnamon
Cinnamon is required
'Cinnamon' is required.
Bad Request
Passed
3ms
4
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
4ms
5
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
13ms
6
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
12ms
Steps
✓Givena valid muffin request with "Apples" set to ""(1ms)
✓Whenthe invalid muffin request is submitted(5ms)
✓Thenthe muffin response should contain error "'Apples' is required." with status "Bad Request"(0ms)
✓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>"(45ms)
✓Whenthe invalid muffin request is submitted(86ms)
✓Thenthe muffin response should contain error "Cinnamon contains potentially dangerous content." with status "Bad Request"(8ms)
✓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(1ms)
✓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(2ms)
✓Thenthe muffin response should contain error "'Eggs' is required." with status "Bad Request"(0ms)
✓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(9ms)
✓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(7ms)
✓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 76ms🔗Steps✓Givena pancake batch has been created(20ms)
✓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(31ms)
✓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(16ms)
✓Thenthe audit log response should contain the specific order entry(4ms)
✓Audit log response status code should be OK(0ms)
✓Audit logs should contain [ l => l.EntityId == '1225c540-fc34-42ec-bd50-f571f2f7ad3b' ](0ms)
Diagrams
Details:lines
Audit logs should be filterable by entity type 64ms🔗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)
✓Andan order has been created for the batch(9ms)
✓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(38ms)
✓Thenthe audit log response should only contain order entries(3ms)
✓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 75ms🔗Steps✓Givena pancake batch has been created(13ms)
✓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)
✓Whenaudit logs are requested filtered by entity type(37ms)
✓Thenthe audit logs should be ordered by timestamp descending(8ms)
✓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 21ms🔗Steps
✓Whenaudit logs are requested filtered by a non-existent entity type(17ms)
✓Thenthe audit log response should be an empty collection(2ms)
✓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 Path1.4s🔗Steps✓Givena pancake batch has been created(29ms)
✓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(1.2s)
✓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(120ms)
✓Thenthe audit log response should contain the order creation entry(29ms)
✓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_5087308258725742595') ](0ms)
✓Andthe cow service should have received a milk request(15ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ](0ms)
✓Andthe kitchen service should have received a preparation request(8ms)
✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ](0ms)
Diagrams
(Warning: 30 spans. This might indicate a problem/recursive loop in your test.)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 Path952ms🔗Steps✓Givena pancake batch has been created(24ms)
✓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(2ms)
✓Whenthe breakfast order is placed(15ms)
✓Thenthe order response should contain a complete order(3ms)
✓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_4149930143794899280'(0ms)
✓Order steps response items should have count 1(0ms)
✓Andan order created event should have been published(904ms)
✓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 375ms🔗Steps✓Givena pancake batch has been created(23ms)
✓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(8ms)
✓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_8955333127263298112'(0ms)
✓Order steps response items should have count 1(0ms)
✓Andan order created event should have been published(305ms)
✓Event store should not be null(0ms)
✓Anda recipe log should have been published to kafka(32ms)
✓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 117ms🔗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)
✓Anda valid order request for the created batch(3ms)
✓Whenthe breakfast order is placed(19ms)
✓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_9019933390544792711'(0ms)
✓Order steps response items should have count 1(0ms)
✓Andan outbox message should have been written for the order created event(42ms)
✓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(22ms)
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 Path190ms🔗Steps✓Givena pancake batch has been created(25ms)
✓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(21ms)
✓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(39ms)
✓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 'e5804843-c0ec-4c70-afc5-3754e060bea6'(0ms)
✓Get order steps response status should be Completed(0ms)
✓Get order steps response customer name should be 'LifecycleTestCustomer_987755649001087723'(0ms)
✓Andan audit log entry should exist for the order(42ms)
✓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_987755649001087723') ](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
(Warning: 36 spans. This might indicate a problem/recursive loop in your test.)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 Path37ms🔗Steps
✓Givena request with a known correlation id(0ms)
✓Whenthe request is sent to the menu endpoint(28ms)
✓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 '023c0fff-af9e-4d07-b256-b00932c43422'(0ms)
Diagrams
Details:lines
Missing correlation IDs are generated automaticallyA request without a correlation id should have one generated in the response 11ms🔗Steps
✓Whena request without a correlation id is sent to the menu endpoint(6ms)
✓Thenthe response should contain a generated correlation id(4ms)
✓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 Path9ms🔗Steps
✓Givena valid customer preference request(0ms)
✓Whenthe customer preferences are saved(6ms)
✓Thenthe preference response should contain the saved preferences(1ms)
✓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 66ms🔗Steps✓Givencustomer preferences exist(7ms)
✓Put steps response message status code should be OK(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe customer preferences are retrieved(54ms)
✓Thenthe preference get response should contain the preferences(2ms)
✓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 '4aa27e86e2f645939c442e6b31c88c9e'(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 839ms🔗Steps
✓Whennon-existent customer preferences are retrieved(835ms)
✓Thenthe preference get response should indicate not found(1ms)
✓Get steps response message status code should be NotFound(0ms)
Diagrams
(Warning: 68 spans. This might indicate a problem/recursive loop in your test.)Details:lines
Preference requests must pass validationSaving customer preferences with missing customer name should return bad request 5ms🔗Steps
✓Givena customer preference request with missing customer name(0ms)
✓Whenthe customer preferences are saved(2ms)
✓Thenthe preference response should indicate bad request(0ms)
✓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 205ms🔗Steps✓Givencustomer preferences exist(183ms)
✓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(6ms)
✓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 36ms🔗Background
✓Giventhe cinnamon swirl order count is reset(1ms)
Steps
✓Andan order request for the same special(2ms)
✓Whenthe order is submitted with two different idempotency keys(27ms)
✓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 '48db32fc-02af-4784-aa25-5ac1c277c4e8'(0ms)
Diagrams
Details:lines
Submitting the same order with the same idempotency key should return the same confirmation 24ms🔗Background
✓Giventhe cinnamon swirl order count is reset(1ms)
Steps
✓Andan order request with an idempotency key(0ms)
✓Whenthe order is submitted twice with the same idempotency key(14ms)
✓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(3ms)
✓First confirmation id should be '3f090a35-0e34-4a9e-ac43-dcc2d08fa68a'(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 12ms🔗Steps
✓Givena daily special order request for a non-existent special(6ms)
✓Whenthe daily special order is submitted(1ms)
✓Thenthe daily special response should indicate not found(0ms)
✓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 Path50ms🔗Steps
✓Giventhe cinnamon swirl order count is reset(16ms)
✓Anda valid daily special order request for cinnamon swirl(0ms)
✓Whenthe daily special order is submitted(17ms)
✓Thenthe daily special order response should contain a valid confirmation(10ms)
✓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 IgnoreIfExternalSut10ms🔗Steps
✓Giventhe matcha waffles order count is reset(2ms)
✓Andthe matcha waffles special has been ordered up to the configured limit(3ms)
✓Post steps response message status code should be Created(0ms)
✓Whenanother order is placed for the matcha waffles special(2ms)
✓Thenthe response should indicate the daily special is sold out(0ms)
✓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 IgnoreIfExternalSut24ms🔗Steps
✓Giventhe lemon ricotta order count is reset(4ms)
✓Anda daily special order for lemon ricotta of quantity one is placed(8ms)
✓Post steps response message status code should be Created(0ms)
✓Whenthe available daily specials are requested(0ms)
✓Thenthe lemon ricotta special should have one fewer remaining(1ms)
✓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 33ms🔗Steps
✓Whenthe available daily specials are requested(22ms)
✓Thenthe daily specials response should contain all expected specials(10ms)
✓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 passed102ms🔗
#
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
92ms
2
SpecialId
SpecialId is required
'Special Id' is required.
Bad Request
Passed
9ms
Steps
✓Givena valid daily special order request with "Quantity" set to "0"(20ms)
✓Whenthe invalid daily special order request is submitted(41ms)
✓Thenthe daily special response should contain error "Quantity must be greater than zero." with status "Bad Request"(26ms)
✓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 ""(3ms)
✓Whenthe invalid daily special order request is submitted(3ms)
✓Thenthe daily special response should contain error "'Special Id' is required." with status "Bad Request"(1ms)
✓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 SkipUnlessFakesControllable118ms🔗Background
✓Giventhe cow service is configured to be unreachable(8ms)
Steps
✓Andthe supplier service is configured to be unreachable(0ms)
✓Whenthe health check endpoint is called(101ms)
✓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(1ms)
✓Health check result results should contain key CowService(0ms)
✓Cow service health status should be Degraded(0ms)
✓Andthe supplier service dependency should report degraded(1ms)
✓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 SkipUnlessFakesControllable217ms🔗Background
✓Giventhe cow service is configured to be unreachable(8ms)
Steps
✓Whenthe health check endpoint is called(213ms)
✓Thenthe health check response should indicate a degraded status(1ms)
✓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 SkipUnlessFakesControllable481ms🔗Steps
✓Giventhe kitchen service health check is configured to use a failing endpoint(448ms)
✓Whenthe health check endpoint is called(24ms)
✓Thenthe health check response should indicate a degraded status(2ms)
✓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(1ms)
✓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 Path1.8s🔗Steps✓Givena pancake batch has been created(371ms)
✓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(1.4s)
✓Thenthe graphql response should contain the equipment alert record(25ms)
✓Graph ql steps response message status code should be OK(0ms)
/feedback - Submitting and retrieving customer feedback
Feedback can be submitted and retrievedSubmitting feedback should return the created feedback Happy Path11ms🔗Steps
✓Givena valid feedback request(0ms)
✓Whenthe feedback is submitted(7ms)
✓Thenthe feedback response should contain the created feedback(1ms)
✓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 60ms🔗Steps✓Givena feedback entry exists(30ms)
✓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(21ms)
✓Thenthe feedback list response should contain the feedback(5ms)
✓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 == '46bd731b-4d28-4409-8a90-b757c4998423' ](0ms)
Diagrams
Details:lines
Retrieving existing feedback by id should return the feedback 20ms🔗Steps✓Givena feedback entry exists(5ms)
✓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(11ms)
✓Thenthe feedback get response should contain the feedback(2ms)
✓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 '5f161554-efb2-455a-b2b1-167c85f66155'(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 21ms🔗Steps
✓Whena non-existent feedback is retrieved(19ms)
✓Thenthe feedback get response should indicate not found(0ms)
✓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 6ms🔗Steps
✓Givena feedback request with an invalid rating(0ms)
✓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 8ms🔗Steps
✓Givena feedback request with missing customer name(2ms)
✓Whenthe feedback is submitted(3ms)
✓Thenthe feedback response should indicate bad request(0ms)
✓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 SkipUnlessFakesControllable9ms🔗Steps
✓Giventhe goat service will return service unavailable(0ms)
✓Whengoat milk is requested(4ms)
✓Thenthe goat milk response should indicate a bad gateway(1ms)
✓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 SkipUnlessFakesControllable6ms🔗Steps
✓Giventhe goat service will return an invalid response(0ms)
✓Whengoat milk is requested(4ms)
✓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 IgnoreIfExternalSut265ms🔗Steps
✓Giventhe goat milk feature flag is enabled(229ms)
✓Whengoat milk is requested(33ms)
✓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
Goat milk is hidden when the feature flag is disabledGoat milk endpoint should return not found when feature is disabled IgnoreIfExternalSut155ms🔗Steps
✓Giventhe goat milk feature flag is disabled(131ms)
✓Whengoat milk is requested(18ms)
✓Thenthe goat milk response should indicate feature disabled(1ms)
✓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 Path29ms🔗Steps
✓Whengoat milk is requested(25ms)
✓Thenthe goat milk response should contain fresh goat milk(1ms)
✓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 PathSkipUnlessFakesControllable11ms🔗Background
✓Givena request with a known correlation id(0ms)
Steps
✓Whenmilk is requested with the correlation id(7ms)
✓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 '112bad74-b74f-4e30-b61a-1500c866cddd'(0ms)
Diagrams
Details:lines
A request with a correlation id should forward it to the supplier service SkipUnlessFakesControllable27ms🔗Background
✓Givena request with a known correlation id(0ms)
Steps
✓Andthe menu cache is cleared(6ms)
✓Whenthe menu is requested with the correlation id(10ms)
✓Thenthe supplier service should have received the correlation id(7ms)
✓Requests should not be empty(0ms)
✓Request headers should contain key CorrelationId(0ms)
✓Request headers[ custom headers correlation id] should be '6bc7999a-5d46-4f38-b195-d8ed6f847658'(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 Path15ms🔗Steps
✓Whenthe health check endpoint is called(10ms)
✓Thenthe health check response should indicate healthy with all dependencies(2ms)
✓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 412ms🔗Steps
✓Whenthe health check endpoint is called(278ms)
✓Thenthe health check response should contain detailed entries(83ms)
✓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 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)
Diagrams
Details:lines
Heartbeat
/heartbeat - Heartbeat endpoint confirming the service is running
The heartbeat endpoint should return a running message Happy Path11ms🔗Steps
✓Whenthe heartbeat endpoint is called(6ms)
✓Thenthe heartbeat response should indicate the service is running(2ms)
✓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 Path20ms🔗Steps
✓Givena valid ingredient usage request(0ms)
✓Whenthe ingredient usage is recorded(3ms)
✓Thenthe usage response should contain the created record(3ms)
✓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-2d9a52c56d284e1f8fe57553d9f0b342'(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 97ms🔗Steps✓Givenan ingredient usage record has been created(3ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe usage summary is requested(74ms)
✓Thenthe summary should contain aggregated data(18ms)
✓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-360d85ab65be476a8ef37e1ddae90f46' ](0ms)
Diagrams
Details:lines
Listing usage by ingredient should return matching records 726ms🔗Steps✓Givenan ingredient usage record has been created(90ms)
✓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(629ms)
✓Thenthe usage list response should contain the record(4ms)
✓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-b9be93c0ea4f4d45a1ff20050785def4' ](0ms)
Diagrams
Details:lines
Recording usage with missing ingredient name should return bad request 121ms🔗Steps
✓Givenan ingredient usage request with a missing ingredient name(1ms)
✓Whenthe ingredient usage is recorded(112ms)
✓Thenthe usage post response should indicate bad request(2ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Recording usage with zero quantity should return bad request 13ms🔗Steps
✓Givenan ingredient usage request with zero quantity(0ms)
✓Whenthe ingredient usage is recorded(11ms)
✓Thenthe usage post response should indicate bad request(0ms)
✓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 Path10ms🔗Steps
✓Givena valid inventory item request(0ms)
✓Whenthe inventory item is submitted(5ms)
✓Thenthe inventory response should contain the created item(1ms)
✓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 22ms🔗Steps✓Givenan inventory item exists(3ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe inventory item is deleted(15ms)
✓Thenthe inventory delete response should indicate no content(0ms)
✓Delete steps response message status code should be NoContent(0ms)
Diagrams
Details:lines
Listing all inventory items should return all items 76ms🔗Steps✓Givenan inventory item exists(16ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenall inventory items are requested(53ms)
✓Thenthe inventory list response should contain the item(4ms)
✓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 6ms🔗Steps
✓Whena non-existent inventory item is retrieved(3ms)
✓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 177ms🔗Steps✓Givenan inventory item exists(124ms)
✓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(37ms)
✓Thenthe inventory get response should contain the item(4ms)
✓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 29ms🔗Steps✓Givenan inventory item exists(3ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe inventory item is updated(22ms)
✓Thenthe inventory update response should contain the updated values(2ms)
✓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 SkipUnlessFakesControllable27ms🔗Steps✓Givena pancake batch has been created(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)
✓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)
✓Andthe kitchen service is configured to return busy(0ms)
✓Whenthe breakfast order is placed(11ms)
✓Thenthe order should still be created successfully despite the kitchen failure(1ms)
✓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 Path10ms🔗Steps
✓Whenthe menu is requested(1ms)
✓Thenthe menu response should contain all menu items(6ms)
✓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 SkipUnlessFakesControllable41ms🔗Steps✓Giventhe menu has been requested and cached(6ms)
✓Menu steps response message status code should be OK(0ms)
✓Andthe supplier service is then made unavailable(1ms)
✓Whenthe menu is requested again(2ms)
✓Thenthe menu response should still return available items(1ms)
✓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 SkipUnlessFakesControllable412ms🔗Steps
✓Giventhe supplier service will return service unavailable(222ms)
✓Whenthe menu is requested(102ms)
✓Thenthe menu response should mark all items as unavailable(38ms)
✓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 SkipUnlessFakesControllable36ms🔗Steps
✓Giventhe cow service will return service unavailable(5ms)
✓Whenmilk is requested(28ms)
✓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 SkipUnlessFakesControllable412ms🔗Steps
✓Giventhe cow service will return an invalid response(33ms)
✓Whenmilk is requested(246ms)
✓Thenthe milk response should indicate a bad gateway(63ms)
✓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 SkipUnlessFakesControllable61ms🔗Steps
✓Giventhe cow service will return a timeout(5ms)
✓Whenmilk is requested(52ms)
✓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 IgnoreIfExternalSut313ms🔗Background
✓Giventhe maximum items per order is configured to two(221ms)
✓Anda pancake batch has been created(62ms)
✓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)
Steps
✓Andan order request with two items(1ms)
✓Whenthe order is submitted(23ms)
✓Thenthe response should indicate success(1ms)
✓Order steps response message status code should be Created(0ms)
Diagrams
Details:lines
An order exceeding the maximum items per order should be rejected IgnoreIfExternalSut155ms🔗Background
✓Giventhe maximum items per order is configured to two(221ms)
✓Anda pancake batch has been created(62ms)
✓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)
Steps
✓Andan order request with three items(1ms)
✓Whenthe order is submitted(11ms)
✓Thenthe response should indicate a validation error(0ms)
✓Order steps response message status code should be BadRequest(0ms)
✓Andthe error message should reference the item limit(1ms)
✓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 Path98ms🔗Steps✓Givenmultiple orders have been created(79ms)
✓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(10ms)
✓Thenthe paginated response should contain the orders(7ms)
✓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
(Warning: 39 spans. This might indicate a problem/recursive loop in your test.)Details:lines
Listing orders when none exist should return an empty page IgnoreIfNeedsDirectDbAccessIgnoreUnlessInMemoryDb16ms🔗Steps
✓Whenorders are listed with default pagination(11ms)
✓Thenthe paginated response should be empty(2ms)
✓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 51ms🔗Steps✓Givenmultiple orders have been created(27ms)
✓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(21ms)
✓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
(Warning: 39 spans. This might indicate a problem/recursive loop in your test.)Details:lines
Requesting the second page should return different orders 2.2s🔗Steps✓Givenmultiple orders have been created(2.1s)
✓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(39ms)
✓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
(Warning: 40 spans. This might indicate a problem/recursive loop in your test.)Details:lines
Order Rate Limiting
/orders - Rate limiting on order creation
Exceeding the rate limit should return too many requests IgnoreIfExternalSut256ms🔗Steps
✓Giventhe rate limit is configured to allow one request per window(153ms)
✓Anda pancake batch has been created(58ms)
✓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(0ms)
✓Whenthe order is submitted twice in rapid succession(37ms)
✓Thenthe first request should succeed(1ms)
✓First response status code should be Created(0ms)
✓Andthe second request should be rate limited(0ms)
✓Second response status code should be TooManyRequests(0ms)
Diagrams
(Warning: 30 spans. This might indicate a problem/recursive loop in your test.)Details:lines
Order Retrieval
/orders - Retrieving orders by ID
Existing orders can be retrievedA created order should be retrievable by its ID Happy PathIgnoreIfNeedsEventInfrastructure41ms🔗Steps✓Givenan order has been created(32ms)
✓Response content is valid json should be true(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe order is retrieved by id(3ms)
✓Thenthe order retrieval response should contain the order(3ms)
✓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 'bd9643a9-1fbf-4230-b687-11b3b0524ecc'(0ms)
Diagrams
Details:lines
Non-existent orders return not foundRetrieving a non-existent order should return not found 62ms🔗Steps
✓Whena non-existent order is retrieved(58ms)
✓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 passed165ms🔗
#
Input Parameters
Status
Duration
From Status
To Status
1
Created
Cancelled
Passed
43ms
2
Created
Preparing
Passed
50ms
3
Preparing
Ready
Passed
28ms
4
Ready
Completed
Passed
42ms
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 "Cancelled"(6ms)
✓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"(38ms)
✓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"(10ms)
✓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"(21ms)
✓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"(28ms)
✓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"(8ms)
✓Thenthe order status should be updated successfully to "Completed"(2ms)
✓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 passed347ms🔗
#
Input Parameters
Status
Duration
From Status
To Status
1
Cancelled
Preparing
Passed
42ms
2
Cancelled
Ready
Passed
53ms
3
Completed
Preparing
Passed
53ms
4
Created
Completed
Passed
89ms
5
Created
Ready
Passed
47ms
6
Preparing
Cancelled
Passed
32ms
7
Ready
Preparing
Passed
28ms
Steps✓Givenan order exists with status "Cancelled"(39ms)
✓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"(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 "Cancelled"(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 "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"(50ms)
✓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"(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 "Created"(41ms)
✓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"(40ms)
✓Thenthe response should indicate an invalid state transition(4ms)
✓Patch steps response message status code should be Conflict(0ms)
Steps✓Givenan order exists with status "Created"(43ms)
✓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"(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 "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"(24ms)
✓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 Path130ms🔗Steps✓Givena pancake batch has been created(45ms)
✓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(61ms)
✓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(20ms)
✓Thenthe gRPC response should contain the order details(1ms)
✓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_4093842508475643706'(0ms)
✓Grpc steps order status reply status should be Created(0ms)
Diagrams
(Warning: 31 spans. This might indicate a problem/recursive loop in your test.)Details:lines
Order status for non-existent order should return not found 59ms🔗Steps
✓Whenthe order status for a non-existent order is requested via gRPC(47ms)
✓Thenthe gRPC response should be a not found error(10ms)
✓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 PathIgnoreIfNeedsDirectDbAccess31ms🔗Steps
✓Givenan order has been created and ingested into the reporting database(3ms)
✓Whenthe order summaries are queried via graphql(16ms)
✓Thenthe graphql response should contain the ingested order summary(8ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Graph ql steps order summaries should contain [ o => o.OrderId == '4b801808-9ab4-4a58-8cae-43e1f1b32960' && o.CustomerName == 'TestCustomer_4857168459066677736' && o.ItemCount == 3 && o.TableNumber == 7 ](0ms)
Diagrams
Details:lines
Order summaries should return an empty list when no orders exist 17ms🔗Steps
✓Whenthe order summaries are queried via graphql(10ms)
✓Thenthe graphql response should be successful(0ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Andthe order summaries list should be empty or not contain the test order(5ms)
✓Graph ql steps order summaries should not contain [ o => o.OrderId == 'b484d44f-156d-424b-b1f8-82a85360fa94' ](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 passed22ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Status
Status is required
'Status' is required.
Bad Request
Passed
22ms
Steps
✓Givena valid status update request with "Status" set to ""(1ms)
✓Whenthe invalid status update request is submitted(7ms)
✓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 passed43ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
CustomerName
Customer name is required
'Customer Name' is required.
Bad Request
Passed
16ms
2
Items[0].BatchId
Batch ID is required
'Batch Id' is required.
Bad Request
Passed
6ms
3
Items[0].ItemType
Item type is required
'Item Type' is required.
Bad Request
Passed
9ms
4
Items[0].Quantity
0
Quantity must be greater than zero
Quantity must be greater than zero.
Bad Request
Passed
6ms
5
Items
At least one item is required
The Items field is required.
Bad Request
Passed
4ms
Steps
✓Givena valid order request with "CustomerName" set to ""(5ms)
✓Whenthe invalid order request is submitted(3ms)
✓Thenthe order response should contain error "'Customer Name' is required." with status "Bad Request"(4ms)
✓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(1ms)
✓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(5ms)
✓Thenthe order response should contain error "'Item Type' is required." with status "Bad Request"(0ms)
✓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"(0ms)
✓Whenthe invalid order request is submitted(1ms)
✓Thenthe order response should contain error "Quantity must be greater than zero." with status "Bad Request"(0ms)
✓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(2ms)
✓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(137ms)
✓Anda pending outbox message with a test-specific destination(6ms)
✓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 passed21ms🔗
#
Input Parameters
Status
Duration
Content Type
1
application/xml
Passed
13ms
2
text/html
Passed
3ms
3
text/plain
Passed
4ms
Steps
✓Givena pancake request with content type "application/xml"(0ms)
✓Whenthe pancakes are prepared with the given content type(5ms)
✓Thenthe response should indicate unsupported media type(1ms)
✓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 Path20ms🔗Steps✓Givena valid pancake recipe with all ingredients(4ms)
✓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(8ms)
✓Thenthe pancakes response should contain a valid batch with all ingredients(2ms)
✓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(3ms)
✓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 IgnoreIfExternalSut16ms🔗Steps
✓Giventhe max toppings per item is the configured limit(0ms)
✓Anda valid pancake recipe with all ingredients(6ms)
✓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(2ms)
✓Thenthe pancakes response should indicate too many toppings(1ms)
✓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 passed52ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Error Message
Response Status
1
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
3ms
2
Eggs
javascript:void(0)
XSS in eggs
Eggs contains potentially dangerous content.
Bad Request
Passed
4ms
3
Flour
<img onerror=x>
XSS in flour
Flour contains potentially dangerous content.
Bad Request
Passed
3ms
4
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
3ms
5
Milk
<script>alert</script>
XSS in milk
Milk contains potentially dangerous content.
Bad Request
Passed
32ms
6
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
4ms
Steps
✓Givena valid pancake request with "Eggs" set to ""(0ms)
✓Whenthe invalid pancake request is submitted(1ms)
✓Thenthe response should contain error "'Eggs' is required." with status "Bad Request"(1ms)
✓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(2ms)
✓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(1ms)
✓Thenthe response should contain error "'Flour' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Flour' is required.') ](0ms)
Steps
✓Givena valid pancake request with "Milk" set to "<script>alert</script>"(4ms)
✓Whenthe invalid pancake request is submitted(3ms)
✓Thenthe response should contain error "Milk contains potentially dangerous content." with status "Bad Request"(3ms)
✓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(1ms)
✓Thenthe response should contain error "'Milk' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Milk' is required.') ](0ms)
Diagrams
Details:lines
Recipe Reports
/graphql - Querying recipe reports and aggregations via GraphQL
Recipe reports should contain ingested recipe data Happy PathIgnoreIfNeedsDirectDbAccess22ms🔗Steps
✓Givenrecipe logs have been ingested into the reporting database(2ms)
✓Whenthe recipe reports are queried via graphql(10ms)
✓Thenthe graphql response should contain the ingested recipe reports(7ms)
✓Graph ql steps response message status code should be OK(0ms)
✓Graph ql steps recipe reports should contain [ r => r.OrderId == '28de65e4-2e7f-4182-ba7d-c9d8ec73d451' && r.RecipeType == "Pancakes" && r.Ingredients.Contains("Milk") ](0ms)
Diagrams
Details:lines
Ingredient usage should aggregate across multiple recipes IgnoreIfNeedsDirectDbAccess34ms🔗Steps
✓Givenmultiple recipe logs have been ingested with overlapping ingredients(3ms)
✓Whenthe ingredient usage is queried via graphql(16ms)
✓Thenthe ingredient usage should reflect aggregated counts(10ms)
✓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 IgnoreIfNeedsDirectDbAccess74ms🔗Steps
✓Givenmultiple recipe logs of different types have been ingested(4ms)
✓Whenthe popular recipes are queried via graphql(62ms)
✓Thenthe popular recipes should be ordered by count descending(6ms)
✓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 Path86ms🔗Steps
✓Givena valid recipe review request(1ms)
✓Whenthe recipe review is submitted(74ms)
✓Thenthe recipe review response should contain the created review(7ms)
✓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-91f209c670f4499680fd0f13b16107b8'(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 157ms🔗Steps✓Givena recipe review has been created(5ms)
✓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(145ms)
✓Thenthe list response should contain the review(4ms)
✓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 == '2961cf3d-5a72-40ea-af9a-6d8a8ab9631d' ](0ms)
Diagrams
Details:lines
Retrieving a non-existent review should return not found 24ms🔗Steps
✓Whena non-existent review is retrieved(22ms)
✓Thenthe review get response should indicate not found(0ms)
✓Get steps response message status code should be NotFound(0ms)
Diagrams
Details:lines
Retrieving existing review by id should return the review 14ms🔗Steps✓Givena recipe review has been created(4ms)
✓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(4ms)
✓Thenthe get response should contain the review(2ms)
✓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 '3d19adfb-8632-4d96-a44e-75c97d25788b'(0ms)
✓Get steps response recipe name should be 'Recipe-2aa60219bcc3446eb8bbc1924a392c3a'(0ms)
Diagrams
Details:lines
Submitting a review with an invalid rating should return bad request 10ms🔗Steps
✓Givena recipe review request with an invalid rating(6ms)
✓Whenthe recipe review is submitted(2ms)
✓Thenthe review post response should indicate bad request(0ms)
✓Post steps response message status code should be BadRequest(0ms)
Diagrams
Details:lines
Submitting a review with missing recipe name should return bad request 11ms🔗Steps
✓Givena recipe review request with a missing recipe name(3ms)
✓Whenthe recipe review is submitted(3ms)
✓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 Path153ms🔗Steps
✓Whena recipe summary is requested for "Pancakes" via gRPC(16ms)
✓Thenthe recipe summary should contain 42 total batches(1ms)
✓Grpc steps recipe summary reply total batches should be '42'(0ms)
✓Andthe recipe summary should contain ingredients "Milk, Flour, Eggs"(130ms)
✓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 Path19ms🔗Steps
✓Whena recipe summary is requested for "Waffles" via gRPC(12ms)
✓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"(4ms)
✓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 32ms🔗Steps
✓Whena recipe summary is requested for "Unknown" via gRPC(20ms)
✓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(8ms)
✓Grpc steps recipe summary reply common ingredients should be empty(0ms)
Diagrams
Details:lines
Reservations Management
/reservations - Managing table reservations with full CRUD operations and cancellation
Reservations can be created and retrievedCreating a reservation should return the confirmed reservation Happy Path8ms🔗Steps
✓Givena valid reservation request(0ms)
✓Whenthe reservation is submitted(4ms)
✓Thenthe reservation response should contain the confirmed booking(1ms)
✓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 12ms🔗Steps✓Givena reservation exists(4ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe reservation is cancelled(4ms)
✓Thenthe cancellation response should indicate the reservation is cancelled(2ms)
✓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 197ms🔗Steps✓Givena cancelled reservation exists(178ms)
✓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(7ms)
✓Thenthe cancellation response should indicate a conflict(1ms)
✓Cancel steps response message status code should be Conflict(0ms)
Diagrams
Details:lines
Reservations can be deletedDeleting a reservation should return no content 27ms🔗Steps✓Givena reservation exists(13ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe reservation is deleted(12ms)
✓Thenthe reservation delete response should indicate no content(1ms)
✓Delete response status code should be NoContent(0ms)
Diagrams
Details:lines
Reservations can be created and retrievedRetrieving an existing reservation should return the reservation 24ms🔗Steps✓Givena reservation exists(8ms)
✓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(11ms)
✓Thenthe reservation get response should contain the reservation(3ms)
✓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
Specifications Async Api
/asyncapi/asyncapi.json - Serving the AsyncAPI specification describing event-driven messaging
The AsyncApi endpoint should return a valid specification Happy Path227ms🔗Steps
✓Whenthe asyncapi endpoint is called(170ms)
✓Thenthe response should be valid(4ms)
✓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(44ms)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 Path393ms🔗Steps
✓Whenthe open api endpoint is called(383ms)
✓Thenthe response should be valid(2ms)
✓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(1ms)
✓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(2ms)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 Path211ms🔗Steps
✓Whenthe scalar ui endpoint is called(206ms)
✓Thenthe response should be a valid scalar page(1ms)
✓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(10ms)
✓Thenthe staff response should contain the created member(2ms)
✓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 19ms🔗Steps
✓Givena staff member request with an invalid role(0ms)
✓Whenthe staff member is submitted(16ms)
✓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 45ms🔗Steps✓Givena staff member exists(3ms)
✓Post steps response message status code should be Created(0ms)
✓Response content is valid json should be true(0ms)
✓Whenthe staff member is deleted(39ms)
✓Thenthe staff delete response should indicate no content(0ms)
✓Delete response status code should be NoContent(0ms)
Diagrams
Details:lines
Retrieving an existing staff member should return the member 1.0s🔗Steps✓Givena staff member exists(424ms)
✓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(566ms)
✓Thenthe staff get response should contain the member(13ms)
✓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 29ms🔗Steps
✓Whena status update is sent for a non-existent order(23ms)
✓Thenthe status update response should indicate not found(0ms)
✓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 Path75ms🔗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)
✓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)
✓Whenorder updates are streamed via gRPC(48ms)
✓Thenthe streamed response should contain the order status(1ms)
✓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_3877867903006277200'(0ms)
✓Grpc steps streamed replies[0] status should be Created(0ms)
Diagrams
(Warning: 31 spans. This might indicate a problem/recursive loop in your test.)Details:lines
Streaming updates for non-existent order should return not found 37ms🔗Steps
✓Whenorder updates for a non-existent order are streamed via gRPC(31ms)
✓Thenthe gRPC stream should return a not found error(4ms)
✓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 PathIgnoreIfExternalSut323ms🔗Steps
✓Giventhe application is configured with an in-memory log capture(113ms)
✓Anda pancake batch has been created(117ms)
✓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(68ms)
✓Thena structured log entry should have been captured for order creation(10ms)
✓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 Path33ms🔗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 14ms🔗Steps
✓Givena topping id that does not exist(9ms)
✓Whenthe topping is deleted(3ms)
✓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 IgnoreIfExternalSut135ms🔗Steps
✓Giventhe raspberry topping feature flag is disabled(114ms)
✓Whenthe available toppings are requested(13ms)
✓Thenthe toppings response should not include raspberries(5ms)
✓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 IgnoreIfExternalSut180ms🔗Steps
✓Giventhe raspberry topping feature flag is enabled(135ms)
✓Whenthe available toppings are requested(35ms)
✓Thenthe toppings response should include raspberries(7ms)
✓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 Path8ms🔗Steps
✓Whenthe available toppings are requested(2ms)
✓Thenthe toppings response should contain the default toppings(4ms)
✓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 14ms🔗Steps
✓Givena valid topping request(0ms)
✓Whenthe new topping is submitted(8ms)
✓Thenthe topping response should contain the created topping(2ms)
✓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 Path70ms🔗Steps
✓Givena known blueberry topping exists(0ms)
✓Anda valid update topping request(1ms)
✓Whenthe topping is updated(59ms)
✓Thenthe update response should contain the updated topping(4ms)
✓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 passed66ms🔗
#
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
15ms
2
Category
Category is required
'Category' is required.
Bad Request
Passed
8ms
3
Category
javascript:alert(1)
Javascript protocol
Category contains potentially dangerous content.
Bad Request
Passed
8ms
4
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
10ms
5
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
7ms
6
Name
Name is required
'Name' is required.
Bad Request
Passed
14ms
Background
✓Givena known topping exists(0ms)
Steps
✓Anda valid update topping request with "Category" set to "<script>alert('xss')</script>"(2ms)
✓Whenthe invalid update topping request is submitted(6ms)
✓Thenthe update response should contain error "Category contains potentially dangerous content." with status "Bad Request"(4ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Category contains potentially dangerous content.') ](0ms)
Background
✓Givena known topping exists(0ms)
Steps
✓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)
Background
✓Givena known topping exists(0ms)
Steps
✓Anda valid update topping request with "Category" set to "javascript:alert(1)"(0ms)
✓Whenthe invalid update topping request is submitted(1ms)
✓Thenthe update 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)
Background
✓Givena known topping exists(0ms)
Steps
✓Anda valid update topping request with "Name" set to "<img src=x onerror=alert(1)>"(0ms)
✓Whenthe invalid update topping request is submitted(8ms)
✓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)
Background
✓Givena known topping exists(0ms)
Steps
✓Anda valid update topping request with "Name" set to "<script>alert('xss')</script>"(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)
Background
✓Givena known topping exists(0ms)
Steps
✓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 14ms🔗Steps
✓Givena topping id that does not exist(0ms)
✓Anda valid update topping request(0ms)
✓Whenthe topping is updated(4ms)
✓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 passed132ms🔗
#
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
6ms
2
Category
Category is required
'Category' is required.
Bad Request
Passed
62ms
3
Category
javascript:alert(1)
Javascript protocol
Category contains potentially dangerous content.
Bad Request
Passed
9ms
4
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
20ms
5
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
14ms
6
Name
Name is required
'Name' is required.
Bad Request
Passed
18ms
Steps
✓Givena valid topping request with "Category" set to "<script>alert('xss')</script>"(0ms)
✓Whenthe invalid topping request is submitted(4ms)
✓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 "Category" set to ""(3ms)
✓Whenthe invalid topping request is submitted(41ms)
✓Thenthe topping response should contain error "'Category' is required." with status "Bad Request"(2ms)
✓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(7ms)
✓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(16ms)
✓Thenthe topping 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 valid topping request with "Name" set to "<script>alert('xss')</script>"(0ms)
✓Whenthe invalid topping request is submitted(11ms)
✓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(13ms)
✓Thenthe topping 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
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 passed16ms🔗
#
Input Parameters
Status
Duration
Content Type
1
application/xml
Passed
2ms
2
text/html
Passed
9ms
3
text/plain
Passed
4ms
Steps
✓Givena waffle request with content type "application/xml"(0ms)
✓Whenthe waffles are prepared with the given content type(0ms)
✓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"(1ms)
✓Whenthe waffles are prepared with the given content type(2ms)
✓Thenthe waffle response should indicate unsupported media type(3ms)
✓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 Path38ms🔗Steps✓Givena valid waffle recipe with all ingredients(5ms)
✓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(25ms)
✓Thenthe waffles response should contain a valid batch with all ingredients(4ms)
✓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(1ms)
✓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 IgnoreIfExternalSut17ms🔗Steps
✓Giventhe max toppings per item is the configured limit(0ms)
✓Anda valid waffle recipe with all ingredients(7ms)
✓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(1ms)
✓Whenthe waffles are prepared(4ms)
✓Thenthe waffles response should indicate too many toppings(1ms)
✓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 passed200ms🔗
#
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
67ms
2
Butter
Butter is required
'Butter' is required.
Bad Request
Passed
4ms
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
6ms
5
Flour
<img onerror=x>
XSS in flour
Flour contains potentially dangerous content.
Bad Request
Passed
77ms
6
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
3ms
7
Milk
<script>alert</script>
XSS in milk
Milk contains potentially dangerous content.
Bad Request
Passed
9ms
8
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
25ms
Steps
✓Givena valid waffle request with "Butter" set to "<script>alert</script>"(7ms)
✓Whenthe invalid waffle request is submitted(34ms)
✓Thenthe waffle response should contain error "Butter contains potentially dangerous content." with status "Bad Request"(23ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains('Butter contains potentially dangerous content.') ](0ms)
Steps
✓Givena valid waffle request with "Butter" set to ""(0ms)
✓Whenthe invalid waffle request is submitted(2ms)
✓Thenthe waffle response should contain error "'Butter' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Butter' is required.') ](0ms)
Steps
✓Givena valid waffle request with "Eggs" set to ""(1ms)
✓Whenthe invalid waffle request is submitted(2ms)
✓Thenthe waffle response should contain error "'Eggs' is required." with status "Bad Request"(1ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Eggs' is required.') ](0ms)
Steps
✓Givena valid waffle request with "Eggs" set to "javascript:void(0)"(1ms)
✓Whenthe invalid waffle request is submitted(2ms)
✓Thenthe waffle response should contain error "Eggs contains potentially dangerous content." with status "Bad Request"(1ms)
✓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>"(66ms)
✓Whenthe invalid waffle request is submitted(2ms)
✓Thenthe waffle response should contain error "Flour contains potentially dangerous content." with status "Bad Request"(1ms)
✓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"(0ms)
✓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(3ms)
✓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 ""(0ms)
✓Whenthe invalid waffle request is submitted(22ms)
✓Thenthe waffle response should contain error "'Milk' is required." with status "Bad Request"(0ms)
✓Actual results should contain [ r => r.ErrorMessage.Contains(''Milk' is required.') ](0ms)