lambda-simulator

0.0.19 • Public • Published

License: WTFPL Deployment Status Tests Most recent version in NPM

What is this?

This is a simple project that allows you to unit test your AWS Lambda handlers. Additionally, you can use it to run the Lambda locally for some manual testing.

Do not use this as a replacement for AWS Lambda services in production. This would be a terrible idea.

How do I use it?

Unit testing

First, add the project as a test dependency in package.json file (see most recent version in npm):

"devDependencies": {
    "lambda-simulator": "^version"
    ...
}

Next, import it in your unit test along with your AWS Lambda handler:

const LambdaSimulator = require('lambda-simulator').LambdaSimulator;
const handler = require('../index').handler;

Additionally, if you're planning to proxy your requests through AWS Gateway, import the proxy:

const AwsGatewayLambdaIntegrationProxy = require('lambda-simulator').AwsGatewayLambdaIntegrationProxy;

Finally, create the simulator in your test and add assertions:

describe('my AWS Lambda handler', function() {
   
    const simulator = new LambdaSimulator(handler, new AwsGatewayLambdaIntegrationProxy()); // proxy is optional
    
    it('should reply with status 200', async () => {
        // when:
        const response = await simulator.sendPostRequest('/', { someField: 'someValue' }, { someHeader: 'someHeaderValue' });
        
        // then:
        assert.deepStrictEqual(response.httpStatusCode, 200);
    });
    
});

Path parameters

If you'd like the path parameters to be parsed by the AwsGatewayLambdaIntegrationProxy, you need to provide a URL template. For example this proxy object:

new AwsGatewayLambdaIntegrationProxy('/resource/:resourceId/sub-resource/:subResourceId')

Will yield the following pathParameters object in your Lambda:

{
  "resourceId": "5",
  "subResourceId": "bla"
}

Headers

The AwsGatewayLambdaIntegrationProxy will handle headers passed in the request in two ways. First, all headers will be available in event.headers field, unchanged. Additionally, all headers will be split by comma and available in event.multiValueHeaders field.

Manual testing

If you'd like to test your Lambda manually, start the LambdaSimulator server by calling the listen method:

const LambdaSimulator = require('lambda-simulator').LambdaSimulator;
const handler = require('../index').handler;

new LambdaSimulator(handler).listen();

Now, you can send requests directly to your Lambda:

curl -vsX POST \
     -H 'Content-Type:application/json' \
     -d '{"testVariable": "testValue"}' \
     'http://localhost:3000/test?testQueryParam=testValue'

What features does it have?

Very few. It merely mimics AWS Lambda and, therefore, will never be perfect. It's good enough for testing though.

Stuff that is missing, from the top of my head:

  • many fields when using the AWS API Gateway proxy
  • other proxy implementations
  • memory allocation statistics (not sure if possible with Node)

Contribution guidelines

All I ask for is tests and documentation in form of JS docstrings. Feel free to submit a PR if you feel like it.

Versions

Current Tags

VersionDownloads (Last 7 Days)Tag
0.0.194latest

Version History

VersionDownloads (Last 7 Days)Published
0.0.194
0.0.180
0.0.176
0.0.161
0.0.150
0.0.140
0.0.123
0.0.110
0.0.100
0.0.90
0.0.824
0.0.70
0.0.60
0.0.50
0.0.30
0.0.20

Package Sidebar

Install

npm i lambda-simulator

Weekly Downloads

38

Version

0.0.19

License

WTFPL

Unpacked Size

34.6 kB

Total Files

11

Last publish

Collaborators

  • jezor