Breakfast Provider (NUnit) Test Run Report

Features Summary
FeatureScenariosPassedFailedSkippedStepsPassedFailedSkippedDurationAvgLongest
Apple Cinnamon Muffins Creation Tests10100000001s100ms879ms
Audit Logs Filtering Tests440000001s270ms990ms
Audit Logs Retrieval Tests110018180063ms63ms63ms
Chef Notes Management Tests88000000321ms40ms120ms
Customer Feedback Alert Tests1100000030ms30ms30ms
Customer Preferences Management Tests55000000574ms114ms538ms
Daily Specials Idempotency Tests22000000108ms54ms93ms
Daily Specials Not Found Tests110000003ms3ms3ms
Daily Specials Ordering Tests4400000037ms9ms16ms
Daily Specials Validation Tests2200000013ms6ms9ms
Equipment Readings Monitoring Tests55000000334ms66ms279ms
Feedback Management Tests66000000130ms21ms76ms
Grpc Order Status Tests2200000063ms31ms35ms
Grpc Recipe Summary Tests3300000064ms21ms54ms
Grpc Stream Order Updates Tests2200000044ms22ms36ms
Infrastructure Correlation Id Tests2200000036ms18ms31ms
Infrastructure Degraded Health Check Tests22000000317ms158ms222ms
Infrastructure Downstream Error Health Check Tests11000000122ms122ms122ms
Infrastructure Header Propagation Tests2200000047ms23ms25ms
Infrastructure Health Check Detail Tests1100000014ms14ms14ms
Infrastructure Health Check Tests1100000011ms11ms11ms
Infrastructure Heartbeat Tests110000007ms7ms7ms
Infrastructure Telemetry Tests11000000223ms223ms223ms
Ingredients Goat Milk Downstream Failure Tests2200000028ms14ms22ms
Ingredients Goat Milk Feature Flag Tests22000000229ms114ms126ms
Ingredients Goat Milk Sourcing Tests110000008ms8ms8ms
Ingredients Milk Downstream Failure Tests3300000089ms29ms74ms
Ingredient Usage Analytics Tests55000000455ms91ms365ms
Ingredient Waste Tracking Tests66000000103ms17ms51ms
Inventory Management Tests66000000243ms40ms69ms
Menu Availability Tests1100000058ms58ms58ms
Menu Caching Tests1100000034ms34ms34ms
Menu Downstream Failure Tests1100000028ms28ms28ms
Orders Breakfast Order Tests330000001s651ms966ms
Orders Complete Lifecycle Tests11000000142ms142ms142ms
Orders Cross Field Validation Tests22000000257ms128ms128ms
Orders Kitchen Service Failure Tests1100000024ms24ms24ms
Orders Order Retrieval Tests2200000031ms15ms28ms
Orders Outbox Retry Exhaustion Tests110000001s1s1s
Orders Pagination Tests44000000257ms64ms95ms
Orders Rate Limiting Tests11000000147ms147ms147ms
Orders Status Transition Tests1111000000213ms19ms34ms
Orders Status Update Not Found Tests110000003ms3ms3ms
Orders Validation Tests6600000019ms3ms6ms
Order Timings Analytics Tests55000000106ms21ms61ms
Pancakes Content Negotiation Tests330000003ms1ms2ms
Pancakes Creation Tests8800000039ms4ms17ms
Recipe Cost Analysis Tests1100000020ms20ms20ms
Recipe Review Management Tests6600000090ms15ms57ms
Reporting Batch Completions Tests11000000725ms725ms725ms
Reporting Equipment Alerts Tests1100000038ms38ms38ms
Reporting Event Grid Webhook Tests1100000065ms65ms65ms
Reporting Order Summaries Tests2200000047ms23ms40ms
Reporting Recipe Reports Tests33000000114ms38ms56ms
Reservations Management Tests55000000151ms30ms99ms
Service Time Analysis Tests1100000020ms20ms20ms
Specifications Async Api Tests11000000677ms677ms677ms
Specifications Open Api Scalar UI Tests11000000126ms126ms126ms
Specifications Open Api Tests11000000210ms210ms210ms
Staff Management Tests44000000103ms25ms53ms
Toppings Deletion Tests2200000012ms6ms8ms
Toppings Feature Flag Tests22000000185ms92ms96ms
Toppings Management Tests2200000035ms17ms26ms
Toppings Update Tests8800000034ms4ms16ms
Toppings Xss Validation Tests6600000010ms1ms5ms
Waffles Content Negotiation Tests330000003ms1ms2ms
Waffles Creation Tests8800000067ms8ms46ms

Test Execution Summary

ExecutionContent
Overall status:PassedFeatures: 67
Start Date:2026-09-05 (UTC)Scenarios: 203
Start Time:07:57:28 (UTC)Passed Scenarios: 203
End Time:07:57:46 (UTC)Failed Scenarios: 0
Duration:18sSkipped Scenarios: 0
Kronikol Version:3.0.83+ab26fa9c690342d2737338029b76c2d104cc118d
Passed: 203 (100%)100%

Filtering

Filters
Status:
Happy Paths:
Duration ≥:
Dependencies:
Details:lines
Apple Cinnamon Muffins Creation Tests
Valid apple cinnamon muffin request should return a fresh batch Happy Path 36ms🔗
Diagrams
Details:lines
Different muffin recipes should produce the expected batch 3/3 passed 909ms🔗
#Input ParametersStatusDuration
Recipe NameRecipeTemperatureDuration MinutesPan TypeExpected
1Classic
{ Ingredients: { Flour = Plain Flour, Apples = Granny Smith, Cinnamon = Ceylon }, Toppings: 2 }
{ "Ingredients": { "Flour": "Plain Flour", "Apples": "Granny Smith", "Cinnamon": "Ceylon" }, "Toppings": [ { "Name": "Streusel", "Amount": "Light" }, { "Name": "Icing Glaze", "Amount": "Drizzle" } ] }
18025Standard
ExpectedIngredientCount5
ExpectedToppingCount2
HasBakingInfoTrue
Passed879ms
2Rustic Wholesome
{ Ingredients: { Flour = Whole Wheat, Apples = Honeycrisp, Cinnamon = Cassia }, Toppings: 2 }
{ "Ingredients": { "Flour": "Whole Wheat", "Apples": "Honeycrisp", "Cinnamon": "Cassia" }, "Toppings": [ { "Name": "Brown Sugar Crumb", "Amount": "Heavy" }, { "Name": "Maple Drizzle", "Amount": "Light" } ] }
17530Cast Iron
ExpectedIngredientCount5
ExpectedToppingCount2
HasBakingInfoTrue
Passed18ms
3Spiced Deluxe
{ Ingredients: { Flour = Almond Flour, Apples = Pink Lady, Cinnamon = Saigon }, Toppings: 2 }
{ "Ingredients": { "Flour": "Almond Flour", "Apples": "Pink Lady", "Cinnamon": "Saigon" }, "Toppings": [ { "Name": "Cinnamon Sugar", "Amount": "Heavy" }, { "Name": "Cream Cheese Swirl", "Amount": "Thick" } ] }
19020Silicone
ExpectedIngredientCount5
ExpectedToppingCount2
HasBakingInfoTrue
Passed11ms
Diagrams
Details:lines
Muffin request with invalid field should return bad request 6/6 passed 61ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1ApplesApples is required'Apples' is required.Bad RequestPassed2ms
2CinnamonCinnamon is required'Cinnamon' is required.Bad RequestPassed1ms
3Cinnamon<script>alert('xss')</script>XSS in cinnamonCinnamon contains potentially dangerous content.Bad RequestPassed3ms
4EggsEggs is required'Eggs' is required.Bad RequestPassed1ms
5FlourFlour is required'Flour' is required.Bad RequestPassed50ms
6MilkMilk is required'Milk' is required.Bad RequestPassed1ms
Diagrams
Details:lines
Audit Logs Filtering Tests
Audit logs should be filterable by entity id 990ms🔗
Diagrams
Details:lines
Audit logs should be filterable by entity type 43ms🔗
Diagrams
Details:lines
Audit logs should be returned in descending timestamp order 35ms🔗
Diagrams
Details:lines
Filtering audit logs by a non existent entity type should return an empty collection 10ms🔗
Diagrams
Details:lines
Audit Logs Retrieval Tests
Creating an order should produce a retrievable audit log entry Happy Path 63ms🔗
Steps
Given A pancake batch has been created (18ms)
Pancake steps response message status code should be Created (0ms)
Response content is valid json should be true (0ms)
Pancake steps response should not be null (0ms)
Pancake steps response batch id should not be empty (0ms)
And An order has been created for the batch (12ms)
Order steps response message status code should be Created (0ms)
Response content is valid json should be true (0ms)
Order steps response should not be null (0ms)
Order steps response order id should not be empty (0ms)
When The audit logs are retrieved (18ms)
Then The response contains the order creation entry (4ms)
Audit steps response message status code should be OK (0ms)
Response content is valid json should be true (0ms)
Audit steps response should contain [ a => a.Action == AuditLogDefaults.CreatedAction && a.EntityType == AuditLogDefaults.OrderEntityType && a.Details.Contains('TestCustomer_7617924526793713528') ] (0ms)
And The downstream services received requests (2ms)
Requests should contain [ r => r.RequestUri.AbsolutePath == "/milk" && r.Method == HttpMethod.Get ] (0ms)
Requests should contain [ r => r.RequestUri.AbsolutePath == "/prepare" && r.Method == HttpMethod.Post ] (0ms)
Diagrams
Details:lines
Chef Notes Management Tests
Creating a chef note should return the created note Happy Path 80ms🔗
Diagrams
Details:lines
Creating a note with missing note text should return bad request 19ms🔗
Diagrams
Details:lines
Creating a note with missing recipe name should return bad request 4ms🔗
Diagrams
Details:lines
Listing notes by recipe should return matching notes 120ms🔗
Diagrams
Details:lines
Retrieving a non existent note should return not found 26ms🔗
Diagrams
Details:lines
Retrieving an existing note by id should return the note 11ms🔗
Diagrams
Details:lines
Updating a non existent note should return not found 36ms🔗
Diagrams
Details:lines
Updating an existing note should return the updated note 22ms🔗
Diagrams
Details:lines
Customer Feedback Alert Tests
Consuming customer feedback event should trigger downstream processing Happy Path 30ms🔗
Diagrams
Details:lines
Customer Preferences Management Tests
Saving customer preferences should return the saved preferences Happy Path 8ms🔗
Diagrams
Details:lines
Retrieving existing customer preferences should return the preferences 538ms🔗
Diagrams
Details:lines
Retrieving non existent customer preferences should return not found 9ms🔗
Diagrams
Details:lines
Saving customer preferences with missing customer name should return bad request 4ms🔗
Diagrams
Details:lines
Updating customer preferences should return the updated preferences 13ms🔗
Diagrams
Details:lines
Daily Specials Idempotency Tests
Same order with different idempotency keys should return different confirmations 93ms🔗
Diagrams
Details:lines
Same order with same idempotency key should return same confirmation 14ms🔗
Diagrams
Details:lines
Daily Specials Not Found Tests
Ordering non existent daily special should return not found 3ms🔗
Diagrams
Details:lines
Daily Specials Ordering Tests
Valid daily special order should return a confirmation Happy Path 6ms🔗
Diagrams
Details:lines
Daily specials endpoint should return all available specials 16ms🔗
Diagrams
Details:lines
Ordering daily special beyond threshold should return conflict 7ms🔗
Diagrams
Details:lines
Remaining quantity should decrease after each order 7ms🔗
Diagrams
Details:lines
Daily Specials Validation Tests
Daily special order with invalid field should return bad request 2/2 passed 13ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1Quantity0Quantity must be greater than zeroQuantity must be greater than zero.Bad RequestPassed4ms
2SpecialId
null
Special ID is required'Special Id' is required.Bad RequestPassed9ms
Diagrams
Details:lines
Equipment Readings Monitoring Tests
Recording an equipment reading should return the created record Happy Path 11ms🔗
Diagrams
Details:lines
Deleting a reading should remove it from the list 279ms🔗
Diagrams
Details:lines
Listing readings by equipment should return matching records 33ms🔗
Diagrams
Details:lines
Recording a reading with missing metric should return bad request 4ms🔗
Diagrams
Details:lines
Recording a reading with zero value should return bad request 5ms🔗
Diagrams
Details:lines
Feedback Management Tests
Submitting feedback should return the created feedback Happy Path 8ms🔗
Diagrams
Details:lines
Listing feedback for an order should return the feedback 76ms🔗
Diagrams
Details:lines
Retrieving existing feedback by id should return the feedback 33ms🔗
Diagrams
Details:lines
Retrieving non existent feedback should return not found 5ms🔗
Diagrams
Details:lines
Submitting feedback with invalid rating should return bad request 3ms🔗
Diagrams
Details:lines
Submitting feedback with missing customer name should return bad request 2ms🔗
Diagrams
Details:lines
Grpc Order Status Tests
Order status via grpc should return order details Happy Path 35ms🔗
Diagrams
Details:lines
Order status for non existent order should return not found 27ms🔗
Diagrams
Details:lines
Grpc Recipe Summary Tests
Pancake recipe summary should return correct data Happy Path 54ms🔗
Diagrams
Details:lines
Waffle recipe summary should return correct data Happy Path 4ms🔗
Diagrams
Details:lines
Unknown recipe type should return zero batches 5ms🔗
Diagrams
Details:lines
Grpc Stream Order Updates Tests
Streaming order updates should return the current status Happy Path 36ms🔗
Diagrams
Details:lines
Streaming updates for non existent order should return not found 8ms🔗
Diagrams
Details:lines
Infrastructure Correlation Id Tests
Request with correlation id should return same id in response Happy Path 31ms🔗
Diagrams
Details:lines
Request without correlation id should have one generated in response 4ms🔗
Diagrams
Details:lines
Infrastructure Degraded Health Check Tests
Health check should report degraded when cow service is unavailable 222ms🔗
Diagrams
Details:lines
Health check should report degraded when multiple downstream services are unavailable 95ms🔗
Diagrams
Details:lines
Infrastructure Downstream Error Health Check Tests
Health check should report degraded when downstream service returns non success status 122ms🔗
Diagrams
Details:lines
Infrastructure Header Propagation Tests
Request with correlation id should forward it to cow service Happy Path 21ms🔗
Diagrams
Details:lines
Request with correlation id should forward it to supplier service 25ms🔗
Diagrams
Details:lines
Infrastructure Health Check Detail Tests
Health check response should include description and data for each entry 14ms🔗
Diagrams
Details:lines
Infrastructure Health Check Tests
Health check endpoint should return healthy status with all dependency details Happy Path 11ms🔗
Diagrams
Details:lines
Infrastructure Heartbeat Tests
Heartbeat endpoint should return a running message Happy Path 7ms🔗
Diagrams
Details:lines
Infrastructure Telemetry Tests
Creating an order should emit a structured log entry Happy Path 223ms🔗
Diagrams
Details:lines
Ingredients Goat Milk Downstream Failure Tests
Requesting goat milk when goat service returns invalid response should return bad gateway 22ms🔗
Diagrams
Details:lines
Requesting goat milk when goat service unavailable should return bad gateway 5ms🔗
Diagrams
Details:lines
Ingredients Goat Milk Feature Flag Tests
Goat milk endpoint should return fresh goat milk when feature is enabled 103ms🔗
Diagrams
Details:lines
Goat milk endpoint should return not found when feature is disabled 126ms🔗
Diagrams
Details:lines
Ingredients Goat Milk Sourcing Tests
Goat milk endpoint should return fresh goat milk from goat service Happy Path 8ms🔗
Diagrams
Details:lines
Ingredients Milk Downstream Failure Tests
Requesting milk when cow service returns invalid response should return bad gateway 74ms🔗
Diagrams
Details:lines
Requesting milk when cow service times out should return bad gateway 7ms🔗
Diagrams
Details:lines
Requesting milk when cow service unavailable should return bad gateway 7ms🔗
Diagrams
Details:lines
Ingredient Usage Analytics Tests
Recording ingredient usage should return the created record Happy Path 7ms🔗
Diagrams
Details:lines
Getting usage summary should return aggregated data 365ms🔗
Diagrams
Details:lines
Listing usage by ingredient should return matching records 61ms🔗
Diagrams
Details:lines
Recording usage with missing ingredient name should return bad request 3ms🔗
Diagrams
Details:lines
Recording usage with zero quantity should return bad request 18ms🔗
Diagrams
Details:lines
Ingredient Waste Tracking Tests
Recording ingredient waste should return the created record Happy Path 8ms🔗
Diagrams
Details:lines
Deleting a waste record should return no content 51ms🔗
Diagrams
Details:lines
Listing waste by recipe should return matching records 34ms🔗
Diagrams
Details:lines
Recording waste with missing ingredient name should return bad request 3ms🔗
Diagrams
Details:lines
Recording waste with missing reason should return bad request 2ms🔗
Diagrams
Details:lines
Recording waste with zero quantity should return bad request 2ms🔗
Diagrams
Details:lines
Inventory Management Tests
Adding a new inventory item should return the created item Happy Path 69ms🔗
Diagrams
Details:lines
Deleting an inventory item should return no content 68ms🔗
Diagrams
Details:lines
Listing all inventory items should return all items 45ms🔗
Diagrams
Details:lines
Retrieving a non existent inventory item should return not found 16ms🔗
Diagrams
Details:lines
Retrieving an existing inventory item should return the item 11ms🔗
Diagrams
Details:lines
Updating an inventory item should return the updated item 33ms🔗
Diagrams
Details:lines
Menu Availability Tests
Menu endpoint should return all menu items with availability Happy Path 58ms🔗
Diagrams
Details:lines
Menu Caching Tests
Menu should return cached results on subsequent requests 34ms🔗
Diagrams
Details:lines
Menu Downstream Failure Tests
Requesting menu when supplier service unavailable should mark items as unavailable 28ms🔗
Diagrams
Details:lines
Orders Breakfast Order Tests
Valid order should be created and an event published Happy Path 933ms🔗
Diagrams
Details:lines
Creating an order should produce an audit log entry and events 966ms🔗
Diagrams
Details:lines
Creating an order should write an outbox message that gets processed 54ms🔗
Diagrams
Details:lines
Orders Complete Lifecycle Tests
Order should progress through all status transitions to completion Happy Path 142ms🔗
Diagrams
Details:lines
Orders Cross Field Validation Tests
Order at maximum items per order should be accepted 128ms🔗
Diagrams
Details:lines
Order exceeding maximum items per order should be rejected 128ms🔗
Diagrams
Details:lines
Orders Kitchen Service Failure Tests
Creating an order when kitchen service returns error should still create the order 24ms🔗
Diagrams
Details:lines
Orders Order Retrieval Tests
Previously created order should be retrievable by id Happy Path 28ms🔗
Diagrams
Details:lines
Retrieving a non existent order should return not found 2ms🔗
Diagrams
Details:lines
Orders Outbox Retry Exhaustion Tests
Outbox message should transition to failed after exhausting retries 1.0s🔗
Sequence Diagrams
Details:lines
Orders Pagination Tests
Listing orders should return a paginated response Happy Path 95ms🔗
Diagrams
Details:lines
Listing orders when none exist should return an empty page 18ms🔗
Diagrams
Details:lines
Listing orders with small page size should limit results 71ms🔗
Diagrams
Details:lines
Requesting second page should return different orders 72ms🔗
Diagrams
Details:lines
Orders Rate Limiting Tests
Exceeding rate limit should return too many requests 147ms🔗
Diagrams
Details:lines
Orders Status Transition Tests
Invalid status transition should return conflict 7/7 passed 141ms🔗
#Input ParametersStatusDuration
From StatusTo Status
1CancelledPreparingPassed16ms
2CancelledReadyPassed34ms
3CompletedPreparingPassed19ms
4CreatedCompletedPassed13ms
5CreatedReadyPassed22ms
6PreparingCancelledPassed15ms
7ReadyPreparingPassed18ms
Diagrams
Details:lines
Valid status transition should update the order 4/4 passed 71ms🔗
#Input ParametersStatusDuration
From StatusTo Status
1CreatedCancelledPassed14ms
2CreatedPreparingPassed21ms
3PreparingReadyPassed16ms
4ReadyCompletedPassed19ms
Diagrams
Details:lines
Orders Status Update Not Found Tests
Updating status of non existent order should return not found 3ms🔗
Diagrams
Details:lines
Orders Validation Tests
Order status update with invalid field should return bad request 1/1 passed 6ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1StatusStatus is required'Status' is required.Bad RequestPassed6ms
Diagrams
Details:lines
Order with invalid field should return bad request 5/5 passed 12ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1CustomerNameCustomer name is required'Customer Name' is required.Bad RequestPassed6ms
2Items
null
At least one item is requiredThe Items field is required.Bad RequestPassed1ms
3Items[0].BatchId
null
Batch ID is required'Batch Id' is required.Bad RequestPassed1ms
4Items[0].ItemTypeItem type is required'Item Type' is required.Bad RequestPassed1ms
5Items[0].Quantity0Quantity must be greater than zeroQuantity must be greater than zero.Bad RequestPassed1ms
Diagrams
Details:lines
Order Timings Analytics Tests
Recording an order timing should return the created record Happy Path 6ms🔗
Diagrams
Details:lines
Getting the timing summary should return aggregated data 61ms🔗
Diagrams
Details:lines
Listing timings by station should return matching records 32ms🔗
Diagrams
Details:lines
Recording a timing with missing station should return bad request 3ms🔗
Diagrams
Details:lines
Recording a timing with zero prep seconds should return bad request 2ms🔗
Diagrams
Details:lines
Pancakes Content Negotiation Tests
Request with unsupported content type should return unsupported media type 3/3 passed 3ms🔗
#Input ParametersStatusDuration
Content Type
1application/xmlPassed0ms
2text/htmlPassed0ms
3text/plainPassed2ms
Diagrams
Details:lines
Pancakes Creation Tests
Valid pancake request with all ingredients should return a fresh batch Happy Path 17ms🔗
Diagrams
Details:lines
Pancake request with invalid ingredient should return bad request 6/6 passed 11ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1EggsEggs is required'Eggs' is required.Bad RequestPassed1ms
2Eggsjavascript:void(0)XSS in eggsEggs contains potentially dangerous content.Bad RequestPassed1ms
3FlourFlour is required'Flour' is required.Bad RequestPassed1ms
4Flour<img onerror=x>XSS in flourFlour contains potentially dangerous content.Bad RequestPassed1ms
5MilkMilk is required'Milk' is required.Bad RequestPassed5ms
6Milk<script>alert</script>XSS in milkMilk contains potentially dangerous content.Bad RequestPassed1ms
Diagrams
Details:lines
Pancake request with more toppings than allowed should return bad request 10ms🔗
Diagrams
Details:lines
Recipe Cost Analysis Tests
Consuming recipe cost event should trigger downstream processing Happy Path 20ms🔗
Diagrams
Details:lines
Recipe Review Management Tests
Submitting a recipe review should return the created review Happy Path 5ms🔗
Diagrams
Details:lines
Listing reviews by recipe should return matching reviews 57ms🔗
Diagrams
Details:lines
Retrieving existing review by id should return the review 21ms🔗
Diagrams
Details:lines
Retrieving non existent review should return not found 2ms🔗
Diagrams
Details:lines
Submitting review with invalid rating should return bad request 2ms🔗
Diagrams
Details:lines
Submitting review with missing recipe name should return bad request 2ms🔗
Diagrams
Details:lines
Reporting Batch Completions Tests
Batch completions should contain data ingested via pubsub consumer Happy Path 725ms🔗
Diagrams
Details:lines
Reporting Equipment Alerts Tests
Equipment alerts should contain data ingested via event hub consumer Happy Path 38ms🔗
Diagrams
Details:lines
Reporting Event Grid Webhook Tests
Ingredient shipments should be recorded when delivered via eventgrid webhook Happy Path 65ms🔗
Diagrams
Details:lines
Reporting Order Summaries Tests
Order summaries should contain ingested order data Happy Path 40ms🔗
Diagrams
Details:lines
Order summaries should return an empty list when no orders exist 6ms🔗
Diagrams
Details:lines
Reporting Recipe Reports Tests
Recipe reports should contain ingested recipe data Happy Path 33ms🔗
Diagrams
Details:lines
Ingredient usage should aggregate across multiple recipes 24ms🔗
Diagrams
Details:lines
Reservations Management Tests
Creating a reservation should return the confirmed reservation Happy Path 6ms🔗
Diagrams
Details:lines
Cancelling a reservation should return the cancelled reservation 99ms🔗
Diagrams
Details:lines
Cancelling an already cancelled reservation should return a conflict response 10ms🔗
Diagrams
Details:lines
Deleting a reservation should return no content 15ms🔗
Diagrams
Details:lines
Retrieving an existing reservation should return the reservation 19ms🔗
Diagrams
Details:lines
Service Time Analysis Tests
Consuming an order served event should trigger downstream processing Happy Path 20ms🔗
Diagrams
Details:lines
Specifications Async Api Tests
The async api endpoint should return a valid specification Happy Path 677ms🔗
Diagrams
Details:lines
Specifications Open Api Scalar UI Tests
The scalar ui endpoint should return a valid page Happy Path 126ms🔗
Diagrams
Details:lines
Specifications Open Api Tests
The open api endpoint should return a valid specification Happy Path 210ms🔗
Diagrams
Details:lines
Staff Management Tests
Adding a new staff member should return the created member Happy Path 53ms🔗
Diagrams
Details:lines
Adding a staff member with an invalid role should return a bad request response 3ms🔗
Diagrams
Details:lines
Deleting a staff member should return no content 25ms🔗
Diagrams
Details:lines
Retrieving an existing staff member should return the member 22ms🔗
Diagrams
Details:lines
Toppings Deletion Tests
Deleting an existing topping should return no content Happy Path 3ms🔗
Diagrams
Details:lines
Deleting a non existent topping should return not found 8ms🔗
Diagrams
Details:lines
Toppings Feature Flag Tests
Toppings should exclude raspberries when feature flag is disabled 89ms🔗
Diagrams
Details:lines
Toppings should include raspberries when feature flag is enabled 96ms🔗
Diagrams
Details:lines
Toppings Management Tests
Toppings endpoint should return all available toppings Happy Path 8ms🔗
Diagrams
Details:lines
Adding a new topping should return the created topping 26ms🔗
Diagrams
Details:lines
Toppings Update Tests
Updating an existing topping should return the updated topping Happy Path 6ms🔗
Diagrams
Details:lines
Update topping with invalid or dangerous input should return bad request 6/6 passed 22ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1CategoryCategory is required'Category' is required.Bad RequestPassed0ms
2Category<script>alert('xss')</script>Script tag in categoryCategory contains potentially dangerous content.Bad RequestPassed1ms
3Categoryjavascript:alert(1)Javascript protocolCategory contains potentially dangerous content.Bad RequestPassed0ms
4NameName is required'Name' is required.Bad RequestPassed0ms
5Name<img src=x onerror=alert(1)>Event handler in nameName contains potentially dangerous content.Bad RequestPassed1ms
6Name<script>alert('xss')</script>Script tag in nameName contains potentially dangerous content.Bad RequestPassed16ms
Diagrams
Details:lines
Updating a non existent topping should return not found 5ms🔗
Diagrams
Details:lines
Toppings Xss Validation Tests
Topping request with invalid or dangerous input should return bad request 6/6 passed 10ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1CategoryCategory is required'Category' is required.Bad RequestPassed0ms
2Category<script>alert('xss')</script>Script tag in categoryCategory contains potentially dangerous content.Bad RequestPassed0ms
3Categoryjavascript:alert(1)Javascript protocolCategory contains potentially dangerous content.Bad RequestPassed0ms
4NameName is required'Name' is required.Bad RequestPassed0ms
5Name<img src=x onerror=alert(1)>Event handler in nameName contains potentially dangerous content.Bad RequestPassed2ms
6Name<script>alert('xss')</script>Script tag in nameName contains potentially dangerous content.Bad RequestPassed5ms
Diagrams
Details:lines
Waffles Content Negotiation Tests
Sending request with unsupported content type should return unsupported media type 3/3 passed 3ms🔗
#Input ParametersStatusDuration
Content Type
1application/xmlPassed0ms
2text/htmlPassed0ms
3text/plainPassed2ms
Diagrams
Details:lines
Waffles Creation Tests
Valid waffle request with all ingredients should return a fresh batch Happy Path 46ms🔗
Diagrams
Details:lines
Waffle request with invalid ingredient should return bad request 6/6 passed 12ms🔗
#Input ParametersStatusDuration
FieldValueReasonExpected ErrorExpected Status
1ButterButter is required'Butter' is required.Bad RequestPassed0ms
2Butter<img onerror=x>XSS in butterButter contains potentially dangerous content.Bad RequestPassed1ms
3EggsEggs is required'Eggs' is required.Bad RequestPassed0ms
4FlourFlour is required'Flour' is required.Bad RequestPassed2ms
5MilkMilk is required'Milk' is required.Bad RequestPassed5ms
6Milk<script>alert</script>XSS in milkMilk contains potentially dangerous content.Bad RequestPassed0ms
Diagrams
Details:lines
Waffle request with more toppings than allowed should return bad request 8ms🔗
Diagrams
Details:lines