|
| 1 | +@endpoint(rum-replay-analysis) @endpoint(rum-replay-analysis-v2) |
| 2 | +Feature: Rum Replay Analysis |
| 3 | + Analyze RUM replay sessions to identify and investigate user-facing |
| 4 | + issues. Retrieve issues detected by AI analysis, get details for |
| 5 | + individual issues, and explore the sessions associated with each issue. |
| 6 | + |
| 7 | + Background: |
| 8 | + Given a valid "apiKeyAuth" key in the system |
| 9 | + And a valid "appKeyAuth" key in the system |
| 10 | + And an instance of "RumReplayAnalysis" API |
| 11 | + |
| 12 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 13 | + Scenario: Get replay analysis issue returns "Bad Request" response |
| 14 | + Given operation "GetReplayAnalysisIssue" enabled |
| 15 | + And new "GetReplayAnalysisIssue" request |
| 16 | + And request contains "issue_id" parameter from "REPLACE.ME" |
| 17 | + When the request is sent |
| 18 | + Then the response status is 400 Bad Request |
| 19 | + |
| 20 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 21 | + Scenario: Get replay analysis issue returns "Not Found" response |
| 22 | + Given operation "GetReplayAnalysisIssue" enabled |
| 23 | + And new "GetReplayAnalysisIssue" request |
| 24 | + And request contains "issue_id" parameter from "REPLACE.ME" |
| 25 | + When the request is sent |
| 26 | + Then the response status is 404 Not Found |
| 27 | + |
| 28 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 29 | + Scenario: Get replay analysis issue returns "OK" response |
| 30 | + Given operation "GetReplayAnalysisIssue" enabled |
| 31 | + And new "GetReplayAnalysisIssue" request |
| 32 | + And request contains "issue_id" parameter from "REPLACE.ME" |
| 33 | + When the request is sent |
| 34 | + Then the response status is 200 OK |
| 35 | + |
| 36 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 37 | + Scenario: List replay analysis issue sessions returns "Bad Request" response |
| 38 | + Given operation "ListReplayAnalysisIssueSessions" enabled |
| 39 | + And new "ListReplayAnalysisIssueSessions" request |
| 40 | + And request contains "issue_id" parameter from "REPLACE.ME" |
| 41 | + When the request is sent |
| 42 | + Then the response status is 400 Bad Request |
| 43 | + |
| 44 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 45 | + Scenario: List replay analysis issue sessions returns "Not Found" response |
| 46 | + Given operation "ListReplayAnalysisIssueSessions" enabled |
| 47 | + And new "ListReplayAnalysisIssueSessions" request |
| 48 | + And request contains "issue_id" parameter from "REPLACE.ME" |
| 49 | + When the request is sent |
| 50 | + Then the response status is 404 Not Found |
| 51 | + |
| 52 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 53 | + Scenario: List replay analysis issue sessions returns "OK" response |
| 54 | + Given operation "ListReplayAnalysisIssueSessions" enabled |
| 55 | + And new "ListReplayAnalysisIssueSessions" request |
| 56 | + And request contains "issue_id" parameter from "REPLACE.ME" |
| 57 | + When the request is sent |
| 58 | + Then the response status is 200 OK |
| 59 | + |
| 60 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 61 | + Scenario: List replay analysis issues returns "Bad Request" response |
| 62 | + Given operation "ListReplayAnalysisIssues" enabled |
| 63 | + And new "ListReplayAnalysisIssues" request |
| 64 | + When the request is sent |
| 65 | + Then the response status is 400 Bad Request |
| 66 | + |
| 67 | + @generated @skip @team:DataDog/product-analytics-backend @team:DataDog/rum-backend @team:DataDog/session-replay-backend |
| 68 | + Scenario: List replay analysis issues returns "OK" response |
| 69 | + Given operation "ListReplayAnalysisIssues" enabled |
| 70 | + And new "ListReplayAnalysisIssues" request |
| 71 | + When the request is sent |
| 72 | + Then the response status is 200 OK |
0 commit comments