Skip to content

Commit 8d77e2d

Browse files
committed
updated oracle descriptions
1 parent b83a587 commit 8d77e2d

1 file changed

Lines changed: 22 additions & 13 deletions

File tree

core/src/main/kotlin/org/evomaster/core/problem/enterprise/ExperimentalFaultCategory.kt

Lines changed: 22 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -11,29 +11,38 @@ enum class ExperimentalFaultCategory(
1111

1212
//9xx for experimental, work-in-progress oracles
1313

14-
14+
/*
15+
TODO Is this one still relevant? or subsumed by SCHEMA_INVALID_RESPONSE?
16+
old comment was:
17+
syntactically invalid response (eg, non-quoted text when expecting JSON. this happens in pet-clinic for example)
18+
*/
1519
HTTP_INVALID_PAYLOAD_SYNTAX(911, "Invalid Payload Syntax", "rejectedWithInvalidPayloadSyntax",
1620
"TODO"),
21+
22+
1723
HTTP_INVALID_LOCATION(912, "Invalid Location HTTP Header", "returnsInvalidLocationHeader",
1824
"TODO"),
19-
HTTP_NONWORKING_DELETE(913,"DELETE Method Does Not Work", "deleteDoesNotWork",
25+
HTTP_NONWORKING_DELETE(913,"Resource Still Accessible After Successful DELETE", "deleteDoesNotWork",
26+
"If a resource is deleted, and the API responds that such request was successful, then such" +
27+
" resource should no longer being available." +
28+
" New requests to access it should fail." +
29+
" Otherwise, if it is still possible to access the resource, then it was not really deleted." +
30+
" Then, as such, it means that the delete operation is faulty."),
31+
HTTP_REPEATED_CREATE_PUT(914, "Repeated PUT Creates Resource With 201 Instead of Updating", "repeatedCreatePut",
2032
"TODO"),
21-
HTTP_REPEATED_CREATE_PUT(914, "Repeated PUT Creates Resource With 201", "repeatedCreatePut",
33+
HTTP_SIDE_EFFECTS_FAILED_MODIFICATION(915, "A Failed PUT or PATCH Must Not Change The Resource", "sideEffectsFailedModification",
2234
"TODO"),
23-
HTTP_SIDE_EFFECTS_FAILED_MODIFICATION(915, "A failed PUT or PATCH must not change the resource", "sideEffectsFailedModification",
35+
HTTP_PARTIAL_UPDATE_PUT(916, "The Verb PUT Must Make a Full Replacement", "partialUpdatePut",
2436
"TODO"),
25-
HTTP_PARTIAL_UPDATE_PUT(916, "The verb PUT makes a full replacement", "partialUpdatePut",
37+
HTTP_MISLEADING_CREATE_PUT(917, "If a PUT Creates a Resource, It Must Return 201", "misleadingCreatePut",
2638
"TODO"),
27-
HTTP_MISLEADING_CREATE_PUT(917, "PUT if creating, must get 201", "misleadingCreatePut",
28-
"TODO"),
29-
30-
HTTP_NON_IDEMPOTENT_PUT(918, "PUT is idempotent", "nonIdempotentPut",
39+
HTTP_NON_IDEMPOTENT_PUT(918, "PUT Implementation Must be Idempotent", "nonIdempotentPut",
3140
"TODO"),
32-
HTTP_INVALID_ALLOW(919, "Invalid allow", "invalidAllow",
41+
HTTP_INVALID_ALLOW(919, "Invalid Allow HTTP Header", "invalidAllow",
3342
"TODO"),
34-
HTTP_TIMEOUT(921, "Timeout", "timeout", "TODO"),
35-
HTTP_INVALID_MERGE_PATCH(922, "JSON Merge Patch changes untouched fields", "invalidMergePatch",
43+
HTTP_INVALID_MERGE_PATCH(920, "Invalid JSON Merge Patch", "invalidMergePatch",
3644
"TODO"),
45+
HTTP_TIMEOUT(921, "Request Timeout", "requestTimeout", "TODO"),
3746

3847
HTTP_STATUS_NO_NON_STANDARD_CODES(950, "HTTP/REST-Design Violation: no-non-standard-codes", "invalidStatusCode", "TODO"),
3948
HTTP_STATUS_NO_201_IF_DELETE(951, "HTTP/REST-Design Violation: no-201-if-delete", "201OnDelete", "TODO"),
@@ -53,7 +62,7 @@ enum class ExperimentalFaultCategory(
5362
HTTP_STATUS_NO_426_IF_NO_UPGRADE(965,"HTTP/REST-Design Violation: no-426-if-no-upgrade","426MissingUpgrade", "TODO"),
5463

5564
//3xx: GraphQL
56-
GQL_ERROR_FIELD(920, "Error Field", "returnedErrors",
65+
GQL_ERROR_FIELD(930, "Error Field", "returnedErrors",
5766
"TODO"),
5867

5968
//4xx: RPC

0 commit comments

Comments
 (0)