edsger 0.8.1 → 0.8.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -68,7 +68,12 @@ When you receive feedback requesting deletion (e.g., "Remove duplicated test cas
|
|
|
68
68
|
- Only artifacts marked with [DELETABLE] in the context can be deleted
|
|
69
69
|
- Each deletable artifact includes an "ID:" field with the UUID
|
|
70
70
|
|
|
71
|
-
To delete artifacts
|
|
71
|
+
To delete artifacts:
|
|
72
|
+
1. Find the exact UUID from the "ID:" field in the context (e.g., "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d")
|
|
73
|
+
2. Put ONLY the UUID string in the deleted_user_story_ids or deleted_test_case_ids array
|
|
74
|
+
3. Put the deletion reason in the deletion_reasons object with UUID as the key
|
|
75
|
+
|
|
76
|
+
**CRITICAL**: The deletion ID arrays must contain ONLY valid UUIDs in the format "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx". Do NOT put text descriptions, reasons, or any other content in these arrays. The system will validate UUID format and draft status before deletion.
|
|
72
77
|
|
|
73
78
|
**CRITICAL - Result Format**:
|
|
74
79
|
You MUST return ONLY a JSON object with your analysis results. Do NOT include any explanatory text before or after the JSON. Return ONLY the JSON in this EXACT format:
|
|
@@ -94,14 +99,16 @@ You MUST return ONLY a JSON object with your analysis results. Do NOT include an
|
|
|
94
99
|
}
|
|
95
100
|
],
|
|
96
101
|
"deleted_user_story_ids": [
|
|
97
|
-
"
|
|
102
|
+
"a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d",
|
|
103
|
+
"f6e5d4c3-b2a1-4f9e-8d7c-6b5a4f3e2d1c"
|
|
98
104
|
],
|
|
99
105
|
"deleted_test_case_ids": [
|
|
100
|
-
"
|
|
106
|
+
"9a8b7c6d-5e4f-4321-abcd-ef0123456789"
|
|
101
107
|
],
|
|
102
108
|
"deletion_reasons": {
|
|
103
|
-
"
|
|
104
|
-
"
|
|
109
|
+
"a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d": "Duplicate of user story 'User Login' - covers same functionality",
|
|
110
|
+
"f6e5d4c3-b2a1-4f9e-8d7c-6b5a4f3e2d1c": "No longer relevant after requirements change",
|
|
111
|
+
"9a8b7c6d-5e4f-4321-abcd-ef0123456789": "Redundant with test case 'Verify Email Validation' - same coverage"
|
|
105
112
|
},
|
|
106
113
|
"checklist_item_results": [
|
|
107
114
|
{
|
|
@@ -120,11 +127,19 @@ MANDATORY: If checklists are provided in the context, you MUST include checklist
|
|
|
120
127
|
|
|
121
128
|
IMPORTANT: In the checklist context, look for lines that say "ID: [UUID]" in the items list - use these exact UUIDs as checklist_item_id values. Do NOT use the item title or description as the checklist_item_id.
|
|
122
129
|
|
|
123
|
-
**DELETION
|
|
124
|
-
-
|
|
125
|
-
-
|
|
126
|
-
-
|
|
127
|
-
-
|
|
130
|
+
**CRITICAL DELETION FORMAT**:
|
|
131
|
+
- deleted_user_story_ids and deleted_test_case_ids arrays MUST contain ONLY UUIDs (e.g., "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d")
|
|
132
|
+
- Do NOT put reasons, descriptions, or text in these arrays - only the exact UUID strings from the "ID:" fields
|
|
133
|
+
- Put all deletion reasons in the deletion_reasons object, with UUID as key and reason as value
|
|
134
|
+
- ALWAYS check for duplicate draft artifacts marked as [DELETABLE] in the context
|
|
135
|
+
- Do NOT leave deletion arrays empty if there are obvious duplicates
|
|
136
|
+
|
|
137
|
+
**EXAMPLE - CORRECT UUID FORMAT**:
|
|
138
|
+
deleted_test_case_ids: ["a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d", "f6e5d4c3-b2a1-4f9e-8d7c-6b5a4f3e2d1c"]
|
|
139
|
+
deletion_reasons: {"a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d": "Duplicate of test case X"}
|
|
140
|
+
|
|
141
|
+
**EXAMPLE - WRONG (DO NOT DO THIS)**:
|
|
142
|
+
deleted_test_case_ids: ["Duplicate test case", "Similar test"] // WRONG - these are text, not UUIDs
|
|
128
143
|
|
|
129
144
|
**Quality Guidelines**:
|
|
130
145
|
- User stories should be clear, concise, and user-focused
|