Open Source API Test Tool Hitchhiker v0.5 Update-Complete details

This is a creation in Article, where the information may have evolved or changed.

Hitchhiker is an open source, Restful API test tool that supports multiplayer collaboration, supports schedule, data comparison, stress testing, support for upload script customization requests, can be easily deployed locally, and manages APIs with your team members.

For more information, see: http://doc.hitchhiker-api.com/cn/introduction.html

Online experience: http://www.hitchhiker-api.com/, can be used try without login for free login use (online demo does not support stress testing and upload JS, virtual machine single core, Can't hold).

Here's a look at this update:

Request and Setrequest

Script adds the property request to get the requested information, including method, URL, headers, body.

const req = hitchhiker.request;const {url, headers, method, body} = req;

In addition, a method setrequest (request) is added, which modifies requests.
The request and setrequest can be used in conjunction with an appropriate edit before sending it, such as adding a signature, adding a header, and so on.

const crypto = hitchhiker.require('crypto-js');const sign = crypto.HmacSHA1('test', 'asdf');const req = hitchhiker.request;url = `${url}?sign=${sign}`;hitchhiker.setRequest({...hitchhiker.request, url});

Of course, it's too much of a point to turn a GET request into a POST request:

let url = hitchhiker.request.url;url = `${url.substr(0, url.lastIndexOf('/'))}/post?c=d`;hitchhiker.setRequest({...hitchhiker.request, url, body: '{"name":"brook"}', method: 'POST'});

Common Pre Request Script

There was a pre request Script, which is the request level, but a collection often has a lot of request with almost the same operation, if each request to write will be very cumbersome, maintenance is not convenient.

A typical application scenario is that all of the request URLs under collection need to add a dynamic hash value before sending, and it is very convenient to put these common things into the collection level.

Configure invitememberdirectly

Hitchhiker adds a new configuration: invitememberdirectly, which determines whether or not to send an e-mail when inviting a member, or to pull it directly into project, which is true by default.

The background is that some of the company's server is not able to access the external network, but also can not use the Hitchhiker to provide mail features, this direct pull colleagues to project in the function is very useful.

Of course, hitchhiker is to support the external mail interface, in fact, if you want to build a mail server in the network does not bother.

These configurations can be consulted: configuration

Request follow Redirect and request Strict SSL

Both of these are properties that are collection below.

Request follow Redirect is used to set this collection the following requests continue to redirect to the next page when the return status code is 3xx, false by default.

Request Strict SSL is used to set this collection if the following requests are sent with SSL certificate verification, because some companies use their own certificates, these certificates in strict SSL mode will return the certificate error message, do not tick this option will ignore the error, The default is False.

Organize your documents

The document was re-organized, using Gitbook to write and publish, but Gitbook seemingly in the domestic often by the wall, so in Hitchhiker's website also put a copy, convenient to consult.

Document Address: http://doc.hitchhiker-api.com/cn/introduction.html

Draw a script flowchart:

Follow-up plan

The next main goal is to let the stress test support ES6 and Support JS Library, but because the pressure point is written using go, Otto's interpreter, and Otto only support to ES5, need to do the server conversion, and also support async/await, may be a bit of a hassle.

Github: https://github.com/brookshi/Hitchhiker , feel good if you have trouble Star support, thank you.