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
671ms
67ms
579ms
4
4
0
0
0
0
0
0
860ms
215ms
732ms
1
1
0
0
18
18
0
0
49ms
49ms
49ms
8
8
0
0
0
0
0
0
220ms
27ms
99ms
1
1
0
0
0
0
0
0
22ms
22ms
22ms
5
5
0
0
0
0
0
0
459ms
91ms
437ms
2
2
0
0
0
0
0
0
66ms
33ms
58ms
1
1
0
0
0
0
0
0
2ms
2ms
2ms
4
4
0
0
0
0
0
0
20ms
5ms
11ms
2
2
0
0
0
0
0
0
6ms
3ms
5ms
5
5
0
0
0
0
0
0
197ms
39ms
123ms
6
6
0
0
0
0
0
0
74ms
12ms
23ms
2
2
0
0
0
0
0
0
52ms
26ms
27ms
3
3
0
0
0
0
0
0
15ms
5ms
11ms
2
2
0
0
0
0
0
0
34ms
17ms
20ms
2
2
0
0
0
0
0
0
24ms
12ms
21ms
2
2
0
0
0
0
0
0
259ms
129ms
158ms
1
1
0
0
0
0
0
0
88ms
88ms
88ms
2
2
0
0
0
0
0
0
57ms
28ms
30ms
1
1
0
0
0
0
0
0
20ms
20ms
20ms
1
1
0
0
0
0
0
0
5ms
5ms
5ms
1
1
0
0
0
0
0
0
6ms
6ms
6ms
1
1
0
0
0
0
0
0
149ms
149ms
149ms
2
2
0
0
0
0
0
0
16ms
8ms
12ms
2
2
0
0
0
0
0
0
163ms
81ms
89ms
1
1
0
0
0
0
0
0
4ms
4ms
4ms
3
3
0
0
0
0
0
0
9ms
3ms
4ms
5
5
0
0
0
0
0
0
369ms
73ms
319ms
6
6
0
0
0
0
0
0
61ms
10ms
22ms
6
6
0
0
0
0
0
0
161ms
26ms
68ms
1
1
0
0
0
0
0
0
39ms
39ms
39ms
1
1
0
0
0
0
0
0
24ms
24ms
24ms
1
1
0
0
0
0
0
0
22ms
22ms
22ms
3
3
0
0
0
0
0
0
1s
447ms
928ms
1
1
0
0
0
0
0
0
83ms
83ms
83ms
2
2
0
0
0
0
0
0
280ms
140ms
148ms
1
1
0
0
0
0
0
0
23ms
23ms
23ms
2
2
0
0
0
0
0
0
23ms
11ms
21ms
1
1
0
0
0
0
0
0
1s
1s
1s
4
4
0
0
0
0
0
0
264ms
66ms
88ms
1
1
0
0
0
0
0
0
140ms
140ms
140ms
11
11
0
0
0
0
0
0
229ms
20ms
40ms
1
1
0
0
0
0
0
0
2ms
2ms
2ms
6
6
0
0
0
0
0
0
21ms
3ms
11ms
5
5
0
0
0
0
0
0
150ms
30ms
115ms
3
3
0
0
0
0
0
0
2ms
0ms
1ms
8
8
0
0
0
0
0
0
25ms
3ms
10ms
1
1
0
0
0
0
0
0
14ms
14ms
14ms
6
6
0
0
0
0
0
0
61ms
10ms
26ms
1
1
0
0
0
0
0
0
665ms
665ms
665ms
1
1
0
0
0
0
0
0
27ms
27ms
27ms
1
1
0
0
0
0
0
0
46ms
46ms
46ms
2
2
0
0
0
0
0
0
34ms
17ms
29ms
3
3
0
0
0
0
0
0
83ms
27ms
46ms
5
5
0
0
0
0
0
0
107ms
21ms
68ms
1
1
0
0
0
0
0
0
13ms
13ms
13ms
1
1
0
0
0
0
0
0
93ms
93ms
93ms
1
1
0
0
0
0
0
0
4ms
4ms
4ms
2
2
0
0
0
0
0
0
92ms
46ms
48ms
1
1
0
0
0
0
0
0
9ms
9ms
9ms
2
2
0
0
0
0
0
0
64ms
32ms
61ms
2
2
0
0
0
0
0
0
39ms
19ms
30ms
1
1
0
0
0
0
0
0
12ms
12ms
12ms
1
1
0
0
0
0
0
0
100ms
100ms
100ms
1
1
0
0
0
0
0
0
172ms
172ms
172ms
4
4
0
0
0
0
0
0
76ms
19ms
56ms
2
2
0
0
0
0
0
0
6ms
3ms
4ms
2
2
0
0
0
0
0
0
215ms
107ms
114ms
2
2
0
0
0
0
0
0
44ms
22ms
38ms
8
8
0
0
0
0
0
0
37ms
4ms
19ms
6
6
0
0
0
0
0
0
9ms
1ms
3ms
3
3
0
0
0
0
0
0
2ms
0ms
1ms
8
8
0
0
0
0
0
0
50ms
6ms
21ms
Apple Cinnamon Muffins Creation TestsValid apple cinnamon muffin request should return a fresh batch Happy Path26ms🔗Diagrams
This scenario:Payloads
Different muffin recipes should produce the expected batch 3/3 passed599ms ยท 479ms warm-up🔗
Muffin request with invalid field should return bad request 6/6 passed45ms🔗
#
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
4ms
4
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
1ms
5
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
35ms
6
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
1ms
Diagrams
This scenario:Payloads
Audit Logs Filtering TestsAudit logs should be filterable by entity id 732ms ยท 648ms warm-up🔗Diagrams
This scenario:Payloads
Audit logs should be filterable by entity type 68ms🔗Diagrams
This scenario:Payloads
Audit logs should be returned in descending timestamp order 28ms🔗Diagrams
This scenario:Payloads
Filtering audit logs by a non existent entity type should return an empty collection 31ms🔗Diagrams
This scenario:Payloads
Audit Logs Retrieval TestsCreating an order should produce a retrievable audit log entry Happy Path49ms🔗Steps✓GivenA pancake batch has been created(21ms)
✓Pancake steps response message status code should be equal to 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 equal to Empty(0ms)
✓AndAn order has been created for the batch(9ms)
✓Order steps response message status code should be equal to 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 equal to Empty(0ms)
✓WhenThe audit logs are retrieved(10ms)
✓ThenThe response contains the order creation entry(2ms)
✓Audit steps response message status code should be equal to 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_1198682930102706920') ](0ms)
✓AndThe downstream services received requests(1ms)
✓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 Path2ms🔗Diagrams
This scenario:Payloads
Creating a note with missing note text should return bad request 1ms🔗Diagrams
This scenario:Payloads
Creating a note with missing recipe name should return bad request 15ms🔗Diagrams
This scenario:Payloads
Listing notes by recipe should return matching notes 56ms🔗Diagrams
This scenario:Payloads
Retrieving a non existent note should return not found 22ms🔗Diagrams
This scenario:Payloads
Retrieving an existing note by id should return the note 5ms🔗Diagrams
This scenario:Payloads
Updating a non existent note should return not found 99ms🔗Diagrams
This scenario:Payloads
Updating an existing note should return the updated note 15ms🔗Diagrams
Staff Management TestsAdding a new staff member should return the created member Happy Path4ms🔗Diagrams
This scenario:Payloads
Adding a staff member with an invalid role should return a bad request response 1ms🔗Diagrams
This scenario:Payloads
Deleting a staff member should return no content 56ms🔗Diagrams
This scenario:Payloads
Retrieving an existing staff member should return the member 14ms🔗Diagrams
This scenario:Payloads
Toppings Deletion TestsDeleting an existing topping should return no content Happy Path1ms🔗Diagrams
This scenario:Payloads
Deleting a non existent topping should return not found 4ms🔗Diagrams
This scenario:Payloads
Toppings Feature Flag TestsToppings should exclude raspberries when feature flag is disabled 101ms🔗Diagrams
This scenario:Payloads
Toppings should include raspberries when feature flag is enabled 114ms🔗Diagrams
This scenario:Payloads
Toppings Management TestsToppings endpoint should return all available toppings Happy Path5ms🔗Diagrams
This scenario:Payloads
Adding a new topping should return the created topping 38ms🔗Diagrams
This scenario:Payloads
Toppings Update TestsUpdating an existing topping should return the updated topping Happy Path3ms🔗Diagrams
This scenario:Payloads
Update topping with invalid or dangerous input should return bad request 6/6 passed31ms🔗
#
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
2ms
3
Category
javascript:alert(1)
Javascript protocol
Category contains potentially dangerous content.
Bad Request
Passed
19ms
4
Name
Name is required
'Name' is required.
Bad Request
Passed
0ms
5
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
4ms
6
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
3ms
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 passed9ms🔗
#
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
3ms
5
Name
<img src=x onerror=alert(1)>
Event handler in name
Name contains potentially dangerous content.
Bad Request
Passed
0ms
6
Name
<script>alert('xss')</script>
Script tag in name
Name contains potentially dangerous content.
Bad Request
Passed
0ms
Diagrams
This scenario:Payloads
Waffles Content Negotiation TestsSending request with unsupported content type should return unsupported media type 3/3 passed2ms🔗
#
Input Parameters
Status
Duration
Content Type
1
application/xml
Passed
1ms
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 Path18ms🔗Diagrams
This scenario:Payloads
Waffle request with invalid ingredient should return bad request 6/6 passed10ms🔗
#
Input Parameters
Status
Duration
Field
Value
Reason
Expected Error
Expected Status
1
Butter
Butter is required
'Butter' is required.
Bad Request
Passed
1ms
2
Butter
<img onerror=x>
XSS in butter
Butter contains potentially dangerous content.
Bad Request
Passed
1ms
3
Eggs
Eggs is required
'Eggs' is required.
Bad Request
Passed
1ms
4
Flour
Flour is required
'Flour' is required.
Bad Request
Passed
0ms
5
Milk
Milk is required
'Milk' is required.
Bad Request
Passed
4ms
6
Milk
<script>alert</script>
XSS in milk
Milk contains potentially dangerous content.
Bad Request
Passed
1ms
Diagrams
This scenario:Payloads
Waffle request with more toppings than allowed should return bad request 21ms🔗Diagrams
This scenario:Payloads
Scenario Timeline 🛈
ShowWarm-upOrder
Outbox message should transition to failed after exhausting retries
1.0s
Valid order should be created and an event published
928ms
Audit logs should be filterable by entity id
732ms
Batch completions should contain data ingested via pubsub consumer
665ms
Different muffin recipes should produce the expected batch [Classic, MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Plain Flour, Apples = Granny Smith, Cinnamon = Ceylon }, Toppings = System.Collections.Generic.List`1[BreakfastProvider.Tests.Compโฆ]
579ms
Retrieving existing customer preferences should return the preferences
437ms
Creating an order should produce an audit log entry and events
335ms
Getting usage summary should return aggregated data
319ms
The open api endpoint should return a valid specification
172ms
Health check should report degraded when multiple downstream services are unavailable
158ms
Creating an order should emit a structured log entry
149ms
Order at maximum items per order should be accepted
148ms
Exceeding rate limit should return too many requests
140ms
Order exceeding maximum items per order should be rejected
132ms
Recording an equipment reading should return the created record
123ms
Getting the timing summary should return aggregated data
115ms
Toppings should include raspberries when feature flag is enabled
114ms
Toppings should exclude raspberries when feature flag is disabled
101ms
Health check should report degraded when cow service is unavailable
100ms
The scalar ui endpoint should return a valid page
100ms
Updating a non existent note should return not found
99ms
The async api endpoint should return a valid specification
93ms
Goat milk endpoint should return fresh goat milk when feature is enabled
89ms
Listing orders should return a paginated response
88ms
Health check should report degraded when downstream service returns non success status
88ms
Requesting second page should return different orders
86ms
Order should progress through all status transitions to completion
83ms
Creating an order should write an outbox message that gets processed
78ms
Goat milk endpoint should return not found when feature is disabled
74ms
Listing orders with small page size should limit results
72ms
Listing all inventory items should return all items
68ms
Cancelling a reservation should return the cancelled reservation
68ms
Audit logs should be filterable by entity type
68ms
The grpc contract endpoint should return a valid specification
61ms
Same order with same idempotency key should return same confirmation
58ms
Listing notes by recipe should return matching notes
56ms
Deleting a staff member should return no content
56ms
Listing readings by equipment should return matching records
50ms
Creating an order should produce a retrievable audit log entry
49ms
The graph ql schema definition endpoint should return the schema definition
48ms
Ingredient shipments should be recorded when delivered via eventgrid webhook
46ms
Popular recipes should return recipe types ordered by frequency
46ms
The graph ql schema endpoint should return a valid specification
44ms
Valid status transition should update the order [Created, Cancelled]
40ms
Menu endpoint should return all menu items with availability
39ms
Listing usage by ingredient should return matching records
39ms
Adding a new topping should return the created topping
38ms
Muffin request with invalid field should return bad request [Flour, , Flour is required, 'Flour' is required·, Bad Request]
35ms
Retrieving a non existent inventory item should return not found
31ms
Filtering audit logs by a non existent entity type should return an empty collection
31ms
Request with correlation id should forward it to cow service
30ms
Grpc server reflection should list the breakfast service
30ms
Order summaries should contain ingested order data
29ms
Audit logs should be returned in descending timestamp order
28ms
Invalid status transition should return conflict [Completed, Preparing]
27ms
Order status for non existent order should return not found
27ms
Equipment alerts should contain data ingested via event hub consumer
27ms
Deleting an inventory item should return no content
26ms
Valid apple cinnamon muffin request should return a fresh batch
26ms
Request with correlation id should forward it to supplier service
26ms
Submitting a recipe review should return the created review
26ms
Order status via grpc should return order details
25ms
Updating an inventory item should return the updated item
24ms
Menu should return cached results on subsequent requests
24ms
Listing feedback for an order should return the feedback
23ms
Creating an order when kitchen service returns error should still create the order
23ms
Consuming customer feedback event should trigger downstream processing
22ms
Retrieving a non existent note should return not found
22ms
Submitting feedback should return the created feedback
22ms
Requesting menu when supplier service unavailable should mark items as unavailable
22ms
Deleting a waste record should return no content
22ms
Request with correlation id should return same id in response
21ms
Recipe reports should contain ingested recipe data
21ms
Listing timings by station should return matching records
21ms
Previously created order should be retrievable by id
21ms
Waffle request with more toppings than allowed should return bad request
21ms
Valid status transition should update the order [Ready, Completed]
20ms
Streaming order updates should return the current status
20ms
Health check response should include description and data for each entry
20ms
Valid status transition should update the order [Created, Preparing]
19ms
Update topping with invalid or dangerous input should return bad request [Category, javascript:alert(1), Javascript protocol, Category contains potentially dangerous content·, Bad Request]
19ms
Invalid status transition should return conflict [Ready, Preparing]
19ms
Deleting a reading should remove it from the list
18ms
Valid waffle request with all ingredients should return a fresh batch
18ms
Valid status transition should update the order [Preparing, Ready]
18ms
Invalid status transition should return conflict [Cancelled, Preparing]
17ms
Invalid status transition should return conflict [Cancelled, Ready]
17ms
Invalid status transition should return conflict [Preparing, Cancelled]
17ms
Listing orders when none exist should return an empty page
16ms
Invalid status transition should return conflict [Created, Completed]
16ms
Listing waste by recipe should return matching records
16ms
Ingredient usage should aggregate across multiple recipes
15ms
Updating an existing note should return the updated note
15ms
Retrieving existing review by id should return the review
15ms
Creating a note with missing recipe name should return bad request
15ms
Recording waste with missing reason should return bad request
15ms
Invalid status transition should return conflict [Created, Ready]
15ms
Retrieving an existing staff member should return the member
14ms
Consuming recipe cost event should trigger downstream processing
14ms
Streaming updates for non existent order should return not found
13ms
Retrieving non existent feedback should return not found
13ms
Consuming an order served event should trigger downstream processing
13ms
Retrieving an existing reservation should return the reservation
12ms
Listing reviews by recipe should return matching reviews
12ms
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.โฆ]
12ms
The grpc ui endpoint should return a page describing the service
12ms
Requesting goat milk when goat service unavailable should return bad gateway
12ms
Deleting a reservation should return no content
11ms
Pancake recipe summary should return correct data
11ms
Remaining quantity should decrease after each order
11ms
Order status update with invalid field should return bad request [Status, , Status is required, 'Status' is required·, Bad Request]
11ms
Valid pancake request with all ingredients should return a fresh batch
10ms
Grpc server reflection should describe the breakfast service
9ms
Retrieving existing feedback by id should return the feedback
9ms
The graph ql ui endpoint should return a valid page
9ms
Cancelling an already cancelled reservation should return a conflict response
9ms
Same order with different idempotency keys should return different confirmations
7ms
Updating customer preferences should return the updated preferences
7ms
Different muffin recipes should produce the expected batch [Rustic Wholesome, MuffinRecipeTestData { Ingredients = IngredientSet { Flour = Whole Wheat, Apples = Honeycrisp, Cinnamon = Cassia }, Toppings = System.Collections.Generic.List`1[BreakfastProvider.Tesโฆ]
7ms
Recording an order timing should return the created record
7ms
Saving customer preferences should return the saved preferences
6ms
Pancake request with more toppings than allowed should return bad request
6ms
Heartbeat endpoint should return a running message
6ms
Retrieving an existing inventory item should return the item
6ms
Recording ingredient usage should return the created record
5ms
Retrieving an existing note by id should return the note
5ms
Toppings endpoint should return all available toppings
5ms
Creating a reservation should return the confirmed reservation
5ms
Health check endpoint should return healthy status with all dependency details
5ms
Daily special order with invalid field should return bad request [SpecialId, null, Special ID is required, 'Special Id' is required·, Bad Request]
5ms
Waffle request with invalid ingredient should return bad request [Milk, , Milk is required, 'Milk' is required·, Bad Request]
4ms
Order with invalid field should return bad request [Items, null, At least one item is required, The Items field is required·, Bad Request]
4ms
The async api ui endpoint should return a valid page
4ms
Order summaries should return an empty list when no orders exist
4ms
Retrieving non existent customer preferences should return not found
4ms
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]
4ms
Deleting a non existent topping should return not found
4ms
Muffin request with invalid field should return bad request [Cinnamon, <script>alert('xss')</script>, XSS in cinnamon, Cinnamon contains potentially dangerous content·, Bad Request]
4ms
Goat milk endpoint should return fresh goat milk from goat service
4ms
Adding a new inventory item should return the created item
4ms
Requesting milk when cow service returns invalid response should return bad gateway
4ms
Adding a new staff member should return the created member
4ms
Ordering daily special beyond threshold should return conflict
3ms
Requesting goat milk when goat service returns invalid response should return bad gateway
3ms
Topping request with invalid or dangerous input should return bad request [Name, , Name is required, 'Name' is required·, Bad Request]
3ms
Recording ingredient waste should return the created record
3ms
Updating an existing topping should return the updated topping
3ms
Recording a timing with missing station should return bad request
3ms
Pancake request with invalid ingredient should return bad request [Flour, <img onerror=x>, XSS in flour, Flour contains potentially dangerous content·, Bad Request]
3ms
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]
3ms
Recording usage with zero quantity should return bad request
3ms
Saving customer preferences with missing customer name should return bad request
3ms
Valid daily special order should return a confirmation
3ms
Requesting milk when cow service times out should return bad gateway
3ms
Creating a chef note should return the created note
2ms
Updating a non existent topping should return not found
2ms
Recording a reading with zero value should return bad request
2ms
Submitting review with invalid rating should return bad request
2ms
Submitting feedback with missing customer name should return bad request
2ms
Retrieving a non existent order should return not found
2ms
The grpc proto endpoint should return the proto file
2ms
Requesting milk when cow service unavailable should return bad gateway
2ms
Recording a timing with zero prep seconds should return bad request
2ms
Daily specials endpoint should return all available specials
2ms
Submitting feedback with invalid rating should return bad request
2ms
Request without correlation id should have one generated in response
2ms
Retrieving non existent review should return not found
2ms
Ordering non existent daily special should return not found
2ms
Recording waste with zero quantity should return bad request
2ms
Submitting review with missing recipe name should return bad request
2ms
Updating status of non existent order should return not found
2ms
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]
2ms
Waffle recipe summary should return correct data
1ms
Order with invalid field should return bad request [Items[0]·BatchId, null, Batch ID is required, 'Batch Id' is required·, Bad Request]
1ms
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]
1ms
Deleting an existing topping should return no content
1ms
Recording a reading with missing metric should return bad request
1ms
Recording waste with missing ingredient name should return bad request
1ms
Recording usage with missing ingredient name should return bad request
1ms
Creating a note with missing note text should return bad request
1ms
Topping request with invalid or dangerous input should return bad request [Category, javascript:alert(1), Javascript protocol, Category contains potentially dangerous content·, Bad Request]
1ms
Request with unsupported content type should return unsupported media type [text/html]
1ms
Unknown recipe type should return zero batches
1ms
Adding a staff member with an invalid role should return a bad request response
1ms
Muffin request with invalid field should return bad request [Cinnamon, , Cinnamon is required, 'Cinnamon' is required·, Bad Request]
1ms
Sending request with unsupported content type should return unsupported media type [application/xml]
1ms
Muffin request with invalid field should return bad request [Apples, , Apples is required, 'Apples' is required·, Bad Request]
1ms
Muffin request with invalid field should return bad request [Milk, , Milk is required, 'Milk' 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
Waffle request with invalid ingredient should return bad request [Butter, <img onerror=x>, XSS in butter, Butter contains potentially dangerous content·, Bad Request]
1ms
Muffin request with invalid field should return bad request [Eggs, , Eggs is required, 'Eggs' is required·, Bad Request]
1ms
Topping request with invalid or dangerous input should return bad request [Category, , Category is required, 'Category' is required·, 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
Waffle request with invalid ingredient 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 [Category, , Category is required, 'Category' is required·, 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]·ItemType, , Item type is required, 'Item Type' is required·, Bad Request]
1ms
Waffle request with invalid ingredient should return bad request [Butter, , Butter is required, 'Butter' is required·, Bad Request]
1ms
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
Update topping with invalid or dangerous input should return bad request [Name, , Name is required, 'Name' is required·, Bad Request]
0ms
Order with invalid field should return bad request [CustomerName, , Customer name is required, 'Customer Name' is required·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Milk, <script>alert</script>, XSS in milk, Milk contains potentially dangerous content·, Bad Request]
0ms
Waffle request with invalid ingredient should return bad request [Flour, , Flour is required, 'Flour' is required·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Eggs, , Eggs is required, 'Eggs' is required·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Flour, , Flour is required, 'Flour' is required·, Bad Request]
0ms
Pancake request with invalid ingredient should return bad request [Milk, , Milk is required, 'Milk' is required·, Bad Request]
0ms
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]
0ms
Topping request with invalid or dangerous input should return bad request [Name, <img src=x onerror=alert(1)>, Event handler in name, Name contains potentially dangerous content·, Bad Request]
0ms
Sending request with unsupported content type should return unsupported media type [text/html]
0ms
Sending request with unsupported content type should return unsupported media type [text/plain]
0ms
Request with unsupported content type should return unsupported media type [text/plain]
0ms
Request with unsupported content type should return unsupported media type [application/xml]
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