mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-10 08:08:06 -05:00
QA 2025Q2 commitments and tasks (#105)
This commit is contained in:
fbarbu15
93
content/qa/ift/2025q2-qa-rfc-sync-waku.md
Normal file
93
content/qa/ift/2025q2-qa-rfc-sync-waku.md
Normal file
@@ -0,0 +1,93 @@
|
||||
---
|
||||
|
||||
title: QA & RFC Synchronization for Waku Project - Core Protocols
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "qa"
|
||||
- "ift"
|
||||
draft: false
|
||||
description: Expand and formalize the QA & RFC synchronization process for the core protocols across all Waku implementations.
|
||||
|
||||
---
|
||||
|
||||
`vac:qa:ift:2025q2-qa-rfc-sync-waku`
|
||||
|
||||
## Description
|
||||
Expand and formalize the QA & RFC synchronization process across all Waku Implementations,
|
||||
ensuring that core protocol implementations match specifications and have adequate test coverage.
|
||||
|
||||
Building on the previous quarter's efforts,
|
||||
this commitment focuses on systematically reviewing each Waku implementation (nim, js, go).
|
||||
to ensure core protocol implementations match the corresponding RFCs.
|
||||
Any discrepancies will be flagged for either:
|
||||
1. RFC updates (in collaboration with the RFC team), or
|
||||
2. Bug fixes and/or implementing missing parts in the respective repositories.
|
||||
|
||||
As part of this process, we will also assess the level of test automation and coverage for each core protocol,
|
||||
identifying gaps and proposing or creating additional tests as necessary.
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* Continues fostering collaboration between QA, RFC contributors, and engineering teams, ensuring changes in one area promptly reflect across the ecosystem.
|
||||
* Helps maintain a high standard for both internal and external contributions by detecting discrepancies early and closing testing gaps.
|
||||
|
||||
## Task List
|
||||
|
||||
### nwaku
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q2-qa-rfc-sync-waku:nwaku`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
- Compare each core protocol implemented in `nwaku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for each core protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
* Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
* GitHub issues for required fixes or RFC updates.
|
||||
* Recommendations for improved or additional test coverage.
|
||||
|
||||
### js-waku
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q2-qa-rfc-sync-waku:js-waku`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
- Compare each core protocol implemented in `js-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for each core protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
* Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
* GitHub issues for required fixes or RFC updates.
|
||||
* Recommendations for improved or additional test coverage.
|
||||
|
||||
### go-waku
|
||||
|
||||
* fully qualified name: `vac:qa:ift:2025q2-qa-rfc-sync-waku:go-waku`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
- Compare each core protocol implemented in `go-waku` against the Waku RFCs.
|
||||
- Document any discrepancies found, such as missing specifications or incomplete implementations,
|
||||
and clarify whether the RFC or the implementation requires an update.
|
||||
- Verify test automation exists for each core protocol and note any coverage gaps.
|
||||
- Coordinate with developers for bug fixes and/or additional tests.
|
||||
|
||||
#### Deliverables
|
||||
* Notion page summarizing the current implementation-to-RFC mapping, discrepancies, and action items.
|
||||
* GitHub issues for required fixes or RFC updates.
|
||||
* Recommendations for improved or additional test coverage.
|
||||
@@ -6,6 +6,26 @@ tags:
|
||||
|
||||
---
|
||||
|
||||
## 2025q2 `vac:qa:`
|
||||
---
|
||||
|
||||
### `ift:`
|
||||
* [[qa/ift/2025q2-qa-rfc-sync-waku|2025q2-qa-rfc-sync-waku ]]
|
||||
|
||||
### `vac:`
|
||||
* [[qa/vac/2025q2-nim-libp2p-testing|2025q2-nim-libp2p-testing ]]
|
||||
|
||||
### `waku:`
|
||||
* [[qa/waku/2025q2-interop-testing|2025q2-interop-testing ]]
|
||||
* [[qa/waku/2025q2-waku-go-bindings-testing|2025q2-waku-go-bindings-testing ]]
|
||||
* [[qa/waku/2025q2-messaging-api-testing|2025q2-messaging-api-testing ]]
|
||||
* [[qa/waku/2025q2-status-go-functional-testing|2025q2-status-go-functional-testing ]]
|
||||
|
||||
### `nomos:`
|
||||
* [[qa/nomos/2025q2-da-testing|2025q2-da-testing ]]
|
||||
* [[qa/nomos/2025q2-e2e-testing|2025q2-e2e-testing ]]
|
||||
---
|
||||
|
||||
## 2025q1 `vac:qa:`
|
||||
---
|
||||
|
||||
|
||||
93
content/qa/nomos/2025q2-da-testing.md
Normal file
93
content/qa/nomos/2025q2-da-testing.md
Normal file
@@ -0,0 +1,93 @@
|
||||
---
|
||||
|
||||
title: Nomos Data Availability Testing
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "qa"
|
||||
- "nomos"
|
||||
draft: true
|
||||
description: Implement data availability test plans for the Nomos project at the cluster level.
|
||||
|
||||
---
|
||||
|
||||
`vac:qa:nomos:2025q2-da-testing`
|
||||
|
||||
## Description
|
||||
Implement data availability test plans for the Nomos project at the cluster level,
|
||||
focusing on protocol compatibility, internal interactions, data confidentiality, and resilience against failures.
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
- By developing and constantly updating tests for data availability,
|
||||
VAC QA ensures that the feature's implementation aligns with high standards.
|
||||
- This continuous testing helps identify any spec-related issues early,
|
||||
contributing to the RFC culture and improving spec quality.
|
||||
- The effort also supports IFT's strategic objective of scaling the project’s capacity
|
||||
and ensuring a reliable system for future community involvement.
|
||||
|
||||
## Task List
|
||||
|
||||
### Protocol and API Compatibility Tests
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-da-testing:protocol-api-compatibility`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date: 2025/04/1
|
||||
* end-date: 2025/04/15
|
||||
|
||||
#### Description
|
||||
Add integration tests to verify DA works well with other blockchain components.
|
||||
|
||||
#### Deliverables
|
||||
* PR link with added tests
|
||||
* CI runs showing successful or failed executions with detailed reports
|
||||
|
||||
|
||||
### Internal Interaction and Data Flow Tests
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-da-testing:interaction-data-flow`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date: 2025/04/16
|
||||
* end-date: 2025/05/16
|
||||
|
||||
#### Description
|
||||
Add integration tests to verify correct interaction of the internal DA components
|
||||
to ensure correct data flow and end-to-end processing.
|
||||
|
||||
#### Deliverables
|
||||
* PR link with added tests
|
||||
* CI runs showing successful or failed executions with detailed reports
|
||||
|
||||
|
||||
### Data Confidentiality
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-da-testing:data-confidentiality`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date: 2025/05/19
|
||||
* end-date: 2025/06/6
|
||||
|
||||
#### Description
|
||||
Add integration tests to verify data confidentiality,
|
||||
ensuring secure communications, and controlling unauthorized access.
|
||||
|
||||
#### Deliverables
|
||||
* PR link with added tests
|
||||
* CI runs showing successful or failed executions with detailed reports
|
||||
|
||||
|
||||
### Data Integrity and Dispersal Process Resilience
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-da-testing:dispersal-resilience`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date: 2025/06/9
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
Add integration tests to verify the robustness of internal processes against tampering or malformed inputs
|
||||
and maintaining the integrity of the data handling mechanisms.
|
||||
|
||||
#### Deliverables
|
||||
* PR link with added tests
|
||||
* CI runs showing successful or failed executions with detailed reports
|
||||
41
content/qa/nomos/2025q2-e2e-testing.md
Normal file
41
content/qa/nomos/2025q2-e2e-testing.md
Normal file
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Nomos E2E Testing for Nomos Node
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "qa"
|
||||
- "nomos"
|
||||
draft: false
|
||||
description: Maintain and ensure the reliability of Nomos e2e tests.
|
||||
---
|
||||
|
||||
`vac:qa:nomos:2025q2-e2e-testing`
|
||||
|
||||
## Description
|
||||
Maintain and ensure the continued reliability of the Nomos end to end testing framework.
|
||||
This includes addressing regressions, adapting code in `nomos-e2e-tests` and `nomos-node`,
|
||||
adapting to other changes in `nomos-node`,
|
||||
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 Nomos E2E framework.
|
||||
|
||||
## Task List
|
||||
|
||||
### Maintenance
|
||||
|
||||
* fully qualified name: `vac:qa:nomos:2025q2-e2e-testing:maintenance`
|
||||
* owner: romanzac
|
||||
* status: not started
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
Ongoing maintenance of Nomos E2E tests and changes in Nomos Node repository related to Nomos E2E testing.
|
||||
This includes updating tests for changes in `nomos-node`, addressing regressions,
|
||||
investigating and resolving issues, and implementing minor improvements to the testing framework as needed.
|
||||
|
||||
#### Deliverables
|
||||
* PR link with added tests
|
||||
* CI runs showing successful or failed executions with detailed reports
|
||||
@@ -41,7 +41,7 @@ Improve tooling around nim libp2p testing.
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
In 2025 Q1, expand Gossipsub test coverage to include more advanced
|
||||
In 2025 Q2, expand Gossipsub test coverage to include more advanced
|
||||
and edge-case scenarios that go beyond core functionality.
|
||||
This will cover additional use cases and less common interactions within the protocol,
|
||||
ensuring the robustness of Gossipsub in a wider range of environments.
|
||||
@@ -91,7 +91,7 @@ checking what’s not covered, and implementing new tests for those scenarios.
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Add new test plans for identify / push identify, ping, mplex multiplexer,
|
||||
Update and add new test plans for identify / push identify, ping, mplex multiplexer,
|
||||
and others to be determined later.
|
||||
|
||||
#### Deliverables
|
||||
|
||||
39
content/qa/waku/2025q2-interop-testing.md
Normal file
39
content/qa/waku/2025q2-interop-testing.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: Waku Interop Testing
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "qa"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: Maintain and ensure the reliability of Waku interop tests.
|
||||
---
|
||||
|
||||
`vac:qa:waku:2025q2-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:2025q2-interop-testing:maintenance`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date: 2025/04/01
|
||||
* end-date: 2025/06/30
|
||||
|
||||
#### Description
|
||||
Ongoing maintenance of Waku interop tests.
|
||||
This includes updating tests for changes in `nwaku`, `gowaku` or `js-waku`, addressing regressions,
|
||||
investigating and resolving issues, and implementing minor improvements to the testing framework as needed.
|
||||
|
||||
#### Deliverables
|
||||
PRs and issues
|
||||
@@ -11,10 +11,9 @@ description: Enhance functional testing for status-go features by implementing t
|
||||
`vac:qa:waku:2025q2-status-go-functional-testing`
|
||||
|
||||
## Description
|
||||
Collaborate with the Status QA team to improve functional testing coverage
|
||||
by adding new tests outlined in this [epic](https://github.com/status-im/status-go/issues/6064).
|
||||
Additionally, work on enhancing the framework to support more advanced functional testing scenarios.
|
||||
Note: This commitment is being deferred to Q2 to avoid overcommitting, but tasks may be taken on in Q1 if time permits.
|
||||
Expand functional testing for status-go by implementing targeted Waku feature tests,
|
||||
including chat actions, contact requests, and group chats,
|
||||
as outlined in this [epic](https://github.com/status-im/status-go/issues/6064).
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
* By helping create a robust functional testing framework for Status Go,
|
||||
@@ -25,16 +24,16 @@ Note: This commitment is being deferred to Q2 to avoid overcommitting, but tasks
|
||||
## Task List
|
||||
|
||||
|
||||
### Message tests
|
||||
### Chat actions tests
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-status-go-functional-testing:message-tests`
|
||||
* fully qualified name: `vac:qa:waku:2025q2-status-go-functional-testing:chat-actions-tests`
|
||||
* owner: fbarbu15
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Cover the core functionality of Status related to [wakuext messages](https://github.com/status-im/status-go/issues/6084)
|
||||
Cover the core functionality of Status related to [wakuext messages](https://github.com/status-im/status-go/issues/6072)
|
||||
|
||||
#### Deliverables
|
||||
* PRs with the new tests
|
||||
|
||||
75
content/qa/waku/2025q2-waku-go-bindings-testing.md
Normal file
75
content/qa/waku/2025q2-waku-go-bindings-testing.md
Normal file
@@ -0,0 +1,75 @@
|
||||
---
|
||||
title: waku-go-bindings Testing
|
||||
tags:
|
||||
- "2025q2"
|
||||
- "qa"
|
||||
- "waku"
|
||||
draft: false
|
||||
description: Expand protocol coverage for waku-go-bindings
|
||||
---
|
||||
|
||||
`vac:qa:waku:2025q2-waku-go-bindings-testing`
|
||||
|
||||
## Description
|
||||
Expand protocol coverage for `waku-go-bindings` with filter and lightpush tests.
|
||||
|
||||
The framework should cover those protocols as they are covered in `waku-interop-tests`
|
||||
|
||||
**Alignment with VAC Narratives:**
|
||||
|
||||
* The VAC QA team plays a key role in supporting internal collaboration
|
||||
and efficiency across projects by ensuring the quality of Nwaku Go Bindings
|
||||
and the sunsetting of go-waku.
|
||||
* By finding issues in specs during testing,
|
||||
VAC strengthens the RFC culture,
|
||||
contributing to continuous improvement and community engagement.
|
||||
|
||||
## Task List
|
||||
|
||||
### Filter Protocol Testing
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-waku-go-bindings-testing:filter`
|
||||
* owner: aya
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Add test coverage by implementing tests for the filter protocol.
|
||||
These tests should mirror the approach used in `waku-interop-tests`
|
||||
and ensure reliable message propagation across multiple nodes.
|
||||
|
||||
#### Deliverables
|
||||
PRs and issues
|
||||
|
||||
### Lightpush Protocol Testing
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-waku-go-bindings-testing:lightpush`
|
||||
* owner: aya
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Add test coverage by implementing tests for the lightpush protocol.
|
||||
These tests should mirror the approach used in `waku-interop-tests`
|
||||
and ensure reliable message propagation across multiple nodes.
|
||||
|
||||
#### Deliverables
|
||||
PRs and issues
|
||||
|
||||
### Maintenance
|
||||
|
||||
* fully qualified name: `vac:qa:waku:2025q2-waku-go-bindings-testing:maintenance`
|
||||
* owner: aya
|
||||
* status: not started
|
||||
* start-date:
|
||||
* end-date:
|
||||
|
||||
#### Description
|
||||
Ongoing maintenance of Waku go bindings tests.
|
||||
This includes updating tests for changes in the bindings or in `nwaku`, addressing regressions,
|
||||
investigating and resolving issues, and implementing minor improvements to the testing framework as needed.
|
||||
|
||||
#### Deliverables
|
||||
PRs and issues
|
||||
Reference in New Issue
Block a user