Space-separated words use implicit AND. Press / to focus the search bar. Operators &&||!! activate advanced mode; without them, legacy tag expressions (@a and @b or not @c) are also supported. dep:, duration: and is: always narrow the search: they combine with the rest of it by AND, and can be negated with !! or not. Inside a group that !! or not negates, one is read as text, and the search bar is marked.
Status
Duration โฅseconds
Happy paths
Tags
Dependencies
All 212 scenarios, 73 featuresAll 212 scenarios
featuresscenarios
Payloads
No scenarios match the filters.
Scenarios
Steps
Duration
Feature
Total
Passed
Failed
Skipped
Total
Passed
Failed
Skipped
Total
Avg
Longest
10
10
0
0
0
0
0
0
121ms
12ms
39ms
4
4
0
0
0
0
0
0
110ms
27ms
42ms
1
1
0
0
18
18
0
0
47ms
47ms
47ms
8
8
0
0
0
0
0
0
153ms
19ms
46ms
1
1
0
0
0
0
0
0
32ms
32ms
32ms
5
5
0
0
0
0
0
0
80ms
16ms
34ms
2
2
0
0
0
0
0
0
27ms
13ms
18ms
1
1
0
0
0
0
0
0
3ms
3ms
3ms
4
4
0
0
0
0
0
0
112ms
28ms
92ms
2
2
0
0
0
0
0
0
6ms
3ms
5ms
5
5
0
0
0
0
0
0
106ms
21ms
78ms
6
6
0
0
0
0
0
0
419ms
69ms
369ms
2
2
0
0
0
0
0
0
1s
554ms
993ms
3
3
0
0
0
0
0
0
51ms
17ms
34ms
2
2
0
0
0
0
0
0
66ms
33ms
50ms
2
2
0
0
0
0
0
0
16ms
8ms
12ms
2
2
0
0
0
0
0
0
169ms
84ms
106ms
1
1
0
0
0
0
0
0
76ms
76ms
76ms
2
2
0
0
0
0
0
0
177ms
88ms
95ms
1
1
0
0
0
0
0
0
14ms
14ms
14ms
1
1
0
0
0
0
0
0
11ms
11ms
11ms
1
1
0
0
0
0
0
0
7ms
7ms
7ms
1
1
0
0
0
0
0
0
137ms
137ms
137ms
2
2
0
0
0
0
0
0
25ms
12ms
19ms
2
2
0
0
0
0
0
0
155ms
77ms
91ms
1
1
0
0
0
0
0
0
8ms
8ms
8ms
3
3
0
0
0
0
0
0
13ms
4ms
5ms
5
5
0
0
0
0
0
0
326ms
65ms
229ms
6
6
0
0
0
0
0
0
91ms
15ms
31ms
6
6
0
0
0
0
0
0
174ms
29ms
86ms
1
1
0
0
0
0
0
0
73ms
73ms
73ms
1
1
0
0
0
0
0
0
96ms
96ms
96ms
1
1
0
0
0
0
0
0
80ms
80ms
80ms
3
3
0
0
0
0
0
0
1s
648ms
935ms
1
1
0
0
0
0
0
0
121ms
121ms
121ms
2
2
0
0
0
0
0
0
296ms
148ms
194ms
1
1
0
0
0
0
0
0
29ms
29ms
29ms
2
2
0
0
0
0
0
0
34ms
17ms
30ms
1
1
0
0
0
0
0
0
1s
1s
1s
4
4
0
0
0
0
0
0
569ms
142ms
204ms
1
1
0
0
0
0
0
0
119ms
119ms
119ms
11
11
0
0
0
0
0
0
206ms
18ms
33ms
1
1
0
0
0
0
0
0
27ms
27ms
27ms
6
6
0
0
0
0
0
0
40ms
6ms
23ms
5
5
0
0
0
0
0
0
307ms
61ms
226ms
3
3
0
0
0
0
0
0
3ms
1ms
2ms
8
8
0
0
0
0
0
0
38ms
4ms
17ms
1
1
0
0
0
0
0
0
459ms
459ms
459ms
6
6
0
0
0
0
0
0
204ms
34ms
152ms
1
1
0
0
0
0
0
0
32ms
32ms
32ms
1
1
0
0
0
0
0
0
606ms
606ms
606ms
1
1
0
0
0
0
0
0
53ms
53ms
53ms
2
2
0
0
0
0
0
0
69ms
34ms
62ms
3
3
0
0
0
0
0
0
123ms
41ms
56ms
5
5
0
0
0
0
0
0
150ms
30ms
97ms
1
1
0
0
0
0
0
0
26ms
26ms
26ms
1
1
0
0
0
0
0
0
168ms
168ms
168ms
1
1
0
0
0
0
0
0
5ms
5ms
5ms
2
2
0
0
0
0
0
0
88ms
44ms
47ms
1
1
0
0
0
0
0
0
21ms
21ms
21ms
2
2
0
0
0
0
0
0
92ms
46ms
86ms
2
2
0
0
0
0
0
0
47ms
23ms
32ms
1
1
0
0
0
0
0
0
36ms
36ms
36ms
1
1
0
0
0
0
0
0
94ms
94ms
94ms
1
1
0
0
0
0
0
0
175ms
175ms
175ms
4
4
0
0
0
0
0
0
99ms
24ms
34ms
2
2
0
0
0
0
0
0
34ms
17ms
30ms
2
2
0
0
0
0
0
0
144ms
72ms
82ms
2
2
0
0
0
0
0
0
25ms
12ms
14ms
8
8
0
0
0
0
0
0
35ms
4ms
14ms
6
6
0
0
0
0
0
0
24ms
4ms
18ms
3
3
0
0
0
0
0
0
3ms
1ms
2ms
8
8
0
0
0
0
0
0
72ms
9ms
47ms
Apple Cinnamon Muffins Creation TestsValid apple cinnamon muffin request should return a fresh batch Happy Path24ms🔗Diagrams
This scenario:Payloads
Different muffin recipes should produce the expected batch 3/3 passed49ms🔗
Muffin request with invalid field should return bad request 6/6 passed47ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Expected Error
Expected Status
1
Apples
Apples is required
'Apples' is required.
Bad Request
Passed
1ms
2
Cinnamon
Cinnamon is required
'Cinnamon' is required.
Bad Request
Passed
1ms
3
Cinnamon
<script>alert('xss')</script>
XSS in cinnamon
Cinnamon contains potentially dangerous content.
Bad Request
Passed
2ms
4
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
1ms
5
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
39ms
6
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
2ms
Diagrams
This scenario:Payloads
Audit Logs Filtering TestsAudit logs should be filterable by entity id 22ms🔗Diagrams
This scenario:Payloads
Audit logs should be filterable by entity type 42ms🔗Diagrams
This scenario:Payloads
Audit logs should be returned in descending timestamp order 35ms🔗Diagrams
This scenario:Payloads
Filtering audit logs by a non existent entity type should return an empty collection 10ms🔗Diagrams
This scenario:Payloads
Audit Logs Retrieval TestsCreating an order should produce a retrievable audit log entry Happy Path47ms🔗Steps✓GivenA pancake batch has been created(14ms)
✓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)
✓AndAn order has been created for the batch(8ms)
✓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)
✓WhenThe audit logs are retrieved(13ms)
✓ThenThe response contains the order creation entry(5ms)
✓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_6167054177480145683') ](0ms)
✓AndThe downstream services received requests(0ms)
✓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
This scenario:Payloads
Chef Notes Management TestsCreating a chef note should return the created note Happy Path6ms🔗Diagrams
This scenario:Payloads
Creating a note with missing note text should return bad request 2ms🔗Diagrams
This scenario:Payloads
Creating a note with missing recipe name should return bad request 2ms🔗Diagrams
This scenario:Payloads
Listing notes by recipe should return matching notes 24ms🔗Diagrams
This scenario:Payloads
Retrieving a non existent note should return not found 3ms🔗Diagrams
This scenario:Payloads
Retrieving an existing note by id should return the note 46ms🔗Diagrams
This scenario:Payloads
Updating a non existent note should return not found 33ms🔗Diagrams
This scenario:Payloads
Updating an existing note should return the updated note 33ms🔗Diagrams
Staff Management TestsAdding a new staff member should return the created member Happy Path34ms🔗Diagrams
This scenario:Payloads
Adding a staff member with an invalid role should return a bad request response 20ms🔗Diagrams
This scenario:Payloads
Deleting a staff member should return no content 24ms🔗Diagrams
This scenario:Payloads
Retrieving an existing staff member should return the member 20ms🔗Diagrams
This scenario:Payloads
Toppings Deletion TestsDeleting an existing topping should return no content Happy Path3ms🔗Diagrams
This scenario:Payloads
Deleting a non existent topping should return not found 30ms🔗Diagrams
This scenario:Payloads
Toppings Feature Flag TestsToppings should exclude raspberries when feature flag is disabled 61ms🔗Diagrams
This scenario:Payloads
Toppings should include raspberries when feature flag is enabled 82ms🔗Diagrams
This scenario:Payloads
Toppings Management TestsToppings endpoint should return all available toppings Happy Path10ms🔗Diagrams
This scenario:Payloads
Adding a new topping should return the created topping 14ms🔗Diagrams
This scenario:Payloads
Toppings Update TestsUpdating an existing topping should return the updated topping Happy Path12ms🔗Diagrams
This scenario:Payloads
Update topping with invalid or dangerous input should return bad request 6/6 passed20ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Expected Error
Expected Status
1
Category
Category is required
'Category' is required.
Bad Request
Passed
1ms
2
Category
<script>alert('xss')</script>
Script tag in category
Category contains potentially dangerous content.
Bad Request
Passed
1ms
3
Category
javascript:alert(1)
Javascript protocol
Category contains potentially dangerous content.
Bad Request
Passed
14ms
4
Name
Name is required
'Name' is required.
Bad Request
Passed
1ms
5
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
1ms
6
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
1ms
Diagrams
This scenario:Payloads
Updating a non existent topping should return not found 2ms🔗Diagrams
This scenario:Payloads
Toppings Xss Validation TestsTopping request with invalid or dangerous input should return bad request 6/6 passed24ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Expected Error
Expected Status
1
Category
Category is required
'Category' is required.
Bad Request
Passed
1ms
2
Category
<script>alert('xss')</script>
Script tag in category
Category contains potentially dangerous content.
Bad Request
Passed
0ms
3
Category
javascript:alert(1)
Javascript protocol
Category contains potentially dangerous content.
Bad Request
Passed
1ms
4
Name
Name is required
'Name' is required.
Bad Request
Passed
1ms
5
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
1ms
6
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
18ms
Diagrams
This scenario:Payloads
Waffles Content Negotiation TestsSending request with unsupported content type should return unsupported media type 3/3 passed3ms🔗
#
Input Parameters
Status
Duration
Content Type
1
application/xml
Passed
2ms
2
text/html
Passed
0ms
3
text/plain
Passed
0ms
Diagrams
This scenario:Payloads
Waffles Creation TestsValid waffle request with all ingredients should return a fresh batch Happy Path47ms🔗Diagrams
This scenario:Payloads
Waffle request with invalid ingredient should return bad request 6/6 passed16ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Expected Error
Expected Status
1
Butter
Butter is required
'Butter' is required.
Bad Request
Passed
2ms
2
Butter
<img onerror=x>
XSS in butter
Butter contains potentially dangerous content.
Bad Request
Passed
0ms
3
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
5ms
4
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
0ms
5
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
6ms
6
Milk
<script>alert</script>
XSS in milk
Milk contains potentially dangerous content.
Bad Request
Passed
0ms
Diagrams
This scenario:Payloads
Waffle request with more toppings than allowed should return bad request 8ms🔗Diagrams
This scenario:Payloads
Scenario Timeline 🛈
ShowWarm-upOrder
Outbox message should transition to failed after exhausting retries
1.1s
Order status via grpc should return order details
993ms
Creating an order should produce an audit log entry and events
935ms
Valid order should be created and an event published
923ms
Equipment alerts should contain data ingested via event hub consumer
606ms
Consuming recipe cost event should trigger downstream processing
459ms
Listing feedback for an order should return the feedback
369ms
Getting usage summary should return aggregated data
229ms
Listing timings by station should return matching records
226ms
Requesting second page should return different orders
204ms
Order exceeding maximum items per order should be rejected
194ms
The open api endpoint should return a valid specification
175ms
The async api endpoint should return a valid specification
168ms
Listing orders should return a paginated response
153ms
Retrieving existing review by id should return the review
152ms
Creating an order should emit a structured log entry
137ms
Listing orders with small page size should limit results
128ms
Order should progress through all status transitions to completion
121ms
Exceeding rate limit should return too many requests
119ms
Order status for non existent order should return not found
115ms
Health check should report degraded when multiple downstream services are unavailable
106ms
Order at maximum items per order should be accepted
102ms
Cancelling a reservation should return the cancelled reservation
97ms
Menu should return cached results on subsequent requests
96ms
Request with correlation id should forward it to supplier service
95ms
The scalar ui endpoint should return a valid page
94ms
Remaining quantity should decrease after each order
92ms
Goat milk endpoint should return fresh goat milk when feature is enabled
91ms
Creating an order should write an outbox message that gets processed
86ms
The grpc contract endpoint should return a valid specification
86ms
Retrieving an existing inventory item should return the item
86ms
Listing orders when none exist should return an empty page
83ms
Toppings should include raspberries when feature flag is enabled
82ms
Request with correlation id should forward it to cow service
81ms
Requesting menu when supplier service unavailable should mark items as unavailable
80ms
Deleting a reading should remove it from the list
78ms
Health check should report degraded when downstream service returns non success status
76ms
Menu endpoint should return all menu items with availability
73ms
Goat milk endpoint should return not found when feature is disabled
64ms
Health check should report degraded when cow service is unavailable
62ms
Order summaries should contain ingested order data
62ms
Toppings should exclude raspberries when feature flag is disabled
61ms
Popular recipes should return recipe types ordered by frequency
56ms
Ingredient shipments should be recorded when delivered via eventgrid webhook
53ms
Getting the timing summary should return aggregated data
51ms
Listing usage by ingredient should return matching records
51ms
Streaming order updates should return the current status
50ms
Creating an order should produce a retrievable audit log entry
47ms
The graph ql schema endpoint should return a valid specification
47ms
Valid waffle request with all ingredients should return a fresh batch
47ms
Retrieving an existing note by id should return the note
46ms
Audit logs should be filterable by entity type
42ms
The graph ql schema definition endpoint should return the schema definition
41ms
Muffin request with invalid field should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]
39ms
The grpc ui endpoint should return a page describing the service
36ms
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โฆ]
35ms
Audit logs should be returned in descending timestamp order
35ms
Recipe reports should contain ingested recipe data
34ms
Saving customer preferences should return the saved preferences
34ms
Pancake recipe summary should return correct data
34ms
Adding a new staff member should return the created member
34ms
Updating an existing note should return the updated note
33ms
Updating a non existent note should return not found
33ms
Valid status transition should update the order [fromStatus: "Ready", toStatus: "Completed"]
33ms
Grpc server reflection should list the breakfast service
32ms
Consuming customer feedback event should trigger downstream processing
32ms
Batch completions should contain data ingested via pubsub consumer
32ms
Ingredient usage should aggregate across multiple recipes
31ms
Recording ingredient waste should return the created record
31ms
Deleting a non existent topping should return not found
30ms
Previously created order should be retrievable by id
30ms
Listing reviews by recipe should return matching reviews
30ms
Updating an inventory item should return the updated item
30ms
Retrieving existing feedback by id should return the feedback
29ms
Creating an order when kitchen service returns error should still create the order
29ms
Invalid status transition should return conflict [fromStatus: "Cancelled", toStatus: "Preparing"]
28ms
Listing waste by recipe should return matching records
28ms
Recording usage with zero quantity should return bad request
27ms
Updating status of non existent order should return not found
27ms
Consuming an order served event should trigger downstream processing
26ms
Invalid status transition should return conflict [fromStatus: "Cancelled", toStatus: "Ready"]
25ms
Valid apple cinnamon muffin request should return a fresh batch
24ms
Deleting an inventory item should return no content
24ms
Deleting a staff member should return no content
24ms
Listing notes by recipe should return matching notes
24ms
Listing all inventory items should return all items
23ms
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"]
23ms
Audit logs should be filterable by entity id
22ms
The graph ql ui endpoint should return a valid page
21ms
Deleting a waste record should return no content
20ms
Retrieving an existing reservation should return the reservation
20ms
Invalid status transition should return conflict [fromStatus: "Created", toStatus: "Completed"]
20ms
Retrieving an existing staff member should return the member
20ms
Adding a staff member with an invalid role should return a bad request response
20ms
Requesting goat milk when goat service unavailable should return bad gateway
19ms
Recording a timing with zero prep seconds should return bad request
19ms
Same order with different idempotency keys should return different confirmations
18ms
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"]
18ms
Retrieving non existent customer preferences should return not found
17ms
Valid pancake request with all ingredients should return a fresh batch
17ms
Valid status transition should update the order [fromStatus: "Preparing", toStatus: "Ready"]
16ms
Invalid status transition should return conflict [fromStatus: "Completed", toStatus: "Preparing"]
16ms
Deleting a reservation should return no content
15ms
Streaming updates for non existent order should return not found
15ms
Grpc server reflection should describe the breakfast service
15ms
Valid status transition should update the order [fromStatus: "Created", toStatus: "Preparing"]
14ms
Adding a new topping should return the created topping
14ms
Recording ingredient usage should return the created record
14ms
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"]
14ms
Health check response should include description and data for each entry
14ms
Invalid status transition should return conflict [fromStatus: "Ready", toStatus: "Preparing"]
13ms
Retrieving existing customer preferences should return the preferences
13ms
Valid status transition should update the order [fromStatus: "Created", toStatus: "Cancelled"]
13ms
Invalid status transition should return conflict [fromStatus: "Preparing", toStatus: "Cancelled"]
13ms
Listing readings by equipment should return matching records
12ms
Unknown recipe type should return zero batches
12ms
Updating an existing topping should return the updated topping
12ms
Request without correlation id should have one generated in response
12ms
Updating customer preferences should return the updated preferences
12ms
Invalid status transition should return conflict [fromStatus: "Created", toStatus: "Ready"]
11ms
Health check endpoint should return healthy status with all dependency details
11ms
Toppings endpoint should return all available toppings
10ms
Filtering audit logs by a non existent entity type should return an empty collection
10ms
Submitting feedback should return the created feedback
10ms
Pancake request with more toppings than allowed should return bad request
9ms
Same order with same idempotency key should return same confirmation
8ms
Waffle request with more toppings than allowed should return bad request
8ms
Recording an equipment reading should return the created record
8ms
Ordering daily special beyond threshold should return conflict
8ms
Creating a reservation should return the confirmed reservation
8ms
Valid daily special order should return a confirmation
8ms
Order status update with invalid field should return bad request [field: "Status", value: "", reason: "Status is required", expectedError: "'Status' is required.", expectedStatus: "Bad Request"]
8ms
Goat milk endpoint should return fresh goat milk from goat service
8ms
Cancelling an already cancelled reservation should return a conflict response
8ms
Recording an order timing should return the created record
7ms
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โฆ]
7ms
Heartbeat endpoint should return a running message
7ms
Order summaries should return an empty list when no orders exist
6ms
Creating a chef note should return the created note
6ms
The grpc proto endpoint should return the proto file
6ms
Submitting a recipe review should return the created review
6ms
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"]
6ms
Submitting review with invalid rating should return bad request
6ms
Waffle request with invalid ingredient should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "Bad Request"]
6ms
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โฆ]
5ms
Requesting goat milk when goat service returns invalid response should return bad gateway
5ms
Adding a new inventory item should return the created item
5ms
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"]
5ms
Submitting review with missing recipe name should return bad request
5ms
The async api ui endpoint should return a valid page
5ms
Waffle request with invalid ingredient should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]
5ms
Requesting milk when cow service unavailable should return bad gateway
5ms
Retrieving a non existent inventory item should return not found
4ms
Recording waste with missing ingredient name should return bad request
4ms
Waffle recipe summary should return correct data
4ms
Requesting milk when cow service times out should return bad gateway
4ms
Recording usage with missing ingredient name should return bad request
4ms
Retrieving non existent feedback should return not found
4ms
Requesting milk when cow service returns invalid response should return bad gateway
4ms
Recording waste with zero quantity should return bad request
4ms
Deleting an existing topping should return no content
3ms
Retrieving a non existent order should return not found
3ms
Ordering non existent daily special should return not found
3ms
Request with correlation id should return same id in response
3ms
Retrieving a non existent note should return not found
3ms
Daily specials endpoint should return all available specials
3ms
Retrieving non existent review should return not found
3ms
Submitting feedback with invalid rating should return bad request
3ms
Recording a reading with zero value should return bad request
3ms
Submitting feedback with missing customer name should return bad request
3ms
Recording waste with missing reason should return bad request
3ms
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"]
3ms
Recording a reading with missing metric should return bad request
2ms
Saving customer preferences with missing customer name should return bad request
2ms
Recording a timing with missing station should return bad request
2ms
Creating a note with missing recipe name should return bad request
2ms
Updating a non existent topping should return not found
2ms
Creating a note with missing note text should return 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
Request with unsupported content type should return unsupported media type [contentType: "application/xml"]
2ms
Sending request with unsupported content type should return unsupported media type [contentType: "application/xml"]
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
Muffin request with invalid field should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", expectedStatus: "Bad Request"]
2ms
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"]
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"]
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
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: "Category", value: "", reason: "Category is required", expectedError: "'Category' is required.", expectedStatus: "Bad Request"]
1ms
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"]
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
Pancake request with invalid ingredient should return bad request [field: "Milk", value: "", reason: "Milk is required", expectedError: "'Milk' is required.", 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
Muffin request with invalid field should return bad request [field: "Cinnamon", value: "", reason: "Cinnamon is required", expectedError: "'Cinnamon' 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: "<img src=x onerror=alert(1)>", reason: "Event handler in name", expectedError: "Name contains potentially dangerous content.", 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
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
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
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
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"]
0ms
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"]
0ms
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"]
0ms
Pancake request with invalid ingredient should return bad request [field: "Eggs", value: "", reason: "Eggs is required", expectedError: "'Eggs' is required.", expectedStatus: "Bad Request"]
0ms
Pancake request with invalid ingredient should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]
0ms
Waffle request with invalid ingredient should return bad request [field: "Flour", value: "", reason: "Flour is required", expectedError: "'Flour' is required.", expectedStatus: "Bad Request"]
0ms
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"]
0ms
Request with unsupported content type should return unsupported media type [contentType: "text/html"]
0ms
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"]
0ms
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
Component Diagram 🛈
ShowDirectionCall summaries
History nothing changed (against 50 earlier runs on main)
stream main ยท run gh:40174567678:1 ยท 50 earlier runs in the window