just-api VS http.cat

would like to introduce Just-API, An open source framework that I built to help people with testing APIs.

To test the API, I recommend a proper API testing framework that can run a full test suite without you having to write a single test case. In this area, I recommend Dredd and schemathesis. These frameworks will get you covered when it comes to ensuring that the API server complies with the API specification. You may find Dredd a bit confusing at the beginning, in which case I recommend a tutorial I wrote a while ago about testing with Dredd. In addition, you can consider using just-apis, which allows you to define your own test cases for the API in YAML files (so no programming required).

Cats for other HTTP status codes can be found (or not found :-)) one level up

https://http.cat

Whenever we request data or services from a server, it can respond with status codes represented by numbers. You've probably heard of "404" which means "not found", but there are others like "201 - Created" and "500 - Internal Server Error." During one of my mentoring sessions, I was given a website that showcased all these status codes with kitten memes and a brief description. It was fantastic and helped me grasp each one of those statuses better.

import { Module, OnModuleInit } from '@nestjs/common' import { HttpModule, HttpService } from '@nestjs/axios' import { CatApi } from './cat-api.service' @Module({ imports: [ HttpModule.register({ // line A timeout: 1_000, maxRedirects: 2, baseURL: 'https://http.cat', }), ], providers: [ { provide: CatApi, useExisting: HttpService, // line B } ], exports: [CatApi], // line C }) export class CatApiModule implements OnModuleInit { constructor(private readonly httpService: HttpService) {} onModuleInit() { this.httpService.axiosRef.defaults.headers.common['Accept'] = 'application/json' } }