Qa updates - Week 7 of 2025Q1 (#90)

This commit is contained in:
fbarbu15
2025-02-12 12:30:03 +02:00
committed by GitHub
parent a6721014a5
commit 55fdb5a420
5 changed files with 36 additions and 13 deletions

View File

@@ -29,7 +29,7 @@ Implement data availability test plans for the Nomos project at the cluster leve
* fully qualified name: `vac:qa:nomos:2025q1-da-testing:data-integrity-tests`
* owner: romanzac
* status: in progress (80% - Blocked by unfinished dev work on Nomos testnet, preventing tests to run)
* status: in progress (90%)
* start-date: 2025/01/06
* end-date: 2025/01/17

View File

@@ -26,7 +26,7 @@ and performing minor improvements to keep the framework functional and effective
* fully qualified name: `vac:qa:nomos:2025q1-e2e-testing:maintenance`
* owner: romanzac
* status: in progress (20%)
* status: in progress (30%)
* start-date: 2025/01/01
* end-date: 2025/03/31
@@ -39,3 +39,4 @@ investigating and resolving issues, and implementing minor improvements to the t
* [Two node cluster start automation](https://github.com/logos-co/nomos-e2e-tests/pull/1)
* [fix: Temporarily downgrade cargo-binstall to 1.10.19](https://github.com/logos-co/nomos-node/pull/983)
* [chore: Add LogOutput and LogLevel property to Cfgsync config](https://github.com/logos-co/nomos-node/pull/978)
* [chore: Add reconstruct command to nomos-cli](https://github.com/logos-co/nomos-node/pull/994)

View File

@@ -32,7 +32,7 @@ and validating the application of MVDS for improved message delivery reliability
* fully qualified name: `vac:qa:waku:2025q1-direct-message-reliability-testing:functional`
* owner: fbarbu15
* status: in progress (90%)
* status: done
* start-date: 2025/01/06
* end-date: 2025/01/25
@@ -41,16 +41,18 @@ Implement and execute functional tests for direct message flows,
including 1:1 chats and private groups.
#### Deliverables
* PRs with functional test cases
* CI pipelines for automated functional tests
* Documentation outlining tested scenarios
* [Test reliability workflow](https://github.com/status-im/status-go/pull/6236)
* [Test private chat messages](https://github.com/status-im/status-go/pull/6259)
* [reactivate reliability workflow](https://github.com/status-im/status-go/pull/6280)
* [community messages](https://github.com/status-im/status-go/pull/6294)
* [CI RUN](https://github.com/status-im/status-go/actions/runs/13232288117)
### Reliability Testing Under Degraded Network Conditions
* fully qualified name: `vac:qa:waku:2025q1-direct-message-reliability-testing:degraded-network`
* owner: fbarbu15
* status: in progress (80%)
* status: done
* start-date: 2025/01/25
* end-date: 2025/02/15
@@ -60,15 +62,17 @@ Specifically, also ensure messages are automatically retrieved in the Status app
after a network reconnection.
#### Deliverables
* PRs with reliability test cases
* Reports on test results under degraded conditions
* Recommendations for improving message flow resilience
* [Test reliability workflow](https://github.com/status-im/status-go/pull/6236)
* [Test private chat messages](https://github.com/status-im/status-go/pull/6259)
* [reactivate reliability workflow](https://github.com/status-im/status-go/pull/6280)
* [community messages](https://github.com/status-im/status-go/pull/6294)
* [CI RUN](https://github.com/status-im/status-go/actions/runs/13232288117)
### Rate Limit Testing
* fully qualified name: `vac:qa:waku:2025q1-direct-message-reliability-testing:rate-limit`
* owner: fbarbu15
* status: in progress (10%)
* status: in progress (90%)
* start-date: 2025/02/25
* end-date: 2025/03/10
@@ -80,6 +84,21 @@ but TBD when status-backend will support all this.
#### Deliverables
* PRs with new test cases
### IP Change Testing
* fully qualified name: `vac:qa:waku:2025q1-direct-message-reliability-testing:ip-change`
* owner: fbarbu15
* status: not started
* start-date: 2025/02/10
* end-date: 2025/02/17
#### Description
Perform tests to validate how status-backend handes ip change
and if message flow resumes after such event.
#### Deliverables
* PRs with new test cases
### Wakuext One To One Messages
* fully qualified name: `vac:qa:waku:2025q1-direct-message-reliability-testing:wakuext-one-to-one-message`

View File

@@ -40,3 +40,6 @@ investigating and resolving issues, and implementing minor improvements to the t
* [bug: nwaku<->gowaku interop tests started failing at filter subscription](https://github.com/waku-org/nwaku/issues/3263)
* [chore: store fixes](https://github.com/waku-org/waku-interop-tests/pull/101)
* [chore: add reconciliation metrics](https://github.com/waku-org/waku-interop-tests/pull/100)
* [bug: nwaku<->gowaku interop tests fail with only one received message push when multiple messages are sent](https://github.com/waku-org/nwaku/issues/3271)
* [chore: js-waku test report improvements](https://github.com/waku-org/js-waku/pull/2247)
* [chore: store hash fixes](https://github.com/waku-org/waku-interop-tests/pull/104)

View File

@@ -53,7 +53,7 @@ It should also be adaptable to future testing needs.
* fully qualified name: `vac:qa:waku:2025q1-waku-go-bindings-testing:relay`
* owner: aya
* status: in progress (60%)
* status: in progress (80%)
* start-date: 2025/01/20
* end-date: 2025/02/25
@@ -71,7 +71,7 @@ and ensure reliable message propagation across multiple nodes.
* fully qualified name: `vac:qa:waku:2025q1-waku-go-bindings-testing:store`
* owner: aya
* status: not started
* status: in progress (20%)
* start-date: 2025/02/10
* end-date: 2025/03/10