Jeff Schmidt

HIP-646/657/765: Verify token metadata in acceptance tests

2

### Problem Once token `metadata` (and the `metadata_key`) have been exposed (#6549) in the REST API, test via acceptance tests. ### Solution As much as possible utilize the existing token/NFT...

HIP-646/657/765: Implement token metadata acceptance tests

3

**Description**: Acceptance tests and token/mirror client updates to invoke the new HAPI and MAPI functionality recently implemented. Test fungible and non-fungible metadata capabilities as well as that "dynamic" NFTs. **Related...

Port REST specs to Java, phase 1

2

**Description**: To confidently be able to port over existing JavaScript REST APIs to Java, we need to ensure the existing spec tests continue to work against the newly converted API....

### Problem The ultimate goal is the capability to run spec tests against the Java REST API, not just the legacy JS REST API. Having proved the new Java based...

### Problem Advance from the first phase implementation, which largely laid in the groundwork for deserializing existing spec tests, being able to customize and create a small subset of database...

### Problem The existing JS REST API spec test framework supports the `matrix` and `fakeTime` feature. Java equivalents need to be provided in order for those specs to pass as...

Add an application cache for REST API

2

**Description**: Very preliminary draft to get feedback on general approach to the solution. There is still more implementation and testing to be done. There are many times that the same...

### Problem Implement remaining single-entity builds and all multiple-entity builders and run specs to verify they work. ### Solution Features * Implement additional entity builders to create, customize and persist...