Kalin from Glue42 also has an approach based on WebSockets (I think).
It would be nice to create an abstraction so that we can vary this. The main advantage would be that there is less FDC3 stuff happening, which makes debugging the tests easier and figuring out exactly what went wrong when they fail
The main test app and the mocks currently communicate via FDC3. We should abstract this so that we can change the underlying communication mechanism.
It would be nice to create an abstraction so that we can vary this. The main advantage would be that there is less FDC3 stuff happening, which makes debugging the tests easier and figuring out exactly what went wrong when they fail