There is a video I've done on that just here kzfaq.info/get/bejne/q9KPa5iby7OUn6M.html

Much appreciated!

Glad it was helpful!

The ticks and crosses are the "vs code jest" extension. The multi coloured tabs is "Rainbow intent"

Thanks!

Glad you liked it Christian

When you run tests it creates a local mock of dynamo so it doesn't polute your real data

Yes, if you need to mock context the that would be the easiest way. Over time you can add parameters to vary the context data you generate

You could do it another way. When you start jest, it starts serverless offline. Your jest tests then call the serverless offline endpoints. You can even then reuse your tests on your deployed resources too which is really cool

Is the table that you are passing in (user) the same as the name of the table you've set in your resources config in serverless?

@@CompleteCoding I created a Gist file where you can see a resumed version of my serverless.yml file. Not sure if it looks ok, right now it works for my purpose of having multiple environments using --stage in AWS. gist.github.com/crisecheverria/15ea7aa275df344f1d1f647eb0af91d1

as you will be testing locally, you can just run usersTableName=user-dev projectsTableName=projects-dev jest

If there is a java test library that can execute a function with an set event then it would be very similar. If you're also testing with a dynamo table you'll have to script a local version of dynamo to start and the configure your dynamo to connect to that. With JS, that is done by the jest dynamo plugin. There might even be a similar plugin for java

Hey Pete. Are you using Windows, Mac or Linux? Also are you entering it all on a single line

Sam - sorry for the delayed response. I'm using windows and yes I'm entering it on all on one line

spread works brilliantly with flat objects but struggles with deep or nested objects. One thing we're setting it response.requestContext.httpMethod. If we used spread then you would have to pass in the whole requestContext object, not just the method value. You could also make a recursive function that means you can pass in partial objects and it joins them but that would be a lot more work

@@CompleteCoding I've been doing spreading for 2 years now, never seen a "struggle". Do you have any references for that as I would be curious what "struggles" exist? As far as the comment about passing the parent objects, yes, but it does also make it more readable, easier to maintain, and far more flexible/future proof.

Right now the best thing I can do is to like and comment on the new videos that come out. It really helps show the video to more people. I'm toying with the KZfaq Membership, Pateron, or having some T-Shirts and merch. Is this the kind of thing you were thinking of?

Integration tests are often hard to define with Serverless. In this video I go with "testing a lambda locally without mocking - using local versions instead". In this case you can integration test any Lambda exactly as I do in this video. You may need to change the event that you pass into the handler from your test. The other definition of integration testing is "testing a deployed Lambda that integrates with all of the real services". You can also do this with no-API lambdas. Once everything is deployed, in your tests use the same `lambda.invoke` that you would when calling from another lambda. That will trigger the real lambda and you can see if your tests work.

That sounds like you're wanting to test what the user experience would be? Is that right?

The first thing is to check your version of serverless-offline. There was a change to v6 that broke the way that it works with the dynamo configuration. You can manually set the version to 5 and it should work

To test the actual endpoints you'd need to deploy the service first. This is actually what I do a lot more now. I automatically deploy a temporary stack to a 'testing' account when a PR is created. The tests then run and if they fail, that shows up in the PR.