mock

Context

This isn't really a feature request, as what I need is possible with nock as-is. But I spent several hours searching, reading old issues and searching through the source code to find the solution, so I thought this might help others.

I am testing code that accesses a service that sets the statusMessage of the response, as well as the statusCode. I am using nock to mock the server

What

A new ctx.forward utility may be added to forward the currently captured request to its original destination (bypass).

Why

• See #655

Currently bypassing is done via implicit/explicit return in the resolver. This is not intuitive and deterministic action, which also makes it hard to distinguish when the user forgot to return a mocked response, and when they meant to b

Expected Behavior

Invoking a mockk should never cause a test to hang. If too many invocations lead to performance issues, it would be better to either:

• throw an exception once a reasonable cap is reached
• rotate away old data

Current Behavior

After invoking a mock around 130 000 times (on my machine, running JDK 15 on Windows) further invocations will hit a wall and take for

I would welcome a feature when, at the same url which is set to respond with OK status, I could have an error response generated with a random seed.

I am developing an Observable pattern to perform a series of retries to call an endpoint, with increasing delay. The problem is that during testing, I cannot really mock up the condition by randomly switching between two mocky.io urls (error and ok

A "normal" event on an instance ignores null subscriptions. If I do so on a substituted interface, a null subscription leads to an exception. I have a not so nice legacy code with different listeners to an event an one class that does null-attach internally under some conditions, would be nice if this behaviour would be able to be tested as well. Example code for the problem:

        publ

What you did:

Create a route:
/orders/*
then set the delay to 2000ms.

What happened:

route not delayed when hit with another param beside *
/orders/1 not delayed

/orders/900 not delayed
/orders/* delayed
![image](https://user-images.githubusercontent.com/19

Take this class, for example:

`
import Foundation

// some comment has import SOMEBADTHING
public protocol TestProtocol: AnyObject {
func doSomething() -> Void
}
`

The generated mock ends up having:

... import SOMEBADTHING ...

Looks like it is looking for "{import .*}" in source files and just adding that verbatim to the output file, causing compile issues.