An attempt to utilise the AWS Serverless Developer Portal which is updated through the use of CI/CD to ensure that published API documentation is kept in sync with whats actually running.
An attempt to utilise the AWS Serverless Developer Portal which is updated through the use of CI/CD to ensure that published API documentation is kept in sync with whats actually running.
A reflection on why when migrating to this new style of blog I have chosen to remove posts from previous iterations of the blog during my migration.
A brief summary of the workflow used to update my new blog, utilising Git, Bitbucket Pipelines and 11ty.
And finally, utilising custom annotations to populate our data stores. For those joining at this point, I’m exploring the ability to succinctly inject test data sets into my JUnit test cases (running DynamoDb in a LocalStack container).
In the last post in the series we showed how to setup a DynamoDb container through docker, and connect to that from a running java client. But that just created a database instance and not the data structures that we’re going to need.
In my last post I wrote about the general approaches to testing if you’re looking at organisational level structuring. This time around I’ll be looking at the benefits for an individual developer.