playwright/docs/src/test-api/class-testerror.md

# class: TestError
* langs: js

Information about an error thrown during test execution.

## property: TestError.message
- type: ?<[string]>

Error message. Set when [Error] (or its subclass) has been thrown.

## property: TestError.stack
- type: ?<[string]>

Error stack. Set when [Error] (or its subclass) has been thrown.

## property: TestError.value
- type: ?<[string]>

The value that was thrown. Set when anything except the [Error] (or its subclass) has been thrown.
docs(test runner): api reference for reporter api (#7811) 2021-07-22 19:56:36 -07:00			`# class: TestError`
			`* langs: js`

			`Information about an error thrown during test execution.`

			`## property: TestError.message`
docs: mark optional properties/arguments explicitly with "?" (#13369) Previously, we were guessing whether something is optional from the comment (looking for stuff like "defaults to" or "optional"). To remove this error-prone technique, every optional property or argument (but not option) is explicitly marked with "?". 2022-04-06 19:02:10 -07:00			`- type: ?<[string]>`
docs(test runner): api reference for reporter api (#7811) 2021-07-22 19:56:36 -07:00
docs: mark optional properties/arguments explicitly with "?" (#13369) Previously, we were guessing whether something is optional from the comment (looking for stuff like "defaults to" or "optional"). To remove this error-prone technique, every optional property or argument (but not option) is explicitly marked with "?". 2022-04-06 19:02:10 -07:00			`Error message. Set when [Error] (or its subclass) has been thrown.`
docs(test runner): api reference for reporter api (#7811) 2021-07-22 19:56:36 -07:00
			`## property: TestError.stack`
docs: mark optional properties/arguments explicitly with "?" (#13369) Previously, we were guessing whether something is optional from the comment (looking for stuff like "defaults to" or "optional"). To remove this error-prone technique, every optional property or argument (but not option) is explicitly marked with "?". 2022-04-06 19:02:10 -07:00			`- type: ?<[string]>`
docs(test runner): api reference for reporter api (#7811) 2021-07-22 19:56:36 -07:00
docs: mark optional properties/arguments explicitly with "?" (#13369) Previously, we were guessing whether something is optional from the comment (looking for stuff like "defaults to" or "optional"). To remove this error-prone technique, every optional property or argument (but not option) is explicitly marked with "?". 2022-04-06 19:02:10 -07:00			`Error stack. Set when [Error] (or its subclass) has been thrown.`
docs(test runner): api reference for reporter api (#7811) 2021-07-22 19:56:36 -07:00
			`## property: TestError.value`
docs: mark optional properties/arguments explicitly with "?" (#13369) Previously, we were guessing whether something is optional from the comment (looking for stuff like "defaults to" or "optional"). To remove this error-prone technique, every optional property or argument (but not option) is explicitly marked with "?". 2022-04-06 19:02:10 -07:00			`- type: ?<[string]>`
docs(test runner): api reference for reporter api (#7811) 2021-07-22 19:56:36 -07:00
docs: mark optional properties/arguments explicitly with "?" (#13369) Previously, we were guessing whether something is optional from the comment (looking for stuff like "defaults to" or "optional"). To remove this error-prone technique, every optional property or argument (but not option) is explicitly marked with "?". 2022-04-06 19:02:10 -07:00			`The value that was thrown. Set when anything except the [Error] (or its subclass) has been thrown.`