# Ognyan's CDAP Development Update 4 ## Testing portal network peer-to-peer network calls Since last update, I'm mostly working on prototyping and investigating different options for testing peer-to-peer network calls between portal network clients. Right now, we are leaning towards to split the testing into two separate vectors: **1) Internal to Trin tests** Testing network request/response messages between portal network [Trin](https://github.com/ethereum/trin) instances. **2) Testing framework for p2p networking tests** The idea here is to be able to test cross-client portal network implementations. One viable way to do this is to run a dummy peer that is responsible for talking to the target client, and provoking expected results. In the future, we can see this easy evolving into its own repository and serving as a global testing framework for portal network clients implemented in different languages. ### Current progress - experimental PR is in progress for a testing framework prototype [here](https://github.com/ethereum/trin/pull/78). - Some code refactoring was done which made it feasible to run a "dummy" peer version of the portal network layer without introducing additional code duplication. ### Next goals There was a discussion about alternative ways to send commands to the dummy node and we came to a conclusion that it may be best for us to use json-rpc over IPC for transport layer and encoding. We have code ready for serving json-rpc, and tools are built to readily parse it. It doesn't make sense to invent any new encoding standards. To keep progressing forward, we were able to identify the following tasks that need to be done: - implement custom json-rpc handler for the dummy node to invoke talking to the target client, and provoking expected results. - add internal to Trin networking tests for portal network request/response messages.