-
Updated
Aug 25, 2021 - Vue
mock
Here are 1,902 public repositories matching this topic...
-
Updated
Aug 27, 2021 - Java
-
Updated
Aug 26, 2021 - JavaScript
-
Updated
Aug 25, 2021 - Vue
-
Updated
Aug 25, 2021 - PHP
-
Updated
Feb 17, 2021 - JavaScript
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
-
Updated
Aug 6, 2021 - Objective-C
-
Updated
Aug 28, 2021 - TypeScript
The Answers section in the docs doesn't mention returnsArgument, even though that has been implemented for more than 1 year now. Nor does the function have any KDoc comments.
Please update the docs to cover this as well.
Prerequisites
Please answer the following questions for yourself before submitting an issue.
- I am running the latest version
-
Updated
Aug 26, 2021 - TypeScript
-
Updated
Jun 29, 2021 - JavaScript
-
Updated
Aug 14, 2021 - JavaScript
-
Updated
May 11, 2020 - Vue
-
Updated
Aug 16, 2021 - Python
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
-
Updated
Jul 12, 2021 - Ruby
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
-
Updated
Aug 28, 2021 - TypeScript
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
 -> 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.
Improve this page
Add a description, image, and links to the mock topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the mock topic, visit your repo's landing page and select "manage topics."


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