Metadata testcases

[hhsecond]

Description

Basic test cases for Metadata

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[rlizzo]

A few bug's which need fixing before we merge, but in general these are a good start.

Let's also add a few tests which stress the amount of text which can be in a value, and the length of a metadata key name as well. I have a sinking suspicion that the default lmdb key length limit (511 bytes) will raise errors which may not propagate clearly through to user space if they are exceeded.

Nice work!

[hhsecond]

Let's also add a few tests which stress the amount of text which can be in a value, and the length of a metadata key name as well. I have a sinking suspicion that the default lmdb key length limit (511 bytes) will raise errors which may not propagate clearly through to user space if they are exceeded.

Will add this to stress test cases

[hhsecond]

@rlizzo Verified, rebased and pushed. This can be merged if you are good. The pending TODOs can be tracked through corresponding issues. Keeping this open till those are fixed might make this stale

[rlizzo]

Looks good. Let's merge!