Breakfast Provider (xUnit3) Test Run Report

Creating an order should produce an audit log entry and events

Order status via grpc should return order details

Outbox message should transition to failed after exhausting retries

Equipment alerts should contain data ingested via event hub consumer

Consuming recipe cost event should trigger downstream processing

Listing feedback for an order should return the feedback

Valid order should be created and an event published

Getting usage summary should return aggregated data

The open api endpoint should return a valid specification

Order exceeding maximum items per order should be rejected

Listing orders should return a paginated response

Requesting second page should return different orders

Listing orders with small page size should limit results

Order at maximum items per order should be accepted

Retrieving existing review by id should return the review

The async api endpoint should return a valid specification

Creating an order should emit a structured log entry

Request with correlation id should forward it to supplier service

Order status for non existent order should return not found

Health check should report degraded when multiple downstream services are unavailable

Order should progress through all status transitions to completion

Exceeding rate limit should return too many requests

The scalar ui endpoint should return a valid page

Menu should return cached results on subsequent requests

Creating an order should write an outbox message that gets processed

Goat milk endpoint should return not found when feature is disabled

Menu endpoint should return all menu items with availability

Cancelling a reservation should return the cancelled reservation

Request with correlation id should forward it to cow service

Retrieving an existing inventory item should return the item

Toppings should exclude raspberries when feature flag is disabled

Toppings should include raspberries when feature flag is enabled

Requesting menu when supplier service unavailable should mark items as unavailable

Health check should report degraded when cow service is unavailable

Listing orders when none exist should return an empty page

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

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

Audit logs should be returned in descending timestamp order

Creating an order should produce a retrievable audit log entry

Remaining quantity should decrease after each order

Order summaries should contain ingested order data

Popular recipes should return recipe types ordered by frequency

Ingredient shipments should be recorded when delivered via eventgrid webhook

Listing usage by ingredient should return matching records

Retrieving an existing note by id should return the note

Valid waffle request with all ingredients should return a fresh batch

Recording ingredient waste should return the created record

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

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

Pancake recipe summary should return correct data

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

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

Batch completions should contain data ingested via pubsub consumer

Updating a non existent note should return not found

Adding a new staff member should return the created member

Listing waste by recipe should return matching records

Previously created order should be retrievable by id

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

Recipe reports should contain ingested recipe data

Saving customer preferences should return the saved preferences

Audit logs should be filterable by entity type

Ingredient usage should aggregate across multiple recipes

Listing reviews by recipe should return matching reviews

Audit logs should be filterable by entity id

Updating an inventory item should return the updated item

Deleting an inventory item should return no content

Retrieving existing feedback by id should return the feedback

Streaming order updates should return the current status

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

Recording usage with zero quantity should return bad request

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

Listing notes by recipe should return matching notes

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

Deleting a staff member should return no content

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

Listing all inventory items should return all items

Updating status of non existent order should return not found

Deleting a waste record should return no content

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

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

Consuming customer feedback event should trigger downstream processing

Valid apple cinnamon muffin request should return a fresh batch

Retrieving an existing reservation should return the reservation

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

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

Updating an existing note should return the updated note

Requesting goat milk when goat service unavailable should return bad gateway

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

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

Same order with different idempotency keys should return different confirmations

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

Retrieving an existing staff member should return the member

Deleting a reservation should return no content

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

Retrieving non existent customer preferences should return not found

Valid pancake request with all ingredients should return a fresh batch

Recording ingredient usage should return the created record

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

Retrieving existing customer preferences should return the preferences

Streaming updates for non existent order should return not found

Unknown recipe type should return zero batches

Adding a new topping should return the created topping

Updating customer preferences should return the updated preferences

Request without correlation id should have one generated in response

Order summaries should return an empty list when no orders exist

Deleting a non existent topping should return not found

Updating an existing topping should return the updated topping

Health check response should include description and data for each entry

Health check endpoint should return healthy status with all dependency details

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

Submitting feedback should return the created feedback

Valid daily special order should return a confirmation

Cancelling an already cancelled reservation should return a conflict response

Pancake request with more toppings than allowed 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…]

Goat milk endpoint should return fresh goat milk from goat service

Same order with same idempotency key should return same confirmation

Toppings endpoint should return all available toppings

Ordering daily special beyond threshold should return conflict

Waffle request with more toppings than allowed should return bad request

Creating a reservation should return the confirmed reservation

Heartbeat endpoint should return a running message

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

Order status update with invalid field should return bad request [field: "Status", value: "", reason: "Status is required", expectedError: "'Status' 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"]

Submitting a recipe review should return the created review

Submitting review with invalid rating 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"]

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

Submitting review with missing recipe name should return bad request

Retrieving non existent feedback should return not found

Creating a chef note should return the created note

Recording usage with missing ingredient name should return bad request

Requesting milk when cow service unavailable should return bad gateway

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

Recording waste with missing ingredient name should return bad request

Deleting an existing topping should return no content

Retrieving a non existent inventory item should return not found

Adding a new inventory item should return the created item

Ordering non existent daily special should return not found

Recording waste with zero quantity should return bad request

Request with correlation id should return same id in response

Retrieving non existent review should return not found

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

Waffle recipe summary should return correct data

Requesting milk when cow service times out should return bad gateway

Retrieving a non existent order should return not found

Recording waste with missing reason should return 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"]

Daily specials endpoint should return all available specials

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

Retrieving a non existent note should return not found

Muffin request with invalid field should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", 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"]

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

Creating a note with missing recipe name should return bad request

Submitting feedback with invalid rating should return bad request

Submitting feedback with missing customer name should return bad request

Updating a non existent topping should return not found

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

Saving customer preferences with missing customer name should return 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: "application/xml"]

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

Creating a note with missing note text should return 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"]

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: "Name", value: "<script>alert('xss')</script>", reason: "Script tag in name", expectedError: "Name contains potentially dangerous content.", 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"]

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

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: "Apples", value: "", reason: "Apples is required", expectedError: "'Apples' is required.", 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"]

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

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

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: "<script>alert('xss')</script>", reason: "Script tag in category", expectedError: "Category contains potentially dangerous content.", expectedStatus: "Bad Request"]

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

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

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

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: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", 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"]

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

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

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

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

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

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

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

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