|
| 1 | +@endpoint(bits-ai) @endpoint(bits-ai-v2) |
| 2 | +Feature: Bits AI |
| 3 | + Use the Bits AI endpoints to retrieve AI-powered investigations. |
| 4 | + |
| 5 | + Background: |
| 6 | + Given a valid "apiKeyAuth" key in the system |
| 7 | + And a valid "appKeyAuth" key in the system |
| 8 | + And an instance of "BitsAI" API |
| 9 | + |
| 10 | + @generated @skip @team:DataDog/bits-ai |
| 11 | + Scenario: Get a Bits AI investigation returns "Bad Request" response |
| 12 | + Given operation "GetInvestigation" enabled |
| 13 | + And new "GetInvestigation" request |
| 14 | + And request contains "id" parameter from "REPLACE.ME" |
| 15 | + When the request is sent |
| 16 | + Then the response status is 400 Bad Request |
| 17 | + |
| 18 | + @generated @skip @team:DataDog/bits-ai |
| 19 | + Scenario: Get a Bits AI investigation returns "Not Found" response |
| 20 | + Given operation "GetInvestigation" enabled |
| 21 | + And new "GetInvestigation" request |
| 22 | + And request contains "id" parameter from "REPLACE.ME" |
| 23 | + When the request is sent |
| 24 | + Then the response status is 404 Not Found |
| 25 | + |
| 26 | + @generated @skip @team:DataDog/bits-ai |
| 27 | + Scenario: Get a Bits AI investigation returns "OK" response |
| 28 | + Given operation "GetInvestigation" enabled |
| 29 | + And new "GetInvestigation" request |
| 30 | + And request contains "id" parameter from "REPLACE.ME" |
| 31 | + When the request is sent |
| 32 | + Then the response status is 200 OK |
| 33 | + |
| 34 | + @generated @skip @team:DataDog/bits-ai |
| 35 | + Scenario: List Bits AI investigations returns "Bad Request" response |
| 36 | + Given operation "ListInvestigations" enabled |
| 37 | + And new "ListInvestigations" request |
| 38 | + When the request is sent |
| 39 | + Then the response status is 400 Bad Request |
| 40 | + |
| 41 | + @generated @skip @team:DataDog/bits-ai |
| 42 | + Scenario: List Bits AI investigations returns "OK" response |
| 43 | + Given operation "ListInvestigations" enabled |
| 44 | + And new "ListInvestigations" request |
| 45 | + When the request is sent |
| 46 | + Then the response status is 200 OK |
| 47 | + |
| 48 | + @generated @skip @team:DataDog/bits-ai @with-pagination |
| 49 | + Scenario: List Bits AI investigations returns "OK" response with pagination |
| 50 | + Given operation "ListInvestigations" enabled |
| 51 | + And new "ListInvestigations" request |
| 52 | + When the request with pagination is sent |
| 53 | + Then the response status is 200 OK |
| 54 | + |
| 55 | + @generated @skip @team:DataDog/bits-ai |
| 56 | + Scenario: Trigger a Bits AI investigation returns "Bad Request" response |
| 57 | + Given operation "TriggerInvestigation" enabled |
| 58 | + And new "TriggerInvestigation" request |
| 59 | + And body with value {"data": {"attributes": {"trigger": {"monitor_alert_trigger": {"event_id": "1234567890123456789", "event_ts": 1700000000000, "monitor_id": 12345678}, "type": "monitor_alert_trigger"}}, "type": "trigger_investigation_request"}} |
| 60 | + When the request is sent |
| 61 | + Then the response status is 400 Bad Request |
| 62 | + |
| 63 | + @generated @skip @team:DataDog/bits-ai |
| 64 | + Scenario: Trigger a Bits AI investigation returns "OK" response |
| 65 | + Given operation "TriggerInvestigation" enabled |
| 66 | + And new "TriggerInvestigation" request |
| 67 | + And body with value {"data": {"attributes": {"trigger": {"monitor_alert_trigger": {"event_id": "1234567890123456789", "event_ts": 1700000000000, "monitor_id": 12345678}, "type": "monitor_alert_trigger"}}, "type": "trigger_investigation_request"}} |
| 68 | + When the request is sent |
| 69 | + Then the response status is 200 OK |
0 commit comments