Waku Interop Testing

vac:qa:waku:2025q3-interop-testing

Description §

Maintain and ensure the continued reliability of the Waku interop testing framework. This includes addressing regressions, adapting to changes in nwaku and gowaku, and performing minor improvements to keep the framework functional and effective.

Alignment with VAC Narratives:

• The VAC QA team supports internal collaboration and efficiency by maintaining the quality and reliability of the Waku interop framework.

Task List §

Maintenance §

• fully qualified name: vac:qa:waku:2025q3-interop-testing:maintenance
• owner: fbarbu15
• status: done
• start-date: 2025/07/01
• end-date: 2025/09/30

Description §

Ongoing maintenance of Waku interop tests. This includes updating tests for changes in nwaku or js-waku, addressing regressions, investigating and resolving issues, and implementing minor improvements to the testing framework as needed.

Deliverables §

• Adjust waku interop tests to latest nwaku changes and fixes
• chore: shard-specific metrics update
• chore: fix waku_connected_peers_per_shard metric
• bug: nwaku returns invalid message JSON when contentTopic contains backslashes
• chore: maintenance

js-waku filter hardening §

• fully qualified name: vac:qa:waku:2025q3-interop-testing:jswaku-filter-hardening
• owner: fbarbu15
• status: done
• start-date: 2025/07/01
• end-date: 2025/07/14

Description §

Harden js-waku filter protocol by adding more advanced tests like:

• Sanity checks in terms of throughput of Waku messages of different sizes
• Sending/receiving thousands of messages in a short period of time

Deliverables §

• chore: add throughput reliability tests
• chore: network conditions tests

Lite protocol tester §

• fully qualified name: vac:qa:waku:2025q3-interop-testing:liteprotocoltester
• owner: aya
• status: done
• start-date: 2025/09/01
• end-date: 2025/09/30

Description §

Explore, fix and improve waku lite protocol tester based on nwaku dev requirements

Deliverables §

• chore: Adding store scripts
• chore: Qa tests
• chore: rework old scripts

Waku cannary tool §

• fully qualified name: vac:qa:waku:2025q3-interop-testing:wakucannary
• owner: aya
• status: in progress (90%)
• start-date: 2025/07/01
• end-date: 2025/07/30

Description §

Explore, fix and improve waku canary tool based on nwaku dev requirements

Deliverables §

• bug: Canary app fails to connect to well-known Waku peers over all transports
• bug:waku canary web-socket not working

12H Longevity §

• fully qualified name: vac:qa:waku:2025q3-interop-testing:12hlongevity
• owner: aya
• status: in progress (90%)
• start-date: 2025/07/21
• end-date: 2025/08/15

Description §

Create a github actions workflow that can run a 12 hour longevity test for waku go bindings.

Deliverables §

• PR and CI run

Waku rendezvous peer discovery §

• fully qualified name: vac:qa:waku:2025q3-interop-testing:rendezvous-peer-discovery
• owner: aya
• status: in progress (40%)
• start-date: 2025/08/20
• end-date: 2025/09/10

Description §

Test that Relay nodes finds new peers when solely using rendezvous. See FURPS

Deliverables §

• bug: Rendezvous peer discovery is not functioning

Waku REST APIs for admin/debug §

• fully qualified name: vac:qa:waku:2025q3-interop-testing:REST-APIs-extended
• owner: aya
• status: done
• start-date: 2025/08/05
• end-date: 2025/08/20

Description §

Adding E2E tests to cover REST APIs for admin/debug endpoints

Deliverables §

• chore: Add rest APIs and wrappers
• bug: Empty shards in /admin/v1/peer/{peerId}
• bug:Peers stats count looks inconsistent (/admin/v1/peers/stats)
• chore: Add rest APIs and wrappers p2