From 93f7304c6db55d6bc94d118992b7af3b397f88d2 Mon Sep 17 00:00:00 2001 From: Florin Barbu Date: Thu, 17 Sep 2026 17:56:37 +0300 Subject: [PATCH] docs(qa): add 2026 Q4 commitments and tasks --- content/qa/ift/2026q4-nim-libp2p-testing.md | 54 ++++++++ content/qa/index.md | 21 +++ content/qa/logos/2026q4-lez-fuzz-testing.md | 38 ++++++ content/qa/logos/2026q4-lez-sequencing.md | 36 +++++ content/qa/logos/2026q4-logos-basecamp.md | 73 ++++++++++ content/qa/logos/2026q4-logos-core.md | 53 ++++++++ content/qa/logos/2026q4-messaging-testing.md | 54 ++++++++ .../qa/logos/2026q4-rfp-lambda-prizes-qa.md | 56 ++++++++ .../qa/logos/2026q4-source-code-level-qa.md | 43 ++++++ content/qa/logos/2026q4-specs.md | 54 ++++++++ .../2026q4-status-go-functional-testing.md | 56 ++++++++ content/qa/status/2026q4-status-qa-desktop.md | 127 ++++++++++++++++++ content/qa/status/2026q4-status-qa-mobile.md | 112 +++++++++++++++ 13 files changed, 777 insertions(+) create mode 100644 content/qa/ift/2026q4-nim-libp2p-testing.md create mode 100644 content/qa/logos/2026q4-lez-fuzz-testing.md create mode 100644 content/qa/logos/2026q4-lez-sequencing.md create mode 100644 content/qa/logos/2026q4-logos-basecamp.md create mode 100644 content/qa/logos/2026q4-logos-core.md create mode 100644 content/qa/logos/2026q4-messaging-testing.md create mode 100644 content/qa/logos/2026q4-rfp-lambda-prizes-qa.md create mode 100644 content/qa/logos/2026q4-source-code-level-qa.md create mode 100644 content/qa/logos/2026q4-specs.md create mode 100644 content/qa/status/2026q4-status-go-functional-testing.md create mode 100644 content/qa/status/2026q4-status-qa-desktop.md create mode 100644 content/qa/status/2026q4-status-qa-mobile.md diff --git a/content/qa/ift/2026q4-nim-libp2p-testing.md b/content/qa/ift/2026q4-nim-libp2p-testing.md new file mode 100644 index 0000000000..6e8e304554 --- /dev/null +++ b/content/qa/ift/2026q4-nim-libp2p-testing.md @@ -0,0 +1,54 @@ +--- +title: Nim Libp2p Testing +tags: + - "2026q4" + - "qa" + - "ift" +draft: false +description: Add dial ranking and backoff coverage and maintain nim-libp2p test reliability. +--- + +`ift-ts:qa:ift:2026q4-nim-libp2p-testing` + +## Description + +Continue nim-libp2p QA with coverage for opt-in dial ranking and backoffs carried over from Q3. +Maintain existing tests as the library evolves and investigate regressions and flaky scenarios. + +## Task List + +### Opt-in Dial Ranking and Backoffs Testing + +* fully qualified name: `ift-ts:qa:ift:2026q4-nim-libp2p-testing:opt-in-dial-ranking-and-backoffs` +* owner: radek +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Implement tests for opt-in dial ranking and backoff behavior. +Cover address and transport preference, concurrent dial cancellation, failed-address backoffs, and compatibility when the feature is disabled, in coordination with the P2P team. + +#### Deliverables + +- PRs adding unit and integration tests for dial ranking and backoffs. +- Tracked defects and coverage gaps found during validation. + +### Maintenance + +* fully qualified name: `ift-ts:qa:ift:2026q4-nim-libp2p-testing:maintenance` +* owner: radek +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Provide ongoing QA maintenance for nim-libp2p, including regression fixes, flaky-test investigation, and test updates required by upstream changes. +Handle issue-driven validation that does not require a separate feature-specific task. + +#### Deliverables + +- PRs maintaining tests and resolving failures or flaky scenarios. +- Regression findings and verification results linked to tracked issues. diff --git a/content/qa/index.md b/content/qa/index.md index 5713b53900..6ed96b2e79 100644 --- a/content/qa/index.md +++ b/content/qa/index.md @@ -8,6 +8,27 @@ tags: [[qa/preview|Roadmap Preview]] +## 2026q4 `ift-ts:qa:` +--- + +### `ift` +* [[qa/ift/2026q4-nim-libp2p-testing|nim-libp2p-testing ]] + +### `status:` +* [[qa/status/2026q4-status-go-functional-testing|status-go-functional-testing ]] +* [[qa/status/2026q4-status-qa-desktop|status-qa-desktop ]] +* [[qa/status/2026q4-status-qa-mobile|status-qa-mobile ]] + +### `logos:` +* [[qa/logos/2026q4-logos-basecamp|logos-basecamp ]] +* [[qa/logos/2026q4-logos-core|logos-core ]] +* [[qa/logos/2026q4-rfp-lambda-prizes-qa|rfp-lambda-prizes-qa ]] +* [[qa/logos/2026q4-lez-fuzz-testing|lez-fuzz-testing ]] +* [[qa/logos/2026q4-lez-sequencing|lez-sequencing ]] +* [[qa/logos/2026q4-messaging-testing|messaging-testing ]] +* [[qa/logos/2026q4-source-code-level-qa|source-code-level-qa ]] +* [[qa/logos/2026q4-specs|specs ]] + ## 2026q3 `ift-ts:qa:` --- diff --git a/content/qa/logos/2026q4-lez-fuzz-testing.md b/content/qa/logos/2026q4-lez-fuzz-testing.md new file mode 100644 index 0000000000..5fb44b99d2 --- /dev/null +++ b/content/qa/logos/2026q4-lez-fuzz-testing.md @@ -0,0 +1,38 @@ +--- +title: Logos LEZ Fuzz Testing +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Maintain LEZ fuzz targets, corpus automation, and CI reliability as the implementation evolves. +--- + +`ift-ts:qa:logos:2026q4-lez-fuzz-testing` + +## Description + +Continue maintaining the LEZ fuzz testing framework in Q4. +Keep targets compatible with upstream changes and preserve useful corpus handling, automated execution, and regression coverage. + +## Task List + +### Framework maintenance + +* fully qualified name: `ift-ts:qa:logos:2026q4-lez-fuzz-testing:framework-maintenance` +* owner: Roman +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +- Maintain existing fuzz targets as LEZ code and interfaces change. +- Extend or adjust targets for newly exposed execution paths, invariants, or regressions. +- Maintain corpus update automation and CI execution, documenting infrastructure constraints when they arise. + +#### Deliverables + +- PRs maintaining or extending fuzz targets and regression coverage. +- Corpus automation and CI maintenance changes. +- Tracked findings and documented execution or infrastructure gaps. diff --git a/content/qa/logos/2026q4-lez-sequencing.md b/content/qa/logos/2026q4-lez-sequencing.md new file mode 100644 index 0000000000..8ddca5f67a --- /dev/null +++ b/content/qa/logos/2026q4-lez-sequencing.md @@ -0,0 +1,36 @@ +--- +title: Logos LEZ Sequencing +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Complete the remaining planned Cucumber test coverage for Logos Execution Zone sequencing. +--- + +`ift-ts:qa:logos:2026q4-lez-sequencing` + +## Description + +Continue automated behavioral testing for Logos Execution Zone sequencing, building on the Cucumber scenarios introduced in Q3. +At Q4 planning, 63 of the 128 planned tests remain to be written. + +## Task List + +### Cucumber tests + +* fully qualified name: `ift-ts:qa:logos:2026q4-lez-sequencing:cucumber-tests` +* owner: Roman +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Implement the remaining 63 tests from the 128-test LEZ sequencing plan. +Continue coverage of sequencer registration and related sequencing behavior, adapting scenarios to implementation changes and recording defects or missing prerequisites. + +#### Deliverables + +- PRs implementing the remaining 63 planned Cucumber tests. +- Updated coverage tracking and issues for sequencing defects or blocked scenarios. diff --git a/content/qa/logos/2026q4-logos-basecamp.md b/content/qa/logos/2026q4-logos-basecamp.md new file mode 100644 index 0000000000..11fb7dfd98 --- /dev/null +++ b/content/qa/logos/2026q4-logos-basecamp.md @@ -0,0 +1,73 @@ +--- +title: Logos Basecamp QA +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Expand Basecamp MCP coverage, validate releases, and maintain existing automated tests. +--- + +`ift-ts:qa:logos:2026q4-logos-basecamp` + +## Description + +Continue the Logos Basecamp MCP testing work from Q3, expanding automated UI integration coverage for preparation, installation navigation, and workspace application lifecycle behavior. +At Q4 planning, 61 of the 78 planned tests remain to be written. +Validate release artifacts and maintain the existing smoke, UI, sandbox, and doctest coverage as Basecamp evolves. + +## Task List + +### MCP tests + +* fully qualified name: `ift-ts:qa:logos:2026q4-logos-basecamp:mcp-tests` +* owner: Roman +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Implement the remaining 61 tests from the 78-test Basecamp MCP plan. +Keep new scenarios compatible with the existing test framework and track any scope changes or blockers as Basecamp evolves. + +#### Deliverables + +- PRs implementing the remaining 61 planned MCP tests. +- Updated coverage tracking and issues for defects or blocked scenarios found during implementation. + +### Release validation + +* fully qualified name: `ift-ts:qa:logos:2026q4-logos-basecamp:release-validation` +* owner: TBD +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Validate Basecamp release artifacts and confirm the application starts cleanly on supported platforms. +Run release smoke checks, report defects and release risks, and verify fixes. + +#### Deliverables + +- Release validation checklists and test reports for the builds tested during Q4. +- Tracked release defects and verification results. + +### Test coverage and maintenance + +* fully qualified name: `ift-ts:qa:logos:2026q4-logos-basecamp:maintenance` +* owner: Roman +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Maintain and extend Basecamp smoke, UI, sandbox, and doctest coverage as the project evolves. +Investigate failing or flaky tests, adapt existing scenarios to application changes, and add regression coverage where needed. + +#### Deliverables + +- PRs maintaining the existing suites and adding targeted regression tests. +- Tracked application or test-framework defects and verification results. diff --git a/content/qa/logos/2026q4-logos-core.md b/content/qa/logos/2026q4-logos-core.md new file mode 100644 index 0000000000..31f4481264 --- /dev/null +++ b/content/qa/logos/2026q4-logos-core.md @@ -0,0 +1,53 @@ +--- +title: Logos Core QA +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Validate Logos Core and establish automated testing foundations. +--- + +`ift-ts:qa:logos:2026q4-logos-core` + +## Description + +Continue the Logos Core QA scope from Q3: evaluate stability, feature completeness, and integration risks, and establish automated coverage that can run in CI. + +## Task List + +### Evaluate and test Logos Core + +* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:evaluate` +* owner: radek +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +- Review shipped scope for Logos Core and create a focused acceptance checklist. +- Log defects and gaps with priority/severity and expected fixes or LIP clarifications. + +#### Deliverables + +- Test reports summarizing coverage, findings, and confidence level. +- GitHub issues for discovered defects or specification mismatches. + +### Establish automated testing framework + +* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:automation-framework` +* owner: radek +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +- Select or adapt a harness suitable for Logos Core, including test runner, fixtures, and environment orchestration. +- Implement automated scenarios covering the initial feature set and stability checks, and integrate their execution into CI. + +#### Deliverables + +- PRs establishing or adapting the testing framework and CI execution. +- Automated scenarios for the initial Logos Core feature set and stability checks. diff --git a/content/qa/logos/2026q4-messaging-testing.md b/content/qa/logos/2026q4-messaging-testing.md new file mode 100644 index 0000000000..6308477e4b --- /dev/null +++ b/content/qa/logos/2026q4-messaging-testing.md @@ -0,0 +1,54 @@ +--- +title: Messaging Testing +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Maintain messaging testing frameworks and continue migrating interop tests into Logos Delivery. +--- + +`ift-ts:qa:logos:2026q4-messaging-testing` + +## Description + +Continue improving messaging test reliability by maintaining existing frameworks and migrating the remaining interop tests into the Logos Delivery repository. +Adapt tests to messaging component changes, address regressions, and keep coverage useful as the implementation evolves. + +## Task List + +### Interop migration + +* fully qualified name: `ift-ts:qa:logos:2026q4-messaging-testing:interop-migration` +* owner: radek +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Continue the Q3 migration of messaging interop tests into the Logos Delivery repository. +Port the remaining scenarios to the repository's E2E workflow, preserve relevant protocol coverage, and resolve failures or gaps exposed by the migration. + +#### Deliverables + +- PRs migrating remaining interop scenarios and integrating them into the Logos Delivery test workflow. +- Tracked regressions and remaining coverage gaps identified during migration. + +### Maintenance + +* fully qualified name: `ift-ts:qa:logos:2026q4-messaging-testing:maintenance` +* owner: aya +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Provide ongoing maintenance of messaging testing frameworks. +Update tests for messaging component changes, investigate failing or flaky tests, address regressions, and make minor framework improvements needed to keep the suites reliable. + +#### Deliverables + +- PRs maintaining messaging tests, fixing failures, and improving framework reliability. +- Tracked messaging or test-framework issues found during maintenance. diff --git a/content/qa/logos/2026q4-rfp-lambda-prizes-qa.md b/content/qa/logos/2026q4-rfp-lambda-prizes-qa.md new file mode 100644 index 0000000000..10f8e19798 --- /dev/null +++ b/content/qa/logos/2026q4-rfp-lambda-prizes-qa.md @@ -0,0 +1,56 @@ +--- +title: RFP and Lambda Prizes QA +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Provide QA for Logos RFP deliverables and Lambda Prizes submissions against agreed requirements. +--- + +`ift-ts:qa:logos:2026q4-rfp-lambda-prizes-qa` + +## Description + +Support Logos RFP and Lambda Prizes work by evaluating delivered software against the relevant brief and agreed acceptance criteria. +Define concrete testing scope with the program and project owners as deliverables become available, record defects and coverage gaps, and verify fixes. + +## Task List + +### RFP deliverables QA + +* fully qualified name: `ift-ts:qa:logos:2026q4-rfp-lambda-prizes-qa:rfp-qa` +* owner: TBD +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +- Review the requirements and acceptance criteria for RFP deliverables selected for QA with the program owners. +- Prepare a focused checklist and test delivered functionality, including integration with Logos components where relevant. +- Report defects and missing requirements, verify fixes, and document remaining limitations for acceptance review. + +#### Deliverables + +- Acceptance checklists and test reports for the RFP deliverables reviewed during Q4. +- Tracked defects, verification results, and remaining coverage gaps. + +### Lambda Prizes submissions QA + +* fully qualified name: `ift-ts:qa:logos:2026q4-rfp-lambda-prizes-qa:lambda-prizes-qa` +* owner: TBD +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +- Agree the QA scope for selected Lambda Prizes submissions with the program owners using each submission's brief and requirements. +- Reproduce setup and key user flows, test claimed functionality, and evaluate relevant Logos integrations. +- Report defects and gaps, verify fixes when available, and provide testing evidence for the program's review. + +#### Deliverables + +- Test checklists and evaluation reports for the Lambda Prizes submissions reviewed during Q4. +- Tracked defects, reproduction steps, and verification results. diff --git a/content/qa/logos/2026q4-source-code-level-qa.md b/content/qa/logos/2026q4-source-code-level-qa.md new file mode 100644 index 0000000000..7cc2c0ee1b --- /dev/null +++ b/content/qa/logos/2026q4-source-code-level-qa.md @@ -0,0 +1,43 @@ +--- +title: Source Code Level QA +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Prototype an AI code analysis system for bug discovery, independent review, precise classification, and reproducible findings. +--- + +`ift-ts:qa:logos:2026q4-source-code-level-qa` + +## Description + +Build an AI code analysis system prototype that helps discover new bugs quickly and turns findings into actionable issues. +Use a second agent to independently review candidate findings and reduce false positives, then provide precise classifications and fix proposals. +Generate proofs or exploit reproductions for high-severity issues and regression tests where possible. + +## Task List + +### System prototype + +* fully qualified name: `ift-ts:qa:logos:2026q4-source-code-level-qa:system-prototype` +* owner: Roman +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Prototype an AI code analysis workflow covering: +- Fast discovery of new bugs through agent-assisted code analysis. +- Independent cross-review by a second agent to challenge findings and reduce false positives. +- Precise issue classification, including impact, severity, affected scope, supporting code evidence, and a proposed fix. Use [LEZ issue #866](https://github.com/logos-blockchain/logos-execution-zone/issues/866) as an example of the expected reporting detail. +- Proof or exploit generation to reproduce and demonstrate high-severity findings. +- Regression test creation where possible, so confirmed bugs can be detected automatically in future changes. + +#### Deliverables + +- A working prototype and documentation for the discovery, cross-review, and reporting workflow. +- Classified findings with supporting evidence, second-agent review results, and fix proposals. +- Reproducible proofs or exploits for high-severity findings, with any reproduction limitations recorded. +- Regression test PRs where feasible, with remaining test coverage gaps documented. diff --git a/content/qa/logos/2026q4-specs.md b/content/qa/logos/2026q4-specs.md new file mode 100644 index 0000000000..35eaaec2f8 --- /dev/null +++ b/content/qa/logos/2026q4-specs.md @@ -0,0 +1,54 @@ +--- +title: Logos Specs +tags: + - "2026q4" + - "qa" + - "logos" +draft: false +description: Maintain the LIP index and review Logos specifications as part of the QA service unit. +--- + +`ift-ts:qa:logos:2026q4-specs` + +## Description + +Continue supporting Logos specification quality through recurring LIP maintenance and review of specifications used by Logos teams. +Keep published documents consistent, usable by developers, and aligned with feedback from specification owners. + +## Task List + +### LIP Maintenance + +* fully qualified name: `ift-ts:qa:logos:2026q4-specs:lip-maintenance` +* owner: florin +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Maintain lip.logos.co through routine review and cleanup of content consistency, metadata, and publication quality. +Implement site rules, features, and improvements agreed with the teams. + +#### Deliverables + +- PRs correcting content, metadata, and publication issues. +- Site improvements and tracked maintenance issues. + +### Review Specs + +* fully qualified name: `ift-ts:qa:logos:2026q4-specs:review-specs` +* owner: florin +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Review specifications used by Logos teams for clarity, edge cases, and sufficient detail for implementation. +Coordinate review comments and approvals with specification owners and follow up on identified gaps. + +#### Deliverables + +- Specification reviews, comments, and approvals. +- Issues and PRs addressing specification gaps, corrections, or publication updates. diff --git a/content/qa/status/2026q4-status-go-functional-testing.md b/content/qa/status/2026q4-status-go-functional-testing.md new file mode 100644 index 0000000000..25d54290f9 --- /dev/null +++ b/content/qa/status/2026q4-status-go-functional-testing.md @@ -0,0 +1,56 @@ +--- +title: Status Go Functional Testing +tags: + - "2026q4" + - "qa" + - "status" +draft: false +description: Maintain status-go functional tests and expand backend coverage through status-backend. +--- + +`ift-ts:qa:status:2026q4-status-go-functional-testing` + +## Description + +Continue backend functional testing through status-backend to support Status releases and catch regressions below the desktop and mobile UI layers. + +Proposed Q4 scope: the planning discussion reserves one or two backend functional-testing tasks without specifying their details. +The maintenance and coverage tasks below continue the Q3 direction; concrete scenarios and ownership remain to be defined. + +## Task List + +### Maintenance + +* fully qualified name: `ift-ts:qa:status:2026q4-status-go-functional-testing:maintenance` +* owner: TBD +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Maintain the status-go functional test suite as backend APIs and behavior evolve. +Investigate failing or flaky tests, update fixtures and the Python SDK where needed, and assist with test changes in pull requests. + +#### Deliverables + +- PRs fixing functional test failures and maintaining fixtures, SDK helpers, and CI execution. +- Tracked backend or test-framework defects found during maintenance. + +### Functional test coverage + +* fully qualified name: `ift-ts:qa:status:2026q4-status-go-functional-testing:coverage` +* owner: TBD +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Add functional tests for prioritized backend coverage gaps and new Status release behavior using status-backend. +Select concrete scenarios from the existing backlog and issues found during desktop and mobile testing, including delivery, synchronization, or send behavior where backend-level coverage is appropriate. + +#### Deliverables + +- PRs adding backend functional tests for selected scenarios and regressions. +- Tracked backend issues and remaining coverage gaps. diff --git a/content/qa/status/2026q4-status-qa-desktop.md b/content/qa/status/2026q4-status-qa-desktop.md new file mode 100644 index 0000000000..5efa2fa332 --- /dev/null +++ b/content/qa/status/2026q4-status-qa-desktop.md @@ -0,0 +1,127 @@ +--- +title: Status QA Desktop +tags: + - "2026q4" + - "qa" + - "status" +draft: false +description: Support Status Desktop releases, maintain automated tests, and expand feature and performance coverage. +--- + +`ift-ts:qa:status:2026q4-status-qa-desktop` + +## Description + +Collaborate with the Status team on manual and automated QA for ongoing Desktop releases, including at least 2.40 and 2.41. +Maintain the existing test suite and expand coverage for new features as release scope becomes clear. +Keep feature automation flexible as priorities and delivery dates change; select concrete scenarios with the Status team as the automation backlog is clarified. +Continue Windows performance testing. macOS and Linux performance work remains tentative, subject to infrastructure availability and prioritization. + +## Task List + +### Release Testing + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-desktop:release-testing` +* owner: nastya +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Support ongoing Status Desktop releases, including at least 2.40 and 2.41, with exploratory testing, regression testing, and validation of new features. +Report bugs and release risks and verify fixes with the Status team. + +#### Deliverables + +- Release test reports and tracked issues for Status Desktop 2.40, 2.41, and other releases tested during Q4. + +### Maintenance + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-desktop:maintenance` +* owner: nastya +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Investigate and fix failing nightly tests, address flaky scenarios, and keep the suite compatible with Status Desktop changes. +Assist developers with test changes in pull requests. + +#### Deliverables + +- PRs fixing nightly failures and updating existing tests for application changes. +- Tracked product or framework issues found while maintaining the suite. + +### Performance tests for desktop application on Windows + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-desktop:windows-performance-tests` +* owner: nastya +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Continue creating Windows performance tests for the main Status Desktop user flows. +Maintain useful measurements for comparing releases and detecting performance regressions. + +#### Deliverables + +- PRs extending Windows performance test coverage. +- Performance measurements and tracked regressions. + +### New tests + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-desktop:new-tests` +* owner: nastya +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Add automated coverage for new Status Desktop features, including those delivered in 2.40 and 2.41. +Choose scenarios as feature scope and the automation backlog are clarified with the Status team, and adjust coverage when features are delayed or changed. + +#### Deliverables + +- PRs adding automated tests for new release features. +- Tracked coverage gaps or automation constraints for features under test. + +### Performance tests for desktop application on Mac + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-desktop:mac-performance-tests` +* owner: nastya +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Tentative: confirm with Infra whether a supported environment for macOS performance testing can be provided. +If the infrastructure dependency is resolved and the work is prioritized, add performance tests for the main Status Desktop user flows on macOS. + +#### Deliverables + +- A documented infrastructure decision and any remaining constraints. +- Performance test PRs and measurements if the work proceeds. + +### Performance tests for desktop application on Linux + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-desktop:linux-performance-tests` +* owner: nastya +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Tentative: confirm whether Linux performance testing remains a Q4 priority and identify the scenarios worth covering. +If prioritized, add performance tests for the main Status Desktop user flows on Linux. + +#### Deliverables + +- A documented scope and prioritization decision. +- Performance test PRs and measurements if the work proceeds. diff --git a/content/qa/status/2026q4-status-qa-mobile.md b/content/qa/status/2026q4-status-qa-mobile.md new file mode 100644 index 0000000000..3bc4cad735 --- /dev/null +++ b/content/qa/status/2026q4-status-qa-mobile.md @@ -0,0 +1,112 @@ +--- +title: Status QA Mobile +tags: + - "2026q4" + - "qa" + - "status" +draft: false +description: Support Status Mobile releases, maintain reliable automation, and expand coverage, framework capabilities, and performance testing. +--- + +`ift-ts:qa:status:2026q4-status-qa-mobile` + +## Description + +Support ongoing Status Mobile releases, including at least 2.40 and 2.41, and test the new features in each release. +Keep nightly automation and the per-PR gate reliable, add coverage for existing features, and improve the test harness. +Maintain the performance suite and extend measurements to a loaded existing account. + +## Task List + +### Release testing + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-mobile:release-testing` +* owner: magnus +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Support ongoing Status Mobile releases, including at least 2.40 and 2.41. +Perform exploratory and regression testing, test new features in each release, and report issues and release risks. + +#### Deliverables + +- Release test reports and tracked issues for Status Mobile 2.40, 2.41, and other releases tested during Q4. + +### Maintenance + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-mobile:maintenance` +* owner: magnus +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Investigate and fix failing nightly tests and keep the per-PR gate running as a trusted regression signal. +Address flaky tests and assist developers with test changes in pull requests as the app evolves. + +#### Deliverables + +- PRs fixing nightly failures, flaky tests, and per-PR gate issues. +- Test updates for application changes and tracked product or framework defects. + +### Coverage for existing features + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-mobile:coverage` +* owner: magnus +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Add automated tests for existing Status Mobile features that lack coverage. +Prioritize gaps with the Status team based on user impact and the feasibility of reliable device-level automation. + +#### Deliverables + +- PRs covering previously untested existing features. +- Tracked coverage gaps and any constraints preventing automation. + +### Framework improvements + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-mobile:framework` +* owner: magnus +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Improve the mobile test harness in the following areas: +- iOS build and execution support. +- Repeatable setup and reuse of a loaded existing account. +- Accessibility properties that provide stable locators and assertions. +- App/backend binding checks that detect missing or changed backend methods. +- Backend-peer support for messaging scenarios with a headless second participant. + +#### Deliverables + +- PRs implementing harness improvements and contract checks. +- Setup and usage documentation for iOS, loaded accounts, and backend-peer scenarios. + +### Performance + +* fully qualified name: `ift-ts:qa:status:2026q4-status-qa-mobile:performance` +* owner: magnus +* status: not started +* start-date: 2026/10/01 +* end-date: 2026/12/31 + +#### Description + +Maintain the mobile performance suite and add a loaded-account scenario using the account setup provided by the framework task. +Keep measurements useful for comparing releases and identifying performance regressions. + +#### Deliverables + +- PRs maintaining the performance suite and adding loaded-account measurements. +- Performance reports and tracked regressions.