Order status via grpc should return order details
1.1s
Outbox message should transition to failed after exhausting retries
1.1s
Creating an order should produce an audit log entry and events
927ms
Valid order should be created and an event published
919ms
Equipment alerts should contain data ingested via event hub consumer
645ms
Listing feedback for an order should return the feedback
406ms
Order status for non existent order should return not found
403ms
Getting usage summary should return aggregated data
397ms
The open api endpoint should return a valid specification
255ms
Order exceeding maximum items per order should be rejected
254ms
Listing orders with small page size should limit results
169ms
Order at maximum items per order should be accepted
165ms
Requesting second page should return different orders
148ms
Listing orders should return a paginated response
144ms
Creating an order should emit a structured log entry
143ms
Exceeding rate limit should return too many requests
125ms
Health check should report degraded when cow service is unavailable
121ms
Retrieving existing review by id should return the review
119ms
Menu should return cached results on subsequent requests
114ms
Menu endpoint should return all menu items with availability
113ms
Request with correlation id should forward it to supplier service
110ms
The scalar ui endpoint should return a valid page
108ms
Request with correlation id should forward it to cow service
99ms
The async api endpoint should return a valid specification
97ms
Creating an order should write an outbox message that gets processed
88ms
Health check should report degraded when multiple downstream services are unavailable
79ms
Order should progress through all status transitions to completion
78ms
Requesting menu when supplier service unavailable should mark items as unavailable
77ms
Toppings should include raspberries when feature flag is enabled
77ms
Goat milk endpoint should return fresh goat milk when feature is enabled
71ms
Health check should report degraded when downstream service returns non success status
70ms
Retrieving an existing inventory item should return the item
68ms
Goat milk endpoint should return not found when feature is disabled
68ms
Listing orders when none exist should return an empty page
66ms
Cancelling a reservation should return the cancelled reservation
65ms
Toppings should exclude raspberries when feature flag is disabled
59ms
Audit logs should be filterable by entity type
52ms
Popular recipes should return recipe types ordered by frequency
49ms
Ingredient shipments should be recorded when delivered via eventgrid webhook
46ms
Remaining quantity should decrease after each order
46ms
Creating an order should produce a retrievable audit log entry
46ms
Listing usage by ingredient should return matching records
40ms
Audit logs should be returned in descending timestamp order
38ms
Order summaries should contain ingested order data
36ms
Muffin request with invalid field should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]
32ms
Pancake recipe summary should return correct data
31ms
Valid waffle request with all ingredients should return a fresh batch
29ms
Adding a new staff member should return the created member
26ms
Audit logs should be filterable by entity id
26ms
Valid status transition should update the order [fromStatus: "Ready", toStatus: "Completed"]
22ms
Creating an order when kitchen service returns error should still create the order
22ms
Recipe reports should contain ingested recipe data
21ms
Saving customer preferences should return the saved preferences
21ms
Ingredient usage should aggregate across multiple recipes
21ms
Invalid status transition should return conflict [fromStatus: "Created", toStatus: "Completed"]
21ms
Deleting an inventory item should return no content
20ms
Streaming order updates should return the current status
20ms
Updating an inventory item should return the updated item
20ms
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…]
19ms
Batch completions should contain data ingested via pubsub consumer
19ms
Updating status of non existent order should return not found
18ms
Invalid status transition should return conflict [fromStatus: "Cancelled", toStatus: "Preparing"]
18ms
Invalid status transition should return conflict [fromStatus: "Completed", toStatus: "Preparing"]
18ms
Deleting a staff member should return no content
17ms
Listing reviews by recipe should return matching reviews
17ms
Previously created order should be retrievable by id
16ms
Valid status transition should update the order [fromStatus: "Created", toStatus: "Cancelled"]
16ms
Valid status transition should update the order [fromStatus: "Preparing", toStatus: "Ready"]
16ms
Listing all inventory items should return all items
16ms
Valid status transition should update the order [fromStatus: "Created", toStatus: "Preparing"]
16ms
Adding a staff member with an invalid role should return a bad request response
16ms
Invalid status transition should return conflict [fromStatus: "Ready", toStatus: "Preparing"]
15ms
Invalid status transition should return conflict [fromStatus: "Cancelled", toStatus: "Ready"]
15ms
Invalid status transition should return conflict [fromStatus: "Preparing", toStatus: "Cancelled"]
15ms
Retrieving existing feedback by id should return the feedback
14ms
Invalid status transition should return conflict [fromStatus: "Created", toStatus: "Ready"]
14ms
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"]
13ms
Same order with different idempotency keys should return different confirmations
13ms
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"]
13ms
Requesting goat milk when goat service unavailable should return bad gateway
12ms
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"]
12ms
Valid apple cinnamon muffin request should return a fresh batch
11ms
Retrieving an existing reservation should return the reservation
11ms
Retrieving non existent customer preferences should return not found
11ms
Retrieving an existing staff member should return the member
11ms
Filtering audit logs by a non existent entity type should return an empty collection
11ms
Valid pancake request with all ingredients should return a fresh batch
10ms
Deleting a reservation should return no content
10ms
Order summaries should return an empty list when no orders exist
8ms
Request without correlation id should have one generated in response
8ms
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…]
8ms
Recording usage with zero quantity should return bad request
8ms
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…]
8ms
Unknown recipe type should return zero batches
8ms
Updating customer preferences should return the updated preferences
8ms
Updating an existing topping should return the updated topping
7ms
Retrieving existing customer preferences should return the preferences
7ms
Streaming updates for non existent order should return not found
6ms
Deleting a non existent topping should return not found
6ms
Cancelling an already cancelled reservation should return a conflict response
6ms
Adding a new topping should return the created topping
6ms
Retrieving non existent review should return not found
6ms
Pancake request with more toppings than allowed should return bad request
6ms
Submitting feedback should return the created feedback
5ms
Goat milk endpoint should return fresh goat milk from goat service
5ms
Recording ingredient usage should return the created record
5ms
Ordering daily special beyond threshold should return conflict
5ms
Valid daily special order should return a confirmation
5ms
Same order with same idempotency key should return same confirmation
5ms
Creating a reservation should return the confirmed reservation
5ms
Health check response should include description and data for each entry
5ms
Waffle request with more toppings than allowed should return bad request
5ms
Health check endpoint should return healthy status with all dependency details
5ms
Toppings endpoint should return all available toppings
4ms
Retrieving a non existent inventory item should return not found
4ms
Requesting goat milk when goat service returns invalid response 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
Heartbeat endpoint should return a running message
4ms
Ordering non existent daily special should return not found
3ms
Waffle request with invalid ingredient should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "Bad Request"]
3ms
Deleting an existing topping should return no content
3ms
Retrieving non existent feedback should return not found
3ms
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"]
3ms
Submitting review with missing recipe name should return bad request
3ms
Submitting review with invalid rating should return bad request
3ms
Requesting milk when cow service unavailable should return bad gateway
3ms
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"]
2ms
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"]
2ms
Adding a new inventory item should return the created item
2ms
Requesting milk when cow service times out should return bad gateway
2ms
Muffin request with invalid field should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "Bad Request"]
2ms
Submitting a recipe review should return the created review
2ms
Retrieving a non existent order should return not found
2ms
Requesting milk when cow service returns invalid response should return bad gateway
2ms
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"]
2ms
Waffle request with invalid ingredient should return bad request [field: "Butter", value: "", reason: "Butter is required", expectedError: "'Butter' is required.", expectedStatus: "Bad Request"]
2ms
Recording usage with missing ingredient name should return bad request
2ms
Order with invalid field should return bad request [field: "CustomerName", value: "", reason: "Customer name is required", expectedError: "'Customer Name' is required.", expectedStatus: "Bad Request"]
2ms
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"]
2ms
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"]
2ms
Daily specials endpoint should return all available specials
2ms
Waffle recipe summary should return correct data
2ms
Updating a non existent topping should return not found
2ms
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"]
1ms
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"]
1ms
Request with correlation id should return same id in response
1ms
Muffin request with invalid field should return bad request [field: "Cinnamon", value: "", reason: "Cinnamon is required", expectedError: "'Cinnamon' is required.", expectedStatus: "Bad Request"]
1ms
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"]
1ms
Submitting feedback with missing customer name should return bad request
1ms
Request with unsupported content type should return unsupported media type [contentType: "application/xml"]
1ms
Saving customer preferences with missing customer name should return bad request
1ms
Muffin request with invalid field should return bad request [field: "Apples", value: "", reason: "Apples is required", expectedError: "'Apples' is required.", expectedStatus: "Bad Request"]
1ms
Submitting feedback with invalid rating should return bad request
1ms
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"]
1ms
Pancake request with invalid ingredient should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "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
Muffin request with invalid field should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]
1ms
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"]
1ms
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"]
1ms
Sending request with unsupported content type should return unsupported media type [contentType: "application/xml"]
1ms
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"]
1ms
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"]
1ms
Pancake request with invalid ingredient should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]
1ms
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"]
1ms
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"]
1ms
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"]
1ms
Pancake request with invalid ingredient should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]
1ms
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"]
1ms
Waffle request with invalid ingredient should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]
1ms
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"]
1ms
Waffle request with invalid ingredient should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]
1ms
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"]
1ms
Request with unsupported content type should return unsupported media type [contentType: "text/html"]
1ms
Sending request with unsupported content type should return unsupported media type [contentType: "text/plain"]
0ms
Request with unsupported content type should return unsupported media type [contentType: "text/plain"]
0ms
Sending request with unsupported content type should return unsupported media type [contentType: "text/html"]
0ms