@typespec/http-specs 0.1.0-alpha.9 → 0.1.0-dev.0

package/spec-summary.md

@@ -39,6 +39,18 @@ Expect error code 403 and error body:
 
 Expects header 'Authorization': 'SharedAccessKey valid-key'
 
+### Authentication_Noauth_Union_validNoAuth
+
+- Endpoint: `get /authentication/noauth/union/valid`
+
+Expects no authentication. The server accepts requests without any authentication header.
+
+### Authentication_Noauth_Union_validToken
+
+- Endpoint: `get /authentication/noauth/union/validtoken`
+
+Expects header 'authorization': 'Bearer https://security.microsoft.com/.default'
+
 ### Authentication_OAuth2_invalid
 
 - Endpoint: `get /authentication/oauth2/invalid`
@@ -71,6 +83,292 @@ Expects header 'x-ms-api-key': 'valid-key'
 
 Expects header 'authorization': 'Bearer https://security.microsoft.com/.default'
 
+### Documentation_Lists_bulletPointsOp
+
+- Endpoint: `get /documentation/lists/bullet-points/op`
+
+Test simple bullet points in documentation.
+Expected behavior: Should render properly formatted bullet lists.
+
+### Documentation_Lists_numbered
+
+- Endpoint: `get /documentation/lists/numbered`
+
+Test numbered lists.
+Expected behavior: Should render numbered list properly.
+
+### Documentation_TextFormatting_boldText
+
+- Endpoint: `get /documentation/text-formatting/bold`
+
+Expected behavior: Text between \*\* should render as bold.
+
+### Documentation_TextFormatting_combinedFormatting
+
+- Endpoint: `get /documentation/text-formatting/combined`
+
+Test combined bold and italic formatting.
+Expected behavior: Should handle nested and combined formatting.
+
+### Documentation_TextFormatting_italicText
+
+- Endpoint: `get /documentation/text-formatting/italic`
+
+Test italic text formatting using _single asterisks_.
+Expected behavior: Text between \* should render as italic.
+
+### Encode_Array_Property_commaDelimited
+
+- Endpoint: `post /encode/array/property/comma-delimited`
+
+Test operation with request and response model contains a string array property with commaDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+### Encode_Array_Property_enumCommaDelimited
+
+- Endpoint: `post /encode/array/property/enum/comma-delimited`
+
+Test operation with request and response model contains an enum array property with commaDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+### Encode_Array_Property_enumNewlineDelimited
+
+- Endpoint: `post /encode/array/property/enum/newline-delimited`
+
+Test operation with request and response model contains an enum array property with newlineDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+### Encode_Array_Property_enumPipeDelimited
+
+- Endpoint: `post /encode/array/property/enum/pipe-delimited`
+
+Test operation with request and response model contains an enum array property with pipeDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+### Encode_Array_Property_enumSpaceDelimited
+
+- Endpoint: `post /encode/array/property/enum/space-delimited`
+
+Test operation with request and response model contains an enum array property with spaceDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
+### Encode_Array_Property_extensibleEnumCommaDelimited
+
+- Endpoint: `post /encode/array/property/extensible-enum/comma-delimited`
+
+Test operation with request and response model contains an extensible enum (union) array property with commaDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+### Encode_Array_Property_extensibleEnumNewlineDelimited
+
+- Endpoint: `post /encode/array/property/extensible-enum/newline-delimited`
+
+Test operation with request and response model contains an extensible enum (union) array property with newlineDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+### Encode_Array_Property_extensibleEnumPipeDelimited
+
+- Endpoint: `post /encode/array/property/extensible-enum/pipe-delimited`
+
+Test operation with request and response model contains an extensible enum (union) array property with pipeDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+### Encode_Array_Property_extensibleEnumSpaceDelimited
+
+- Endpoint: `post /encode/array/property/extensible-enum/space-delimited`
+
+Test operation with request and response model contains an extensible enum (union) array property with spaceDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
+### Encode_Array_Property_newlineDelimited
+
+- Endpoint: `post /encode/array/property/newline-delimited`
+
+Test operation with request and response model contains a string array property with newlineDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+### Encode_Array_Property_pipeDelimited
+
+- Endpoint: `post /encode/array/property/pipe-delimited`
+
+Test operation with request and response model contains a string array property with pipeDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+### Encode_Array_Property_spaceDelimited
+
+- Endpoint: `post /encode/array/property/space-delimited`
+
+Test operation with request and response model contains a string array property with spaceDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
 ### Encode_Bytes_Header_base64
 
 - Endpoint: `get /encode/bytes/header/base64`
@@ -240,22 +538,21 @@ Expected body:
 - Endpoint: `post /encode/bytes/body/request/custom-content-type`
 
 When content type is a custom type(image/png here) and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+File should match packages/http-specs/assets/image.png.
 
 ### Encode_Bytes_RequestBody_default
 
 - Endpoint: `post /encode/bytes/body/request/default`
 
-Test default encode (base64) for bytes in a json body.
-Expected body:
-"dGVzdA==" (base64 encode of test, in JSON string)
+When content type is not defined and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Bytes_RequestBody_octetStream
 
 - Endpoint: `post /encode/bytes/body/request/octet-stream`
 
-When content type is application/octet-stream and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+When content type is application/octet-stream and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Bytes_ResponseBody_base64
 
@@ -278,22 +575,21 @@ Expected body:
 - Endpoint: `get /encode/bytes/body/response/custom-content-type`
 
 When content type is a custom type(image/png here) and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+File should match packages/http-specs/assets/image.png
 
 ### Encode_Bytes_ResponseBody_default
 
 - Endpoint: `get /encode/bytes/body/response/default`
 
-Test default encode (base64) for bytes in a json body.
-Expected body:
-"dGVzdA==" (base64 encode of test, in JSON string)
+When content type is not defined and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Bytes_ResponseBody_octetStream
 
 - Endpoint: `get /encode/bytes/body/response/octet-stream`
 
-When content type is application/octet-stream and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+When content type is application/octet-stream and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Datetime_Header_default
 
@@ -519,6 +815,13 @@ value=1686566864
 Test default encode for a duration header.
 Expected header `input=P40D`
 
+### Encode_Duration_Header_float64Milliseconds
+
+- Endpoint: `get /encode/duration/header/float64-milliseconds`
+
+Test float64 milliseconds encode for a duration header.
+Expected header `duration: 35625`
+
 ### Encode_Duration_Header_float64Seconds
 
 - Endpoint: `get /encode/duration/header/float64-seconds`
@@ -526,6 +829,21 @@ Expected header `input=P40D`
 Test float64 seconds encode for a duration header.
 Expected header `duration: 35.625`
 
+### Encode_Duration_Header_floatMilliseconds
+
+- Endpoint: `get /encode/duration/header/float-milliseconds`
+
+Test float milliseconds encode for a duration header.
+Expected header `duration: 35625`
+
+### Encode_Duration_Header_floatMillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/float-milliseconds-larger-unit`
+
+Test float milliseconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3.5) in C#.
+Expected header `duration: 210000.0`
+
 ### Encode_Duration_Header_floatSeconds
 
 - Endpoint: `get /encode/duration/header/float-seconds`
@@ -533,6 +851,36 @@ Expected header `duration: 35.625`
 Test float seconds encode for a duration header.
 Expected header `duration: 35.625`
 
+### Encode_Duration_Header_floatSecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/float-seconds-larger-unit`
+
+Test float seconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2.5) in C#.
+Expected header `duration: 150.0`
+
+### Encode_Duration_Header_int32Milliseconds
+
+- Endpoint: `get /encode/duration/header/int32-milliseconds`
+
+Test int32 milliseconds encode for a duration header.
+Expected header `duration: 36000`
+
+### Encode_Duration_Header_int32MillisecondsArray
+
+- Endpoint: `get /encode/duration/header/int32-milliseconds-array`
+
+Test int32 milliseconds encode for a duration array header.
+Expected header `duration: [36000,47000]`
+
+### Encode_Duration_Header_int32MillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/int32-milliseconds-larger-unit`
+
+Test int32 milliseconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3) in C#.
+Expected header `duration: 180000`
+
 ### Encode_Duration_Header_int32Seconds
 
 - Endpoint: `get /encode/duration/header/int32-seconds`
@@ -540,6 +888,14 @@ Expected header `duration: 35.625`
 Test int32 seconds encode for a duration header.
 Expected header `duration: 36`
 
+### Encode_Duration_Header_int32SecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/int32-seconds-larger-unit`
+
+Test int32 seconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2) in C#.
+Expected header `duration: 120`
+
 ### Encode_Duration_Header_iso8601
 
 - Endpoint: `get /encode/duration/header/iso8601`
@@ -575,16 +931,16 @@ Expected response body:
 }
 ```
 
-### Encode_Duration_Property_float64Seconds
+### Encode_Duration_Property_float64Milliseconds
 
-- Endpoint: `get /encode/duration/property/float64-seconds`
+- Endpoint: `get /encode/duration/property/float64-milliseconds`
 
-Test operation with request and response model contains a duration property with float64 seconds encode.
+Test operation with request and response model contains a duration property with float64 milliseconds encode.
 Expected request body:
 
 ```json
 {
-  "value": 35.625
+  "value": 35625
 }
 ```
 
@@ -592,15 +948,15 @@ Expected response body:
 
 ```json
 {
-  "value": 35.625
+  "value": 35625
 }
 ```
 
-### Encode_Duration_Property_floatSeconds
+### Encode_Duration_Property_float64Seconds
 
-- Endpoint: `get /encode/duration/property/float-seconds`
+- Endpoint: `get /encode/duration/property/float64-seconds`
 
-Test operation with request and response model contains a duration property with float seconds encode.
+Test operation with request and response model contains a duration property with float64 seconds encode.
 Expected request body:
 
 ```json
@@ -617,11 +973,96 @@ Expected response body:
 }
 ```
 
-### Encode_Duration_Property_floatSecondsArray
+### Encode_Duration_Property_floatMilliseconds
 
-- Endpoint: `get /encode/duration/property/float-seconds-array`
+- Endpoint: `get /encode/duration/property/float-milliseconds`
 
-Test operation with request and response model contains an array property which elements are duration with float seconds encode.
+Test operation with request and response model contains a duration property with float milliseconds encode.
+Expected request body:
+
+```json
+{
+  "value": 35625
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": 35625
+}
+```
+
+### Encode_Duration_Property_floatMillisecondsArray
+
+- Endpoint: `get /encode/duration/property/float-milliseconds-array`
+
+Test operation with request and response model contains an array property which elements are duration with float milliseconds encode.
+Expected request body:
+
+```json
+{
+  "value": [35625, 46750]
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": [35625, 46750]
+}
+```
+
+### Encode_Duration_Property_floatMillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/property/float-milliseconds-larger-unit`
+
+Test operation with request and response model contains a duration property with float milliseconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3.5) in C#.
+Expected request body:
+
+```json
+{
+  "value": 210000.0
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": 210000.0
+}
+```
+
+### Encode_Duration_Property_floatSeconds
+
+- Endpoint: `get /encode/duration/property/float-seconds`
+
+Test operation with request and response model contains a duration property with float seconds encode.
+Expected request body:
+
+```json
+{
+  "value": 35.625
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": 35.625
+}
+```
+
+### Encode_Duration_Property_floatSecondsArray
+
+- Endpoint: `get /encode/duration/property/float-seconds-array`
+
+Test operation with request and response model contains an array property which elements are duration with float seconds encode.
 Expected request body:
 
 ```json
@@ -638,6 +1079,71 @@ Expected response body:
 }
 ```
 
+### Encode_Duration_Property_floatSecondsLargerUnit
+
+- Endpoint: `get /encode/duration/property/float-seconds-larger-unit`
+
+Test operation with request and response model contains a duration property with float seconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2.5) in C#.
+Expected request body:
+
+```json
+{
+  "value": 150.0
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": 150.0
+}
+```
+
+### Encode_Duration_Property_int32Milliseconds
+
+- Endpoint: `get /encode/duration/property/int32-milliseconds`
+
+Test operation with request and response model contains a duration property with int32 milliseconds encode.
+Expected request body:
+
+```json
+{
+  "value": 36000
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": 36000
+}
+```
+
+### Encode_Duration_Property_int32MillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/property/int32-milliseconds-larger-unit`
+
+Test operation with request and response model contains a duration property with int32 milliseconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3) in C#.
+Expected request body:
+
+```json
+{
+  "value": 180000
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": 180000
+}
+```
+
 ### Encode_Duration_Property_int32Seconds
 
 - Endpoint: `get /encode/duration/property/int32-seconds`
@@ -659,6 +1165,28 @@ Expected response body:
 }
 ```
 
+### Encode_Duration_Property_int32SecondsLargerUnit
+
+- Endpoint: `get /encode/duration/property/int32-seconds-larger-unit`
+
+Test operation with request and response model contains a duration property with int32 seconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2) in C#.
+Expected request body:
+
+```json
+{
+  "value": 120
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": 120
+}
+```
+
 ### Encode_Duration_Property_iso8601
 
 - Endpoint: `post /encode/duration/property/iso8601`
@@ -687,6 +1215,13 @@ Expected response body:
 Test default encode for a duration parameter.
 Expected query parameter `input=P40D`
 
+### Encode_Duration_Query_float64Milliseconds
+
+- Endpoint: `get /encode/duration/query/float64-milliseconds`
+
+Test float64 milliseconds encode for a duration parameter.
+Expected query parameter `input=35625`
+
 ### Encode_Duration_Query_float64Seconds
 
 - Endpoint: `get /encode/duration/query/float64-seconds`
@@ -694,6 +1229,21 @@ Expected query parameter `input=P40D`
 Test float64 seconds encode for a duration parameter.
 Expected query parameter `input=35.625`
 
+### Encode_Duration_Query_floatMilliseconds
+
+- Endpoint: `get /encode/duration/query/float-milliseconds`
+
+Test float milliseconds encode for a duration parameter.
+Expected query parameter `input=35625`
+
+### Encode_Duration_Query_floatMillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/float-milliseconds-larger-unit`
+
+Test float milliseconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3.5) in C#.
+Expected query parameter `input=210000.0`
+
 ### Encode_Duration_Query_floatSeconds
 
 - Endpoint: `get /encode/duration/query/float-seconds`
@@ -701,6 +1251,36 @@ Expected query parameter `input=35.625`
 Test float seconds encode for a duration parameter.
 Expected query parameter `input=35.625`
 
+### Encode_Duration_Query_floatSecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/float-seconds-larger-unit`
+
+Test float seconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2.5) in C#.
+Expected query parameter `input=150.0`
+
+### Encode_Duration_Query_int32Milliseconds
+
+- Endpoint: `get /encode/duration/query/int32-milliseconds`
+
+Test int32 milliseconds encode for a duration parameter.
+Expected query parameter `input=36000`
+
+### Encode_Duration_Query_int32MillisecondsArray
+
+- Endpoint: `get /encode/duration/query/int32-milliseconds-array`
+
+Test int32 milliseconds encode for a duration array parameter.
+Expected query parameter `input=36000,47000`
+
+### Encode_Duration_Query_int32MillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/int32-milliseconds-larger-unit`
+
+Test int32 milliseconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3) in C#.
+Expected query parameter `input=180000`
+
 ### Encode_Duration_Query_int32Seconds
 
 - Endpoint: `get /encode/duration/query/int32-seconds`
@@ -715,6 +1295,14 @@ Expected query parameter `input=36`
 Test int32 seconds encode for a duration array parameter.
 Expected query parameter `input=36,47`
 
+### Encode_Duration_Query_int32SecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/int32-seconds-larger-unit`
+
+Test int32 seconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2) in C#.
+Expected query parameter `input=120`
+
 ### Encode_Duration_Query_iso8601
 
 - Endpoint: `get /encode/duration/query/iso8601`
@@ -838,7 +1426,10 @@ Expected request body for `set`
 { "name": "foo" }
 ```
 
+Expected Content-Type header: application/json
+
 Expected no request body for `omit`
+Expected Content-Type header: must NOT be present
 
 ### Parameters_BodyOptionality_requiredExplicit
 
@@ -894,11 +1485,54 @@ This test is testing sending a pipes collection format array query parameters
 
 This test is testing sending a ssv collection format array query parameters
 
-### Parameters_CollectionFormat_Query_tsv
+### Parameters_Path_normal
+
+- Endpoint: `get /parameters/path/normal/{name}`
+
+Test case for normal path parameter.
+
+Should generate an operation like below:
+
+```
+normal(name: string)
+```
+
+Expected request path:
+
+```
+/normal/foo
+```
+
+### Parameters_Path_optional
+
+- Endpoint: `get /parameters/path/optional{/name}`
+
+Test case for optional path parameter.
+
+Should generate an operation like below:
+
+```
+optional(name?: string)
+```
+
+Expected two request:
+First request path:
+
+```
+/optional
+```
 
-- Endpoint: `get /parameters/collection-format/query/tsv`
+Second request path:
 
-This test is testing sending a tsv collection format array query parameters
+```
+/optional/foo
+```
+
+### Parameters_Query_Constant_post
+
+- Endpoint: `post /parameters/query/constant`
+
+Expect to handle a constant value for query and mock api returns nothing
 
 ### Parameters_Spread_Alias_spreadAsRequestBody
 
@@ -1165,7 +1799,7 @@ Expected input body:
     }
   ],
   "intValue": 1,
-  "floatValue": 1.1,
+  "floatValue": 1.25,
   "innerModel": {
     "name": "InnerMadge",
     "description": "innerDesc"
@@ -1193,7 +1827,7 @@ Expected response body:
     }
   ],
   "intValue": 1,
-  "floatValue": 1.1,
+  "floatValue": 1.25,
   "innerModel": {
     "name": "InnerMadge",
     "description": "innerDesc"
@@ -1309,9 +1943,9 @@ Expected request body is a string '{cat}'.
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same filedName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same filedName, server can't parse them all.
   ):
 
 ```
@@ -1334,9 +1968,9 @@ Content-Type: application/octet-stream;
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1364,9 +1998,9 @@ Content-Type: application/octet-stream;
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1416,6 +2050,68 @@ Content-Type: image/jpg
 --abcde12345--
 ```
 
+### Payload_MultiPart_FormData_File_uploadFileArray
+
+- Endpoint: `post /multipart/form-data/file/file-array`
+
+Test multiple File instances in multipart form data.
+Expected request:
+
+```
+POST /multipart/form-data/file/file-array HTTP/1.1
+Content-Type: multipart/form-data; boundary=abcde12345
+
+--abcde12345
+Content-Disposition: form-data; name="files"; filename="image1.png"
+Content-Type: image/png
+
+{…file content of image.png…}
+--abcde12345
+Content-Disposition: form-data; name="files"; filename="image2.png"
+Content-Type: image/png
+
+{…file content of image.png…}
+--abcde12345--
+```
+
+### Payload_MultiPart_FormData_File_uploadFileRequiredFilename
+
+- Endpoint: `post /multipart/form-data/file/required-filename`
+
+Test File type in multipart form data with required filename.
+Expected request:
+
+```
+POST /multipart/form-data/file/required-filename HTTP/1.1
+Content-Type: multipart/form-data; boundary=abcde12345
+
+--abcde12345
+Content-Disposition: form-data; name="file"; filename="image.png"
+Content-Type: image/png
+
+{…file content of image.png…}
+--abcde12345--
+```
+
+### Payload_MultiPart_FormData_File_uploadFileSpecificContentType
+
+- Endpoint: `post /multipart/form-data/file/specific-content-type`
+
+Test File type in multipart form data with specific content type.
+Expected request:
+
+```
+POST /multipart/form-data/file/specific-content-type HTTP/1.1
+Content-Type: multipart/form-data; boundary=abcde12345
+
+--abcde12345
+Content-Disposition: form-data; name="file"; filename="image.png"
+Content-Type: image/png
+
+{…file content of image.png…}
+--abcde12345--
+```
+
 ### Payload_MultiPart_FormData_fileArrayAndBasic
 
 - Endpoint: `post /multipart/form-data/complex-parts`
@@ -1423,9 +2119,9 @@ Content-Type: image/jpg
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1533,7 +2229,7 @@ Content-Type: application/octet-stream
 
 - Endpoint: `post /multipart/form-data/complex-parts-with-httppart`
 
-For File part, filename will not be checked but it is necessary otherwise cadl-ranch can't parse it;
+For File part, filename will not be checked but it is necessary otherwise server can't parse it;
 content-type will be checked with value "application/octet-stream". Expect request:
 
 ```
@@ -1606,9 +2302,9 @@ Content-Type: text/plain
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1638,9 +2334,9 @@ Content-Type: application/octet-stream
 Please send request twice, first time with only profileImage, second time with both profileImage and picture(
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1661,39 +2357,642 @@ Content-Type: application/octet-stream
 --abcde12345--
 ```
 
-### Payload_Pageable_ServerDrivenPagination_link
+### Payload_MultiPart_FormData_optionalParts
 
-- Endpoint: `get /payload/pageable/server-driven-pagination/link`
+- Endpoint: `post /multipart/form-data/optional-parts`
 
-Test case for using link as pagination.
+Please send request three times:
+
+- First time with only id
+- Second time with only profileImage
+- Third time with both id and profileImage
+
+Expect requests (
+
+- according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
+- according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
+  If there are duplicated filename in same fieldName, server can't parse them all.
+  ):
+
+```
+POST /upload HTTP/1.1
+Content-Length: 428
+Content-Type: multipart/form-data; boundary=abcde12345
+
+--abcde12345
+Content-Disposition: form-data; name="id"
+Content-Type: text/plain
+
+123
+--abcde12345--
+```
+
+```
+POST /upload HTTP/1.1
+Content-Length: 428
+Content-Type: multipart/form-data; boundary=abcde12345
+
+--abcde12345
+Content-Disposition: form-data; name="profileImage"; filename="<any-or-no-name-is-ok>"
+Content-Type: application/octet-stream
+
+{…file content of .jpg file…}
+--abcde12345--
+```
+
+```
+POST /upload HTTP/1.1
+Content-Length: 428
+Content-Type: multipart/form-data; boundary=abcde12345
+
+--abcde12345
+Content-Disposition: form-data; name="id"
+Content-Type: text/plain
+
+123
+--abcde12345
+Content-Disposition: form-data; name="profileImage"; filename="<any-or-no-name-is-ok>"
+Content-Type: application/octet-stream
+
+{…file content of .jpg file…}
+--abcde12345--
+```
+
+### Payload_MultiPart_FormData_withWireName
+
+- Endpoint: `post /multipart/form-data/mixed-parts-with-wire-name`
+
+Expect request with wire names (
+
+- according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
+- according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
+  If there are duplicated filename in same fieldName, server can't parse them all.
+  ):
+
+```
+POST /upload HTTP/1.1
+Content-Length: 428
+Content-Type: multipart/form-data; boundary=abcde12345
+
+--abcde12345
+Content-Disposition: form-data; name="id"
+Content-Type: text/plain
+
+123
+--abcde12345
+Content-Disposition: form-data; name="profileImage"; filename="<any-or-no-name-is-ok>"
+Content-Type: application/octet-stream;
+
+{…file content of .jpg file…}
+--abcde12345--
+```
+
+### Payload_Pageable_PageSize_listWithoutContinuation
+
+- Endpoint: `get /payload/pageable/pagesize/without-continuation`
+
+Test case for simple pagination without nextlink or continuationToken.
+
+Single request:
+Expected route: /payload/pageable/pagesize/without-continuation
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" },
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_PageSize_listWithPageSize
+
+- Endpoint: `get /payload/pageable/pagesize/list`
+
+Test case for pagination with a regular @pageSize parameter.
+
+Two requests need to be tested:
+
+1. Request with pageSize=2:
+   Expected route: /payload/pageable/pagesize/list?pageSize=2
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ]
+}
+```
+
+2. Request with pageSize=4:
+   Expected route: /payload/pageable/pagesize/list?pageSize=4
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" },
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderNestedResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-header-nested-response-body`
+
+Test case for using continuation token as pagination with nested response structure. Continuation token is passed in the request header and nested within response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-nested-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "1", "name": "dog" },
+      { "id": "2", "name": "cat" }
+    ]
+  },
+  "next": {
+    "nextToken": "page2"
+  }
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-nested-response-body?bar=bar
+
+Expected request header:
+token=page2
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "3", "name": "bird" },
+      { "id": "4", "name": "fish" }
+    ]
+  }
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-body`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request header and response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ],
+  "nextToken": "page2"
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-body?bar=bar
+
+Expected request header:
+token=page2
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderResponseHeader
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-header`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request header and response header.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-header?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ]
+}
+```
+
+Expected response header:
+next-token=page2
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-header?bar=bar
+
+Expected request header:
+token=page2
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryNestedResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-query-nested-response-body`
+
+Test case for using continuation token as pagination with nested response structure. Continuation token is passed in the request query and nested within response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-nested-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "1", "name": "dog" },
+      { "id": "2", "name": "cat" }
+    ]
+  },
+  "nestedNext": {
+    "nextToken": "page2"
+  }
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-nested-response-body?bar=bar&token=page2
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "3", "name": "bird" },
+      { "id": "4", "name": "fish" }
+    ]
+  }
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-body`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request query and response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ],
+  "nextToken": "page2"
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-body?bar=bar&token=page2
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseHeader
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-header`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request query and response header.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-header?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ]
+}
+```
+
+Expected response header:
+next-token=page2
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-header?bar=bar&token=page2
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_link
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/link`
+
+Test case for using link as pagination.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/link
+   Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ],
+  "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/link/nextPage"
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/link/nextPage
+   Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_linkString
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/link-string`
+
+Test case for using link as pagination with string nextLink.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/link-string
+   Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ],
+  "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/link-string/nextPage"
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/link-string/nextPage
+   Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_nestedLink
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/nested-link`
+
+Test case for using link as pagination with nested structure.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/nested-link
+   Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "1", "name": "dog" },
+      { "id": "2", "name": "cat" }
+    ]
+  },
+  "nestedNext": {
+    "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/nested-link/nextPage"
+  }
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/nested-link/nextPage
+   Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "3", "name": "bird" },
+      { "id": "4", "name": "fish" }
+    ]
+  }
+}
+```
+
+### Payload_Pageable_XmlPagination_listWithContinuation
+
+- Endpoint: `get /payload/pageable/xml/list-with-continuation`
+
+Test case for XML pagination with continuation token. Continuation token is passed in the request query and response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/xml/list
+
+Expected response body:
+
+```xml
+<PetListResult>
+  <Pets>
+    <Pet>
+      <Id>1</Id>
+      <Name>dog</Name>
+    </Pet>
+    <Pet>
+      <Id>2</Id>
+      <Name>cat</Name>
+    </Pet>
+  </Pets>
+  <NextMarker>page2</NextMarker>
+</PetListResult>
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/xml/list?marker=page2
+
+Expected response body:
+
+```xml
+<PetListResult>
+  <Pets>
+    <Pet>
+      <Id>3</Id>
+      <Name>bird</Name>
+    </Pet>
+    <Pet>
+      <Id>4</Id>
+      <Name>fish</Name>
+    </Pet>
+  </Pets>
+</PetListResult>
+```
+
+### Payload_Pageable_XmlPagination_listWithNextLink
+
+- Endpoint: `get /payload/pageable/xml/list-with-next-link`
+
+Test case for XML pagination with next link.
 
 Two requests need to be tested.
 
 1. Initial request:
-   Expected route: /payload/pageable/server-driven-pagination/link
-   Expected response body:
+   Expected route: /payload/pageable/xml/list-with-next-link
 
-```json
-{
-  "pets": [
-    { "id": "1", "name": "dog" },
-    { "id": "2", "name": "cat" }
-  ],
-  "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/link/nextPage"
-}
+Expected response body:
+
+```xml
+<PetListResult>
+  <Pets>
+    <Pet>
+      <Id>1</Id>
+      <Name>dog</Name>
+    </Pet>
+    <Pet>
+      <Id>2</Id>
+      <Name>cat</Name>
+    </Pet>
+  </Pets>
+  <NextLink>http://[host]:[port]/payload/pageable/xml/list-with-next-link/nextPage</NextLink>
+</PetListResult>
 ```
 
 2. Next page request:
-   Expected route: /payload/pageable/server-driven-pagination/link/nextPage
-   Expected response body:
+   Expected route: /payload/pageable/xml/list-with-next-link/nextPage
 
-```json
-{
-  "pets": [
-    { "id": "3", "name": "bird" },
-    { "id": "4", "name": "fish" }
-  ]
-}
+Expected response body:
+
+```xml
+<PetListResult>
+  <Pets>
+    <Pet>
+      <Id>3</Id>
+      <Name>bird</Name>
+    </Pet>
+    <Pet>
+      <Id>4</Id>
+      <Name>fish</Name>
+    </Pet>
+  </Pets>
+</PetListResult>
 ```
 
 ### Payload_Xml_ModelWithArrayOfModelValue_get
@@ -1762,6 +3061,32 @@ Expected request body:
 </ModelWithAttributes>
 ```
 
+### Payload_Xml_ModelWithDatetimeValue_get
+
+- Endpoint: `get /payload/xml/modelWithDatetime`
+
+Expected response body:
+
+```xml
+<ModelWithDatetime>
+  <rfc3339>2022-08-26T18:38:00.000Z</rfc3339>
+  <rfc7231>Fri, 26 Aug 2022 14:38:00 GMT</rfc7231>
+</ModelWithDatetime>
+```
+
+### Payload_Xml_ModelWithDatetimeValue_put
+
+- Endpoint: `put /payload/xml/modelWithDatetime`
+
+Expected request body:
+
+```xml
+<ModelWithDatetime>
+  <rfc3339>2022-08-26T18:38:00.000Z</rfc3339>
+  <rfc7231>Fri, 26 Aug 2022 14:38:00 GMT</rfc7231>
+</ModelWithDatetime>
+```
+
 ### Payload_Xml_ModelWithDictionaryValue_get
 
 - Endpoint: `get /payload/xml/modelWithDictionary`
@@ -1858,6 +3183,30 @@ Expected request body:
 </ModelWithEncodedNamesSrc>
 ```
 
+### Payload_Xml_ModelWithEnumValue_get
+
+- Endpoint: `get /payload/xml/modelWithEnum`
+
+Expected response body:
+
+```xml
+<ModelWithEnum>
+  <status>success</status>
+</ModelWithEnum>
+```
+
+### Payload_Xml_ModelWithEnumValue_put
+
+- Endpoint: `put /payload/xml/modelWithEnum`
+
+Expected request body:
+
+```xml
+<ModelWithEnum>
+  <status>success</status>
+</ModelWithEnum>
+```
+
 ### Payload_Xml_ModelWithOptionalFieldValue_get
 
 - Endpoint: `get /payload/xml/modelWithOptionalField`
@@ -2082,6 +3431,19 @@ Expected request body:
 </SimpleModel>
 ```
 
+### Payload_Xml_XmlErrorValue_get
+
+- Endpoint: `get /payload/xml/error`
+
+Expected error response body:
+
+```xml
+<XmlErrorBody>
+  <message>Something went wrong</message>
+  <code>400</code>
+</XmlErrorBody>
+```
+
 ### Response_StatusCodeRange_errorResponseStatusCode404
 
 - Endpoint: `get /response/status-code-range/error-response-status-code-404`
@@ -2200,7 +3562,7 @@ Expected path: /routes/path/label/standard/record.a,1,b,2
 
 Test matrix expansion with explode: true when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/path/matrix/explode/array;a.b
+Expected path: /routes/path/matrix/explode/array;param=a;param=b
 
 ### Routes_PathParameters_MatrixExpansion_Explode_primitive
 
@@ -2208,7 +3570,7 @@ Expected path: /routes/path/matrix/explode/array;a.b
 
 Test matrix expansion with explode: true when passed a primitive value.
 Param value: "a"
-Expected path: /routes/path/matrix/explode/primitive;a
+Expected path: /routes/path/matrix/explode/primitive;param=a
 
 ### Routes_PathParameters_MatrixExpansion_Explode_record
 
@@ -2224,7 +3586,7 @@ Expected path: /routes/path/matrix/explode/record;a=1;b=2
 
 Test matrix expansion with explode: false when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/path/matrix/standard/array;a,b
+Expected path: /routes/path/matrix/standard/array;param=a;param=b
 
 ### Routes_PathParameters_MatrixExpansion_Standard_primitive
 
@@ -2232,7 +3594,7 @@ Expected path: /routes/path/matrix/standard/array;a,b
 
 Test matrix expansion with explode: false when passed a primitive value.
 Param value: "a"
-Expected path: /routes/path/matrix/standard/primitive;a
+Expected path: /routes/path/matrix/standard/primitive;param=a
 
 ### Routes_PathParameters_MatrixExpansion_Standard_record
 
@@ -2240,7 +3602,7 @@ Expected path: /routes/path/matrix/standard/primitive;a
 
 Test matrix expansion with explode: false when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/path/matrix/standard/record;a,1,b,2
+Expected path: /routes/path/matrix/standard/record;a=1;b=2
 
 ### Routes_PathParameters_PathExpansion_Explode_array
 
@@ -2615,6 +3977,36 @@ Expected header parameters:
 
 Check we recognize Repeatability-Request-ID and Repeatability-First-Sent.
 
+### SpecialWords_ExtensibleStrings_putExtensibleStringValue
+
+- Endpoint: `put /special-words/extensible-strings/string`
+
+Verify that enum members with special word names can be sent and received properly.
+Send 'class' and expect the same value back.
+
+### SpecialWords_ModelProperties_dictMethods
+
+- Endpoint: `get /special-words/model-properties/dict-methods`
+
+Verify that model properties can use names that are Python dict methods. These names (keys, items, values, etc.) may conflict with Python's dict class methods.
+
+Send
+
+```json
+{
+  "keys": "ok",
+  "items": "ok",
+  "values": "ok",
+  "popitem": "ok",
+  "clear": "ok",
+  "update": "ok",
+  "setdefault": "ok",
+  "pop": "ok",
+  "get": "ok",
+  "copy": "ok"
+}
+```
+
 ### SpecialWords_ModelProperties_sameAsModel
 
 - Endpoint: `get /special-words/model-properties/same-as-model`
@@ -2627,6 +4019,18 @@ Send
 { "SameAsModel": "ok" }
 ```
 
+### SpecialWords_ModelProperties_withList
+
+- Endpoint: `get /special-words/model-properties/list`
+
+Verify that a property can be named "list", which is a reserved word in many languages like Python.
+
+Send
+
+```json
+{ "list": "ok" }
+```
+
 ### SpecialWords_Models_and
 
 - Endpoint: `get /special-words/models/and`
@@ -3359,6 +4763,18 @@ Verify that the name "with" works. Send this parameter to pass with value `ok`.
 
 Verify that the name "yield" works. Send this parameter to pass with value `ok`.
 
+### Streaming_Jsonl_Basic_receive
+
+- Endpoint: `get /streaming/jsonl/basic/receive`
+
+Basic jsonl streaming for response.
+
+### Streaming_Jsonl_Basic_send
+
+- Endpoint: `post /streaming/jsonl/basic/send`
+
+Basic jsonl streaming for request.
+
 ### Type_Array_BooleanValue_get
 
 - Endpoint: `get /type/array/boolean`
@@ -3913,6 +5329,90 @@ Expect to send a known value. Mock api expect to receive 'Monday'
 
 Expect to handle an unknown value. Mock api expect to receive 'Weekend'
 
+### Type_File_Body_downloadFileDefaultContentType
+
+- Endpoint: `get /type/file/body/response/default-content-type`
+
+Test File type as response body with unspecified content type.
+The File type accepts any content type. For testing, server will return image/png.
+Expected response:
+
+- Content-Type header: image/png
+- Body: binary content matching packages/http-specs/assets/image.png
+
+### Type_File_Body_downloadFileJsonContentType
+
+- Endpoint: `get /type/file/body/response/json-content-type`
+
+Test File type as response body with JSON content type.
+Expected response:
+
+- Content-Type header: application/json
+- Body: JSON content with file data
+
+### Type_File_Body_downloadFileMultipleContentTypes
+
+- Endpoint: `get /type/file/body/response/multiple-content-types`
+
+Test File type as response body with multiple allowed content types.
+Service will return image/png.
+Expected response:
+
+- Content-Type header: image/png
+- Body: binary content matching packages/http-specs/assets/image.png
+
+### Type_File_Body_downloadFileSpecificContentType
+
+- Endpoint: `get /type/file/body/response/specific-content-type`
+
+Test File type as response body with specific content type.
+Expected response:
+
+- Content-Type header: image/png
+- Body: binary content matching packages/http-specs/assets/image.png
+
+### Type_File_Body_uploadFileDefaultContentType
+
+- Endpoint: `post /type/file/body/request/default-content-type`
+
+Test File type as request body with unspecified content type.
+The File type accepts any content type. For testing, sender will use image/png.
+Expected request:
+
+- Content-Type header: image/png
+- Body: binary content matching packages/http-specs/assets/image.png
+
+### Type_File_Body_uploadFileJsonContentType
+
+- Endpoint: `post /type/file/body/request/json-content-type`
+
+Test File type as request body with JSON content type.
+Expected request:
+
+- Content-Type header: application/json
+- Body: JSON content with file data
+
+### Type_File_Body_uploadFileMultipleContentTypes
+
+- Endpoint: `post /type/file/body/request/multiple-content-types`
+
+Test File type as request body with multiple allowed content types (image/png or image/jpeg).
+Client should send image/png.
+Expected request:
+
+- Content-Type header: image/png
+- Body: binary content matching packages/http-specs/assets/image.png
+
+### Type_File_Body_uploadFileSpecificContentType
+
+- Endpoint: `post /type/file/body/request/specific-content-type`
+
+Test File type as request body with specific content type.
+Expected request:
+
+- Content-Type header: image/png
+- Body: binary content matching packages/http-specs/assets/image.png
+
 ### Type_Model_Empty_getEmpty
 
 - Endpoint: `get /type/model/empty/alone`
@@ -4428,13 +5928,7 @@ Expected input body:
 - Endpoint: `get /type/model/visibility`
 
 Generate and receive output model with readonly properties.
-Expected input body:
-
-```json
-{
-  "queryProp": 123
-}
-```
+Expected no body with `?queryProp=123`.
 
 Expected response body:
 
@@ -4449,13 +5943,7 @@ Expected response body:
 - Endpoint: `head /type/model/visibility`
 
 Generate abd send put model with write/create properties.
-Expected input body:
-
-```json
-{
-  "queryProp": 123
-}
-```
+Expected no body with `?queryProp=123`.
 
 ### Type_Model_Visibility_patchModel
 
@@ -5152,42 +6640,6 @@ Expected input body:
 }
 ```
 
-### Type_Property_AdditionalProperties_SpreadRecordDiscriminatedUnion_get
-
-- Endpoint: `get /type/property/additionalProperties/spreadRecordDiscriminatedUnion`
-
-Expected response body:
-
-```json
-{
-  "name": "abc",
-  "prop1": { "kind": "kind0", "fooProp": "abc" },
-  "prop2": {
-    "kind": "kind1",
-    "start": "2021-01-01T00:00:00Z",
-    "end": "2021-01-02T00:00:00Z"
-  }
-}
-```
-
-### Type_Property_AdditionalProperties_SpreadRecordDiscriminatedUnion_put
-
-- Endpoint: `put /type/property/additionalProperties/spreadRecordDiscriminatedUnion`
-
-Expected input body:
-
-```json
-{
-  "name": "abc",
-  "prop1": { "kind": "kind0", "fooProp": "abc" },
-  "prop2": {
-    "kind": "kind1",
-    "start": "2021-01-01T00:00:00Z",
-    "end": "2021-01-02T00:00:00Z"
-  }
-}
-```
-
 ### Type_Property_AdditionalProperties_SpreadRecordNonDiscriminatedUnion_get
 
 - Endpoint: `get /type/property/additionalProperties/spreadRecordNonDiscriminatedUnion`
@@ -6950,6 +8402,178 @@ Expect to handle a unknown type value. Mock api will return 'test'
 
 Expect to send a string value. Mock api expect to receive 'test'
 
+### Type_Union_Discriminated_Envelope_Object_CustomProperties_get
+
+- Endpoint: `get /type/union/discriminated/envelope/object/custom-properties`
+
+Test discriminated union with custom property names.
+When value of query parameter "petType" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "petType": "cat",
+  "petData": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "petType": "dog",
+  "petData": {
+    "name": "Rex",
+    "bark": false
+  }
+}
+```
+
+### Type_Union_Discriminated_Envelope_Object_CustomProperties_put
+
+- Endpoint: `put /type/union/discriminated/envelope/object/custom-properties`
+
+Test discriminated union with custom property names.
+Send the union as:
+
+```json
+{
+  "petType": "cat",
+  "petData": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+### Type_Union_Discriminated_Envelope_Object_Default_get
+
+- Endpoint: `get /type/union/discriminated/envelope/object/default`
+
+Test discriminated union with envelope serialization.
+When value of query parameter "kind" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "kind": "cat",
+  "value": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "kind": "dog",
+  "value": {
+    "name": "Rex",
+    "bark": false
+  }
+}
+```
+
+### Type_Union_Discriminated_Envelope_Object_Default_put
+
+- Endpoint: `put /type/union/discriminated/envelope/object/default`
+
+Test discriminated union with envelope serialization.
+Send the union as:
+
+```json
+{
+  "kind": "cat",
+  "value": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_CustomDiscriminator_get
+
+- Endpoint: `get /type/union/discriminated/no-envelope/custom-discriminator`
+
+Test discriminated union with inline discriminator and custom discriminator property name.
+When value of query parameter "type" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "type": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "type": "dog",
+  "name": "Rex",
+  "bark": false
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_CustomDiscriminator_put
+
+- Endpoint: `put /type/union/discriminated/no-envelope/custom-discriminator`
+
+Test discriminated union with inline discriminator and custom discriminator property name.
+Send the union as:
+
+```json
+{
+  "type": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_Default_get
+
+- Endpoint: `get /type/union/discriminated/no-envelope/default`
+
+Test discriminated union with inline discriminator.
+When value of query parameter "kind" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "kind": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "kind": "dog",
+  "name": "Rex",
+  "bark": false
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_Default_put
+
+- Endpoint: `put /type/union/discriminated/no-envelope/default`
+
+Test discriminated union with inline discriminator.
+Send the union as:
+
+```json
+{
+  "kind": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
 ### Type_Union_EnumsOnly_get
 
 - Endpoint: `get /type/union/enums-only`
@@ -7401,7 +9025,7 @@ Expected request body:
 
 - Endpoint: `post /versioning/removed/api-version:{version}/v3`
 
-path: "/versioning/removed/api-version[:]v1/v3"
+path: "/versioning/removed/api-version:v1/v3"
 Expected request body:
 
 ```json
@@ -7414,7 +9038,7 @@ Expected response body:
 { "id": "123", "enumProp": "enumMemberV1" }
 ```
 
-path: "/versioning/removed/api-version[:]v2preview/v3"
+path: "/versioning/removed/api-version:v2preview/v3"
 Expected request body:
 
 ```json
@@ -7427,7 +9051,7 @@ Expected response body:
 { "id": "123" }
 ```
 
-path: "/versioning/removed/api-version[:]v2/v3"
+path: "/versioning/removed/api-version:v2/v3"
 Expected request body:
 
 ```json