Creating an order should produce an audit log entry and events
1.2s
Outbox message should transition to failed after exhausting retries
1.0s
Valid order should be created and an event published
917ms
The async api endpoint should return a valid specification
590ms
Audit logs should be returned in descending timestamp order
564ms
Batch completions should contain data ingested via pubsub consumer
472ms
Valid apple cinnamon muffin request should return a fresh batch
443ms
Listing usage by ingredient should return matching records
283ms
Retrieving non existent customer preferences should return not found
258ms
The open api endpoint should return a valid specification
102ms
Creating an order should emit a structured log entry
101ms
Health check should report degraded when multiple downstream services are unavailable
99ms
Order at maximum items per order should be accepted
91ms
Exceeding rate limit should return too many requests
90ms
Requesting second page should return different orders
82ms
Health check should report degraded when cow service is unavailable
81ms
Order exceeding maximum items per order should be rejected
78ms
Goat milk endpoint should return fresh goat milk when feature is enabled
72ms
The scalar ui endpoint should return a valid page
71ms
Order should progress through all status transitions to completion
67ms
Updating an inventory item should return the updated item
64ms
Listing orders should return a paginated response
61ms
Audit logs should be filterable by entity id
57ms
Toppings should include raspberries when feature flag is enabled
56ms
Updating customer preferences should return the updated preferences
54ms
Retrieving non existent review should return not found
51ms
Deleting a reservation should return no content
49ms
Health check should report degraded when downstream service returns non success status
49ms
Same order with different idempotency keys should return different confirmations
48ms
Listing orders with small page size should limit results
47ms
Retrieving an existing staff member should return the member
45ms
Goat milk endpoint should return not found when feature is disabled
44ms
Toppings should exclude raspberries when feature flag is disabled
41ms
Requesting menu when supplier service unavailable should mark items as unavailable
40ms
Creating an order should write an outbox message that gets processed
39ms
Creating an order should produce a retrievable audit log entry
38ms
Popular recipes should return recipe types ordered by frequency
34ms
Ingredient shipments should be recorded when delivered via eventgrid webhook
34ms
Submitting a recipe review should return the created review
34ms
Retrieving existing feedback by id should return the feedback
31ms
Menu endpoint should return all menu items with availability
31ms
Valid status transition should update the order [Created, Cancelled]
30ms
Getting usage summary should return aggregated data
26ms
Muffin request with invalid field should return bad request [Flour, , Flour is required, 'Flour' is required·, Bad Request]
26ms
Listing reviews by recipe should return matching reviews
24ms
Order status for non existent order should return not found
20ms
Order summaries should contain ingested order data
18ms
Deleting an inventory item should return no content
18ms
Order status via grpc should return order details
18ms
Audit logs should be filterable by entity type
18ms
Equipment alerts should contain data ingested via event hub consumer
18ms
Request with correlation id should forward it to cow service
17ms
Retrieving existing customer preferences should return the preferences
17ms
Different muffin recipes should produce the expected batch [Spiced Deluxe, MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Almond Flour, Apples = Pink Lady, Cinnamon = Saigon }, Toppings = System.Collections.Generic.List`1[BreakfastProvider.Tests.…]
16ms
Streaming order updates should return the current status
16ms
Menu should return cached results on subsequent requests
16ms
Request with correlation id should return same id in response
16ms
Listing all inventory items should return all items
15ms
Waffle request with more toppings than allowed should return bad request
15ms
Request with correlation id should forward it to supplier service
15ms
Listing feedback for an order should return the feedback
14ms
Creating an order when kitchen service returns error should still create the order
14ms
Previously created order should be retrievable by id
14ms
Invalid status transition should return conflict [Completed, Preparing]
13ms
Recipe reports should contain ingested recipe data
13ms
Valid status transition should update the order [Ready, Completed]
13ms
Adding a new topping should return the created topping
13ms
Topping request with invalid or dangerous input should return bad request [Category, , Category is required, 'Category' is required·, Bad Request]
13ms
Cancelling an already cancelled reservation should return a conflict response
12ms
Submitting feedback with missing customer name should return bad request
12ms
Listing orders when none exist should return an empty page
12ms
Invalid status transition should return conflict [Created, Ready]
11ms
Ingredient usage should aggregate across multiple recipes
11ms
Valid waffle request with all ingredients should return a fresh batch
10ms
Invalid status transition should return conflict [Ready, Preparing]
10ms
Valid status transition should update the order [Preparing, Ready]
10ms
Invalid status transition should return conflict [Cancelled, Preparing]
10ms
Invalid status transition should return conflict [Cancelled, Ready]
10ms
Waffle recipe summary should return correct data
9ms
Valid status transition should update the order [Created, Preparing]
9ms
Invalid status transition should return conflict [Preparing, Cancelled]
9ms
Requesting goat milk when goat service unavailable should return bad gateway
9ms
Retrieving an existing reservation should return the reservation
9ms
Retrieving an existing inventory item should return the item
8ms
Submitting feedback should return the created feedback
8ms
Invalid status transition should return conflict [Created, Completed]
8ms
Deleting a staff member should return no content
7ms
Daily specials endpoint should return all available specials
7ms
Recording ingredient usage should return the created record
7ms
Update topping with invalid or dangerous input should return bad request [Category, , Category is required, 'Category' is required·, Bad Request]
7ms
Valid pancake request with all ingredients should return a fresh batch
6ms
Same order with same idempotency key should return same confirmation
6ms
Filtering audit logs by a non existent entity type should return an empty collection
6ms
Different muffin recipes should produce the expected batch [Classic, MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Plain Flour, Apples = Granny Smith, Cinnamon = Ceylon }, Toppings = System.Collections.Generic.List`1[BreakfastProvider.Tests.Comp…]
6ms
Streaming updates for non existent order should return not found
5ms
Cancelling a reservation should return the cancelled reservation
4ms
Pancake request with more toppings than allowed should return bad request
4ms
Different muffin recipes should produce the expected batch [Rustic Wholesome, MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Whole Wheat, Apples = Honeycrisp, Cinnamon = Cassia }, Toppings = System.Collections.Generic.List`1[BreakfastProvider.Tes…]
4ms
Order with invalid field should return bad request [Items[0]·Quantity, 0, Quantity must be greater than zero, Quantity must be greater than zero·, Bad Request]
4ms
Saving customer preferences with missing customer name should return bad request
4ms
Heartbeat endpoint should return a running message
4ms
Health check response should include description and data for each entry
3ms
Retrieving existing review by id should return the review
3ms
Deleting an existing topping should return no content
3ms
Order summaries should return an empty list when no orders exist
3ms
Daily special order with invalid field should return bad request [Quantity, 0, Quantity must be greater than zero, Quantity must be greater than zero·, Bad Request]
3ms
Requesting goat milk when goat service returns invalid response should return bad gateway
3ms
Goat milk endpoint should return fresh goat milk from goat service
3ms
Requesting milk when cow service unavailable should return bad gateway
3ms
Remaining quantity should decrease after each order
3ms
Updating an existing topping should return the updated topping
3ms
Creating a reservation should return the confirmed reservation
3ms
Health check endpoint should return healthy status with all dependency details
3ms
Saving customer preferences should return the saved preferences
3ms
Adding a new staff member should return the created member
2ms
Retrieving non existent feedback should return not found
2ms
Ordering daily special beyond threshold should return conflict
2ms
Toppings endpoint should return all available toppings
2ms
Waffle request with invalid ingredient should return bad request [Flour, , Flour is required, 'Flour' is required·, Bad Request]
2ms
Order status update with invalid field should return bad request [Status, , Status is required, 'Status' is required·, Bad Request]
2ms
Pancake request with invalid ingredient should return bad request [Milk, <script>alert</script>, XSS in milk, Milk contains potentially dangerous content·, Bad Request]
2ms
Valid daily special order should return a confirmation
2ms
Requesting milk when cow service returns invalid response should return bad gateway
2ms
Submitting review with missing recipe name should return bad request
2ms
Adding a new inventory item should return the created item
2ms
Topping request with invalid or dangerous input should return bad request [Name, , Name is required, 'Name' is required·, Bad Request]
2ms
Requesting milk when cow service times out should return bad gateway
2ms
Request without correlation id should have one generated in response
1ms
Updating status of non existent order should return not found
1ms
Ordering non existent daily special should return not found
1ms
Recording usage with zero quantity should return bad request
1ms
Muffin request with invalid field should return bad request [Cinnamon, <script>alert('xss')</script>, XSS in cinnamon, Cinnamon contains potentially dangerous content·, Bad Request]
1ms
Waffle request with invalid ingredient should return bad request [Eggs, , Eggs is required, 'Eggs' is required·, Bad Request]
1ms
Pancake recipe summary should return correct data
1ms
Retrieving a non existent order should return not found
1ms
Submitting review with invalid rating should return bad request
1ms
Submitting feedback with invalid rating should return bad request
1ms
Adding a staff member with an invalid role should return a bad request response
1ms
Retrieving a non existent inventory item should return not found
1ms
Daily special order with invalid field should return bad request [SpecialId, null, Special ID is required, 'Special Id' is required·, Bad Request]
1ms
Recording usage with missing ingredient name should return bad request
1ms
Unknown recipe type should return zero batches
1ms
Update topping with invalid or dangerous input should return bad request [Name, , Name is required, 'Name' is required·, Bad Request]
1ms
Deleting a non existent topping should return not found
1ms
Updating a non existent topping should return not found
1ms
Request with unsupported content type should return unsupported media type [text/plain]
1ms
Topping request with invalid or dangerous input should return bad request [Name, <script>alert('xss')</script>, Script tag in name, Name contains potentially dangerous content·, Bad Request]
1ms
Sending request with unsupported content type should return unsupported media type [text/plain]
1ms
Order with invalid field should return bad request [Items, null, At least one item is required, The Items field is required·, Bad Request]
1ms
Muffin request with invalid field should return bad request [Eggs, , Eggs is required, 'Eggs' is required·, Bad Request]
0ms
Muffin request with invalid field should return bad request [Apples, , Apples is required, 'Apples' is required·, Bad Request]
0ms
Muffin request with invalid field should return bad request [Cinnamon, , Cinnamon is required, 'Cinnamon' is required·, Bad Request]
0ms
Muffin request with invalid field should return bad request [Milk, , Milk is required, 'Milk' is required·, Bad Request]
0ms
Order with invalid field should return bad request [Items[0]·ItemType, , Item type is required, 'Item Type' is required·, Bad Request]
0ms
Waffle request with invalid ingredient should return bad request [Milk, , Milk is required, 'Milk' is required·, Bad Request]
0ms
Order with invalid field should return bad request [Items[0]·BatchId, null, Batch ID is required, 'Batch Id' is required·, Bad Request]
0ms
Order with invalid field should return bad request [CustomerName, , Customer name is required, 'Customer Name' is required·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Eggs, javascript:void(0), XSS in eggs, Eggs contains potentially dangerous content·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Flour, <img onerror=x>, XSS in flour, Flour contains potentially dangerous content·, Bad Request]
0ms
Update topping with invalid or dangerous input should return bad request [Category, javascript:alert(1), Javascript protocol, Category contains potentially dangerous content·, Bad Request]
0ms
Update topping with invalid or dangerous input should return bad request [Category, <script>alert('xss')</script>, Script tag in category, Category contains potentially dangerous content·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Eggs, , Eggs is required, 'Eggs' is required·, Bad Request]
0ms
Topping request with invalid or dangerous input should return bad request [Category, javascript:alert(1), Javascript protocol, Category contains potentially dangerous content·, Bad Request]
0ms
Update topping with invalid or dangerous input should return bad request [Name, <script>alert('xss')</script>, Script tag in name, Name contains potentially dangerous content·, Bad Request]
0ms
Waffle request with invalid ingredient should return bad request [Butter, <img onerror=x>, XSS in butter, Butter contains potentially dangerous content·, Bad Request]
0ms
Topping request with invalid or dangerous input should return bad request [Name, <img src=x onerror=alert(1)>, Event handler in name, Name contains potentially dangerous content·, Bad Request]
0ms
Update topping with invalid or dangerous input should return bad request [Name, <img src=x onerror=alert(1)>, Event handler in name, Name contains potentially dangerous content·, Bad Request]
0ms
Waffle request with invalid ingredient should return bad request [Milk, <script>alert</script>, XSS in milk, Milk contains potentially dangerous content·, Bad Request]
0ms
Topping request with invalid or dangerous input should return bad request [Category, <script>alert('xss')</script>, Script tag in category, Category contains potentially dangerous content·, Bad Request]
0ms
Waffle request with invalid ingredient should return bad request [Butter, , Butter is required, 'Butter' is required·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Milk, , Milk is required, 'Milk' is required·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Flour, , Flour is required, 'Flour' is required·, Bad Request]
0ms
Request with unsupported content type should return unsupported media type [application/xml]
0ms
Request with unsupported content type should return unsupported media type [text/html]
0ms
Sending request with unsupported content type should return unsupported media type [text/html]
0ms
Sending request with unsupported content type should return unsupported media type [application/xml]
0ms