Skip to content

[Feature](tests): add SDK compatibility e2e suite#835

Open
tinklone wants to merge 4 commits into
masterfrom
feat/sdk-compat-e2e-tests
Open

[Feature](tests): add SDK compatibility e2e suite#835
tinklone wants to merge 4 commits into
masterfrom
feat/sdk-compat-e2e-tests

Conversation

@tinklone

@tinklone tinklone commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Add a backend-neutral pytest E2E suite for CubeSandbox and E2B Python SDK compatibility.
  • Cover lifecycle, commands, filesystem, and code execution flows with backend capability markers and capability-domain test directories.
  • Default live PR-gate runs to the CubeSandbox backend, with optional dual SDK compatibility via SDK_E2E_BACKENDS=e2b,cubesandbox.
  • Add preflight checks and per-test JSONL result reporting for better live-environment diagnostics.
  • Document live environment setup, local CA trust via SSL_CERT_FILE, and E2B TLS fallback behavior.

Test plan

  • python3 -m pytest --collect-only -q collected 18 default CubeSandbox backend cases.
  • SDK_E2E_BACKENDS=e2b,cubesandbox python3 -m pytest --collect-only -q collected 36 dual-backend cases.
  • python3 -m pytest -q skipped all 18 default cases without --run-e2e.

@charliecgxu charliecgxu requested a review from lkml-likexu July 9, 2026 05:51
@lkml-likexu lkml-likexu added the area/CI Continuous Integration testing issue or flake label Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add README_zh.md ?

SDK_E2E_BACKENDS=e2b,cubesandbox pytest --run-e2e -m "p0 or p1"

# Broader regression
SDK_E2E_BACKENDS=e2b,cubesandbox pytest --run-e2e -m "p0 or p1 or p2"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-m "smoke,p0,p1,p2,p3" ? or -m "smoke AND p0 ..."


```bash
export SSL_CERT_FILE=/root/.local/share/mkcert/rootCA.pem
export SDK_E2E_E2B_INSECURE_TLS=false

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

miss E2B_API_KEY ?

@tinklone tinklone added the iter Belongs to iteration label Jul 10, 2026
@tinklone tinklone self-assigned this Jul 10, 2026
@tinklone tinklone changed the title feat(tests): add SDK compatibility e2e suite [Feature](tests): add SDK compatibility e2e suite Jul 10, 2026
maxlong added 3 commits July 10, 2026 14:35
Add a backend-neutral pytest suite for validating CubeSandbox and E2B Python SDK compatibility across lifecycle, commands, filesystem, and code execution flows.

Signed-off-by: maxlong <maxlong@tencent.com>
Default live SDK compatibility runs to the CubeSandbox backend, add preflight checks, and record per-test JSONL results for better PR gate diagnostics.

Signed-off-by: maxlong <maxlong@tencent.com>
Reorganize the SDK compatibility E2E README around setup, execution scope, environment, preflight, reporting, and capability-domain layout.

Signed-off-by: maxlong <maxlong@tencent.com>
Expand lifecycle scenarios for connect, pause/resume, timeout, auto-resume, auto-kill, and cleanup. Add bounded, redacted SDK operation traces so failures retain actionable request and response context without leaking secrets.

Signed-off-by: maxlong <maxlong@tencent.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@tinklone tinklone force-pushed the feat/sdk-compat-e2e-tests branch from f6b1cd3 to 1c67713 Compare July 10, 2026 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/CI Continuous Integration testing issue or flake iter Belongs to iteration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants