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

They are all currently written in groovy; I'd like to migrate them to the build.gradle.kts format to make the whole project Kotlin-based.

I think this can be done in steps, migrating one build.gradle file at a time - not sure about it though.

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

The issue is based on the discussion in #559.

@zvirja

should we probably modify CI so that doc is published automatically on push to master? This way if we don't want doc to be released right now - just keep it in a branch. Otherwise, we have this non-synchronized docs and manual work.. 😟

@dtchepak

I'm not sure what to do about publishing docs. It would be nice to auto-publish,

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.