Add Light client interop tests

[chaitanyaprem]

Planned start date:
Due date:

Summary

All interop tests for Light client with nwaku or go-waku service nodes.

• Refer tests from js-waku (https://github.com/waku-org/js-waku/tree/master/packages/tests)
• any other tests that maybe required??

Acceptance Criteria

• Interop tests with nwaku should be sucessful for light client protocols.

Tasks

RAID (Risks, Assumptions, Issues and Dependencies)

[fryorcraken]

@chaitanyaprem I am not too familiar with the context of this issue, are you happy to update the description as per waku-org/pm#40 ?

[chaitanyaprem]

Ok, the reason i was thinking this may be required is that there seems to be a light node option in status-desktop @richard-ramos was showing in one of the calls. If that is possible, then go-waku <-> nwaku and go-waku(light client) <-> go-waku interop tests would be required right.
Anyways better to confirm this with status-desktop team and if it is not required, we can move it out of 2023 scope.

[fryorcraken]

Oh really sorry, I misread the issue. Yes totally agree it's in scope.

[fryorcraken]

I would focus on go-waku(client)<>go-waku(server) tests. Is something not currently available?

For tests involving js-waku and nwaku. This would be part of the work done by @fbarbu15

[chaitanyaprem]

I would focus on go-waku(client)<>go-waku(server) tests. Is something not currently available?

Ok, As of now I don't think we have any tests for this.
I think we are dependent on Status for these tests. @richard-ramos , correct me if i am wrong.
Shouldn't they be go-waku(client) <-> nwaku interop? I wasn't aware of go-waku is being considered to be run as service-node as being priority.

[fryorcraken]

Actually this is part of the DST work done by @fbarbu15
I created an Epic to track: waku-org/pm#34

[chaitanyaprem]

Closing this based on above comment as it is being tracked by DST work.