Caching responses from real api and use it as the stubbed data (Powered by talkback)
npm install hummockCaching responses from real api and use it as the stubbed data.
This is a standalone GUI application which runs PROXY servers for every host
you provide in the config file. (see the Usage section)
Powered by Talkback.
For those who want to use recording features
when test own applications, please use talkback directly.
create hummock.json file in the root with content as listed below.
Humock sets the port for each listener automatically, but you can specify it by yourself.
``json`
{
"recordFrom": [
{
"host": "https://some-host.com"
},
{
"host": "http://another-host-example-with-custom-port-for-listener.com",
"port": 8001
}
]
}
run npm start and visit http://localhost:3000. If you have port 3000 busy, you can run PORT=3001 npm start where 3001 is any of your free ports.localhost:6000
Hummock will start and you would be able to access new entrypoint on localhost: and localhost:8001 (considering the config above)
Config schema is located in the project root
| Option | Required | Default | Description |
| ---------- | -------- | ------- | ------------------------------------------------- |
| autostart | no | false | Tells hummon to start proxies when app launches |true
| gui | no | | Turn web ui on/off |[]
| recordFrom | yes | | Servers that should be proxied (in form of above) |
By default, hummock looks for config file in the root folder.
You can specify own config path simply running
`bash``
npm start -- --config /path/to/config/hummock.json
Many thanks go to Ignacio Piantanida, who developed a brilliant package
Talkback. Hummock is just a wrapper on top of it which allows to run multiple talkback instances and
modify snapshot on the fly in browser window. The initial idea was to
implement the same as talkback does, so it easily covered most of cases.