chrome-devtools-mcp/tests/tools/console.test.js.snapshot at e1d9d7b8050a96ab6fb145ecf986d99ffadf14b8 · ChromeDevTools/chrome-devtools-mcp · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
exports[`console > get_console_message > applies source maps to stack traces of Error object (with cause) console.log arguments 1`] = `
# test response
ID: 1
Message: log> foo failed Error: bar failed
### Arguments
Arg #0: foo failed
Arg #1: Error: bar failed
at foo (main.js:10:11)
at Iife (main.js:16:5)
at <anonymous> (main.js:14:1)
Caused by: Error: b00m!
at bar (main.js:3:9)
at foo (main.js:8:5)
at Iife (main.js:16:5)
at <anonymous> (main.js:14:1)
Note: line and column numbers use 1-based indexing
### Stack trace
at Iife (main.js:18:13)
at <anonymous> (main.js:14:1)
Note: line and column numbers use 1-based indexing
`;

exports[`console > get_console_message > applies source maps to stack traces of Error object console.log arguments 1`] = `
# test response
ID: 1
Message: log> An error happened: Error: b00m!
### Arguments
Arg #0: An error happened:
Arg #1: Error: b00m!
at bar (main.js:3:9)
at foo (main.js:7:3)
at Iife (main.js:12:5)
at <anonymous> (main.js:10:1)
Note: line and column numbers use 1-based indexing
### Stack trace
at Iife (main.js:14:13)
at <anonymous> (main.js:10:1)
Note: line and column numbers use 1-based indexing
`;

exports[`console > get_console_message > applies source maps to stack traces of console messages 1`] = `
# test response
ID: 1
Message: warn> hello world
### Arguments
Arg #0: hello world
### Stack trace
at bar (main.js:3:11)
at foo (main.js:7:3)
at Iife (main.js:11:3)
at <anonymous> (main.js:10:1)
Note: line and column numbers use 1-based indexing
`;

exports[`console > get_console_message > applies source maps to stack traces of uncaught exceptions 1`] = `
# test response
ID: 1
Message: error> Uncaught Error: b00m!
### Stack trace
at bar (main.js:3:9)
at foo (main.js:7:3)
at Iife (main.js:11:3)
at <anonymous> (main.js:10:1)
Note: line and column numbers use 1-based indexing
`;

exports[`console > get_console_message > applies source maps to stack traces of uncaught exceptions with cause 1`] = `
# test response
ID: 1
Message: error> Uncaught Error: foo failed
### Stack trace
at Iife (main.js:18:11)
at <anonymous> (main.js:14:1)
Caused by: Error: bar failed
at foo (main.js:10:11)
at Iife (main.js:16:5)
at <anonymous> (main.js:14:1)
Caused by: Error: b00m!
at bar (main.js:3:9)
at foo (main.js:8:5)
at Iife (main.js:16:5)
at <anonymous> (main.js:14:1)
Note: line and column numbers use 1-based indexing
`;

exports[`console > get_console_message > ignores frames from ignore listed URLs 1`] = `
# test response
ID: 1
Message: log> hello from callback
### Arguments
Arg #0: hello from callback
### Stack trace
at callback ('main.js':3:21)
at callIt ('main.js':7:13)
at  ('main.js':8:13)
Note: line and column numbers use 1-based indexing
`;

exports[`console > get_console_message > issues type > gets issue details with node id parsing 1`] = `
# test response
ID: 1
Message: issue> An element doesn't have an autocomplete attribute

A form field has an \`id\` or \`name\` attribute that the browser's autofill recognizes. However, it doesn't have an \`autocomplete\` attribute assigned. This might prevent the browser from correctly autofilling the form.

To fix this issue, provide an \`autocomplete\` attribute.
Learn more:
[HTML attribute: autocomplete](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete#values)
### Affected resources
uid=1_1 data={"violatingNodeAttribute":"name"}
`;

exports[`console > get_console_message > issues type > gets issue details with request id parsing 1`] = `
# test response
ID: <ID>
Message: issue> Ensure CORS response header values are valid

A cross-origin resource sharing (CORS) request was blocked because of invalid or missing response headers of the request or the associated [preflight request](issueCorsPreflightRequest).

To fix this issue, ensure the response to the CORS request and/or the associated [preflight request](issueCorsPreflightRequest) are not missing headers and use valid header values.

Note that if an opaque response is sufficient, the request's mode can be set to \`no-cors\` to fetch the resource with CORS disabled; that way CORS headers are not required but the response content is inaccessible (opaque).
Learn more:
[Cross-Origin Resource Sharing (\`CORS\`)](https://web.dev/cross-origin-resource-sharing)
### Affected resources
reqid=<reqid> data={"corsErrorStatus":{"corsError":"PreflightMissingAllowOriginHeader","failedParameter":""},"isWarning":false,"request":{"url":"http://hostname:port/data.json"},"initiatorOrigin":"","clientSecurityState":{"initiatorIsSecureContext":false,"initiatorIPAddressSpace":"Loopback","privateNetworkRequestPolicy":"BlockFromInsecureToMorePrivate"}}
`;

exports[`console > list_console_messages > lists error objects 1`] = `
# test response
## Console messages
Showing 1-1 of 1 (Page 1 of 1).
msgid=1 [error] Error: This is an error (1 args)
`;