Skip to content

Documentation update#6290

Open
nccatoni wants to merge 11 commits intomainfrom
nccatoni/doc
Open

Documentation update#6290
nccatoni wants to merge 11 commits intomainfrom
nccatoni/doc

Conversation

@nccatoni
Copy link
Collaborator

@nccatoni nccatoni commented Feb 12, 2026

Motivation

The current documentation is not very beginner friendly and tend to be quite fragmented

Changes

  • Reorganize the docs/ folder into a clearer structure with four top-level sections: understand/ (concepts, scenarios, weblogs, architecture), execute/ (running tests), edit/ (writing tests), and CI/ (integration)
  • Rewrite the root README.md to serve as a proper landing page with quick start, output guide, and structured documentation links
  • Merge 18 short documentation files (0-19 lines each) into their natural parent pages to reduce fragmentation and improve discoverability
  • Add a new docs/understand/README.md entry point
  • Update all internal cross-references (docs, root README, cursor rules) to match the new file locations

Details

Root README rewrite

The root README.md was restructured into a concise landing page:

  • Quick start: Replaced the multi-step "Getting Started" section with a single copy-pasteable 3-step code block (setup, build, run)
  • Reading the output: Added a new section with a table explaining pytest symbols (., F, x, X, s) and what they mean, so newcomers can understand results immediately
  • Documentation index: Replaced the old mix of prose and links with organized tables grouping docs by activity (understand, run, write, CI, internals, AI tooling)
  • Contributing: Added a new section with a table mapping common tasks ("activate a test", "add a weblog", etc.) to the right guide
  • Technologies: Condensed the technology list from a bullet-heavy section into a single sentence with a collapsible repository structure
  • Ownership: Inlined the ownership rules (previously in a separate who-is-the-owner.md) directly into the README

Directory reorganization (32 file moves)

From To Rationale
docs/scenarios/* docs/understand/scenarios/* Scenarios are conceptual, belong under "understand"
docs/architecture/overview.md docs/understand/architecture.md Architecture is conceptual
docs/weblog/* docs/understand/weblogs/* Weblogs are conceptual
docs/lib-injection/*.png docs/understand/images/* Co-locate images with the pages that use them
docs/internals/test-flow.md docs/understand/test-flow.md Test flow is a concept, not an internal
docs/internals/{agent,backend,library}-interface-*.md docs/edit/* Validation API references are used when writing tests
docs/internals/flushing.md docs/edit/flushing.md Flushing guidance is for test authors

Short file consolidation (18 files deleted)

Deleted file Merged into
docs/internals/history.md (0 lines) docs/internals/README.md (inlined)
docs/internals/requirements.md (1 line) Deleted -- outdated, already covered by root README
docs/execute/skip-empty-scenario.md (3 lines) docs/execute/run.md
docs/execute/force-execute.md (6 lines) docs/execute/run.md
docs/execute/xfail-strict.md (11 lines) docs/execute/test-outcomes.md
docs/edit/troubleshooting.md (13 lines) docs/edit/README.md (logger) + docs/execute/troubleshooting.md (runtime)
docs/internals/pytest.md (5 lines) docs/edit/README.md
docs/execute/dd-trace-debug.md (19 lines) docs/execute/troubleshooting.md
docs/edit/CI-and-scenarios.md (3 lines) docs/CI/system-tests-ci.md
docs/CI/gitlab-ci.md (13 lines) docs/CI/README.md
docs/scenarios/lifecycle.md (9 lines) docs/understand/scenarios/README.md
docs/scenarios/IPv6.md (5 lines) docs/understand/scenarios/README.md
docs/scenarios/go_proxies_envoy_haproxy.md (16 lines) docs/understand/scenarios/README.md
docs/internals/parametric-life-cycle.md (7 lines) docs/understand/scenarios/parametric.md
docs/scenarios/docker_fixtures.md (9 lines) docs/understand/scenarios/parametric.md
docs/internals/recreating_protobuf_files.md (4 lines) docs/internals/README.md (inlined)
docs/ai/cursor-specialized-prompts.md (10 lines) docs/ai/ai-tools-integration-guide.md
docs/who-is-the-owner.md (11 lines) Root README.md

Workflow

  1. ⚠️ Create your PR as draft ⚠️
  2. Work on you PR until the CI passes
  3. Mark it as ready for review
    • Test logic is modified? -> Get a review from RFC owner.
    • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

  • Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
  • A docker base image is modified?
    • the relevant build-XXX-image label is present
  • A scenario is added, removed or renamed?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 12, 2026

CODEOWNERS have been resolved as:

docs/understand/README.md                                               @DataDog/system-tests-core
.cursor/rules/aws-ssi-testing.mdc                                       @DataDog/system-tests-core
.cursor/rules/end-to-end-testing.mdc                                    @DataDog/system-tests-core
.cursor/rules/fine-tuning-guidance.mdc                                  @DataDog/system-tests-core
.cursor/rules/k8s-ssi.mdc                                               @DataDog/system-tests-core
.cursor/rules/repository-structure.mdc                                  @DataDog/system-tests-core
.cursor/rules/system-tests-overview.mdc                                 @DataDog/system-tests-core
README.md                                                               @DataDog/system-tests-core
docs/CI/README.md                                                       @DataDog/system-tests-core
docs/CI/system-tests-ci.md                                              @DataDog/system-tests-core
docs/README.md                                                          @DataDog/system-tests-core
docs/ai/ai-prompt-java-endpoint-prompt.md                               @DataDog/system-tests-core
docs/ai/ai-tools-integration-guide.md                                   @DataDog/system-tests-core
docs/edit/README.md                                                     @DataDog/system-tests-core
docs/edit/add-new-test.md                                               @DataDog/system-tests-core
docs/edit/enable-test.md                                                @DataDog/system-tests-core
docs/execute/README.md                                                  @DataDog/system-tests-core
docs/execute/run.md                                                     @DataDog/system-tests-core
docs/execute/test-outcomes.md                                           @DataDog/system-tests-core
docs/execute/troubleshooting.md                                         @DataDog/system-tests-core
docs/internals/README.md                                                @DataDog/system-tests-core
tests/integration_frameworks/README.md                                  @DataDog/system-tests-core
tests/k8s_lib_injection/README.md                                       @DataDog/system-tests-core
tests/parametric/README.md                                              @DataDog/system-tests-core @DataDog/apm-sdk-capabilities
tests/parametric/test_parametric_endpoints.py                           @DataDog/system-tests-core @DataDog/apm-sdk-capabilities
utils/build/virtual_machine/weblogs/weblog_provision_schema.yml         @DataDog/system-tests-core
utils/scripts/ssi_wizards/aws_onboarding_wizard.sh                      @DataDog/system-tests-core
utils/virtual_machine/aws_provider.py                                   @DataDog/system-tests-core
docs/edit/agent-interface-validation-methods.md                         @DataDog/system-tests-core
docs/edit/backend-interface-validation-methods.md                       @DataDog/system-tests-core
docs/edit/flushing.md                                                   @DataDog/system-tests-core
docs/edit/library-interface-validation-methods.md                       @DataDog/system-tests-core
docs/edit/parametric_contributing.md                                    @DataDog/system-tests-core
docs/understand/architecture.md                                         @DataDog/system-tests-core
docs/understand/images/aws_onboarding_wizard.png                        @DataDog/system-tests-core
docs/understand/images/docker_ssi_lib_injections_folders.png            @DataDog/system-tests-core
docs/understand/images/k8s_djm.png                                      @DataDog/system-tests-core
docs/understand/images/k8s_lib_injections_folders.png                   @DataDog/system-tests-core
docs/understand/images/k8s_lib_injections_log_folders.png               @DataDog/system-tests-core
docs/understand/images/lib-injection-folder.png                         @DataDog/system-tests-core
docs/understand/images/lib-injection-tags.png                           @DataDog/system-tests-core
docs/understand/images/lib-injection-tests.png                          @DataDog/system-tests-core
docs/understand/images/onboarding_overview.png                          @DataDog/system-tests-core
docs/understand/images/ssi_lib_injections_folders.png                   @DataDog/system-tests-core
docs/understand/images/ssi_lib_injections_log_folders.png               @DataDog/system-tests-core
docs/understand/scenarios/README.md                                     @DataDog/system-tests-core
docs/understand/scenarios/aws_lambda.md                                 @DataDog/system-tests-core
docs/understand/scenarios/docker_ssi.md                                 @DataDog/system-tests-core
docs/understand/scenarios/integration_frameworks.md                     @DataDog/system-tests-core
docs/understand/scenarios/k8s_injector_dev.md                           @DataDog/system-tests-core
docs/understand/scenarios/k8s_lib_injection.md                          @DataDog/system-tests-core
docs/understand/scenarios/k8s_library_injection_overview.md             @DataDog/system-tests-core
docs/understand/scenarios/onboarding.md                                 @DataDog/system-tests-core
docs/understand/scenarios/onboarding_provision_section.md               @DataDog/system-tests-core
docs/understand/scenarios/parametric.md                                 @DataDog/system-tests-core
docs/understand/test-flow.md                                            @DataDog/system-tests-core
docs/understand/test_template.py                                        @DataDog/system-tests-core
docs/understand/weblogs/README.md                                       @DataDog/system-tests-core
docs/understand/weblogs/end-to-end_weblog.md                            @DataDog/system-tests-core
docs/understand/weblogs/graphql_weblog.md                               @DataDog/system-tests-core
docs/CI/gitlab-ci.md                                                    @DataDog/system-tests-core
docs/ai/cursor-specialized-prompts.md                                   @DataDog/system-tests-core
docs/edit/CI-and-scenarios.md                                           @DataDog/system-tests-core
docs/edit/troubleshooting.md                                            @DataDog/system-tests-core
docs/execute/dd-trace-debug.md                                          @DataDog/system-tests-core
docs/execute/force-execute.md                                           @DataDog/system-tests-core
docs/execute/skip-empty-scenario.md                                     @DataDog/system-tests-core
docs/execute/xfail-strict.md                                            @DataDog/system-tests-core
docs/internals/history.md                                               @DataDog/system-tests-core
docs/internals/parametric-life-cycle.md                                 @DataDog/system-tests-core
docs/internals/pytest.md                                                @DataDog/system-tests-core
docs/internals/recreating_protobuf_files.md                             @DataDog/system-tests-core
docs/internals/requirements.md                                          @DataDog/system-tests-core
docs/scenarios/IPv6.md                                                  @DataDog/system-tests-core
docs/scenarios/docker_fixtures.md                                       @DataDog/system-tests-core
docs/scenarios/go_proxies_envoy_haproxy.md                              @DataDog/system-tests-core
docs/scenarios/lifecycle.md                                             @DataDog/system-tests-core
docs/who-is-the-owner.md                                                @DataDog/system-tests-core

@datadog-datadog-prod-us1

This comment has been minimized.

@nccatoni nccatoni requested a review from cbeauchesne February 18, 2026 12:58
@nccatoni nccatoni marked this pull request as ready for review February 18, 2026 12:59
@nccatoni nccatoni requested review from a team as code owners February 18, 2026 12:59
@nccatoni nccatoni requested review from mabdinur and removed request for a team February 18, 2026 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments