Postman - API platform for easy endpoint testing

The results of the experiment to retrieve the existing product from the database by its id see GetProductByIdViaAuroraServerlessV2DataApiHandler with Lambda function with 1024 MB memory setting were based on reproducing more than 100 cold and approximately 10.000 warm starts with experiment which ran for approximately 1 hour. For it (and experiments from my previous article) I used the load test tool hey, but you can use whatever tool you want, like Serverless-artillery or Postman. We won't enable SnapStart on the Lambda function first.

Use tools like Postman or Insomnia to test the API endpoints and ensure they behave as expected.

We will be performing all of the authentication requests manually, however for testing purposes, you might want to use an API testing tool such as Postman or Insomnia.

As you can see in the above diagram, a lambda function is scheduled to be executed periodically by EventBridge. This lambda function retrieves the assets exported from Postman (test collection, environment, and global variables), injects secrets from the secrets manager and executes the tests using the newman npm package, and, in case of failures, updates metrics in CloudWatch and stores test results in the S3 bucket. An alarm is triggered in case the metrics exceed a threshold (in this case, a count of 1).

There are a couple of companies out there that offer such continuous testing services, like Uptrends. However, if you’re just looking for having some continuously running integration tests, I believe you could have a much more cost-effective, simpler, and more useful solution if you build it on your own by using Postman as a basis.

I had to do some exploring/testing of an API today and thought that Postman would be the tool for the job.

Let's set up our API route first because we can quickly test it to see if it's working using an API testing tool like Postman. Create an API route for SendGrid by creating this folder structure src/app/api/sendgrid/route.js.

There are several ways to document an API including in an API testing client like Postman, but we will use OpenAPI spec to document. OpenAPI is an evolution of Swagger, which is a popular open source tool for all things API. Swagger comes with a user interface to display, interact and test our API documentation.

Use Postman to manually test endpoints.

Link: https://swr.vercel.app/

Now, it's time to consume our API. We'll use React for this tutorail, but feel free to use any other framework you prefer; the process remains the same. Additionally, we'll utilize SWR to fetch data from the API and TypeScript to ensure type safety.

'use client'; import FormPostUpdate from './components/FormPostUpdate/FormPostUpdate'; import FormDelete from '../app/components/FormDelete/FormDelete'; import { useFetch } from './hooks/useFetch'; import { useFetchSWR } from './hooks/useFetchSWR'; import Chart from './components/Chart/Chart'; export default function Home() { // Uncomment the code below and comment out the "useFetch" code if your want to use SWR for data fetching --> https://swr.vercel.app/docs/with-nextjs // const { data, error, isLoading } = useFetchSWR( // 'http://127.0.0.1:8000/api/anime/' // ); // Uses the Fetch API for data fetching const { data, error, isLoading } = useFetch( 'http://127.0.0.1:8000/api/anime/' ); if (error) return

An error has occurred.

; if (isLoading) return

Loading...

; console.log(data); return ( <>

POST: Add Anime Form

UPDATE: Update Anime Form

Select an ID from the list. You can change the data for Anime ID, Name and Release.

DELETE: Delete Anime Form

GET: Anime Data List

{data.map((anime) => (

• {anime.anime_name}

• ID: {anime.id}
• Anime ID: {anime.anime_id}
• Anime Release Year: {anime.anime_release}

))}

); }

Then install the package SWR into your application with the following command:

SWR

I would suggest taking a look at SWR [0]. I think it strikes a very nice balance between using fetch and something more heavy-handed like React Query.

[0] https://swr.vercel.app/

Check out the official documentation for SWR here

SWR: A React Hooks library for remote data fetching. It supports features like caching, revalidation, error handling, prefetching, pagination, and support for SSG and SSR. Its bundle size is 10kb minified and 4.4kb gzipped

In a Next.js client component, if you need to fetch data, you can call a Route Handler. Next.js extends the native fetch Web API, allowing you to configure caching and revalidation behavior for each fetch request on the server. Alternatively, you can use a third-party library for requesting. In this case, I'm using SWR as recommended in the documentation.

SWR 🕸️