A sample url shortener app to test Keploy integration capabilities using Gin and mongoDB.
git clone https://github.com/keploy/samples-go.git && cd samples-go/gin-mongo
go mod downloadcurl --silent -O -L https://keploy.io/install.sh && source install.shKeploy can be used on Linux, Windows and MacOS through Docker.
Note: To run Keploy on MacOS through Docker the version must be
4.25.2or above.
Using the docker-compose file we will start our mongodb instance:-
sudo docker run -p 27017:27017 -d --network keploy-network --name mongoDb mongoNow, we will create the docker image of our application:-
docker build -t gin-app:1.0 .keploy record -c "docker run -p 8080:8080 --name MongoApp --network keploy-network gin-app:1.0"To genereate testcases we just need to make some API calls. You can use Postman, Hoppscotch, or simply curl
curl --request POST \
--url http://localhost:8080/url \
--header 'content-type: application/json' \
--data '{
"url": "https://google.com"
}'this will return the shortened url.
{
"ts": 1645540022,
"url": "http://localhost:8080/Lhr4BWAi"
}2. Redirect to original url from shortened url
curl --request GET \
--url http://localhost:8080/Lhr4BWAior by querying through the browser http://localhost:8080/Lhr4BWAi Now, let's see the magic! 🪄💫
Now both these API calls were captured as a testcase and should be visible on the Keploy CLI. You should be seeing an app named keploy folder with the test cases we just captured and data mocks created.
Now that we have our testcase captured, run the test file.
keploy test -c "sudo docker run -p 8080:8080 --net keploy-network --name ginMongoApp gin-app:1.0" --delay 10So no need to setup dependencies like mongoDB, web-go locally or write mocks for your testing.
The application thinks it's talking to mongoDB 😄
We will get output something like this:
Go to the Keploy log to get deeper insights on what testcases ran, what failed. The ts is causing be failure during testing because it'll always be different.
In test-1.yml and test-2.yml, go the noisefield and under -header.Data add the -body.ts on line number 37. Now, it's the time to run the test cases again.
keploy test -c "sudo docker run -p 8080:8080 --net keploy-network --name ginMongoApp gin-app:1.0" --delay 10This time all the test cases will pass.
Spin up your mongo container using
sudo docker run --rm -p27017:27017 -d --network keploy-network --name mongoDb mongoSince, we are on the local machine the MongoDB URL will be
localhost:27017. This needs to be updated on the on line 21 inmain.gofile
Now, we will create the binary of our application:-
go build -coverOnce we have our binary file ready,this command will start the recording of API calls using ebpf:-
sudo -E keploy record -c "./test-app-url-shortener"Make API Calls using Hoppscotch, Postman or cURL command. Keploy with capture those calls to generate the test-suites containing testcases and data mocks.
To generate testcases we just need to make some API calls. You can use Postman, Hoppscotch, or simply curl
1. Generate shortened url
curl --request POST \
--url http://localhost:8080/url \
--header 'content-type: application/json' \
--data '{
"url": "https://google.com"
}'this will return the shortened url. The ts would automatically be ignored during testing because it'll always be different.
{
"ts": 1645540022,
"url": "http://localhost:8080/Lhr4BWAi"
}2. Redirect to original url from shortened url
curl --request GET \
--url http://localhost:8080/Lhr4BWAior by querying through the browser http://localhost:8080/Lhr4BWAi
You'll be able to see new test file and mock file generated in your project codebase locally.
Run this command on your terminal to run the testcases and generate the test coverage report:-
sudo -E keploy test -c "./test-app-url-shortener" --delay 10Note: If delay value is not defined, by default it would be
5.
So no need to setup dependencies like mongoDB, web-go locally or write mocks for your testing.
The application thinks it's talking to mongoDB 😄
We will get output something like this:
Go to the Keploy log to get deeper insights on what testcases ran, what failed. The ts is causing be failure during testing because it'll always be different.
In test-1.yml and test-2.yml, go the noisefield and under -header.Data add the -body.ts on line number 37. Now, it's the time to run the test cases again.
sudo -E keploy test -c "./test-app-url-shortener" --goCoverage --delay 10This time all the test cases will pass.



