Currently testing of the remote frameworks done in the is done by creating interfaces to represent the specific framework objects that we use in remote tracing. For example, Apache HttpRequest class is represented by internal interface that has methods corresponding to the original Apache interface.
This is a problem as:
we are not testing against the real implementation / interface, thus any changes in those would not be noticed
we don't have a way of testing different versions of same library to prove it's working
We need to think on better testing strategy. At the moment, and can not define that this better strategy is. The goal should be that each remote sensor is tested with different versions of the library it's made for.