With puppeteer-request-spy you can easily watch, fake or block requests from puppeteer matching patterns.
- allows you to write tests verifying specific resources are loaded as expected
- allows you to exclude unneeded requests from tests, speeding them up significantly
- allows you to alter a request's response with custom content and http status
- avoids conflicts resulting from already aborted / continued or responded requests
npm install puppeteer-request-spy --save-dev
First create a new RequestInterceptor
with a matcher
function and an optional logger.
function KeywordMatcher(testee, keyword) {
return testee.indexOf(keyword) > -1;
}
let requestInterceptor = new RequestInterceptor(KeywordMatcher, console);
Next create a new RequestSpy
with a pattern
to be matched against all requests.
let imageSpy = new RequestSpy('/pictures');
The RequestSpy
needs to be registered with the RequestInterceptor
.
requestInterceptor.addSpy(imageSpy);
To use the puppeteer's request event the RequestInterception flag on the page object has to be set to true.
await page.setRequestInterception(true);
The RequestInterceptor
must be registered with puppeteer.
page.on('request', requestInterceptor.intercept.bind(requestInterceptor));
After puppeteer's page object finished navigating to any page, you can query the RequestSpy
.
await page.goto('https://www.example.com');
assert.ok(!imageSpy.getMatchedRequests()[0].failure());
assert.ok(imageSpy.hasMatch() && imageSpy.getMatchCount() > 0);
When all responses have been loaded you can also query the response of any matched Request. You can ensure all responses have been loaded by using the networkidle0 option. For further information check the official puppeteer API.
for (let match of imagesSpy.getMatchedRequests()) {
assert.ok(match.response().ok());
}
Note
Since unhandled Promise rejections causes the node process to keep running after test failure, the
RequestInterceptor
will catch and log puppeteer's exception, if therequestInterception
flag is not set.
The response of intercepted requests can be replaced by adding a ResponseFaker to the RequestInterceptor. The fake response has to match the Response object as specified in the official puppeteer API.
let responseFaker = new ResponseFaker('/ajax/some-request', {
status: 200,
contentType: 'application/json',
body: JSON.stringify({successful: false, payload: []})
});
requestInterceptor.addFaker(responseFaker);
For further details on how to replace different formats of data like images, text or html, please refer to the examples provided in the github repository.
Optionally you can add patterns
to block requests. Blocking requests speeds up page load since no data is loaded. Blocking requests takes precedence over faking responses, so any request blocked will not be replaced even when matching a ResponseFaker
. Blocked or faked requests will still be counted by a RequestSpy
with a matching pattern.
requestInterceptor.block(['scripts', 'track', '.png']);
puppeteer-request-spy works great with minimatch, it can be passed as the matcher
function.
const minimatch = require('minimatch');
let cssSpy = new RequestSpy('**/*.css');
let responseFaker = new ResponseFaker('**/*.jpg', someFakeResponse);
let requestInterceptor = new RequestInterceptor(minimatch);
responseFaker.addFaker(responseFaker);
requestInterceptor.addSpy(cssSpy);
requestInterceptor.block('**/*.js');
await page.setRequestInterception(true);
page.on('request', requestInterceptor.intercept.bind(requestInterceptor));
await page.goto('https://www.example.com');
assert.ok(cssSpy.hasMatch() && cssSpy.getMatchCount() > 0);
for (let matchedRequest of cssSpy.getMatchedRequests()) {
assert.ok(match.response().status() === 200);
}
The RequestInterceptor
will call all spies, fakers and blocker to dertermine if an intercepted request matches. against the matcher
function and notify all spies with a matching pattern and block requests matching any pattern in urlsToBlock
.
matcher
: <(url: string, pattern: string) => boolean>>logger?
: <{log: (text: string) => void}>
The matcher
will be called for every url, testing the url against patterns of any RequestSpy
provided and also any url added to urlsToBlock
.
The logger
if provided will output any requested url with a 'loaded' or 'aborted' prefix and any exception caused by puppeteer's abort and continue functions.
- interceptedRequest: interceptedRequest provided by puppeteer's 'request' event
Function to be registered with puppeteer's request event.
- requestSpy: <IRequestSpy> spy to register
Register a spy with the RequestInterceptor
.
Clears all registered spies.
- responseFaker: <IResponseFaker> faker to register
Clears all registered fakers.
- urlsToBlock: <Array<string> | <string>> urls to be blocked if matched
block
will always add urls to the list urlsToBlock
. Passed arrays will be merged with urlsToBlock
.
- urlsToBlock: <Array<string>> setter for
urlsToBlock
Clears all registered patterns in urlsToBlock
.
- requestBlocker <IRequestBlocker>
Allows you to replace the default RequestBlocker by your own implementation.
RequestSpy
is used to count and verify intercepted requests matching a specific pattern.
pattern
: <string|Array<string>>
pattern
passed to the matcher
function of the RequestInterceptor
.
- returns: <boolean> returns whether any url matched the
pattern
- returns: <Array<string>> returns a list of urls that matched the
pattern
- returns: <Array<Request>> returns a list of requests that matched the
pattern
- returns: <number> number of urls that matched the
pattern
- request <Request> request object provided by puppeteer
- matcher <(url: string, pattern: string) => boolean>> matching function passed to RequestInterceptor's constructor
- returns: <boolean> returns true if any pattern provided to the RequestSpy matches the request url
The RequestInterceptor
calls this method to determine if an interceptedRequest matches the RequestSpy.
- matchedRequest: <Request> request that was matched
The RequestInterceptor
calls this method when an interceptedRequest matches the pattern.
ResponseFaker
is used to provide a fake response when matched to a specific pattern.
pattern
: <string|Array>responseFake
: <Response
> for details refer to puppeteer API
- returns: <Array<string>> return the
pattern
list of the faker
- returns: <Response> return the fake response
The RequestInterceptor
calls this method when an interceptedUrl matches the pattern.
- request <Request> request object provided by puppeteer
- matcher <(url: string, pattern: string) => boolean>> matching function passed to RequestInterceptor's constructor
- returns: <boolean> returns true if any pattern provided to the ResponseFaker matches the request url
The RequestInterceptor
calls this method to determine if an interceptedRequest matches.
RequestBlocker
is used to by the RequestInterceptor to match requests to block.
- request <Request> request object provided by puppeteer
- matcher <(url: string, pattern: string) => boolean>> matching function passed to RequestInterceptor's constructor
The RequestInterceptor
calls this method to determine if an interceptedRequest matches.
- urls <Array | string>
Adds new urls to the block list.
Removes all entries of the block list.
There are some usage examples included in the github repository. Check them out to get started with writing a simple test with puppeteer and puppeteer-request-spy.
- minimatch - For easily matching path-like strings to patterns.
- puppeteer - Control chrome in headless mode with puppeteer for automated testing.
MIT