mocks

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,

As it is done withe Azure in microcks/microcks-azure component, we'd like to provide simple, demo purposed, CloudFormation template for AWS.

I've initialized stuffs but being a newbee at AWS stuffs, help is welcomed !!

Is your feature request related to a problem? Please describe.
I think there are people who migrate to mocktail from mockito after migrating their app to null safety. I think the migration process can be simplified so that the developers don't have to read the full documentation.

Describe the solution you'd like
A table in README that maps mockito way of doing things to `mocktai

The current mock mechanism is "strict" regarding trailing slashes:

mockiavelli.mockGET('/example', {status: 200})
// GET /example/ => 404

This behaviour should be at least configurable to allow ignoring trailing slashes:

const mockiavelli = await Mockiavelli.setup(page, {ignoreTrailingSlashes: true});
mockiavelli.mockGET('/example', {status: 200})
// GET /example/ => 200