Local dynamodb testing zip file#

* Creates a local DynamoDB instance for testing. Here is a Junit rule that creates local server for that. tProperty('', 'native-libs') ДЄfter these steps you can use DynamoDBLocal as you want. It is OK to do that just before creating your local server. Set to show native librariesДЄs last step, you need to set system property to native-libs directory. Then, add this plugin to get native dependencies to specific folder: ДЈ.

PynamoDB can be used with any server that provides the same API as.

PS: I am aware of Alternator, but it appears to have other drawbacks so IвЂ™m inclined to stick with AmazonвЂ™s supported solution if I can make it work. Several DynamoDB compatible servers have been written for testing and debugging purposes. CanвЂ™t I somehow ask the JVM to fork itself and look inside the resources to build a classpath? Or, even better, canвЂ™t I just call the main method of DynamoDB Local from some other thread so this all happens in a single process? Any ideas? DynamoDB Local is, after all, just Java code. It seems like there should be an easier way. Besides being slow, the potential for left-over processes seems ugly. I have to spawn a process and wait for it to start for each unit test, and then kill that process after each test.

Using local disk is often dicey for testing, especially with continuous builds and such.

I have to unpack a zip to the local disk.

Everyone needs the java executable on their $PATH.

That works, but itвЂ™s ugly and has some drawbacks:

Local dynamodb testing zip file#

zip file of the DynamoDB local stuff in test/resources, then in the method, IвЂ™d extract it to some temporary directory and start a new java process to execute it. I have found a way to make this work, but itвЂ™s ugly, so IвЂ™m looking for alternatives.