mockttp
Version:
Mock HTTP server for testing HTTP clients and stubbing webservices
258 lines (257 loc) • 12.2 kB
TypeScript
import { Readable } from 'stream';
import { MaybePromise } from '@httptoolkit/util';
import { Headers, CompletedRequest, Method, MockedEndpoint, Trailers } from "../../types";
import type { RequestRuleData } from "./request-rule";
import { CallbackResponseResult, PassThroughStepOptions } from "./request-step-definitions";
import { BaseRuleBuilder } from "../base-rule-builder";
/**
* @class RequestRuleBuilder
* A builder for defining mock rules. Create one using a method like
* `.forGet(path)` or `.forPost(path)` on a Mockttp instance, then call
* whatever methods you'd like here to define more precise request
* matching behaviour, control how the request is handled, and how
* many times this rule should be applied.
*
* When you're done, call a `.thenX()` method to register the configured rule
* with the server. These return a promise for a MockedEndpoint, which can be
* used to verify the details of the requests matched by the rule.
*
* This returns a promise because rule registration can be asynchronous,
* either when using a remote server or testing in the browser. Wait for the
* promise returned by `.thenX()` methods to guarantee that the rule has taken
* effect before sending requests to it.
*/
export declare class RequestRuleBuilder extends BaseRuleBuilder {
private addRule;
/**
* Mock rule builders should be constructed through the Mockttp instance you're
* using, not directly. You shouldn't ever need to call this constructor.
*/
constructor(addRule: (rule: RequestRuleData) => Promise<MockedEndpoint>);
constructor(method: Method, path: string | RegExp | undefined, addRule: (rule: RequestRuleData) => Promise<MockedEndpoint>);
private steps;
/**
* Add a delay (in milliseconds) before the next step in the rule
*/
delay(ms: number): this;
/**
* Reply to matched requests with a given status code and (optionally) status message,
* body, headers & trailers.
*
* If one string argument is provided, it's used as the body. If two are
* provided (even if one is empty) then the 1st is the status message, and
* the 2nd the body. If no headers are provided, only the standard required
* headers are set, e.g. Date and Transfer-Encoding.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenReply(status: number, data?: string | Buffer, headers?: Headers, trailers?: Trailers): Promise<MockedEndpoint>;
thenReply(status: number, statusMessage: string, data: string | Buffer, headers?: Headers, trailers?: Trailers): Promise<MockedEndpoint>;
/**
* Reply to matched requests with the given status & JSON and (optionally)
* extra headers.
*
* This method is (approximately) shorthand for:
* server.forGet(...).thenReply(status, JSON.stringify(data), { 'Content-Type': 'application/json' })
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenJson(status: number, data: object, headers?: Headers): Promise<MockedEndpoint>;
/**
* Call the given callback for any matched requests that are received,
* and build a response from the result.
*
* The callback should return a response object with the fields as
* defined by {@link CallbackResponseMessageResult} to define the response,
* or the string 'close' to immediately close the connection. The callback
* can be asynchronous, in which case it should return this value wrapped
* in a promise.
*
* If the callback throws an exception, the server will return a 500
* with the exception message.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenCallback(callback: (request: CompletedRequest) => MaybePromise<CallbackResponseResult>): Promise<MockedEndpoint>;
/**
* Respond immediately with the given status (and optionally, headers),
* and then stream the given stream directly as the response body.
*
* Note that streams can typically only be read once, and as such
* this rule will only successfully trigger once. Subsequent requests
* will receive a 500 and an explanatory error message. To mock
* repeated requests with streams, create multiple streams and mock
* them independently.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenStream(status: number, stream: Readable, headers?: Headers): Promise<MockedEndpoint>;
/**
* Reply to matched requests with a given status code and the current contents
* of a given file. The status message and headers can also be optionally
* provided here. If no headers are provided, only the standard required
* headers are set.
*
* The file is read near-fresh for each request, and external changes to its
* content will be immediately appear in all subsequent requests.
*
* If one string argument is provided, it's used as the body file path.
* If two are provided (even if one is empty), then 1st is the status message,
* and the 2nd the body. This matches the argument order of thenReply().
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenFromFile(status: number, filePath: string, headers?: Headers): Promise<MockedEndpoint>;
thenFromFile(status: number, statusMessage: string, filePath: string, headers?: Headers): Promise<MockedEndpoint>;
/**
* Pass matched requests through to their real destination. This works
* for proxied requests only, direct requests will be rejected with
* an error.
*
* This method takes options to configure how the request is passed
* through. See {@link PassThroughStepOptions} for the full details
* of the options available.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenPassThrough(options?: PassThroughStepOptions): Promise<MockedEndpoint>;
/**
* Forward matched requests on to the specified forwardToUrl. The url
* specified must not include a path. Otherwise, an error is thrown.
* The path portion of the original request url is used instead.
*
* The url may optionally contain a protocol. If it does, it will override
* the protocol (and potentially the port, if unspecified) of the request.
* If no protocol is specified, the protocol (and potentially the port)
* of the original request URL will be used instead.
*
* This method takes options to configure how the request is passed
* through. See {@link PassThroughStepOptions} for the full details
* of the options available.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenForwardTo(target: string, options?: PassThroughStepOptions): Promise<MockedEndpoint>;
/**
* Close connections that match this rule immediately, without
* any status code or response.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenCloseConnection(): Promise<MockedEndpoint>;
/**
* Reset connections that match this rule immediately, sending a TCP
* RST packet directly, without any status code or response, and without
* cleanly closing the TCP connection.
*
* This is only supported in Node.js versions (>=16.17, >=18.3.0, or
* later), where `net.Socket` includes the `resetAndDestroy` method.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenResetConnection(): Promise<MockedEndpoint>;
/**
* Hold open connections that match this rule, but never respond
* with anything at all, typically causing a timeout on the client side.
*
* Calling this method registers the rule with the server, so it
* starts to handle requests.
*
* This method returns a promise that resolves with a mocked endpoint.
* Wait for the promise to confirm that the rule has taken effect
* before sending requests to be matched. The mocked endpoint
* can be used to assert on the requests matched by this rule.
*
* @category Responses
*/
thenTimeout(): Promise<MockedEndpoint>;
/**
* Send a successful JSON-RPC response to a JSON-RPC request. The response data
* can be any JSON-serializable value. If a matching request is received that
* is not a valid JSON-RPC request, it will be rejected with an HTTP error.
*
* @category Responses
*/
thenSendJsonRpcResult(result: any): Promise<MockedEndpoint>;
/**
* Send a failing error JSON-RPC response to a JSON-RPC request. The error data
* can be any JSON-serializable value. If a matching request is received that
* is not a valid JSON-RPC request, it will be rejected with an HTTP error.
*
* @category Responses
*/
thenSendJsonRpcError(error: any): Promise<MockedEndpoint>;
}
//# sourceMappingURL=request-rule-builder.d.ts.map