20 Commits

Author	SHA1	Message	Date
browser-automation-bot	70ad3b2448	feat: roll to Chrome 122.0.6261.57 (r1250580) (#11958) ... Co-authored-by: Alex Rudenko <alexrudenko@chromium.org>	2024-02-21 11:14:39 +01:00
Nikolay Vitkov	b6c5642cc9	chore: update license headers (#11563)	2024-01-03 10:11:33 +00:00
Alex Rudenko	b0d7375519	fix: remove the flag disabling bfcache (#11047)	2023-09-28 11:44:04 +02:00
browser-automation-bot	830f926d48	feat: roll to Chrome 115.0.5790.98 (r1148114) (#10584) ... Co-authored-by: Alex Rudenko <alexrudenko@chromium.org>	2023-07-19 08:11:45 +00:00
Nikolay Vitkov	d0d738d2fc	chore: readd browser setup hook (#10478)	2023-07-03 14:01:29 +02:00
Nikolay Vitkov	ceb6fbb365	chore: use a less chatty BiDi+ (#10453)	2023-06-28 09:54:16 +02:00
Nikolay Vitkov	ff8529696d	ci: remove before hooks (#10431)	2023-06-21 19:41:09 +00:00
Nikolay Vitkov	5e79d53bd3	refactor: tests use toHaveLength and waitEvent (#10061)	2023-04-25 15:02:25 +02:00
Nikolay Vitkov	eefe9583d0	chore: Add EsLint rule import/order (#9685)	2023-02-15 15:09:31 -08:00
Alex Rudenko	06e816bbfa	feat(chromium): roll to Chromium 110.0.5479.0 (r1083080) (#9500) ... Closes #9470	2023-01-12 11:31:20 +01:00
smithc	a032583b6c	feat: add ability to collect JS code coverage at the function level (#9027)	2022-10-06 23:53:05 +02:00
Alex Rudenko	504c7a1ae6	chore: implement custom mocha interface for the runner (#8929) ... Instead of checking skipped tests in mocha-utils this PR implements a custom mocha interface for better flexibility when skipping tests. That should allow skipping tests without running before and after hooks.	2022-09-09 11:12:18 +02:00
Alex Rudenko	d8830cbc55	chore: implement a test runner on top of mocha (#8866) ... * chore: implement a test runner on top of mocha This PR implements a test runner on top of mocha that performs multiple mocha runs as defined in TestSuites.json and compares the outcome of the runs against TestExpectations.json. This allows us to remove most of helpers from mocha-utils and be more flexible when defining the test configurations.	2022-09-08 10:32:39 +00:00
smithc	0c577b9bf8	fix: add missing code coverage ranges that span only a single character (#8911)	2022-09-07 07:10:07 +00:00
jrandolf	28e236f1a6	chore: use --parallel (#8612)	2022-07-05 14:42:55 +02:00
Alex Rudenko	383e855847	fix: CSS coverage should work with empty stylesheets (#8570) ... Closes #8535	2022-06-24 14:17:16 +02:00
jrandolf	26c3acbb07	feat!: type inference for evaluation types (#8547) ... This PR greatly improves the types within Puppeteer: - **Almost everything** is auto-deduced. - Parameters don't need to be specified in the function. They are deduced from the spread. - Return types don't need to be specified. They are deduced from the function. (More on this below) - Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`. - [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons: 1. Setting them will indubitably break auto-deduction. 2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense). - [**BREAKING CHANGE**] `waitFor` is officially gone. To migrate to these changes, there are only four things you may need to change: - If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary). ⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)` ✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType` ⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)` ✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>` - If you set any type parameters in the *parameters* of an evaluation function, remove them. ⛔ `evaluate(a: number, b: number) => {...}, a, b)` ✅ `evaluate(a, b) => {...}, a, b)` - If you set any type parameters in the method's declaration, remove them. ⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)` ✅ `evaluate(a, b) => {...}, a, b)`	2022-06-23 11:29:46 +02:00
jrandolf	84712cbc28	chore: use Google's TS style guide's format config (#8542)	2022-06-22 15:25:44 +02:00
jrandolf	570087ea94	chore: use strict typing in tests (#8524) ... * The testing tsconfig.json inherits from the base TS config. * A lot of type assertions have been inserted...a lot. * All testing utilities have migrated to TS. * text-diff is being replaced with diff for TS compatibility. * ProtocolError has been added to PuppeteerErrors and PuppeteerErrors is no longer a record (it's been frozen). * Fixes a small bug where null was an allowable media type in emulation (should be undefined).	2022-06-15 12:09:22 +02:00
jrandolf	80373f7a12	chore: use composite builds for tests (#8522)	2022-06-15 12:05:25 +02:00