SRVOCF-1070: Update TESTING.md and AGILE.md documentation

[twoGiants]

Summary

• 📚 Update TESTING.md to reflect the test infrastructure changes from SRVOCF-822 (SRVOCF-822: Remove test mocks from list page and clean up naming #144, SRVOCF-822: Replace test mocks with stubs and extract shared test infrastructure #149, SRVOCF-822: Add namespace scoping to function list #155)
• 📚 Update AGILE.md sync ceremonies to match the new schedule
• 🔧 Add TESTING.md checklist item to the PR template

TESTING.md was out of date after the SRVOCF-822 test refactoring. It still described mocking components and hooks with vi.mock, referenced deleted files (testing/msw/, mocks/github.ts), and used "mock" as a catch-all term for all test doubles.

Changes to TESTING.md:

• Add cross-cutting test double terminology table (stub, fake, mock, spy) with frontend and backend examples
• Document the page-first testing approach: no test doubles for components or hooks, only for external boundaries
• Document shared test infrastructure in src/common/testing/ and backend stubs next to their interfaces
• Document the two-boundary test double strategy (MSW for backend API, self-written stubs for OCP SDK)
• Add allowed/forbidden vi.mock patterns with real examples from FunctionsListPage.test.tsx
• Add AAA example, renderHook usage for hook tests, server.boundary() for infinite delays
• Update e2e section: fake GitHub server, new helpers, updated file structure, removed stale page.route section
• Fix incorrect backend stub type names (scmStub to scm.ClientStub, add functions.ClientStub)

Changes to AGILE.md:

• Replace old ceremony schedule with: Tue+Thu weekly syncs, biweekly backlog grooming, review+planning on iteration-end Thu, retrospective on iteration-start Tue
• Simplify facilitator duties to match

Fixes SRVOCF-1070

Checklist

• Updated docs/ARCHITECTURE.md (if there are relevant changes to our layered architecture)
• Updated docs/TESTING.md (if there are relevant changes to our testing framework or setup)

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@twoGiants: This pull request references SRVOCF-1070 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Summary

• 📚 Update TESTING.md to reflect the test infrastructure changes from SRVOCF-822 (SRVOCF-822: Remove test mocks from list page and clean up naming #144, SRVOCF-822: Replace test mocks with stubs and extract shared test infrastructure #149, SRVOCF-822: Add namespace scoping to function list #155)
• 📚 Update AGILE.md sync ceremonies to match the new schedule
• 🔧 Add TESTING.md checklist item to the PR template

TESTING.md was out of date after the SRVOCF-822 test refactoring. It still described mocking components and hooks with vi.mock, referenced deleted files (testing/msw/, mocks/github.ts), and used "mock" as a catch-all term for all test doubles.

Changes to TESTING.md:

• Add cross-cutting test double terminology table (stub, fake, mock, spy) with frontend and backend examples
• Document the page-first testing approach: no test doubles for components or hooks, only for external boundaries
• Document shared test infrastructure in src/common/testing/ and backend stubs next to their interfaces
• Document the two-boundary test double strategy (MSW for backend API, self-written stubs for OCP SDK)
• Add allowed/forbidden vi.mock patterns with real examples from FunctionsListPage.test.tsx
• Add AAA example, renderHook usage for hook tests, server.boundary() for infinite delays
• Update e2e section: fake GitHub server, new helpers, updated file structure, removed stale page.route section
• Fix incorrect backend stub type names (scmStub to scm.ClientStub, add functions.ClientStub)

Changes to AGILE.md:

• Replace old ceremony schedule with: Tue+Thu weekly syncs, biweekly backlog grooming, review+planning on iteration-end Thu, retrospective on iteration-start Tue
• Simplify facilitator duties to match

Fixes SRVOCF-1070

Checklist

• Updated docs/ARCHITECTURE.md (if there are relevant changes to our layered architecture)
• Updated docs/TESTING.md (if there are relevant changes to our testing framework or setup)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[Copilot]

🟡 Changes recommended

There are documentation inconsistencies that can mislead contributors about the current e2e GitHub boundary and refinement ceremony handling.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR updates project documentation to reflect the post SRVOCF-822 testing infrastructure and current team sync cadence, and it adds a docs checklist item to the PR template.

Changes:

• Refresh docs/TESTING.md with updated test double terminology, frontend and backend testing strategy, and current e2e structure.
• Update docs/AGILE.md to match the new ceremony schedule and simplified facilitator duties.
• Add a docs/TESTING.md checklist item to .github/pull_request_template.md.

File summaries

File	Description
docs/TESTING.md	Updates testing guidance to match the current shared test infrastructure and e2e approach.
docs/AGILE.md	Updates ceremony schedule details and facilitator duties.
.github/pull_request_template.md	Adds a checklist item prompting updates to docs/TESTING.md when relevant.

Review details

• Files reviewed: 3/3 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[openshift-merge-bot]

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

• The changed files don't match any pipeline_run_if_changed patterns
• All files match pipeline_skip_if_only_changed patterns
• No pipeline-controlled jobs are defined for the master branch

Use /test ? to see all available tests.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Cragsmann

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Cragsmann]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@twoGiants: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.