@codeparrot/js-agent
v2.0.4
Published
Record and replay API traffic
Downloads
465
Readme
What is CodeParrot?
Get a change report on response body, latency & error rates of your APIs!
An Example Diff
CodeParrot uses AI and production traffic to generate a change report. This report gives you insights on differences in response body for all unique requests coming to your service!
It works by "recording" production (or staging env) traffic. Our AI figures out the unique API calls from this traffic, and also mocks the downstream dependencies! Magic right?! 🤯
Then for every PR, the above unique API calls are run against the new version of code. Its like- auto-generated functional tests (API calls for a service, with dependencies mocked).
Installation
Step 1 - Install the nodeJs "record" agent
Install the CodeParrot dependency
@codeparrot/js-agent
by runningnpm install @codeparrot/js-agent
This will add a dependency
"@codeparrot/js-agent": "^1.2.3"
, in yourpackage.json
Update the
node
start app command with-r @codeparrot/js-agent
, like"scripts": { "server": "node -r @codeparrot/js-agent index.js" }
This basically require
’s the code parrot agent package before your application code.
Set the following env variable:
# set it to your *unique* service name
CODE_PARROT_APP_NAME=<service-name>
When you start your nodeJS application and see a log line like:
@codeparrot/js-agent, v1.2.5 nodejs-agent-<...>gserviceaccount.com
CodeParrot record is set up! 🎉 Use your application as normal, and CodeParrot will record the network traffic.
Step 2 - Install GitHub App
Install the CodeParrot GitHub App in the repo(s) that already have replay set up. (It asks for the minimum possible permissions)
Then, create 2 new files:
codeparrot-replay.Dockerfile
codeparrot.sh
to run the tests. Every code push, this Dockerfile is built and run. This new Dockerfile is almost as same as your existing one, except that it sets the CMD
to run codeparrot.sh
instead of the usual npm start
.
codeparrot.sh
runs your app start command (like npm start
) in a loop, until all the tests execute.
Example codeparrot.sh
:
#!/bin/sh
while :
do
CODE_PARROT_IS_REPLAY=true npm start && break
echo "Non-zero exit! Restarting replay..."
done
Example codeparrot-replay.Dockerfile
:
# ... existing app setup
COPY codeparrot.sh ./codeparrot.sh
CMD ["sh", "./codeparrot.sh"]
Now, in every PR, a GitHub "check" with a link to the Change Report will appear: 🎉
Contributing, Self Setup
Refer to CONTRIBUTING.md