addedInput schema / properties / bddScenarios
Added value: +{
+ "description": "Content for the BDD template. Gherkin source for the BDD template - feature/scenario lines as plain text, exactly as a .feature file would carry them. Always plain gherkin regardless of 'format', and it is not parsed or validated, so malformed gherkin is stored as sent. A top-level `Feature:` line is optional - scenarios on their own are fine. A `# language:` directive is honored; otherwise the dialect is detected from the keywords.",
+ "maxLength": 32000,
+ "type": "string"
+}
addedInput schema / properties / customFields / description
Added value: +"Custom field values to set, keyed by the 'propName' that listProjects reports for the project - custom fields carry a 'cf__' prefix, built-in ones do not. A bare name or a single-underscore 'cf_' prefix is accepted too, but a key that is itself a propName always means that field."
changedInput schema / properties / folder / description
Previous value: -"The test case folder title or key or ID. If multiple folders match, the first one is used. If omitted, the test case is created in the root folder."New value: +"The test case folder title or key or ID. If multiple folders match, the first one is used. If omitted, the test case is created in no folder - use 'moveTestCases' with targetFolderId=0 to put it back there later."
addedInput schema / properties / format
Added value: +{
+ "description": "Format for rich-text fields (descriptions, preconditions, comments, step & result cells, stepsText & expectedResultText) on both input and output: 'markdown' (default) or 'xml'. Read the matching rich-text format reference resource before producing either. Use 'xml' for BOTH the read and the write whenever you are changing a field that already has content: markdown cannot carry an underline or a text color, so an edit written as markdown writes those away. 'markdown' is for writing new content and for reading you will not edit.",
+ "enum": [
+ "markdown",
+ "xml"
+ ],
+ "type": "string"
+}
changedInput schema / properties / precondition / description
Previous value: -"An optional precondition for the test case - can include simple markdown"New value: +"An optional precondition for the test case - rich text in the chosen 'format'"
changedInput schema / properties / precondition / maxLength
Previous value: -8000New value: +16000
changedInput schema / properties / steps / description
Previous value: -"A record of custom field values to set on the test case, the properties must match existing custom field names in the project. "New value: +"The STEPS-template steps (interleaved action + expected result per step). Use this OR the TEXT 'text' content, not both. Omit if the test case has no steps."
changedInput schema / properties / steps / items / properties / expectedResult / description
Previous value: -"The expected result for this step - can include simple markdown"New value: +"The expected result for this step - rich text in the chosen 'format'"
changedInput schema / properties / steps / items / properties / expectedResult / maxLength
Previous value: -8000New value: +16000
changedInput schema / properties / steps / items / properties / step / description
Previous value: -"A single step in the test case - can include simple markdown"New value: +"A single step in the test case - rich text in the chosen 'format'"
changedInput schema / properties / steps / items / properties / step / maxLength
Previous value: -8000New value: +16000
addedInput schema / properties / template
Added value: +{
+ "description": "Which content template to display: \"STEPS\" for interleaved action/expected-result steps, \"TEXT\" for free-form actions and expected-result documents, \"BDD\" for gherkin scenarios. Defaults to STEPS, or to the template of whichever single content field is provided. Provide content for the chosen template only - content another template would display is rejected, not stored invisibly.",
+ "enum": [
+ "TEXT",
+ "STEPS",
+ "BDD"
+ ],
+ "type": "string"
+}
addedInput schema / properties / text
Added value: +{
+ "description": "Content for the TEXT template, as two free-form documents. A test case normally uses EITHER the top-level STEPS 'steps' array OR this TEXT content, not both; the 'template' field decides which is shown.",
+ "properties": {
+ "expectedResultText": {
+ "description": "The TEXT-template expected-result document - one free-form rich-text document",
+ "maxLength": 32000,
+ "type": "string"
+ },
+ "stepsText": {
+ "description": "The TEXT-template steps/actions document - one free-form rich-text document, unrelated to the top-level 'steps' array",
+ "maxLength": 32000,
+ "type": "string"
+ }
+ },
+ "type": "object"
+}
addedOutput schema / properties / _etag
Added value: +{
+ "description": "Conflict tag of the entity - pass it to an edit tool's '_etag' to have that edit rejected if somebody changed the entity in the meantime. Empty for an entity that carries no tag yet.",
+ "type": "string"
+}