Breakfast Provider (BDDfy) Test Run Report

Feature	Scenarios	Passed	Steps	Passed	Duration	Avg	Longest
Apple Cinnamon Muffins	10	10	75	75	62ms	6ms	27ms
Audit Logs	5	5	32	32	52ms	10ms	25ms
Chef Notes	8	8	45	45	66ms	8ms	26ms
Customer Feedback	1	1	6	6	50ms	50ms	50ms
Customer Preferences	5	5	29	29	95ms	19ms	50ms
Daily Specials	9	9	50	50	122ms	13ms	50ms
Feedback	6	6	32	32	88ms	14ms	39ms
Grpc	7	7	36	36	360ms	51ms	284ms
Infrastructure	11	11	108	108	840ms	76ms	280ms
Ingredients	8	8	42	42	610ms	76ms	363ms
Ingredient Usage	5	5	28	28	52ms	10ms	23ms
Ingredient Waste	6	6	31	31	69ms	11ms	43ms
Inventory	6	6	33	33	77ms	12ms	20ms
Menu	3	3	24	24	42ms	14ms	15ms
Orders	33	33	203	203	992ms	30ms	292ms
Pancakes	11	11	64	64	41ms	3ms	17ms
Recipe Costs	1	1	6	6	272ms	272ms	272ms
Recipe Reviews	6	6	32	32	130ms	21ms	78ms
Reporting	8	8	43	43	299ms	37ms	56ms
Reservations	5	5	29	29	61ms	12ms	19ms
Specifications	3	3	38	38	38ms	12ms	17ms
Staff	4	4	23	23	48ms	12ms	17ms
Toppings	20	20	121	121	311ms	15ms	142ms
Waffles	11	11	65	65	68ms	6ms	27ms

Syntax	Meaning	Example
`word`	Text search (feature name, scenario name, step text, tags, diagram source)	`order`
`"phrase"`	Exact phrase match	`"create order"`
`&&`	AND — both sides must match	`order && create`
`\|\|`	OR — either side must match	`payment \|\| order`
`!!`	NOT — excludes matches	`order && !!delete`
`( )`	Parentheses — group expressions	`(a \|\| b) && c`
`@tag`	Filter by tag / category	`@smoke && @api`
`$status`	Filter by status	`$failed`, `$passed`, `$skipped`

Scenario Timeline 🛈

Goat milk endpoint should return fresh goat milk when feature is enabled

363ms

Order exceeding maximum items per order should be rejected

292ms

Pancake recipe summary should return correct data

284ms

Health check should report degraded when cow service is unavailable

280ms

Consuming recipe cost event should trigger downstream processing

272ms

Goat milk endpoint should return not found when feature is disabled

197ms

Health check should report degraded when multiple downstream services are unavailable

187ms

Creating an order should emit a structured log entry

176ms

Order at maximum items per order should be accepted

165ms

Exceeding rate limit should return too many requests

163ms

Health check should report degraded when downstream service returns non success status

155ms

Toppings should include raspberries when feature flag is enabled

142ms

Order should progress through all status transitions to completion

113ms

Toppings should exclude raspberries when feature flag is disabled

85ms

Submitting review with missing recipe name should return bad request

78ms

Creating an order should produce an audit log entry and events

75ms

Batch completions should contain data ingested via pubsub consumer

56ms

Remaining quantity should decrease after each order

50ms

Consuming customer feedback event should trigger downstream processing

50ms

Saving customer preferences should return the saved preferences

50ms

Ingredient shipments should be recorded when delivered via eventgrid webhook

50ms

Recipe reports should contain ingested recipe data

44ms

Popular recipes should return recipe types ordered by frequency

44ms

Previously created order should be retrievable by id

44ms

Deleting a waste record should return no content

43ms

Listing feedback for an order should return the feedback

39ms

Ingredient usage should aggregate across multiple recipes

35ms

Requesting milk when cow service unavailable should return bad gateway

34ms

Equipment alerts should contain data ingested via event hub consumer

31ms

Order summaries should contain ingested order data

31ms

Valid apple cinnamon muffin request should return a fresh batch

27ms

Waffle request with invalid ingredient should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "Bad Request"]

27ms

Daily special order with invalid field should return bad request [field: "SpecialId", value: null, reason: "Special ID is required", expectedError: "'Special Id' is required.", expectedStatus: "Bad Request"]

26ms

Listing notes by recipe should return matching notes

26ms

Creating an order should produce a retrievable audit log entry

25ms

Toppings endpoint should return all available toppings

25ms

Streaming updates for non existent order should return not found

24ms

Valid waffle request with all ingredients should return a fresh batch

24ms

Listing usage by ingredient should return matching records

23ms

Listing orders with small page size should limit results

22ms

Order status via grpc should return order details

22ms

Muffin request with invalid field should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "Bad Request"]

21ms

Retrieving existing customer preferences should return the preferences

20ms

Listing all inventory items should return all items

20ms

Creating a reservation should return the confirmed reservation

19ms

Retrieving existing review by id should return the review

19ms

Retrieving an existing inventory item should return the item

18ms

Updating an inventory item should return the updated item

18ms

Valid pancake request with all ingredients should return a fresh batch

17ms

Adding a staff member with an invalid role should return a bad request response

17ms

The OpenApi endpoint should return a valid specification

17ms

Getting usage summary should return aggregated data

16ms

The AsyncApi endpoint should return a valid specification

16ms

Updating an existing note should return the updated note

16ms

Retrieving existing feedback by id should return the feedback

16ms

Retrieving an existing staff member should return the member

16ms

Listing orders when none exist should return an empty page

15ms

Menu endpoint should return all menu items with availability

15ms

Retrieving an existing reservation should return the reservation

15ms

Creating an order when kitchen service returns error should still create the order

15ms

Menu should return cached results on subsequent requests

15ms

Listing reviews by recipe should return matching reviews

14ms

Invalid status transition should return conflict [fromStatus: "Cancelled", toStatus: "Ready"]

14ms

Submitting feedback should return the created feedback

14ms

Listing waste by recipe should return matching records

14ms

Streaming order updates should return the current status

13ms

Cancelling a reservation should return the cancelled reservation

12ms

Audit logs should be returned in descending timestamp order

12ms

Pancake request with invalid ingredient should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]

12ms

Adding a new staff member should return the created member

12ms

Updating an existing topping should return the updated topping

12ms

Requesting menu when supplier service unavailable should mark items as unavailable

11ms

Deleting an inventory item should return no content

11ms

Valid status transition should update the order [fromStatus: "Created", toStatus: "Preparing"]

11ms

Retrieving non existent customer preferences should return not found

10ms

Outbox message should transition to failed after exhausting retries

10ms

Topping request with invalid or dangerous input should return bad request [field: "Name", value: "<script>alert('xss')</script>", reason: "Script tag in name", expectedError: "Name contains potentially dangerous content.", expectedStatus: "Bad Request"]

10ms

Same order with different idempotency keys should return different confirmations

10ms

Different muffin recipes should produce the expected batch [recipeName: "Classic", recipe: MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Plain Flour, Apples = Granny Smith, Cinnamon = Ceylon }, Toppings = System.Collections.Generic.List`1[Breakf…]

10ms

Retrieving an existing note by id should return the note

9ms

Order with invalid field should return bad request [field: "Items[0].ItemType", value: "", reason: "Item type is required", expectedError: "'Item Type' is required.", expectedStatus: "Bad Request"]

9ms

Submitting feedback with invalid rating should return bad request

9ms

Adding a new topping should return the created topping

9ms

Updating customer preferences should return the updated preferences

8ms

Ordering non existent daily special should return not found

8ms

Health check response should include description and data for each entry

8ms

Submitting review with invalid rating should return bad request

8ms

Ordering daily special beyond threshold should return conflict

8ms

Updating a non existent topping should return not found

8ms

Retrieving non existent feedback should return not found

7ms

Recording ingredient usage should return the created record

7ms

Valid daily special order should return a confirmation

7ms

Submitting a recipe review should return the created review

7ms

Deleting a reservation should return no content

7ms

Health check endpoint should return healthy status with all dependency details

7ms

Request without correlation id should have one generated in response

7ms

Request with correlation id should forward it to supplier service

7ms

Update topping with invalid or dangerous input should return bad request [field: "Category", value: "", reason: "Category is required", expectedError: "'Category' is required.", expectedStatus: "Bad Request"]

7ms

Same order with same idempotency key should return same confirmation

6ms

Adding a new inventory item should return the created item

6ms

Listing orders should return a paginated response

6ms

Recording ingredient waste should return the created record

6ms

Sending request with unsupported content type should return unsupported media type [contentType: "text/plain"]

6ms

Requesting second page should return different orders

6ms

Creating an order should write an outbox message that gets processed

6ms

Order status for non existent order should return not found

6ms

Audit logs should be filterable by entity type

5ms

Unknown recipe type should return zero batches

5ms

Goat milk endpoint should return fresh goat milk from goat service

5ms

Cancelling an already cancelled reservation should return a conflict response

5ms

Waffle request with more toppings than allowed should return bad request

5ms

Creating a chef note should return the created note

4ms

Requesting goat milk when goat service unavailable should return bad gateway

4ms

Order status update with invalid field should return bad request [field: "Status", value: "", reason: "Status is required", expectedError: "'Status' is required.", expectedStatus: "Bad Request"]

4ms

Audit logs should be filterable by entity id

4ms

Saving customer preferences with missing customer name should return bad request

4ms

Deleting an existing topping should return no content

4ms

The Scalar UI endpoint should return a valid page

4ms

Order summaries should return an empty list when no orders exist

4ms

Pancake request with more toppings than allowed should return bad request

4ms

Heartbeat endpoint should return a running message

3ms

Request with correlation id should return same id in response

3ms

Filtering audit logs by a non existent entity type should return an empty collection

3ms

Waffle recipe summary should return correct data

3ms

Request with correlation id should forward it to cow service

3ms

Daily specials endpoint should return all available specials

3ms

Recording usage with zero quantity should return bad request

3ms

Creating a note with missing note text should return bad request

2ms

Deleting a staff member should return no content

2ms

Retrieving a non existent order should return not found

2ms

Updating status of non existent order should return not found

2ms

Waffle request with invalid ingredient should return bad request [field: "Milk", value: "<script>alert</script>", reason: "XSS in milk", expectedError: "Milk contains potentially dangerous content.", expectedStatus: "Bad Request"]

2ms

Requesting milk when cow service returns invalid response should return bad gateway

2ms

Updating a non existent note should return not found

2ms

Request with unsupported content type should return unsupported media type [contentType: "text/plain"]

2ms

Recording waste with missing ingredient name should return bad request

2ms

Retrieving a non existent note should return not found

2ms

Retrieving non existent review should return not found

2ms

Retrieving a non existent inventory item should return not found

2ms

Pancake request with invalid ingredient should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "Bad Request"]

1ms

Recording usage with missing ingredient name should return bad request

1ms

Recording waste with missing reason should return bad request

1ms

Submitting feedback with missing customer name should return bad request

1ms

Valid order should be created and an event published

1ms

Recording waste with zero quantity should return bad request

1ms

Creating a note with missing recipe name should return bad request

1ms

Update topping with invalid or dangerous input should return bad request [field: "Name", value: "<img src=x onerror=alert(1)>", reason: "Event handler in name", expectedError: "Name contains potentially dangerous content.", expectedStatus: "Bad Request"]

1ms

Different muffin recipes should produce the expected batch [recipeName: "Rustic Wholesome", recipe: MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Whole Wheat, Apples = Honeycrisp, Cinnamon = Cassia }, Toppings = System.Collections.Generic.List`1…]

1ms

Deleting a non existent topping should return not found

0ms

Order with invalid field should return bad request [field: "Items[0].Quantity", value: "0", reason: "Quantity must be greater than zero", expectedError: "Quantity must be greater than zero.", expectedStatus: "Bad Request"]

0ms

Valid status transition should update the order [fromStatus: "Preparing", toStatus: "Ready"]

0ms

Different muffin recipes should produce the expected batch [recipeName: "Spiced Deluxe", recipe: MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Almond Flour, Apples = Pink Lady, Cinnamon = Saigon }, Toppings = System.Collections.Generic.List`1[Br…]

0ms

Update topping with invalid or dangerous input should return bad request [field: "Category", value: "javascript:alert(1)", reason: "Javascript protocol", expectedError: "Category contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Order with invalid field should return bad request [field: "Items", value: null, reason: "At least one item is required", expectedError: "The Items field is required.", expectedStatus: "Bad Request"]

0ms

Requesting goat milk when goat service returns invalid response should return bad gateway

0ms

Pancake request with invalid ingredient should return bad request [field: "Eggs", value: "javascript:void(0)", reason: "XSS in eggs", expectedError: "Eggs contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Invalid status transition should return conflict [fromStatus: "Preparing", toStatus: "Cancelled"]

0ms

Update topping with invalid or dangerous input should return bad request [field: "Name", value: "<script>alert('xss')</script>", reason: "Script tag in name", expectedError: "Name contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Valid status transition should update the order [fromStatus: "Created", toStatus: "Cancelled"]

0ms

Muffin request with invalid field should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]

0ms

Valid status transition should update the order [fromStatus: "Ready", toStatus: "Completed"]

0ms

Pancake request with invalid ingredient should return bad request [field: "Flour", value: "<img onerror=x>", reason: "XSS in flour", expectedError: "Flour contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Waffle request with invalid ingredient should return bad request [field: "Butter", value: "", reason: "Butter is required", expectedError: "'Butter' is required.", expectedStatus: "Bad Request"]

0ms

Muffin request with invalid field should return bad request [field: "Cinnamon", value: "<script>alert('xss')</script>", reason: "XSS in cinnamon", expectedError: "Cinnamon contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Waffle request with invalid ingredient should return bad request [field: "Butter", value: "<img onerror=x>", reason: "XSS in butter", expectedError: "Butter contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Invalid status transition should return conflict [fromStatus: "Cancelled", toStatus: "Preparing"]

0ms

Update topping with invalid or dangerous input should return bad request [field: "Category", value: "<script>alert('xss')</script>", reason: "Script tag in category", expectedError: "Category contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Order with invalid field should return bad request [field: "CustomerName", value: "", reason: "Customer name is required", expectedError: "'Customer Name' is required.", expectedStatus: "Bad Request"]

0ms

Requesting milk when cow service times out should return bad gateway

0ms

Order with invalid field should return bad request [field: "Items[0].BatchId", value: null, reason: "Batch ID is required", expectedError: "'Batch Id' is required.", expectedStatus: "Bad Request"]

0ms

Daily special order with invalid field should return bad request [field: "Quantity", value: "0", reason: "Quantity must be greater than zero", expectedError: "Quantity must be greater than zero.", expectedStatus: "Bad Request"]

0ms

Topping request with invalid or dangerous input should return bad request [field: "Category", value: "<script>alert('xss')</script>", reason: "Script tag in category", expectedError: "Category contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Pancake request with invalid ingredient should return bad request [field: "Milk", value: "<script>alert</script>", reason: "XSS in milk", expectedError: "Milk contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Muffin request with invalid field should return bad request [field: "Apples", value: "", reason: "Apples is required", expectedError: "'Apples' is required.", expectedStatus: "Bad Request"]

0ms

Topping request with invalid or dangerous input should return bad request [field: "Name", value: "", reason: "Name is required", expectedError: "'Name' is required.", expectedStatus: "Bad Request"]

0ms

Update topping with invalid or dangerous input should return bad request [field: "Name", value: "", reason: "Name is required", expectedError: "'Name' is required.", expectedStatus: "Bad Request"]

0ms

Invalid status transition should return conflict [fromStatus: "Ready", toStatus: "Preparing"]

0ms

Sending request with unsupported content type should return unsupported media type [contentType: "text/html"]

0ms

Waffle request with invalid ingredient should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]

0ms

Invalid status transition should return conflict [fromStatus: "Created", toStatus: "Ready"]

0ms

Topping request with invalid or dangerous input should return bad request [field: "Category", value: "javascript:alert(1)", reason: "Javascript protocol", expectedError: "Category contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Muffin request with invalid field should return bad request [field: "Cinnamon", value: "", reason: "Cinnamon is required", expectedError: "'Cinnamon' is required.", expectedStatus: "Bad Request"]

0ms

Invalid status transition should return conflict [fromStatus: "Created", toStatus: "Completed"]

0ms

Topping request with invalid or dangerous input should return bad request [field: "Category", value: "", reason: "Category is required", expectedError: "'Category' is required.", expectedStatus: "Bad Request"]

0ms

Invalid status transition should return conflict [fromStatus: "Completed", toStatus: "Preparing"]

0ms

Pancake request with invalid ingredient should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]

0ms

Waffle request with invalid ingredient should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]

0ms

Muffin request with invalid field should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]

0ms

Topping request with invalid or dangerous input should return bad request [field: "Name", value: "<img src=x onerror=alert(1)>", reason: "Event handler in name", expectedError: "Name contains potentially dangerous content.", expectedStatus: "Bad Request"]

0ms

Sending request with unsupported content type should return unsupported media type [contentType: "application/xml"]

0ms

Request with unsupported content type should return unsupported media type [contentType: "application/xml"]

0ms

Request with unsupported content type should return unsupported media type [contentType: "text/html"]

0ms

Apple Cinnamon Muffins

Different muffin recipes should produce the expected batch 3/3 passed 11ms🔗

Input Parameters

Status

Duration

Recipe Name

Recipe

Temperature

Duration Minutes

Pan Type

Expected

Classic

{ Ingredients: { Flour = Plain Flour, Apples = Granny Smith, Cinnamon = Ceylon }, Toppings: 2 }

{ "Ingredients": { "Flour": "Plain Flour", "Apples": "Granny Smith", "Cinnamon": "Ceylon" }, "Toppings": [ { "Name": "Streusel", "Amount": "Light" }, { "Name": "Icing Glaze", "Amount": "Drizzle" } ] }

180

Standard

ExpectedIngredientCount	5
ExpectedToppingCount	2
HasBakingInfo	True

Passed

10ms

Rustic Wholesome

{ Ingredients: { Flour = Whole Wheat, Apples = Honeycrisp, Cinnamon = Cassia }, Toppings: 2 }

{ "Ingredients": { "Flour": "Whole Wheat", "Apples": "Honeycrisp", "Cinnamon": "Cassia" }, "Toppings": [ { "Name": "Brown Sugar Crumb", "Amount": "Heavy" }, { "Name": "Maple Drizzle", "Amount": "Light" } ] }

175

Cast Iron

ExpectedIngredientCount	5
ExpectedToppingCount	2
HasBakingInfo	True

Passed

1ms

Spiced Deluxe

{ Ingredients: { Flour = Almond Flour, Apples = Pink Lady, Cinnamon = Saigon }, Toppings: 2 }

{ "Ingredients": { "Flour": "Almond Flour", "Apples": "Pink Lady", "Cinnamon": "Saigon" }, "Toppings": [ { "Name": "Cinnamon Sugar", "Amount": "Heavy" }, { "Name": "Cream Cheese Swirl", "Amount": "Thick" } ] }

190

Silicone

ExpectedIngredientCount	5
ExpectedToppingCount	2
HasBakingInfo	True

Passed

0ms

Steps

✓Given all ingredients are retrieved for the muffin recipe (4ms)

✓When the muffins are prepared (0ms)

✓Then the response should match the expected batch (5ms)

✓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)

✓Muffin steps response toppings should have count '2' (0ms)

✓Baking temperature matches expectation should be true (0ms)

Steps

✓Given all ingredients are retrieved for the muffin recipe (0ms)

✓When the muffins are prepared (0ms)

✓Then the response should match the expected batch (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)

✓Muffin steps response toppings should have count '2' (0ms)

✓Baking temperature matches expectation should be true (0ms)

Steps

✓Given all ingredients are retrieved for the muffin recipe (0ms)

✓When the muffins are prepared (0ms)

✓Then the response should match the expected batch (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)

✓Muffin steps response toppings should have count '2' (0ms)

✓Baking temperature matches expectation should be true (0ms)

Diagrams

Details:lines

Muffin request with invalid field should return bad request 6/6 passed 23ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	Apples		Apples is required	'Apples' is required.	Bad Request	Passed	0ms
2	Cinnamon		Cinnamon is required	'Cinnamon' is required.	Bad Request	Passed	0ms
3	Cinnamon	<script>alert('xss')</script>	XSS in cinnamon	Cinnamon contains potentially dangerous content.	Bad Request	Passed	0ms
4	Eggs		Eggs is required	'Eggs' is required.	Bad Request	Passed	0ms
5	Flour		Flour is required	'Flour' is required.	Bad Request	Passed	0ms
6	Milk		Milk is required	'Milk' is required.	Bad Request	Passed	21ms

Steps

✓Step A muffin request with invalid Apples (0ms)

✓When the muffin validation request is sent (0ms)

✓Then the response should contain error 'Apples' is required. (0ms)

✓Actual error message should contain ''Apples' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A muffin request with invalid Cinnamon (0ms)

✓When the muffin validation request is sent (0ms)

✓Then the response should contain error 'Cinnamon' is required. (0ms)

✓Actual error message should contain ''Cinnamon' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A muffin request with invalid Cinnamon (0ms)

✓When the muffin validation request is sent (0ms)

✓Then the response should contain error Cinnamon contains potentially dangerous content. (0ms)

✓Actual error message should contain 'Cinnamon contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A muffin request with invalid Eggs (0ms)

✓When the muffin validation request is sent (0ms)

✓Then the response should contain error 'Eggs' is required. (0ms)

✓Actual error message should contain ''Eggs' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A muffin request with invalid Flour (0ms)

✓When the muffin validation request is sent (0ms)

✓Then the response should contain error 'Flour' is required. (0ms)

✓Actual error message should contain ''Flour' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A muffin request with invalid Milk (0ms)

✓When the muffin validation request is sent (18ms)

✓Then the response should contain error 'Milk' is required. (1ms)

✓Actual error message should contain ''Milk' is required.' (0ms)

✓And the response status should be Bad Request (1ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Valid apple cinnamon muffin request should return a fresh batch 27ms🔗

Steps

✓Given all ingredients are retrieved for apple cinnamon muffins (4ms)

✓When the muffins are prepared (5ms)

✓Then the response should contain a valid batch with all ingredients (16ms)

✓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 'Some_Fresh_Milk' (0ms)

✓Muffin steps response ingredients should contain 'Some_Eggs' (0ms)

✓Muffin steps response ingredients should contain 'Some_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)

✓And the 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

Audit Logs

Audit logs should be filterable by entity id 4ms🔗

Steps

✓Given an order has been created to generate an audit log (0ms)

✓When audit logs are requested filtered by entity id (2ms)

✓Then the audit log response should be OK (0ms)

✓Audit log response status code should be OK (0ms)

✓And the audit logs should contain the specific order entry (1ms)

✓Audit logs should contain [ l => l.EntityId == 'eee014a4-efc5-46be-8753-964ad94bae41' ] (0ms)

Diagrams

Details:lines

Audit logs should be filterable by entity type 5ms🔗

Steps

✓Given an order has been created to generate an audit log (0ms)

✓When audit logs are requested filtered by entity type (0ms)

✓Then the audit log response should be OK (0ms)

✓Audit log response status code should be OK (0ms)

✓And the audit logs should only contain order entries (5ms)

✓Audit logs should only contain [ l => l.EntityType == AuditLogDefaults.OrderEntityType ] (0ms)

Diagrams

Details:lines

Audit logs should be returned in descending timestamp order 12ms🔗

Steps

✓Given an order has been created to generate an audit log (4ms)

✓When audit logs are requested filtered by entity type (2ms)

✓Then the audit logs should be ordered by timestamp descending (6ms)

✓Audit logs should not be null or empty (0ms)

✓Audit logs should be in descending order [ l => l.Timestamp ] (0ms)

Diagrams

Details:lines

Creating an order should produce a retrievable audit log entry 25ms🔗

Steps

✓Given a pancake batch has been created (5ms)

✓And an order has been created for the batch (4ms)

✓When the audit logs are retrieved (2ms)

✓Then the audit log response should contain the order creation entry (10ms)

✓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_8471728746641930935') ] (0ms)

✓And the downstream services should have received requests (3ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ] (0ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ] (0ms)

Diagrams

Details:lines

Filtering audit logs by a non existent entity type should return an empty collection 3ms🔗

Steps

✓When audit logs are requested filtered by a non existent entity type (2ms)

✓Then the audit log response should be OK (0ms)

✓Audit log response status code should be OK (0ms)

✓And the audit logs should be empty (0ms)

✓Audit logs should be empty (0ms)

Diagrams

Details:lines

Chef Notes

Creating a chef note should return the created note 4ms🔗

Steps

✓Given a valid chef note request is prepared (0ms)

✓When the note is submitted (0ms)

✓Then the response should contain the created note (4ms)

✓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-2aa9335eb98146b1a38c7fb61c3d2505' (0ms)

✓Post steps response note text should be "Remember to fold the batter gently to keep it fluffy." (0ms)

✓Post steps response category should be "Technique" (0ms)

✓Post steps response note id should not be null or empty (0ms)

Diagrams

Details:lines

Creating a note with missing note text should return bad request 2ms🔗

Steps

✓Given a note request with missing note text is prepared (1ms)

✓When the note is submitted (0ms)

✓Then the note response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Creating a note with missing recipe name should return bad request 1ms🔗

Steps

✓Given a note request with missing recipe name is prepared (1ms)

✓When the note is submitted (0ms)

✓Then the note response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Listing notes by recipe should return matching notes 26ms🔗

Steps

✓Given a chef note exists (14ms)

✓When the notes are listed by recipe (3ms)

✓Then the list response should contain the note (7ms)

✓Get steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Get steps list response should contain [ n => n.NoteId == '6dd49927-92bc-47e5-8434-b77285adc695' ] (0ms)

Diagrams

Details:lines

Retrieving a non existent note should return not found 2ms🔗

Steps

✓When a non existent note is retrieved (1ms)

✓Then the get response should indicate not found (0ms)

✓Get steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Retrieving an existing note by id should return the note 9ms🔗

Steps

✓Given a chef note exists (0ms)

✓When the note is retrieved by id (3ms)

✓Then the get response should contain the note (6ms)

✓Get steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Get steps response note id should be '662a69b3-6bab-4d92-9991-b5e447722a60' (0ms)

✓Get steps response recipe name should be 'Recipe-e6a0b4953d8f40a5ac45d03bb4cf66d4' (0ms)

Diagrams

Details:lines

Updating a non existent note should return not found 2ms🔗

Steps

✓When a non existent note is updated (1ms)

✓Then the update response should indicate not found (0ms)

✓Patch steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Updating an existing note should return the updated note 16ms🔗

Steps

✓Given a chef note exists (1ms)

✓When the note is updated (6ms)

✓Then the update response should contain the modified note (8ms)

✓Patch steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Patch steps response note id should be '2f36d8ea-6009-4db9-9317-10d7c4227af1' (0ms)

✓Patch steps response note text should be "Updated: Use unsalted butter for better flavour control." (0ms)

✓Patch steps response category should be "Ingredients" (0ms)

✓Patch steps response updated at should not be null (0ms)

Diagrams

Details:lines

Customer Feedback

Consuming customer feedback event should trigger downstream processing 50ms🔗

Steps

✓Given a customer feedback received event (1ms)

✓When the event is published to pubsub (37ms)

✓Then the feedback id should be generated (2ms)

✓Publish steps feedback id should not be Empty (0ms)

✓And the supplier service should have received the feedback (8ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/ingredients/feedback" && r.Method == HttpMethod.Post ] (0ms)

Diagrams

Details:lines

Customer Preferences

Retrieving existing customer preferences should return the preferences 20ms🔗

Steps

✓Given customer preferences exist (0ms)

✓When the customer preferences are retrieved (5ms)

✓Then the response should contain the preferences (14ms)

✓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 '8aaa9dd3bd0642029f3990cef2c1c439' (0ms)

✓Get steps response preferred milk type should be "Oat" (0ms)

✓Get steps response likes extra toppings should be true (0ms)

Diagrams

Details:lines

Retrieving non existent customer preferences should return not found 10ms🔗

Steps

✓When non existent customer preferences are retrieved (10ms)

✓Then the get response should indicate not found (0ms)

✓Get steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Saving customer preferences should return the saved preferences 50ms🔗

Steps

✓Given a valid customer preference request is prepared (2ms)

✓When the customer preferences are saved (5ms)

✓Then the response should contain the saved preferences (42ms)

✓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

Saving customer preferences with missing customer name should return bad request 4ms🔗

Steps

✓Given a customer preference request with missing customer name is prepared (3ms)

✓When the customer preferences are saved (0ms)

✓Then the put response should indicate bad request (0ms)

✓Put steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Updating customer preferences should return the updated preferences 8ms🔗

Steps

✓Given customer preferences exist (3ms)

✓When the customer preferences are updated (2ms)

✓Then the 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 preferred milk type should be "Almond" (0ms)

✓Put steps response favourite item should be "Belgian Waffles" (0ms)

Diagrams

Details:lines

Daily Specials

Daily special order with invalid field should return bad request 2/2 passed 26ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	Quantity	0	Quantity must be greater than zero	Quantity must be greater than zero.	Bad Request	Passed	0ms
2	SpecialId	null	Special ID is required	'Special Id' is required.	Bad Request	Passed	26ms

Steps

✓Step A daily special order request with invalid Quantity (0ms)

✓When the daily special order request is sent (0ms)

✓Then the response should contain error Quantity must be greater than zero. (0ms)

✓Actual error message should be 'Quantity must be greater than zero.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Daily specials endpoint should return all available specials 3ms🔗

Steps

✓When the available daily specials are requested (0ms)

✓Then the daily specials response should contain all expected specials (2ms)

✓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

Ordering daily special beyond threshold should return conflict 8ms🔗

Steps

✓Given the matcha waffles order count is reset (3ms)

✓And the matcha waffles special has been ordered up to the configured limit (2ms)

✓When another order is placed for the matcha waffles special (1ms)

✓Then the response should indicate the daily special is sold out (0ms)

✓Post steps response message status code should be Conflict (0ms)

Diagrams

Details:lines

Ordering non existent daily special should return not found 8ms🔗

Steps

✓Given a daily special order request for a non existent special (1ms)

✓When the daily special order is submitted (6ms)

✓Then the response should indicate not found (0ms)

✓Post steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Remaining quantity should decrease after each order 50ms🔗

Steps

✓Given the lemon ricotta order count is reset (3ms)

✓And a daily special order for lemon ricotta of quantity one is placed (2ms)

✓When the available daily specials are requested (9ms)

✓Then the lemon ricotta special should have one fewer remaining (35ms)

✓Response content is valid json should be true (0ms)

✓Lemon ricotta remaining quantity should be MaxOrdersPerSpecial - 1 (0ms)

Diagrams

Details:lines

Same order with different idempotency keys should return different confirmations 10ms🔗

Steps

✓Given the cinnamon swirl order count is reset (3ms)

✓And an order request for the same special (0ms)

✓When the order is submitted with two different idempotency keys (5ms)

✓Then the responses should have different confirmation ids (1ms)

✓First confirmation id should not be 'a40fe59e-bc9f-421f-ad2b-fba2ec444ab8' (0ms)

Diagrams

Details:lines

Same order with same idempotency key should return same confirmation 6ms🔗

Steps

✓Given the cinnamon swirl order count is reset (0ms)

✓And an order request with an idempotency key (0ms)

✓When the order is submitted twice with the same idempotency key (5ms)

✓Then both responses should return the same confirmation id (1ms)

✓First confirmation id should be '9d344cf7-09df-46af-baf9-d9f166c02ca5' (0ms)

Diagrams

Details:lines

Valid daily special order should return a confirmation 7ms🔗

Steps

✓Given the cinnamon swirl order count is reset (1ms)

✓And a valid daily special order request for cinnamon swirl (0ms)

✓When the daily special order is submitted (1ms)

✓Then the daily special order response should contain a valid confirmation (4ms)

✓Post steps response message status code should be Created (0ms)

✓Response content is valid json should be true (0ms)

✓Post steps response special id should be CinnamonSwirlId (0ms)

✓Post steps response order confirmation id should not be empty (0ms)

Diagrams

Details:lines

Feedback

Listing feedback for an order should return the feedback 39ms🔗

Steps

✓Given a feedback entry exists (4ms)

✓When the feedback is retrieved by order id (2ms)

✓Then the list response should contain the feedback (31ms)

✓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 == '06d37898-ce9f-4308-b26f-edf73c17a0d2' ] (0ms)

Diagrams

Details:lines

Retrieving existing feedback by id should return the feedback 16ms🔗

Steps

✓Given a feedback entry exists (0ms)

✓When the feedback is retrieved by id (4ms)

✓Then the get response should contain the feedback (11ms)

✓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 '2f04decc-dca3-4d83-884e-ab427cf2a966' (0ms)

✓Get steps response customer name should be 'CustomerName' (0ms)

✓Get steps response rating should be 4 (0ms)

Diagrams

Details:lines

Retrieving non existent feedback should return not found 7ms🔗

Steps

✓When a non existent feedback is retrieved (7ms)

✓Then the get response should indicate not found (0ms)

✓Get steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Submitting feedback should return the created feedback 14ms🔗

Steps

✓Given a valid feedback request is prepared (1ms)

✓When the feedback is submitted (0ms)

✓Then the response should contain the created feedback (12ms)

✓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

Submitting feedback with invalid rating should return bad request 9ms🔗

Steps

✓Given a feedback request with an invalid rating is prepared (2ms)

✓When the feedback is submitted (6ms)

✓Then the post 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 1ms🔗

Steps

✓Given a feedback request with missing customer name is prepared (1ms)

✓When the feedback is submitted (0ms)

✓Then the post response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Grpc

Order status for non existent order should return not found 6ms🔗

Steps

✓When the order status for a non existent order is requested via grpc (2ms)

✓Then the grpc response should be a not found error (3ms)

✓Grpc steps rpc exception should not be null (0ms)

✓Grpc steps rpc exception status code should be NotFound (0ms)

Diagrams

Details:lines

Order status via grpc should return order details 22ms🔗

Steps

✓Given a pancake batch and order have been created (13ms)

✓When the order status is requested via grpc (6ms)

✓Then the grpc response should contain the order details (2ms)

✓Grpc steps order status reply order id should be '6c54855c-0fb6-4db4-ad81-ec1f4c36b540' (0ms)

✓Grpc steps order status reply customer name should be 'TestCustomer_2895495211665839535' (0ms)

✓Grpc steps order status reply status should be Created (0ms)

Diagrams

Details:lines

Pancake recipe summary should return correct data 284ms🔗

Steps

✓When a recipe summary is requested for pancakes (231ms)

✓Then the recipe summary should contain pancake data (52ms)

✓Grpc steps recipe summary reply recipe type should be "Pancakes" (0ms)

✓Grpc steps recipe summary reply total batches should be 42 (0ms)

✓Grpc steps recipe summary reply common ingredients should be equivalent to ["Milk", "Flour", "Eggs"] (0ms)

Diagrams

Details:lines

Streaming order updates should return the current status 13ms🔗

Steps

✓Given a pancake batch and order have been created (7ms)

✓When order updates are streamed via grpc (2ms)

✓Then the streamed response should contain the order status (3ms)

✓Grpc steps streamed replies should have count 1 (0ms)

✓Grpc steps streamed replies[0] order id should be '1fe17778-2b0d-47bc-9048-8a22052370ff' (0ms)

✓Grpc steps streamed replies[0] customer name should be 'TestCustomer_5643028012835868770' (0ms)

✓Grpc steps streamed replies[0] status should be Created (0ms)

Diagrams

Details:lines

Streaming updates for non existent order should return not found 24ms🔗

Steps

✓When order updates for a non existent order are streamed via grpc (23ms)

✓Then the grpc stream should return a not found error (1ms)

✓Grpc steps rpc exception should not be null (0ms)

✓Grpc steps rpc exception status code should be NotFound (0ms)

Diagrams

Details:lines

Unknown recipe type should return zero batches 5ms🔗

Steps

✓When a recipe summary is requested for an unknown type (1ms)

✓Then the recipe summary should contain zero batches and no ingredients (4ms)

✓Grpc steps recipe summary reply recipe type should be "Unknown" (0ms)

✓Grpc steps recipe summary reply total batches should be 0 (0ms)

✓Grpc steps recipe summary reply common ingredients should be empty (0ms)

Diagrams

Details:lines

Waffle recipe summary should return correct data 3ms🔗

Steps

✓When a recipe summary is requested for waffles (1ms)

✓Then the recipe summary should contain waffle data (1ms)

✓Grpc steps recipe summary reply recipe type should be "Waffles" (0ms)

✓Grpc steps recipe summary reply total batches should be 28 (0ms)

✓Grpc steps recipe summary reply common ingredients should be equivalent to ["Milk", "Flour", "Eggs", "Butter"] (0ms)

Diagrams

Details:lines

Infrastructure

Creating an order should emit a structured log entry 176ms🔗

Steps

✓Given the application is configured with in memory log capture (159ms)

✓And a pancake batch has been created (3ms)

✓When the order is submitted (6ms)

✓Then a structured log entry should have been captured for order creation (6ms)

✓Log provider entries should contain [ e => e.Message.Contains("created for customer") ] (0ms)

✓Log provider entries should contain [ e => e.Message.Contains('TelemetryTest_5128038373169139369') ] (0ms)

✓Log provider entries should contain [ e => e.Message.Contains("1 items") ] (0ms)

Diagrams

Details:lines

Health check endpoint should return healthy status with all dependency details 7ms🔗

Steps

✓When the health check endpoint is called (2ms)

✓Then the response should indicate healthy (1ms)

✓Response status code should be OK (0ms)

✓Result should not be null (0ms)

✓Result status should be Healthy (0ms)

✓And all dependency health checks should be present (3ms)

✓Result results should contain key CowService (0ms)

✓Result results should contain key GoatService (0ms)

✓Result results should contain key SupplierService (0ms)

✓Result results should contain key KitchenService (0ms)

✓Result results should contain key CosmosDb (0ms)

✓Result results should contain key Kafka (0ms)

Diagrams

Details:lines

Health check response should include description and data for each entry 8ms🔗

Steps

✓When the health check endpoint is called (3ms)

✓Then each entry should have a status (1ms)

✓Entry value status should not be null or empty $"health check entry '{entry.Key}' should have a status" (0ms)

✓And each downstream entry should have a description (2ms)

✓Result results should contain key 'CowService' (0ms)

✓Result results[check name] description should not be null or empty $"health check entry '{checkName}' should have a description" (0ms)

✓Result results should contain key 'GoatService' (0ms)

✓Result results[check name] description should not be null or empty $"health check entry '{checkName}' should have a description" (0ms)

✓Result results should contain key 'SupplierService' (0ms)

✓Result results[check name] description should not be null or empty $"health check entry '{checkName}' should have a description" (0ms)

✓Result results should contain key 'KitchenService' (0ms)

✓Result results[check name] description should not be null or empty $"health check entry '{checkName}' should have a description" (0ms)

✓And each entry should have a data object (1ms)

✓Entry value data should not be null $"health check entry '{entry.Key}' should have a data object" (0ms)

Diagrams

Details:lines

Health check should report degraded when cow service is unavailable 280ms🔗

Steps

✓Given the cow service is configured to be unreachable (244ms)

✓When the health check endpoint is called (2ms)

✓Then the response should indicate degraded status (4ms)

✓Response status code should be OK (0ms)

✓Result should not be null (0ms)

✓Result status should be Degraded (0ms)

✓And the cow service dependency should report degraded (29ms)

✓Result results should contain key CowService (0ms)

✓Result results[ health check names cow service] status should be Degraded (0ms)

Diagrams

Details:lines

Health check should report degraded when downstream service returns non success status 155ms🔗

Steps

✓Given the kitchen service health check is configured to use a failing endpoint (149ms)

✓When the health check endpoint is called (2ms)

✓Then the response should indicate degraded status (1ms)

✓Result should not be null (0ms)

✓Result status should be Degraded (0ms)

✓And the kitchen service should report degraded with status code description (1ms)

✓Result results should contain key KitchenService (0ms)

✓Kitchen entry status should be Degraded (0ms)

✓Kitchen entry description should contain "503" (0ms)

Diagrams

Details:lines

Health check should report degraded when multiple downstream services are unavailable 187ms🔗

Steps

✓Given the cow service and supplier service are configured to be unreachable (185ms)

✓When the health check endpoint is called (0ms)

✓Then the response should indicate degraded status (0ms)

✓Response status code should be OK (0ms)

✓Result should not be null (0ms)

✓Result status should be Degraded (0ms)

✓And the cow service dependency should report degraded (0ms)

✓Result results should contain key CowService (0ms)

✓Result results[ health check names cow service] status should be Degraded (0ms)

✓And the supplier service dependency should report degraded (1ms)

✓Result results should contain key SupplierService (0ms)

✓Result results[ health check names supplier service] status should be Degraded (0ms)

Diagrams

Details:lines

Heartbeat endpoint should return a running message 3ms🔗

Steps

✓When the heartbeat endpoint is called (2ms)

✓Then the response should indicate the service is running (1ms)

✓Response status code should be OK (0ms)

✓Result should not be null (0ms)

✓Result status should be HeartbeatStatus (0ms)

Diagrams

Details:lines

Request with correlation id should forward it to cow service 3ms🔗

Steps

✓Given a request with a known correlation id (0ms)

✓When milk is requested from the milk endpoint (1ms)

✓Then the 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 '97b064c1-53aa-444d-beae-11908989fd64' (0ms)

Diagrams

Details:lines

Request with correlation id should forward it to supplier service 7ms🔗

Steps

✓Given a request with a known correlation id (0ms)

✓And the menu cache is cleared (1ms)

✓When the menu is requested (1ms)

✓Then the supplier service should have received the correlation id (2ms)

✓Requests should not be empty (0ms)

✓Request headers should contain key CorrelationId (0ms)

✓Request headers[ custom headers correlation id] should be '6c91348a-6cf4-4e00-9b84-1a39af787bbe' (0ms)

Diagrams

Details:lines

Request with correlation id should return same id in response 3ms🔗

Steps

✓Given a request with a known correlation id (0ms)

✓When the request is sent to the menu endpoint (1ms)

✓Then the response should contain the same correlation id (1ms)

✓Response contains correlation id header should be true (0ms)

✓First value of values should be '0532b3ac-0eb6-4ede-8747-fca5cf15ad70' (0ms)

Diagrams

Details:lines

Request without correlation id should have one generated in response 7ms🔗

Steps

✓When a request without a correlation id is sent to the menu endpoint (5ms)

✓Then the response should contain a generated correlation id (1ms)

✓Response contains correlation id header should be true (0ms)

✓First value of values should not be null or empty (0ms)

Diagrams

Details:lines

Ingredients

Goat milk endpoint should return fresh goat milk from goat service 5ms🔗

Steps

✓When goat milk is requested (1ms)

✓Then the response should contain fresh goat milk (1ms)

✓Goat milk steps response message status code should be OK (0ms)

✓Goat milk steps goat milk response should not be null (0ms)

✓Goat milk steps goat milk response goat milk should be FreshGoatMilk (0ms)

✓And the goat service should have received a goat milk request (2ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/goat-milk" && r.Method == HttpMethod.Get ] (0ms)

Diagrams

Details:lines

Goat milk endpoint should return fresh goat milk when feature is enabled 363ms🔗

Steps

✓Given the goat milk feature flag is enabled (320ms)

✓When goat milk is requested (8ms)

✓Then the response should contain fresh goat milk (34ms)

✓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 endpoint should return not found when feature is disabled 197ms🔗

Steps

✓Given the goat milk feature flag is disabled (194ms)

✓When goat milk is requested (0ms)

✓Then the response should indicate feature disabled (2ms)

✓Goat milk steps response message status code should be NotFound (0ms)

✓Body should contain FeatureDisabled (0ms)

Diagrams

Details:lines

Requesting goat milk when goat service returns invalid response should return bad gateway 0ms🔗

Steps

✓Given the goat service will return an invalid response (0ms)

✓When goat milk is requested (0ms)

✓Then the goat milk response should indicate a bad gateway (0ms)

✓Goat milk steps response message status code should be BadGateway (0ms)

✓Body should contain GoatServiceUnavailableTitle (0ms)

Diagrams

Details:lines

Requesting goat milk when goat service unavailable should return bad gateway 4ms🔗

Steps

✓Given the goat service will return service unavailable (0ms)

✓When goat milk is requested (1ms)

✓Then the goat milk response should indicate a bad gateway (3ms)

✓Goat milk steps response message status code should be BadGateway (0ms)

✓Body should contain GoatServiceUnavailableTitle (0ms)

Diagrams

Details:lines

Requesting milk when cow service returns invalid response should return bad gateway 2ms🔗

Steps

✓Given the cow service will return an invalid response (2ms)

✓When milk is requested (0ms)

✓Then the milk response should indicate a bad gateway with unavailable message (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 cow service times out should return bad gateway 0ms🔗

Steps

✓Given the cow service will return a timeout (0ms)

✓When milk is requested (0ms)

✓Then the milk response should indicate a bad gateway with unavailable message (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 cow service unavailable should return bad gateway 34ms🔗

Steps

✓Given the cow service will return service unavailable (1ms)

✓When milk is requested (30ms)

✓Then the milk response should indicate a bad gateway with unavailable message (2ms)

✓Milk steps response message status code should be BadGateway (0ms)

✓Milk error response body should contain CowServiceUnavailableTitle (0ms)

Diagrams

Details:lines

Ingredient Usage

Getting usage summary should return aggregated data 16ms🔗

Steps

✓Given an ingredient usage record exists (0ms)

✓When the summary is requested (6ms)

✓Then the summary should contain aggregated data (10ms)

✓Get steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Get steps summary response should contain [ s => s.IngredientName == 'Flour-f018ee6edba84857b4efaef06970aabe' ] (0ms)

Diagrams

Details:lines

Listing usage by ingredient should return matching records 23ms🔗

Steps

✓Given an ingredient usage record exists (11ms)

✓When the usage is listed by ingredient (3ms)

✓Then the list response should contain the record (7ms)

✓Get steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Get steps list response should contain [ u => u.IngredientName == 'Flour-6d567d1b8cc44a08a4ae24ca85fe31e6' ] (0ms)

Diagrams

Details:lines

Recording ingredient usage should return the created record 7ms🔗

Steps

✓Given a valid ingredient usage request is prepared (0ms)

✓When the usage is recorded (0ms)

✓Then the response should contain the created record (7ms)

✓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-72dbfecc427a4a93b8daf2ac0bd8b0b6' (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

Recording usage with missing ingredient name should return bad request 1ms🔗

Steps

✓Given a usage request with missing ingredient name is prepared (1ms)

✓When the usage is recorded (0ms)

✓Then the post response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Recording usage with zero quantity should return bad request 3ms🔗

Steps

✓Given a usage request with zero quantity is prepared (1ms)

✓When the usage is recorded (0ms)

✓Then the post response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Ingredient Waste

Deleting a waste record should return no content 43ms🔗

Steps

✓Given an ingredient waste record exists (39ms)

✓When the waste record is deleted (3ms)

✓Then the delete response should indicate no content (0ms)

✓Delete steps response message status code should be NoContent (0ms)

Diagrams

Details:lines

Listing waste by recipe should return matching records 14ms🔗

Steps

✓Given an ingredient waste record exists (0ms)

✓When the waste is listed by recipe (4ms)

✓Then the list response should contain the waste record (8ms)

✓Get steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Get steps list response should contain [ w => w.WasteId == '29d2ab1e-90fe-4042-9205-ea254cd2d11c' ] (0ms)

Diagrams

Details:lines

Recording ingredient waste should return the created record 6ms🔗

Steps

✓Given a valid ingredient waste request is prepared (0ms)

✓When the waste is recorded (0ms)

✓Then the response should contain the created waste record (6ms)

✓Post steps response message status code should be Created (0ms)

✓Response content is valid json should be true (0ms)

✓Post steps response ingredient name should not be null or empty (0ms)

✓Post steps response quantity wasted should be '5m' (0ms)

✓Post steps response waste id should not be null or empty (0ms)

✓Post steps response reason should be "Expired before use" (0ms)

Diagrams

Details:lines

Recording waste with missing ingredient name should return bad request 2ms🔗

Steps

✓Given a waste request with missing ingredient name is prepared (1ms)

✓When the waste is recorded (0ms)

✓Then the waste response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Recording waste with missing reason should return bad request 1ms🔗

Steps

✓Given a waste request with missing reason is prepared (1ms)

✓When the waste is recorded (0ms)

✓Then the waste response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Recording waste with zero quantity should return bad request 1ms🔗

Steps

✓Given a waste request with zero quantity is prepared (1ms)

✓When the waste is recorded (0ms)

✓Then the waste response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Inventory

Adding a new inventory item should return the created item 6ms🔗

Steps

✓Given a valid inventory item request is prepared (2ms)

✓When the inventory item is submitted (1ms)

✓Then the response should contain the created item (3ms)

✓Post steps response message status code should be Created (0ms)

✓Response content is valid json should be true (0ms)

✓Post steps response name should be 'Name' (0ms)

✓Post steps response category should be "Dry Goods" (0ms)

Diagrams

Details:lines

Deleting an inventory item should return no content 11ms🔗

Steps

✓Given an inventory item exists (0ms)

✓When the inventory item is deleted (9ms)

✓Then the delete response should indicate no content (2ms)

✓Delete steps response message status code should be NoContent (0ms)

Diagrams

Details:lines

Listing all inventory items should return all items 20ms🔗

Steps

✓Given an inventory item exists (0ms)

✓When all inventory items are requested (4ms)

✓Then the list response should contain the item (15ms)

✓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 == '4' ] (0ms)

Diagrams

Details:lines

Retrieving a non existent inventory item should return not found 2ms🔗

Steps

✓When a non existent inventory item is retrieved (1ms)

✓Then the get response should indicate not found (0ms)

✓Get steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Retrieving an existing inventory item should return the item 18ms🔗

Steps

✓Given an inventory item exists (9ms)

✓When the inventory item is retrieved by id (3ms)

✓Then the get response should contain the item (5ms)

✓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 18ms🔗

Steps

✓Given an inventory item exists (0ms)

✓When the inventory item is updated (11ms)

✓Then the put 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 category should be "Updated Category" (0ms)

Diagrams

Details:lines

Menu endpoint should return all menu items with availability 15ms🔗

Steps

✓When the menu is requested (1ms)

✓Then the menu response should contain all menu items (7ms)

✓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)

✓And the menu items should be in alphabetical order (4ms)

✓Menu steps response should be in ascending order [ m => m.Name ] (0ms)

✓And the supplier service should have received an availability request (2ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath.Contains("/availability") && r.Method == HttpMethod.Get ] (0ms)

Diagrams

Details:lines

Menu should return cached results on subsequent requests 15ms🔗

Steps

✓Given the menu has been requested and cached (10ms)

✓And the supplier service is then made unavailable (0ms)

✓When the menu is requested again (1ms)

✓Then the menu response should still return available items (2ms)

✓Second menu steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Second menu steps response should contain [ m => m.IsAvailable ] (0ms)

Diagrams

Details:lines

Requesting menu when supplier service unavailable should mark items as unavailable 11ms🔗

Steps

✓Given the supplier service will return service unavailable (1ms)

✓When the menu is requested (3ms)

✓Then the menu response should mark all items as unavailable (6ms)

✓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

Orders

Creating an order should produce an audit log entry and events 75ms🔗

Steps

✓Given a pancake batch is created and order request is ready (10ms)

✓When the order is submitted (1ms)

✓Then the order should be created successfully (4ms)

✓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_196697104908492494' (0ms)

✓Order steps response items should have count 1 (0ms)

✓And an order created event should have been published (9ms)

✓And a recipe log should have been published to kafka (49ms)

✓Recipe log messages should contain [ m => m.Message.RecipeType == OrderDefaults.PancakeItemType, "a RecipeLogEvent should have been published for the pancake recipe" ] (0ms)

Diagrams

Details:lines

Creating an order should write an outbox message that gets processed 6ms🔗

Steps

✓Given a pancake batch is created and order request is ready (0ms)

✓When the order is submitted (0ms)

✓Then the order should be created successfully (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_1986979575048728668' (0ms)

✓Order steps response items should have count 1 (0ms)

✓And an outbox message should have been written and processed (5ms)

Diagrams

Details:lines

Creating an order when kitchen service returns error should still create the order 15ms🔗

Steps

✓Given a pancake batch has been created (7ms)

✓And a valid order request for the created batch (0ms)

✓And the kitchen service will return an error (0ms)

✓When the breakfast order is placed (1ms)

✓Then the order should still be created successfully (2ms)

✓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_5765020406570162111' (0ms)

✓And the order should be retrievable by its id (2ms)

Diagrams

Details:lines

Exceeding rate limit should return too many requests 163ms🔗

Steps

✓Given the rate limit is configured to allow one request per window (154ms)

✓And a pancake batch has been created (4ms)

✓And a valid order request is prepared (0ms)

✓When the order is submitted twice in rapid succession (2ms)

✓Then the first request should succeed and the second should be rate limited (1ms)

✓First response status code should be Created (0ms)

✓Second response status code should be TooManyRequests (0ms)

Diagrams

Details:lines

Invalid status transition should return conflict 7/7 passed 17ms🔗

#	Input Parameters		Status	Duration
#	From Status	To Status	Status	Duration
1	Cancelled	Preparing	Passed	0ms
2	Cancelled	Ready	Passed	14ms
3	Completed	Preparing	Passed	0ms
4	Created	Completed	Passed	0ms
5	Created	Ready	Passed	0ms
6	Preparing	Cancelled	Passed	0ms
7	Ready	Preparing	Passed	0ms

Steps

✓Given an order exists with status Cancelled (0ms)

✓When the order status is updated to Preparing (0ms)

✓Then the response should indicate a conflict (0ms)

✓Patch steps response message status code should be Conflict (0ms)

Steps

✓Given an order exists with status Cancelled (12ms)

✓When the order status is updated to Ready (1ms)

✓Then the response should indicate a conflict (0ms)

✓Patch steps response message status code should be Conflict (0ms)

Steps

✓Given an order exists with status Completed (0ms)

✓When the order status is updated to Preparing (0ms)

✓Then the response should indicate a conflict (0ms)

✓Patch steps response message status code should be Conflict (0ms)

Steps

✓Given an order exists with status Created (0ms)

✓When the order status is updated to Completed (0ms)

✓Then the response should indicate a conflict (0ms)

✓Patch steps response message status code should be Conflict (0ms)

Steps

✓Given an order exists with status Created (0ms)

✓When the order status is updated to Ready (0ms)

✓Then the response should indicate a conflict (0ms)

✓Patch steps response message status code should be Conflict (0ms)

Steps

✓Given an order exists with status Preparing (0ms)

✓When the order status is updated to Cancelled (0ms)

✓Then the response should indicate a conflict (0ms)

✓Patch steps response message status code should be Conflict (0ms)

Steps

✓Given an order exists with status Ready (0ms)

✓When the order status is updated to Preparing (0ms)

✓Then the response should indicate a conflict (0ms)

✓Patch steps response message status code should be Conflict (0ms)

Diagrams

Details:lines

Listing orders should return a paginated response 6ms🔗

Steps

✓Given multiple orders have been created (0ms)

✓When the orders are listed (0ms)

✓Then the response should contain a paginated list of orders (6ms)

✓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)

✓List steps response page should be 1 (0ms)

✓List steps response total count should be greater than or equal to '2' (0ms)

Diagrams

Details:lines

Listing orders when none exist should return an empty page 15ms🔗

Steps

✓When the orders are listed (3ms)

✓Then the response should be an empty page (12ms)

✓List steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓List steps response items should be empty (0ms)

✓List steps response total count should be 0 (0ms)

Diagrams

Details:lines

Listing orders with small page size should limit results 22ms🔗

Steps

✓Given multiple orders have been created (12ms)

✓When the orders are listed with page size 1 (1ms)

✓Then the response should contain only one item per page (8ms)

✓List steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓List steps response items should have count 1 (0ms)

✓List steps response total pages should be greater than or equal to '2' (0ms)

Diagrams

Details:lines

Order at maximum items per order should be accepted 165ms🔗

Steps

✓Given the max items per order is configured to 2 (159ms)

✓And a pancake batch is created (0ms)

✓And an order request has 2 items (4ms)

✓When the order is submitted (0ms)

✓Then the order should be created successfully (1ms)

✓Order steps response message status code should be Created (0ms)

Diagrams

Details:lines

Order exceeding maximum items per order should be rejected 292ms🔗

Steps

✓Given the max items per order is configured to 2 (245ms)

✓And a pancake batch is created (5ms)

✓And an order request has 3 items (2ms)

✓When the order is submitted (17ms)

✓Then the response should indicate too many items (21ms)

✓Order steps response message status code should be BadRequest (0ms)

✓Order validation errors should contain [ e => e.Contains("cannot contain more than 2 items") ] (0ms)

Diagrams

Details:lines

Order should progress through all status transitions to completion 113ms🔗

Steps

✓Given a pancake batch has been created (68ms)

✓And a breakfast order has been placed for the batch (13ms)

✓When the order is progressed through the complete lifecycle (10ms)

✓Then the completed order should be retrievable with all details (13ms)

✓And an audit log entry should exist for the order (5ms)

✓And the downstream services should have received requests (3ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ] (0ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ] (0ms)

Diagrams

Details:lines

Order status update with invalid field should return bad request 1/1 passed 4ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	Status		Status is required	'Status' is required.	Bad Request	Passed	4ms

Steps

✓Step An order status update request with invalid Status (0ms)

✓When the order status update request is sent (4ms)

✓Then the response should contain error 'Status' is required. (0ms)

✓Actual error message should be ''Status' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Order with invalid field should return bad request 5/5 passed 12ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	CustomerName		Customer name is required	'Customer Name' is required.	Bad Request	Passed	0ms
2	Items	null	At least one item is required	The Items field is required.	Bad Request	Passed	0ms
3	Items[0].BatchId	null	Batch ID is required	'Batch Id' is required.	Bad Request	Passed	0ms
4	Items[0].ItemType		Item type is required	'Item Type' is required.	Bad Request	Passed	9ms
5	Items[0].Quantity	0	Quantity must be greater than zero	Quantity must be greater than zero.	Bad Request	Passed	0ms

Steps

✓Step An order request with invalid CustomerName (0ms)

✓When the order request is sent (0ms)

✓Then the response should contain error 'Customer Name' is required. (0ms)

✓Actual error message should be ''Customer Name' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An order request with invalid Items (0ms)

✓When the order request is sent (0ms)

✓Then the response should contain error The Items field is required. (0ms)

✓Actual error message should be 'The Items field is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An order request with invalid Items[0].BatchId (0ms)

✓When the order request is sent (0ms)

✓Then the response should contain error 'Batch Id' is required. (0ms)

✓Actual error message should be ''Batch Id' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An order request with invalid Items[0].ItemType (0ms)

✓When the order request is sent (8ms)

✓Then the response should contain error 'Item Type' is required. (0ms)

✓Actual error message should be ''Item Type' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An order request with invalid Items[0].Quantity (0ms)

✓When the order request is sent (0ms)

✓Then the response should contain error Quantity must be greater than zero. (0ms)

✓Actual error message should be 'Quantity must be greater than zero.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Outbox message should transition to failed after exhausting retries 10ms🔗

Steps

✓Given a pending outbox message with a failing dispatcher (4ms)

✓Then the outbox message should transition to failed after exhausting retries (6ms)

Sequence Diagrams

Details:lines

Previously created order should be retrievable by id 44ms🔗

Steps

✓Given a pancake batch has been created (5ms)

✓And an order has been created for the batch (4ms)

✓When the order is retrieved by id (1ms)

✓Then the retrieved order should match the created order (5ms)

✓Retrieval steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Retrieval steps response order id should be 'OrderId' (0ms)

✓Retrieval steps response customer name should be 'TestCustomer_1197008541115915338' (0ms)

✓Retrieval steps response items should have count 1 (0ms)

✓And the downstream services should have received requests (27ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ] (0ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ] (0ms)

Diagrams

Details:lines

Requesting second page should return different orders 6ms🔗

Steps

✓Given multiple orders have been created (0ms)

✓When the second page is requested with page size 1 (1ms)

✓Then the response should be for page 2 (4ms)

✓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 1 (0ms)

✓List steps response page should be 2 (0ms)

Diagrams

Details:lines

Retrieving a non existent order should return not found 2ms🔗

Steps

✓Given a non existent order id (0ms)

✓When the non existent order is retrieved (1ms)

✓Then the response should be not found (0ms)

✓Retrieval steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Updating status of non existent order should return not found 2ms🔗

Steps

✓Given a non existent order id (0ms)

✓When the order status is updated to preparing (1ms)

✓Then the response should indicate not found (0ms)

✓Patch steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Valid order should be created and an event published 1ms🔗

Steps

✓Given a pancake batch is created and order request is ready (0ms)

✓When the order is submitted (0ms)

✓Then the order should be created successfully (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_9021434462039234909' (0ms)

✓Order steps response items should have count 1 (0ms)

✓And an order created event should have been published (0ms)

✓And the 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

Valid status transition should update the order 4/4 passed 13ms🔗

#	Input Parameters		Status	Duration
#	From Status	To Status	Status	Duration
1	Created	Cancelled	Passed	0ms
2	Created	Preparing	Passed	11ms
3	Preparing	Ready	Passed	0ms
4	Ready	Completed	Passed	0ms

Steps

✓Given an order exists with status Created (0ms)

✓When the order status is updated to Cancelled (0ms)

✓Then the response should indicate status 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

✓Given an order exists with status Created (0ms)

✓When the order status is updated to Preparing (0ms)

✓Then the response should indicate status Preparing (11ms)

✓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

✓Given an order exists with status Preparing (0ms)

✓When the order status is updated to Ready (0ms)

✓Then the response should indicate status 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

✓Given an order exists with status Ready (0ms)

✓When the order status is updated to Completed (0ms)

✓Then the response should indicate status Completed (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 'Completed' (0ms)

Diagrams

Details:lines

Pancakes

Pancake request with invalid ingredient should return bad request 6/6 passed 16ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	Eggs		Eggs is required	'Eggs' is required.	Bad Request	Passed	0ms
2	Eggs	javascript:void(0)	XSS in eggs	Eggs contains potentially dangerous content.	Bad Request	Passed	0ms
3	Flour		Flour is required	'Flour' is required.	Bad Request	Passed	12ms
4	Flour	<img onerror=x>	XSS in flour	Flour contains potentially dangerous content.	Bad Request	Passed	0ms
5	Milk		Milk is required	'Milk' is required.	Bad Request	Passed	1ms
6	Milk	<script>alert</script>	XSS in milk	Milk contains potentially dangerous content.	Bad Request	Passed	0ms

Steps

✓Step A pancake request with invalid Eggs (0ms)

✓When the pancake validation request is sent (0ms)

✓Then the response should contain error 'Eggs' is required. (0ms)

✓Actual error message should be ''Eggs' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A pancake request with invalid Eggs (0ms)

✓When the pancake validation request is sent (0ms)

✓Then the response should contain error Eggs contains potentially dangerous content. (0ms)

✓Actual error message should be 'Eggs contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A pancake request with invalid Flour (0ms)

✓When the pancake validation request is sent (10ms)

✓Then the response should contain error 'Flour' is required. (0ms)

✓Actual error message should be ''Flour' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A pancake request with invalid Flour (0ms)

✓When the pancake validation request is sent (0ms)

✓Then the response should contain error Flour contains potentially dangerous content. (0ms)

✓Actual error message should be 'Flour contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A pancake request with invalid Milk (0ms)

✓When the pancake validation request is sent (1ms)

✓Then the response should contain error 'Milk' is required. (0ms)

✓Actual error message should be ''Milk' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A pancake request with invalid Milk (0ms)

✓When the pancake validation request is sent (0ms)

✓Then the response should contain error Milk contains potentially dangerous content. (0ms)

✓Actual error message should be 'Milk contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Pancake request with more toppings than allowed should return bad request 4ms🔗

Steps

✓Given all ingredients are retrieved for pancakes (0ms)

✓And the request has more toppings than the configured limit (1ms)

✓When the pancakes are prepared (0ms)

✓Then the response should indicate too many toppings (2ms)

✓Pancake steps response message status code should be BadRequest (0ms)

✓Body should contain MaxToppingsExceeded (0ms)

Diagrams

Details:lines

Request with unsupported content type should return unsupported media type 3/3 passed 2ms🔗

#	Input Parameters	Status	Duration
#	Content Type	Status	Duration
1	application/xml	Passed	0ms
2	text/html	Passed	0ms
3	text/plain	Passed	2ms

Steps

✓Given a pancake request with an unsupported content type (0ms)

✓When the request is sent (0ms)

✓Then the response should indicate unsupported media type (0ms)

✓Response status code should be UnsupportedMediaType (0ms)

Steps

✓Given a pancake request with an unsupported content type (0ms)

✓When the request is sent (0ms)

✓Then the response should indicate unsupported media type (0ms)

✓Response status code should be UnsupportedMediaType (0ms)

Steps

✓Given a pancake request with an unsupported content type (0ms)

✓When the request is sent (1ms)

✓Then the response should indicate unsupported media type (0ms)

✓Response status code should be UnsupportedMediaType (0ms)

Diagrams

Details:lines

Valid pancake request with all ingredients should return a fresh batch 17ms🔗

Steps

✓Given all ingredients are retrieved for pancakes (6ms)

✓When the pancakes are prepared (2ms)

✓Then the response should contain a valid batch with all ingredients (7ms)

✓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 'Some_Fresh_Milk' (0ms)

✓Pancake steps response ingredients should contain 'Some_Eggs' (0ms)

✓Pancake steps response ingredients should contain 'Some_Flour' (0ms)

✓And the 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

Recipe Costs

Consuming recipe cost event should trigger downstream processing 272ms🔗

Steps

✓Given a recipe cost calculated event (1ms)

✓When the event is published to kafka (265ms)

✓Then the calculation id should be generated (1ms)

✓Publish steps calculation id should not be Empty (0ms)

✓And the kitchen service should have received the preparation request (2ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ] (0ms)

Diagrams

Details:lines

Recipe Reviews

Listing reviews by recipe should return matching reviews 14ms🔗

Steps

✓Given a review entry exists (0ms)

✓When the reviews are listed by recipe (2ms)

✓Then the list response should contain the review (12ms)

✓Get steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Get steps list response should contain [ r => r.ReviewId == '7c205b2c-b5f4-4a04-9ada-669d52f9df80' ] (0ms)

Diagrams

Details:lines

Retrieving existing review by id should return the review 19ms🔗

Steps

✓Given a review entry exists (7ms)

✓When the review is retrieved by id (3ms)

✓Then the get response should contain the review (8ms)

✓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 '8bc28288-95d5-4d72-9f21-ab2b0948604d' (0ms)

✓Get steps response recipe name should be 'Recipe-47838426c26b4a45995d36ac73fb7c83' (0ms)

Diagrams

Details:lines

Retrieving non existent review should return not found 2ms🔗

Steps

✓When a non existent review is retrieved (1ms)

✓Then the get response should indicate not found (0ms)

✓Get steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Submitting a recipe review should return the created review 7ms🔗

Steps

✓Given a valid recipe review request is prepared (0ms)

✓When the review is submitted (0ms)

✓Then the response should contain the created review (6ms)

✓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-50959a3c6d264f9d980a1614b07c753a' (0ms)

✓Post steps response rating should be 5 (0ms)

✓Post steps response review id should not be null or empty (0ms)

Diagrams

Details:lines

Submitting review with invalid rating should return bad request 8ms🔗

Steps

✓Given a review request with an invalid rating is prepared (4ms)

✓When the review is submitted (4ms)

✓Then the post response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Submitting review with missing recipe name should return bad request 78ms🔗

Steps

✓Given a review request with missing recipe name is prepared (7ms)

✓When the review is submitted (59ms)

✓Then the post response should indicate bad request (11ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Reporting

Batch completions should contain data ingested via pubsub consumer 56ms🔗

Steps

✓Given a pancake batch has been created (17ms)

✓When the batch completions are queried via graphql (13ms)

✓Then the response should contain the batch completion record (25ms)

✓Graph ql steps response message status code should be OK (0ms)

✓Graph ql steps batch completions should contain [ r => r.BatchId == '9eb58f20-1786-45a5-bfea-3ec4d6ae3784' && r.RecipeType == "Pancakes" && r.Ingredients.Contains("Milk") ] (0ms)

Diagrams

Details:lines

Equipment alerts should contain data ingested via event hub consumer 31ms🔗

Steps

✓Given a pancake batch has been created (7ms)

✓When the equipment alerts are queried via graphql (7ms)

✓Then the response should contain the equipment alert record (17ms)

✓Graph ql steps response message status code should be OK (0ms)

✓Graph ql steps equipment alerts should contain [ a => a.BatchId == 'b60605e0-34e0-4924-b1b6-e1772021e364' && a.EquipmentName == "Griddle" && a.AlertType == "UsageCycleCompleted" ] (0ms)

Diagrams

Details:lines

Ingredient shipments should be recorded when delivered via eventgrid webhook 50ms🔗

Steps

✓Given an ingredient delivery event has been received via eventgrid webhook (17ms)

✓When the ingredient shipments are queried via graphql (4ms)

✓Then the response should contain the ingredient shipment (28ms)

✓Graph ql steps response message status code should be OK (0ms)

✓Graph ql steps ingredient shipments should contain [ s => s.DeliveryId == 'fa62c568-3a05-4656-860e-180d2c42a7d1' && s.IngredientName == "Milk" && s.Quantity == 50.0m ] (0ms)

Diagrams

Details:lines

Ingredient usage should aggregate across multiple recipes 35ms🔗

Steps

✓Given multiple recipe logs have been ingested with overlapping ingredients (6ms)

✓When the ingredient usage is queried via graphql (3ms)

✓Then the ingredient usage should reflect aggregated counts (25ms)

✓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

Order summaries should contain ingested order data 31ms🔗

Steps

✓Given a pancake batch has been created (7ms)

✓And a breakfast order has been placed for the batch (5ms)

✓When the order summaries are queried via graphql (5ms)

✓Then the response should contain the ingested order summary (13ms)

✓Graph ql steps response message status code should be OK (0ms)

✓Graph ql steps order summaries should contain [ o => o.OrderId == 'f93dbeea-ed86-498e-bece-461746affd0d' && o.CustomerName == 'TestCustomer_569772054734945185' && o.ItemCount == 1 && o.TableNumber == 7 ] (0ms)

Diagrams

Details:lines

Order summaries should return an empty list when no orders exist 4ms🔗

Steps

✓When the order summaries are queried via graphql (0ms)

✓Then the response should not contain the test order (4ms)

✓Graph ql steps response message status code should be OK (0ms)

✓Graph ql steps order summaries should not contain [ o => o.OrderId == '00000000-0000-0000-0000-000000000000' ] (0ms)

Diagrams

Details:lines

Popular recipes should return recipe types ordered by frequency 44ms🔗

Steps

✓Given multiple recipe logs of different types have been ingested (14ms)

✓When the popular recipes are queried via graphql (4ms)

✓Then the popular recipes should be ordered by count descending (24ms)

✓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 reports should contain ingested recipe data 44ms🔗

Steps

✓Given a pancake batch has been created (8ms)

✓When the recipe reports are queried via graphql (10ms)

✓Then the response should contain the ingested recipe reports (26ms)

✓Graph ql steps response message status code should be OK (0ms)

✓Graph ql steps recipe reports should contain [ r => r.OrderId == '2ade922b-f665-485d-bd30-1690ce733dd2' && r.RecipeType == "Pancakes" && r.Ingredients.Contains("Milk") ] (0ms)

Diagrams

Details:lines

Reservations

Cancelling a reservation should return the cancelled reservation 12ms🔗

Steps

✓Given a reservation exists (0ms)

✓When the reservation is cancelled (5ms)

✓Then the cancellation response should indicate cancelled (7ms)

✓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 5ms🔗

Steps

✓Given a cancelled reservation exists (4ms)

✓When the reservation is cancelled (0ms)

✓Then the cancellation response should indicate conflict (0ms)

✓Cancel steps response message status code should be Conflict (0ms)

Diagrams

Details:lines

Creating a reservation should return the confirmed reservation 19ms🔗

Steps

✓Given a valid reservation request is prepared (2ms)

✓When the reservation is submitted (5ms)

✓Then the response should contain the confirmed booking (11ms)

✓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

Deleting a reservation should return no content 7ms🔗

Steps

✓Given a reservation exists (0ms)

✓When the reservation is deleted (2ms)

✓Then the delete response should indicate no content (4ms)

✓Delete response status code should be NoContent (0ms)

Diagrams

Details:lines

Retrieving an existing reservation should return the reservation 15ms🔗

Steps

✓Given a reservation exists (3ms)

✓When the reservation is retrieved by id (3ms)

✓Then the get response should contain the reservation (8ms)

✓Get steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Get steps response id should be '2' (0ms)

✓Get steps response customer name should be 'CustomerName' (0ms)

✓Get steps response status should be "Confirmed" (0ms)

Diagrams

Details:lines

Specifications

The AsyncApi endpoint should return a valid specification 16ms🔗

Steps

✓When the asyncapi endpoint is called (4ms)

✓Then the response status should be ok (0ms)

✓Async api response status code should be OK (0ms)

✓And the response should be valid json (1ms)

✓Async api response is valid json should be true $"response body (first 500 chars): {_asyncApiJsonString?[..Math.Min(_asyncApiJsonString.Length, 500)]}" (0ms)

✓And the asyncapi spec should contain expected top level properties (4ms)

✓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)

✓And the asyncapi spec is written to disk as json (4ms)

asyncapi.json

Diagrams

Details:lines

The OpenApi endpoint should return a valid specification 17ms🔗

Steps

✓When the open api endpoint is called (4ms)

✓Then the response status should be ok (0ms)

✓Swagger response status code should be OK (0ms)

✓And the response should be valid json (1ms)

✓Open api response is valid json should be true (0ms)

✓And the response should contain all the endpoints (7ms)

✓Swagger json root element get property("paths") get property( endpoints swagger pancakes path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger waffles path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger orders path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger order by id path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger toppings path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger menu path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger milk path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger eggs path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger flour path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger goat milk path) should not be null (0ms)

✓Swagger json root element get property("paths") get property( endpoints swagger audit logs path) should not be null (0ms)

✓And the openapi spec is written to disk as json (2ms)

openapi.json

Diagrams

Details:lines

The Scalar UI endpoint should return a valid page 4ms🔗

Steps

✓When the scalar ui endpoint is called (2ms)

✓Then the response status should be ok (0ms)

✓Scalar response status code should be OK (0ms)

✓And the response should be valid html (0ms)

✓Scalar ui response body should contain "<html" (0ms)

✓And the response should refer to scalar (0ms)

✓Scalar ui response body should contain "scalar" (0ms)

Diagrams

Details:lines

Staff

Adding a new staff member should return the created member 12ms🔗

Steps

✓Given a valid staff member request is prepared (2ms)

✓When the staff member is submitted (0ms)

✓Then the response should contain the created member (8ms)

✓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

Adding a staff member with an invalid role should return a bad request response 17ms🔗

Steps

✓Given a staff member request with an invalid role is prepared (1ms)

✓When the staff member is submitted (15ms)

✓Then the post response should indicate bad request (0ms)

✓Post steps response message status code should be BadRequest (0ms)

Diagrams

Details:lines

Deleting a staff member should return no content 2ms🔗

Steps

✓Given a staff member exists (0ms)

✓When the staff member is deleted (1ms)

✓Then the 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 16ms🔗

Steps

✓Given a staff member exists (3ms)

✓When the staff member is retrieved by id (5ms)

✓Then the get response should contain the member (7ms)

✓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 name should be 'Name' (0ms)

✓Get steps response role should be "Chef" (0ms)

Diagrams

Details:lines

Toppings

Adding a new topping should return the created topping 9ms🔗

Steps

✓Given a valid topping request (0ms)

✓When the new topping is submitted (3ms)

✓Then the topping response should contain the created topping (5ms)

✓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

Deleting a non existent topping should return not found 0ms🔗

Steps

✓Given a topping id that does not exist (0ms)

✓When the topping is deleted (0ms)

✓Then the delete response should indicate not found (0ms)

✓Delete steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Deleting an existing topping should return no content 4ms🔗

Steps

✓Given a known topping exists (0ms)

✓When the topping is deleted (3ms)

✓Then the delete response should indicate success (0ms)

✓Delete steps response message status code should be NoContent (0ms)

Diagrams

Details:lines

Topping request with invalid or dangerous input should return bad request 6/6 passed 12ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	Category		Category is required	'Category' is required.	Bad Request	Passed	0ms
2	Category	<script>alert('xss')</script>	Script tag in category	Category contains potentially dangerous content.	Bad Request	Passed	0ms
3	Category	javascript:alert(1)	Javascript protocol	Category contains potentially dangerous content.	Bad Request	Passed	0ms
4	Name		Name is required	'Name' is required.	Bad Request	Passed	0ms
5	Name	<img src=x onerror=alert(1)>	Event handler in name	Name contains potentially dangerous content.	Bad Request	Passed	0ms
6	Name	<script>alert('xss')</script>	Script tag in name	Name contains potentially dangerous content.	Bad Request	Passed	10ms

Steps

✓Step A topping request with invalid Category (0ms)

✓When the topping request is sent (0ms)

✓Then the response should contain error 'Category' is required. (0ms)

✓Actual error message should be ''Category' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A topping request with invalid Category (0ms)

✓When the topping request is sent (0ms)

✓Then the response should contain error Category contains potentially dangerous content. (0ms)

✓Actual error message should be 'Category contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A topping request with invalid Category (0ms)

✓When the topping request is sent (0ms)

✓Then the response should contain error Category contains potentially dangerous content. (0ms)

✓Actual error message should be 'Category contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A topping request with invalid Name (0ms)

✓When the topping request is sent (0ms)

✓Then the response should contain error 'Name' is required. (0ms)

✓Actual error message should be ''Name' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A topping request with invalid Name (0ms)

✓When the topping request is sent (0ms)

✓Then the response should contain error Name contains potentially dangerous content. (0ms)

✓Actual error message should be 'Name contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A topping request with invalid Name (0ms)

✓When the topping request is sent (8ms)

✓Then the response should contain error Name contains potentially dangerous content. (0ms)

✓Actual error message should be 'Name contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Toppings endpoint should return all available toppings 25ms🔗

Steps

✓When the available toppings are requested (3ms)

✓Then the toppings response should contain the default toppings (21ms)

✓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

Toppings should exclude raspberries when feature flag is disabled 85ms🔗

Steps

✓Given the raspberry topping feature flag is disabled (73ms)

✓When toppings are requested (3ms)

✓Then the toppings response should not include raspberries (8ms)

✓Toppings steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Toppings steps response should not contain [ t => t.Name == ToppingDefaults.Raspberries ] (0ms)

Diagrams

Details:lines

Toppings should include raspberries when feature flag is enabled 142ms🔗

Steps

✓Given the raspberry topping feature flag is enabled (137ms)

✓When toppings are requested (0ms)

✓Then the toppings response should include raspberries (4ms)

✓Toppings steps response message status code should be OK (0ms)

✓Response content is valid json should be true (0ms)

✓Toppings steps response should contain [ t => t.Name == ToppingDefaults.Raspberries ] (0ms)

Diagrams

Details:lines

Update topping with invalid or dangerous input should return bad request 6/6 passed 10ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	Category		Category is required	'Category' is required.	Bad Request	Passed	7ms
2	Category	<script>alert('xss')</script>	Script tag in category	Category contains potentially dangerous content.	Bad Request	Passed	0ms
3	Category	javascript:alert(1)	Javascript protocol	Category contains potentially dangerous content.	Bad Request	Passed	0ms
4	Name		Name is required	'Name' is required.	Bad Request	Passed	0ms
5	Name	<img src=x onerror=alert(1)>	Event handler in name	Name contains potentially dangerous content.	Bad Request	Passed	1ms
6	Name	<script>alert('xss')</script>	Script tag in name	Name contains potentially dangerous content.	Bad Request	Passed	0ms

Steps

✓Step An update topping request with invalid Category (0ms)

✓When the update topping request is sent (5ms)

✓Then the response should contain error 'Category' is required. (0ms)

✓Actual error message should be ''Category' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An update topping request with invalid Category (0ms)

✓When the update topping request is sent (0ms)

✓Then the response should contain error Category contains potentially dangerous content. (0ms)

✓Actual error message should be 'Category contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An update topping request with invalid Category (0ms)

✓When the update topping request is sent (0ms)

✓Then the response should contain error Category contains potentially dangerous content. (0ms)

✓Actual error message should be 'Category contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An update topping request with invalid Name (0ms)

✓When the update topping request is sent (0ms)

✓Then the response should contain error 'Name' is required. (0ms)

✓Actual error message should be ''Name' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An update topping request with invalid Name (0ms)

✓When the update topping request is sent (1ms)

✓Then the response should contain error Name contains potentially dangerous content. (0ms)

✓Actual error message should be 'Name contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step An update topping request with invalid Name (0ms)

✓When the update topping request is sent (0ms)

✓Then the response should contain error Name contains potentially dangerous content. (0ms)

✓Actual error message should be 'Name contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Updating a non existent topping should return not found 8ms🔗

Steps

✓Given a topping id that does not exist and a valid update request (0ms)

✓When the topping is updated (6ms)

✓Then the update response should indicate not found (0ms)

✓Put steps response message status code should be NotFound (0ms)

Diagrams

Details:lines

Updating an existing topping should return the updated topping 12ms🔗

Steps

✓Given a known topping exists and a valid update request (4ms)

✓When the topping is updated (0ms)

✓Then the update response should contain the updated topping (7ms)

✓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

Waffles

Sending request with unsupported content type should return unsupported media type 3/3 passed 6ms🔗

#	Input Parameters	Status	Duration
#	Content Type	Status	Duration
1	application/xml	Passed	0ms
2	text/html	Passed	0ms
3	text/plain	Passed	6ms

Steps

✓Given a waffle request with an unsupported content type (0ms)

✓When the request is sent (0ms)

✓Then the response should indicate unsupported media type (0ms)

✓Response status code should be UnsupportedMediaType (0ms)

Steps

✓Given a waffle request with an unsupported content type (0ms)

✓When the request is sent (0ms)

✓Then the response should indicate unsupported media type (0ms)

✓Response status code should be UnsupportedMediaType (0ms)

Steps

✓Given a waffle request with an unsupported content type (0ms)

✓When the request is sent (2ms)

✓Then the response should indicate unsupported media type (4ms)

✓Response status code should be UnsupportedMediaType (0ms)

Diagrams

Details:lines

Valid waffle request with all ingredients should return a fresh batch 24ms🔗

Steps

✓Given all ingredients are retrieved for waffles (5ms)

✓When the waffles are prepared (2ms)

✓Then the response should contain a valid batch with all ingredients (10ms)

✓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 'Some_Fresh_Milk' (0ms)

✓Waffle steps response ingredients should contain 'Some_Eggs' (0ms)

✓Waffle steps response ingredients should contain 'Some_Flour' (0ms)

✓Waffle steps response ingredients should contain UnsaltedButter (0ms)

✓And the cow service should have received a milk request (5ms)

✓Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ] (0ms)

Diagrams

Details:lines

Waffle request with invalid ingredient should return bad request 6/6 passed 31ms🔗

#	Input Parameters					Status	Duration
#	Field	Value	Reason	Expected Error	Expected Status	Status	Duration
1	Butter		Butter is required	'Butter' is required.	Bad Request	Passed	0ms
2	Butter	<img onerror=x>	XSS in butter	Butter contains potentially dangerous content.	Bad Request	Passed	0ms
3	Eggs		Eggs is required	'Eggs' is required.	Bad Request	Passed	0ms
4	Flour		Flour is required	'Flour' is required.	Bad Request	Passed	0ms
5	Milk		Milk is required	'Milk' is required.	Bad Request	Passed	27ms
6	Milk	<script>alert</script>	XSS in milk	Milk contains potentially dangerous content.	Bad Request	Passed	2ms

Steps

✓Step A waffle request with invalid Butter (0ms)

✓When the waffle validation request is sent (0ms)

✓Then the response should contain error 'Butter' is required. (0ms)

✓Actual error message should be ''Butter' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A waffle request with invalid Butter (0ms)

✓When the waffle validation request is sent (0ms)

✓Then the response should contain error Butter contains potentially dangerous content. (0ms)

✓Actual error message should be 'Butter contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A waffle request with invalid Eggs (0ms)

✓When the waffle validation request is sent (0ms)

✓Then the response should contain error 'Eggs' is required. (0ms)

✓Actual error message should be ''Eggs' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A waffle request with invalid Flour (0ms)

✓When the waffle validation request is sent (0ms)

✓Then the response should contain error 'Flour' is required. (0ms)

✓Actual error message should be ''Flour' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A waffle request with invalid Milk (3ms)

✓When the waffle validation request is sent (22ms)

✓Then the response should contain error 'Milk' is required. (0ms)

✓Actual error message should be ''Milk' is required.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Steps

✓Step A waffle request with invalid Milk (0ms)

✓When the waffle validation request is sent (2ms)

✓Then the response should contain error Milk contains potentially dangerous content. (0ms)

✓Actual error message should be 'Milk contains potentially dangerous content.' (0ms)

✓And the response status should be Bad Request (0ms)

✓Actual response status should be 'Bad Request' (0ms)

Diagrams

Details:lines

Waffle request with more toppings than allowed should return bad request 5ms🔗

Steps

✓Given all ingredients are retrieved for waffles (0ms)

✓And the request has more toppings than the configured limit (2ms)

✓When the waffles are prepared (0ms)

✓Then the response should indicate too many toppings (2ms)

✓Waffle steps response message status code should be BadRequest (0ms)

✓Body should contain MaxToppingsExceeded (0ms)

Diagrams

Details:lines

Execution		Content
Overall status:	Passed	Features:	24
Start Date:	2026-06-23 (UTC)	Scenarios:	192
Start Time:	09:04:05 (UTC)	Passed Scenarios:	192
End Time:	09:04:17 (UTC)	Failed Scenarios:	0
Duration:	11s	Skipped Scenarios:	0
Kronikol Version:	3.0.43+93bf08d0b1f5375ddbce6ed6f5bbd653d4283376

CI (GitHubActions)
Build #:	237
Branch:	main
Commit:	`47252c7`
Pipeline:	View Run
Repository:	lemonlion/BreakfastProvider

Breakfast Provider (BDDfy) Test Run Report

Test Execution Summary

Filtering