Hey, so I've been writing some feature tests to validate the functionality I've built with the help of this package is working correctly.
While doing so, I noticed the tests often got a bit clunky and could be simplified a bit with the help of some new assertions - I ended up creating a trait called DynamoDbTestAssertions that provides the following methods:
public static function assertDynamoDbHasTable(string $table);
public static function assertDynamoDbMissingTable(string $table);
public static function assertDynamoDbHasItem(string $table, string $key, $keyValue);
public static function assertDynamoDbMissingItem(string $table, string $key, $keyValue);
public static function assertDynamoDbItemEquals(string $table, string $key, $keyValue, $expected);
public static function assertDynamoDbItemNotEquals(string $table, string $key, $keyValue, $expected);
My tests are so much easier to read and write because of this...
Hey, so I've been writing some feature tests to validate the functionality I've built with the help of this package is working correctly.
While doing so, I noticed the tests often got a bit clunky and could be simplified a bit with the help of some new assertions - I ended up creating a trait called
DynamoDbTestAssertions
that provides the following methods:My tests are so much easier to read and write because of this...
What do you think?