Is your feature request related to a problem? Please describe.
Reading through what a fake can and can not do is not clear from the documentation.

Describe the solution you'd like
Exact methods that are available to a Fake need to be documented.

First of all thank you for Sinon, I believe the library is powerful and has helped me write a lot of tests. What I'm requesting here is

At the moment MockIt supports

export const StatusCodes = {
  OK: "200",
  CREATED: "201",
  NO_CONTENT: "204",
  BAD_REQUEST: "400",
  FORBIDDEN: "401",
  INTERNAL_SERVER_ERROR: "500"
};

Might be worth adding some more? https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

If anybody is up for the challenge :)?

Today, my project's build failed in CI because of a problem downloading the cuckoo_generator executable in the run script. I'm not sure what the actual issue was (there was an issue extracting the URL from the GH API response), but it started working again by itself sometime later, so I'm assuming that it was a GH blip.

I find it a little strange that the SPM installation for Cuckoo depends

Currently, a user can create the mapping to serve the response from random files or in a round-robin fashion. (wiki)

-  request:
      url: /stubs/employee/([0-9]+)

   response:
      strategy: random
      files: ["<% url.1 %>.xml","file2.xml","file3.xml"]

Or

-  request: