Breakfast Provider (BDDfy) Test Run Report

Toppings should exclude raspberries when feature flag is disabled

Order exceeding maximum items per order should be rejected

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"]

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

Creating an order should emit a structured log entry

Toppings should include raspberries when feature flag is enabled

The Scalar UI endpoint should return a valid page

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

Health check should report degraded when cow service is unavailable

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

Exceeding rate limit should return too many requests

Order at maximum items per order should be accepted

Goat milk endpoint should return not found when feature is disabled

Requesting milk when cow service unavailable should return bad gateway

Health check should report degraded when multiple downstream services are unavailable

Creating an order should produce an audit log entry and events

Consuming customer feedback event should trigger downstream processing

Streaming updates for non existent order should return not found

Menu endpoint should return all menu items with availability

Pancake recipe summary should return correct data

Consuming an order served event should trigger downstream processing

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

Getting usage summary should return aggregated data

Batch completions should contain data ingested via pubsub consumer

Retrieving an existing note by id should return the note

Consuming recipe cost event should trigger downstream processing

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

Recording ingredient waste should return the created record

Retrieving existing review by id should return the review

Updating a non existent topping should return not found

Order should progress through all status transitions to completion

Valid apple cinnamon muffin request should return a fresh batch

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

Recipe reports should contain ingested recipe data

Creating an order should produce a retrievable audit log entry

Creating a reservation should return the confirmed reservation

Listing orders when none exist should return an empty page

Order summaries should contain ingested order data

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

Previously created order should be retrievable by id

Popular recipes should return recipe types ordered by frequency

Remaining quantity should decrease after each order

Valid waffle request with all ingredients should return a fresh batch

Listing usage by ingredient should return matching records

Equipment alerts should contain data ingested via event hub consumer

Valid pancake request with all ingredients should return a fresh batch

Retrieving existing feedback by id should return the feedback

Order status via grpc should return order details

Getting the timing summary should return aggregated data

Audit logs should be returned in descending timestamp order

Retrieving an existing inventory item should return the item

Listing feedback for an order should return the feedback

Valid daily special order should return a confirmation

Listing notes by recipe should return matching notes

Ingredient shipments should be recorded when delivered via eventgrid webhook

Updating an existing note should return the updated note

Ingredient usage should aggregate across multiple recipes

The AsyncApi endpoint should return a valid specification

Adding a new staff member should return the created member

Retrieving an existing reservation should return the reservation

Deleting a waste record should return no content

Retrieving an existing staff member should return the member

Listing orders with small page size should limit results

The OpenApi endpoint should return a valid specification

Saving customer preferences should return the saved preferences

Listing readings by equipment should return matching records

Listing reviews by recipe should return matching reviews

Toppings endpoint should return all available toppings

Listing timings by station should return matching records

Listing orders should return a paginated response

Adding a new topping should return the created topping

Cancelling a reservation should return the cancelled reservation

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"]

Updating status of non existent order should return not found

Listing waste by recipe should return matching records

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"]

Adding a new inventory item should return the created item

Retrieving existing customer preferences should return the preferences

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…]

Recording an order timing should return the created record

Streaming order updates should return the current status

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

Outbox message should transition to failed after exhausting retries

Request with correlation id should forward it to supplier service

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"]

Audit logs should be filterable by entity type

Recording a timing with missing station should return bad request

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

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

Same order with different idempotency keys should return different confirmations

Submitting feedback with invalid rating should return bad request

Creating an order should write an outbox message that gets processed

Requesting goat milk when goat service unavailable should return bad gateway

Submitting review with missing recipe name should return bad request

Listing all inventory items should return all items

Submitting feedback should return the created feedback

Health check response should include description and data for each entry

Recording a reading with zero value should return bad request

Requesting second page should return different orders

Updating an inventory item should return the updated item

Deleting a reading should remove it from the list

Deleting an existing topping should return no content

Same order with same idempotency key should return same confirmation

Updating an existing topping should return the updated topping

Ordering daily special beyond threshold should return conflict

Updating customer preferences should return the updated preferences

Menu should return cached results on subsequent requests

Deleting a staff member should return no content

Ordering non existent daily special should return not found

Heartbeat endpoint should return a running message

Waffle request with more toppings than allowed should return bad request

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

Creating a chef note should return the created note

Request with correlation id should return same id in response

Deleting a non existent topping should return not found

Recording ingredient usage should return the created record

Creating a note with missing recipe name should return bad request

Submitting a recipe review should return the created review

Health check endpoint should return healthy status with all dependency details

Creating a note with missing note text should return bad request

Audit logs should be filterable by entity id

Request without correlation id should have one generated in response

Order status for non existent order should return not found

Pancake request with more toppings than allowed should return bad request

Recording a reading with missing metric should return bad request

Requesting menu when supplier service unavailable should mark items as unavailable

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

Goat milk endpoint should return fresh goat milk from goat service

Cancelling an already cancelled reservation should return a conflict response

Recording an equipment reading should return the created record

Retrieving a non existent note should return not found

Deleting a reservation should return no content

Deleting an inventory item should return no content

Order summaries should return an empty list when no orders exist

Waffle recipe summary should return correct data

Retrieving a non existent order should return not found

Recording waste with zero quantity should return bad request

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

Submitting feedback with missing customer name should return bad request

Daily specials endpoint should return all available specials

Unknown recipe type should return zero batches

Updating a non existent note should return not found

Retrieving non existent customer preferences should return not found

Valid order should be created and an event published

Saving customer preferences with missing customer name should return bad request

Retrieving non existent feedback should return not found

Recording usage with zero quantity should return bad request

Recording waste with missing ingredient name should return bad request

Retrieving a non existent inventory item should return not found

Request with correlation id should forward it to cow service

Retrieving non existent review should return not found

Submitting review with invalid rating should return bad request

Recording a timing with zero prep seconds should return bad request

Recording waste with missing reason should return bad request

Recording usage with missing ingredient name should return bad request

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…]

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"]

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"]

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"]

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

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

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

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

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…]

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

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"]

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

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

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

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"]

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

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"]

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

Requesting milk when cow service times out should return bad gateway

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

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"]

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"]

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"]

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"]

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

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

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

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

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"]

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"]

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"]

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

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"]

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

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"]

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"]

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"]

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

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"]

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

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

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"]

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"]

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

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

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

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

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