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

Describe the bug

I received this error whenever there's code error on the handler code.

Environment

This unit testing running on Node environment

• msw: 0.35.0
• nodejs: 16.6.0
• npm: 7.24.1

To Reproduce

Take a look at the example of the handler code below:

import { rest } from 'msw'

export const handlers = [
  rest.post('/login', (req, res, ctx) => {
    

The test suite is currently split between two organization models: some tests are organized by the component, or the feature, they test (like this), and a lot of tests are organized by the number of the GitHub issue they verify (like [this](https://github.com/mockk/mockk/blob/master/mockk/jvm/s

Checklist

• Feature request has a meaningful title
• I have searched the existing issues. See all issues
• I have tested using the latest version of Pester. See Installation and update guide.

Summary of the feature request

Hi,

we are internally using Gitlab

Description

Create a playground environment on stackblitz using the falso.new domain:

https://developer.stackblitz.com/docs/guide/open-from-github#set-up-the-main-starter-url

See faker.js example.

Proposed solution

No response

Alternatives considered

No response

Do you want to create a pull request?

No

我认为这个写的有问题 (in @/utils/is)

export function isObject(val: any): val is Record<any, any> {
  return val !== null && is(val, 'Object');
}
export function isPromise<T = any>(val: unknown): val is Promise<T> {
  return is(val, 'Promise') && isObject(val) && isFunction(val.then) && isFunction(val.catch);
}

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,