Skip to content

docs: add E2E test running guide - #1697

Open
magic-peach wants to merge 1 commit into
dapr:masterfrom
magic-peach:docs/e2e-test-development-guide
Open

magic-peach wants to merge 1 commit into
dapr:masterfrom
magic-peach:docs/e2e-test-development-guide

Conversation

@magic-peach

Copy link
Copy Markdown

Description

docs/development/development.md had no guidance on running E2E tests: the --tags=e2e requirement, the need to make build first since tests exercise the built binary, or the DAPR_RUNTIME_PINNED_VERSION/DAPR_DASHBOARD_PINNED_VERSION environment variables some standalone tests require. This PR adds tests/docs/running-e2e.md covering those points, per mukundansundar's suggestion on the issue, and links it from the development guide.

Issue reference

Please reference the issue this PR will close: #1313

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Extended the documentation

Notes:

  • Compiles: docs-only change, no code touched.
  • Tests: not applicable.
  • Documentation: this PR is itself the documentation being added.

New contributors hit an opaque failure the first time they try to run
E2E tests, since they need the CLI built first and a couple of pinned
version env vars set that only show up in a code comment. Add a
running-e2e.md under tests/docs per mukundansundar's suggestion on
1313, and link it from the development guide.

Signed-off-by: Akanksha Trehun <akankshatrehun@gmail.com>
@magic-peach
magic-peach requested review from a team as code owners September 6, 2026 14:10
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.

[Proposal] Adding supporting docs for E2E test development under development guide

1 participant