Outbox message should transition to failed after exhausting retries
1.0s
Creating an order should produce an audit log entry and events
947ms
Valid order should be created and an event published
930ms
Audit logs should be filterable by entity id
926ms
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.Com…]
813ms
Batch completions should contain data ingested via pubsub consumer
711ms
The async api endpoint should return a valid specification
668ms
Retrieving existing customer preferences should return the preferences
525ms
Getting usage summary should return aggregated data
385ms
The open api endpoint should return a valid specification
206ms
Health check should report degraded when cow service is unavailable
173ms
Creating an order should emit a structured log entry
173ms
Order at maximum items per order should be accepted
145ms
Goat milk endpoint should return not found when feature is disabled
144ms
Health check should report degraded when downstream service returns non success status
143ms
Exceeding rate limit should return too many requests
140ms
The scalar ui endpoint should return a valid page
128ms
Order exceeding maximum items per order should be rejected
123ms
Toppings should exclude raspberries when feature flag is disabled
116ms
Listing notes by recipe should return matching notes
113ms
Goat milk endpoint should return fresh goat milk when feature is enabled
110ms
Order should progress through all status transitions to completion
101ms
Listing orders should return a paginated response
100ms
Cancelling a reservation should return the cancelled reservation
92ms
Health check should report degraded when multiple downstream services are unavailable
87ms
Listing orders with small page size should limit results
85ms
Toppings should include raspberries when feature flag is enabled
83ms
Same order with different idempotency keys should return different confirmations
77ms
Creating an order should write an outbox message that gets processed
76ms
Requesting second page should return different orders
69ms
Deleting an inventory item should return no content
65ms
Creating a chef note should return the created note
62ms
Order status via grpc should return order details
62ms
Listing usage by ingredient should return matching records
62ms
Adding a new inventory item should return the created item
61ms
Listing feedback for an order should return the feedback
57ms
Creating an order should produce a retrievable audit log entry
56ms
Ingredient shipments should be recorded when delivered via eventgrid webhook
55ms
Popular recipes should return recipe types ordered by frequency
54ms
Listing reviews by recipe should return matching reviews
53ms
Adding a new staff member should return the created member
53ms
Deleting a waste record should return no content
52ms
Muffin request with invalid field should return bad request ["Flour","","Flour is required","'Flour' is required.","Bad Request"]
51ms
Updating a non existent note should return not found
45ms
Pancake recipe summary should return correct data
44ms
Valid waffle request with all ingredients should return a fresh batch
43ms
Audit logs should be filterable by entity type
42ms
Order summaries should contain ingested order data
42ms
Valid apple cinnamon muffin request should return a fresh batch
40ms
Creating an order when kitchen service returns error should still create the order
38ms
Invalid status transition should return conflict ["Cancelled","Preparing"]
38ms
Listing all inventory items should return all items
37ms
Streaming order updates should return the current status
35ms
Audit logs should be returned in descending timestamp order
33ms
Equipment alerts should contain data ingested via event hub consumer
33ms
Menu endpoint should return all menu items with availability
32ms
Listing waste by recipe should return matching records
31ms
Retrieving existing feedback by id should return the feedback
31ms
Request with correlation id should return same id in response
30ms
Recipe reports should contain ingested recipe data
29ms
Menu should return cached results on subsequent requests
28ms
Consuming customer feedback event should trigger downstream processing
27ms
Requesting menu when supplier service unavailable should mark items as unavailable
27ms
Updating an inventory item should return the updated item
27ms
Deleting a staff member should return no content
27ms
Order status for non existent order should return not found
26ms
Previously created order should be retrievable by id
26ms
Ingredient usage should aggregate across multiple recipes
26ms
Request with correlation id should forward it to cow service
25ms
Adding a new topping should return the created topping
24ms
Request with correlation id should forward it to supplier service
23ms
Requesting goat milk when goat service returns invalid response should return bad gateway
22ms
Invalid status transition should return conflict ["Completed","Preparing"]
21ms
Invalid status transition should return conflict ["Created","Ready"]
21ms
Valid pancake request with all ingredients should return a fresh batch
21ms
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.Te…]
20ms
Updating an existing note should return the updated note
20ms
Retrieving existing review by id should return the review
19ms
Invalid status transition should return conflict ["Ready","Preparing"]
19ms
Consuming recipe cost event should trigger downstream processing
19ms
Retrieving a non existent note should return not found
18ms
Listing orders when none exist should return an empty page
18ms
Valid status transition should update the order ["Created","Preparing"]
18ms
Valid status transition should update the order ["Ready","Completed"]
18ms
Retrieving an existing staff member should return the member
18ms
Retrieving an existing reservation should return the reservation
18ms
Valid status transition should update the order ["Preparing","Ready"]
16ms
Creating a note with missing note text should return bad request
16ms
Invalid status transition should return conflict ["Cancelled","Ready"]
15ms
Invalid status transition should return conflict ["Preparing","Cancelled"]
15ms
Valid status transition should update the order ["Created","Cancelled"]
14ms
Deleting a reservation should return no content
14ms
Retrieving a non existent inventory item should return not found
13ms
Invalid status transition should return conflict ["Created","Completed"]
13ms
Health check response should include description and data for each entry
13ms
Daily specials endpoint should return all available specials
12ms
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"]
12ms
Retrieving an existing note by id should return the note
11ms
Filtering audit logs by a non existent entity type should return an empty collection
10ms
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…]
10ms
Updating customer preferences should return the updated preferences
10ms
Same order with same idempotency key should return same confirmation
10ms
Cancelling an already cancelled reservation should return a conflict response
9ms
Retrieving an existing inventory item should return the item
9ms
Streaming updates for non existent order should return not found
9ms
Pancake request with more toppings than allowed should return bad request
9ms
Health check endpoint should return healthy status with all dependency details
8ms
Daily special order with invalid field should return bad request ["SpecialId",null,"Special ID is required","'Special Id' is required.","Bad Request"]
8ms
Waffle request with more toppings than allowed should return bad request
7ms
Recording ingredient usage should return the created record
7ms
Saving customer preferences should return the saved preferences
7ms
Retrieving non existent customer preferences should return not found
7ms
Toppings endpoint should return all available toppings
7ms
Submitting feedback should return the created feedback
7ms
Order summaries should return an empty list when no orders exist
7ms
Deleting a non existent topping should return not found
7ms
Heartbeat endpoint should return a running message
7ms
Goat milk endpoint should return fresh goat milk from goat service
7ms
Recording ingredient waste should return the created record
6ms
Remaining quantity should decrease after each order
6ms
Requesting milk when cow service returns invalid response should return bad gateway
6ms
Order with invalid field should return bad request ["CustomerName","","Customer name is required","'Customer Name' is required.","Bad Request"]
6ms
Creating a reservation should return the confirmed reservation
6ms
Ordering daily special beyond threshold should return conflict
5ms
Updating an existing topping should return the updated topping
5ms
Order status update with invalid field should return bad request ["Status","","Status is required","'Status' is required.","Bad Request"]
5ms
Valid daily special order should return a confirmation
5ms
Updating a non existent topping should return not found
5ms
Retrieving non existent feedback should return not found
5ms
Recording usage with zero quantity should return bad request
5ms
Waffle request with invalid ingredient should return bad request ["Milk","","Milk is required","'Milk' is required.","Bad Request"]
5ms
Pancake request with invalid ingredient should return bad request ["Milk","","Milk is required","'Milk' is required.","Bad Request"]
5ms
Submitting a recipe review should return the created review
5ms
Requesting goat milk when goat service unavailable should return bad gateway
5ms
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"]
4ms
Requesting milk when cow service times out should return bad gateway
4ms
Creating a note with missing recipe name should return bad request
4ms
Requesting milk when cow service unavailable should return bad gateway
4ms
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
Waffle recipe summary should return correct data
3ms
Saving customer preferences with missing customer name should return bad request
3ms
Request without correlation id should have one generated in response
3ms
Unknown recipe type should return zero batches
3ms
Submitting feedback with invalid rating should return bad request
3ms
Deleting an existing topping should return no content
3ms
Updating status of non existent order should return not found
3ms
Adding a staff member with an invalid role should return a bad request response
3ms
Retrieving non existent review should return not found
3ms
Ordering non existent daily special should return not found
2ms
Muffin request with invalid field should return bad request ["Cinnamon","<script>alert('xss')</script>","XSS in cinnamon","Cinnamon contains potentially dangerous content.","Bad Request"]
2ms
Retrieving a non existent order should return not found
2ms
Muffin request with invalid field should return bad request ["Apples","","Apples is required","'Apples' is required.","Bad Request"]
2ms
Recording waste with zero quantity should return bad request
2ms
Submitting feedback with missing customer name should return bad request
2ms
Recording waste with missing ingredient name should return bad request
2ms
Recording usage with missing ingredient name should return bad request
2ms
Waffle request with invalid ingredient should return bad request ["Flour","","Flour is required","'Flour' is required.","Bad Request"]
2ms
Recording waste with missing reason should return bad request
2ms
Submitting review with invalid rating should return bad request
2ms
Submitting review with missing recipe name should return bad request
2ms
Request with unsupported content type should return unsupported media type ["text/plain"]
2ms
Sending request with unsupported content type should return unsupported media type ["text/plain"]
2ms
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"]
1ms
Muffin request with invalid field should return bad request ["Milk","","Milk is required","'Milk' is required.","Bad Request"]
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
Order with invalid field should return bad request ["Items[0].ItemType","","Item type is required","'Item Type' is required.","Bad Request"]
1ms
Update topping with invalid or dangerous input should return bad request ["Category","javascript:alert(1)","Javascript protocol","Category contains potentially dangerous content.","Bad Request"]
1ms
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"]
1ms
Muffin request with invalid field should return bad request ["Cinnamon","","Cinnamon is required","'Cinnamon' is required.","Bad Request"]
1ms
Muffin request with invalid field should return bad request ["Eggs","","Eggs is required","'Eggs' is required.","Bad Request"]
1ms
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"]
1ms
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"]
1ms
Pancake request with invalid ingredient should return bad request ["Flour","","Flour is required","'Flour' is required.","Bad Request"]
1ms
Pancake request with invalid ingredient should return bad request ["Milk","<script>alert</script>","XSS in milk","Milk contains potentially dangerous content.","Bad Request"]
1ms
Pancake request with invalid ingredient should return bad request ["Flour","<img onerror=x>","XSS in flour","Flour contains potentially dangerous content.","Bad Request"]
1ms
Pancake request with invalid ingredient should return bad request ["Eggs","javascript:void(0)","XSS in eggs","Eggs contains potentially dangerous content.","Bad Request"]
1ms
Order with invalid field should return bad request ["Items[0].BatchId",null,"Batch ID is required","'Batch Id' is required.","Bad Request"]
1ms
Pancake request with invalid ingredient should return bad request ["Eggs","","Eggs is required","'Eggs' is required.","Bad Request"]
1ms
Waffle request with invalid ingredient should return bad request ["Butter","<img onerror=x>","XSS in butter","Butter 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
Waffle request with invalid ingredient should return bad request ["Milk","<script>alert</script>","XSS in milk","Milk contains potentially dangerous content.","Bad Request"]
1ms
Update topping with invalid or dangerous input should return bad request ["Name","","Name is required","'Name' is required.","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
Topping request with invalid or dangerous input should return bad request ["Name","","Name is required","'Name' is required.","Bad Request"]
0ms
Waffle request with invalid ingredient should return bad request ["Butter","","Butter is required","'Butter' is required.","Bad Request"]
0ms
Topping request with invalid or dangerous input should return bad request ["Category","","Category is required","'Category' 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 ["Category","","Category is required","'Category' is required.","Bad Request"]
0ms
Sending request with unsupported content type should return unsupported media type ["application/xml"]
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