sample course selling api (express)
Introduction
A simple sample CRUD application and see how seamlessly Keploy integrates with Express and MongoDB Buckle up, it's gonna be a fun ride! 🎢
This runs natively on Linux, macOS (Apple Silicon) and Windows (x86-64) — see Installing Keploy.
🛠️ Platform-Specific Requirements for Keploy
Below is a table summarizing the tools needed for both native and Docker installations of Keploy on macOS, Windows, and Linux:
| Operating System | Without Docker | Docker Installation | Prerequisites |
|---|---|---|---|
| Guide | Native: nothing to install — no Docker, no Lima, no sudo. Only if you choose a container route: Docker Desktop 4.25.2+, or Lima (which is also the route on an Intel Mac). | ||
| Guide | Native: nothing to install — no WSL, no Docker, no Administrator. Only if you choose a container route: WSL ( wsl --install, Windows 10 2004+/build 19041+ or Windows 11 — also the route on Windows/ARM), or Docker Desktop 4.25.2+. | ||
| Linux kernel 5.10 or higher |
Keploy runs natively on macOS (Apple Silicon / arm64) and Windows (x86‑64) — neither has eBPF, so it intercepts traffic in userspace on both, and neither needs sudo or Administrator. Natively on macOS and Windows, Keploy understands HTTP/HTTPS, MySQL and MongoDB calls; calls to other services — PostgreSQL, Redis, Kafka, gRPC and the like — are captured only as raw bytes and usually don't replay, so for an app that runs in containers or depends on them, use Docker. Docker, Lima (macOS) and WSL (Windows) remain supported alternatives, and WSL is the route on Windows on ARM. On an Intel Mac use Lima: the Docker route on macOS still runs the native CLI on the host, so it is Apple Silicon only too.
Low-latency recording (keploy record --low-latency, or a Kubernetes Sidecar with low_latency_mode) and the Kubernetes DaemonSet agent capture with eBPF hooks that arm64 kernels support only from 6.4 (x86-64 kernels from 5.10). On an older arm64 kernel, record without low latency, and use Sidecar mode without low_latency_mode in Kubernetes.
Podman
On Linux, Keploy records and tests applications that run in Podman as well as in Docker. In a keploy record or keploy test command, use podman run (or podman compose) where these docs use docker run (or docker compose). Run every other container command they give, such as creating the network, building the image or starting a database with docker run -d, as sudo podman ..., so that it is in the rootful Podman Keploy uses. See the Podman tab under Linux in Installing Keploy for the commands.
- Rootful Podman. Keploy's agent loads eBPF, which a rootless Podman can't grant, so Keploy drives the rootful Podman and runs as root (it re-runs itself with
sudowhen it needs to). Images and containers you created with Podman withoutsudoaren't visible to it: build or pull your app's image withsudo podman. - Podman's API. Keploy talks to Podman's Docker-compatible API. If the rootful
podman.socketis enabled (sudo systemctl enable --now podman.socket) it uses that; otherwise it starts Podman's API service for the run and stops it when Keploy exits. - Compose.
podman compose(Podman 4.7 or later; Keploy is tested with Podman 5) works with Docker Compose v2 or later (docker-compose) as its compose provider, on a host that runs systemd: Podman runs healthchecks with systemd timers, and your app's service waits for the healthcheck of Keploy's agent service. podman-compose isn't supported. - Local Podman on Linux only. A Podman set up as a podman-remote client (for example with
CONTAINER_HOST,CONTAINER_CONNECTION, orremote = truein containers.conf) runs containers in another Podman service, but Keploy's agent runs in the local rootful Podman, so Keploy refuses it. On macOS and Windows, including Podman machine, Keploy refuses Podman commands: its agent uses Linux's eBPF. - Which Keploy. Podman support is in the Keploy that
curl --silent -O -L https://keploy.io/install.sh && source install.shinstalls (free with an account), from v3.8.60. Akeploybuilt from the open-source repository refuses Podman commands and says where to get it.
Installation Overview
The install is the same whatever your plan. You need a free Keploy account to record and replay: the first keploy record or keploy test signs you in, and your plan decides which additional features are available.
Quick Installation Using CLI
On Linux and macOS (Apple Silicon), install Keploy with:
curl --silent -O -L https://keploy.io/install.sh && source install.sh
You should see something like this:
▓██▓▄
▓▓▓▓██▓█▓▄
████████▓▒
▀▓▓███▄ ▄▄ ▄ ▌
▄▌▌▓▓████▄ ██ ▓█▀ ▄▌▀▄ ▓▓▌▄ ▓█ ▄▌▓▓▌▄ ▌▌ ▓
▓█████████▌▓▓ ██▓█▄ ▓█▄▓▓ ▐█▌ ██ ▓█ █▌ ██ █▌ █▓
▓▓▓▓▀▀▀▀▓▓▓▓▓▓▌ ██ █▓ ▓▌▄▄ ▐█▓▄▓█▀ █▓█ ▀█▄▄█▀ █▓█
▓▌ ▐█▌ █▌
▓
Keploy CLI
Available Commands:
example Example to record and test via keploy
config --generate generate the keploy configuration file
record record the keploy testcases from the API calls
test run the recorded testcases and execute assertions
update Update Keploy
Flags:
--debug Run in debug mode
-h, --help help for keploy
-v, --version version for keploy
Use "keploy [command] --help" for more information about a command.
🎉 Wohoo! You are all set to use Keploy.
On Windows (x86-64), Keploy is a single keploy.exe, installed from PowerShell without Administrator — see Run Keploy natively on Windows.
Other Installation Methods
Install using Docker
Downloading and running Keploy in Docker
With this method your application and Keploy's agent run in Docker, but the keploy CLI — which starts them both — runs on your machine. Use it when your app runs in containers, or on macOS and Windows when your app depends on services beyond HTTP/HTTPS, MySQL and MongoDB: natively there, calls to other services — PostgreSQL, Redis, Kafka, gRPC and the like — are captured only as raw bytes and usually don't replay.
-
Open up a terminal window.
-
Create a bridge network in Docker using the following docker network create command:
docker network create keploy-network
- Install Keploy: on Linux and macOS with the command below, on Windows with the PowerShell steps. On macOS the CLI is Apple Silicon (arm64) only — on an Intel Mac, run Keploy with Lima instead.
curl --silent -O -L https://keploy.io/install.sh && source install.sh
Examples:
Record:
keploy record -c "docker run -p <appPort>:<hostPort> --name <containerName> --network keploy-network <applicationImage>" --container-name "<containerName>" --buildDelay 60
Test:
keploy test --c "docker run -p <appPort>:<hostPort> --name <containerName> --network keploy-network <applicationImage>" --delay 10
Install using Podman (Linux)
Keploy also records and tests applications that run in rootful Podman on Linux, started with podman run or podman compose: see the Podman tab under Linux in Installing Keploy.
Install Manually
Downloading the Keploy binary yourself
These download the same keploy binary the install command above installs.
On Linux
Prerequisite: Linux kernel 5.10 or higher (uname -r shows yours). This picks the build for your architecture:
case "$(uname -m)" in
x86_64) ARCH=amd64 ;;
aarch64 | arm64) ARCH=arm64 ;;
*) echo "unsupported architecture: $(uname -m)" >&2; false ;;
esac &&
curl --fail --silent --show-error --location -o /tmp/keploy \
"https://keploy.io/ent/dl/latest/enterprise_linux_${ARCH}" &&
sudo install -m 0755 /tmp/keploy /usr/local/bin/keploy
The same steps work inside WSL on Windows and inside a Lima VM on macOS.
On macOS (Apple Silicon)
mkdir -p ~/.keploy/bin &&
curl --fail --silent --show-error --location -o ~/.keploy/bin/keploy \
"https://keploy.io/ent/dl/latest/enterprise_darwin_arm64" &&
chmod +x ~/.keploy/bin/keploy
export PATH="$HOME/.keploy/bin:$PATH" # add this line to your ~/.zshrc too
There is no Intel macOS build: on an Intel Mac, use the Linux steps inside Lima.
On Windows (x86-64)
Follow the PowerShell steps. On Windows on ARM, use the Linux steps inside WSL.
If you run Keploy inside WSL with Docker: setting up Docker Desktop for WSL 2
- Install Docker Desktop for Windows from here.
When developing on Windows with Docker Desktop and WSL 2, it's crucial to configure Docker Desktop to allow WSL 2 distributions to access the Docker daemon. This setup enables seamless integration between your Windows environment, WSL 2 Linux distros, and Docker.
By default, Docker Desktop may not be configured to work with all WSL 2 distros out of the box. Proper configuration ensures that you can run Docker commands from within your WSL 2 environment, allowing for a more native Linux development experience while leveraging the power of Windows.
This setup is essential for Keploy to function correctly in a WSL 2 environment, as it needs to interact with the Docker daemon to manage containers and networks effectively. For detailed instructions on how to configure
Docker Desktopfor WSL 2, please refer to the official Docker documentation.
Get Started! 🎬
Clone the repository and move to express-mongoose folder
git clone https://github.com/keploy/samples-typescript && cd samples-typescript/node-mongoose
# Install the dependencies
npm install
Lights, Camera, Record! 🎥
Docker installation and running the mongodb compass
Here I'm using WSL , so follow below steps to configure docker with mongo db compass
1. Install docker in your windows and follow this tutorial to connect with mongodb compass :
https://www.youtube.com/watch?v=NEPZqSvKx40&list=PLff_PESolMjuDXQdjiqYRW_GnDQjU32QX
2. after installing docker and running those commands in video use this command as well to create a network:
docker network create keploy-network
*url should look something like this depending on your connection you can adjust, also update your .env file with mongodb_url:
mongodb://127.0.0.1:27023/courses.
Capturing Testcases
keploy record -c "npm start"
if using wsl use this :
sudo -E env PATH=$PATH keploy record -c 'npm start'
sudo is for Linux (and WSL) only. On macOS, Keploy is dropped by the npm start launcher — run the app's entry point directly instead, here and in keploy test below: keploy record -c "node server.js" (details).
🔥 Challenge time! Generate some test cases. How? Just make some API calls. Postman, Hoppscotch or even curl - take your pick!
Let's generate the testcases.
Make API Calls using Postman or cURL command. Keploy with capture those calls to generate the test-suites containing testcases and data mocks.
🎉 Woohoo! With a simple API call, you've crafted a test case with a mock! Dive into the Keploy directory and feast your eyes on the newly minted test-1.yml and mocks.yml after doing below steps
Time to perform API magic! Follow the breadcrumbs... or Make more API Calls
Some api calls you can make
Get request - Get all courses
curl --request GET \
--url http://localhost:3000/courses
Post request - Add a new course
curl --location 'http://localhost:3000/courses' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'title=react advance' \
--data-urlencode 'description=advance' \
--data-urlencode 'price=1000' \
--data-urlencode 'published=true'
Put request - Add a new course
- Make sure to replace id of course
curl --location --request PUT 'http://localhost:3000/courses/6626a9cd3840cb305c0a6d52' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'title=react advance'
Delete request - Delete a course
- Make sure to replace id of course
curl --location --request DELETE 'http://localhost:3000/courses/6626a9cd3840cb305c0a6d52'
🎉 Easy right! Just one API call and you've whipped up a test case with a mock. Check out the Keploy directory to find your shiny new test-1.yml and mocks.yml files.
version: api.keploy.io/v1beta1
kind: Http
name: test-1
spec:
metadata: {}
req:
method: GET
proto_major: 1
proto_minor: 1
url: http://localhost:3000/courses
header:
Accept: "*/*"
Accept-Encoding: gzip, deflate, br
Cache-Control: no-cache
Connection: keep-alive
Host: localhost:3000
Postman-Token: 61d4ef71-85a9-4dd9-b036-6beb0136c8d7
User-Agent: PostmanRuntime/7.32.1
body: ""
timestamp: 2024-04-22T23:56:36.910408265+05:30
resp:
status_code: 200
header:
Access-Control-Allow-Origin: "*"
Connection: keep-alive
Content-Length: "740"
Content-Type: application/json; charset=utf-8
Date: Mon, 22 Apr 2024 18:26:36 GMT
Etag: W/"2e4-bpK0GltUbFpXKUMEiWddtMBI/a4"
Keep-Alive: timeout=5
X-Powered-By: Express
body: '{"courses":[{"_id":"66269dd4a16b2f11f9c1c0e9","title":"python course","description":"advance","price":1000,"published":true,"__v":0},{"_id":"66269e13a16b2f11f9c1c0ec","title":"react course","description":"advance","price":1000,"published":true,"__v":0},{"_id":"66269f2034c9140719a0f7de","title":"express","description":"advance","price":1000,"published":true,"__v":0},{"_id":"6626a8f2946288ed91737eb7","title":"express and react","description":"advance","price":1000,"published":true,"__v":0},{"_id":"6626a9cd3840cb305c0a6d52","title":"react and next js","description":"advance","price":1000,"published":true,"__v":0},{"_id":"6626aa43f9602455c7dac9ea","title":"react advance","description":"advance","price":1000,"published":true,"__v":0}]}'
status_message: OK
proto_major: 0
proto_minor: 0
timestamp: 2024-04-22T23:56:38.951925148+05:30
objects: []
assertions:
noise:
header.Date: []
created: 1713810398
curl: |
curl --request GET \
--url http://localhost:3000/courses \
--header 'Connection: keep-alive' \
--header 'User-Agent: PostmanRuntime/7.32.1' \
--header 'Accept: */*' \
--header 'Cache-Control: no-cache' \
--header 'Postman-Token: 61d4ef71-85a9-4dd9-b036-6beb0136c8d7' \
--header 'Host: localhost:3000' \
--header 'Accept-Encoding: gzip, deflate, br' \
Or simply wander over to your browser and visit http://localhost:3000/courses.
Did you spot the new test and mock scrolls in your project library? Awesome! 👏
Run Tests
Time to put things to the test 🧪
keploy test -c "npm start" --delay 10
If using wsl use this :
sudo -E env PATH=$PATH keploy test -c 'npm start' --delay 10
Keploy test report:
The
--delayflag? Oh, that's just giving your app a little breather (in seconds) before the test cases come knocking.
To Run test using jest use this command :
npm test
jest test coverage report :
Get Keploy jest sdk
npm i @keploy/sdk nyc jest
Update package file
Update the package.json file that runs the application:
"scripts": {
//other scripts
"test": "jest --coverage --collectCoverageFrom='src/**/*.{js,jsx}'",
"coverage": "nyc npm test && npm run coverage:merge && npm run coverage:report",
"coverage:merge": "mkdir -p ./coverage && nyc merge ./coverage .nyc_output/out.json",
"coverage:report": "nyc report --reporter=lcov --reporter=text"
//other scripts
}
Usage
For the code coverage for the keploy API tests using the jest integration, you need to add the following test to your Jest test file. It can be called as keploy.test.js. Jest test file. It can be called as keploy.test.js.
const {expect} = require("@jest/globals");
const keploy = require("@keploy/sdk");
const timeOut = 300000;
describe(
"Keploy Server Tests",
() => {
test(
"TestKeploy",
(done) => {
const cmd = "npm start";
const options = {};
keploy.Test(cmd, options, (err, res) => {
if (err) {
done(err);
} else {
expect(res).toBeTruthy(); // Assert the test result
done();
}
});
},
timeOut
);
},
timeOut
);
Now let's run jest tests along keploy using command
npm test
To get Combined coverage with keploy test coverage
npm run coverage
Wrapping it up 🎉
Congrats on the journey so far! You've seen Keploy's power, flexed your coding muscles, and had a bit of fun too! Now, go out there and keep exploring, innovating, and creating! Remember, with the right tools and a sprinkle of fun, anything's possible.😊🚀
Happy coding! ✨👩💻👨💻✨
Related
- Node.js MongoDB Sample — Node + MongoDB CRUD.
- Node.js Express Mongoose Sample — closely related Express app.
- Sample JavaScript Apps — browse all JS quickstarts.