Skip to content

test: replace aws-lambda integration tests with RIE-based integration tests - #826

Draft
joeyzhao2018 wants to merge 2 commits into
mainfrom
joey/deprecate-aws-integration-tests
Draft

test: replace aws-lambda integration tests with RIE-based integration tests#826
joeyzhao2018 wants to merge 2 commits into
mainfrom
joey/deprecate-aws-integration-tests

Conversation

@joeyzhao2018

Copy link
Copy Markdown
Contributor

What does this PR do?

Motivation

Testing Guidelines

Additional Notes

Types of Changes

  • Bug fix
  • New feature
  • Breaking change
  • Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

  • This PR's description is comprehensive
  • This PR contains breaking changes that are documented in the description
  • This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
  • This PR impacts documentation, and it has been updated (or a ticket has been logged)
  • This PR's changes are covered by the automated tests
  • This PR collects user input/sensitive content into Datadog
  • This PR passes the integration tests (ask a Datadog member to run the tests)

… serverless-e2e-tests)

The integration_tests/ AWS suite is retired. Its coverage now lives in two
places, each stronger at what it owns:

- Behavior: integration_tests_local/ (docker/RIE, GitHub Actions, per PR) is
  now the behavior oracle — hermetic, contributor-runnable, and strictly
  stronger than the AWS suite at behavior (its goldens preserve span
  meta/metrics keys the AWS normalization stripped wholesale). After #821 and
  #823 it covers every variant the AWS suite pinned, including callback-style
  handlers, fetch, metrics-only mode, payload capture, and the manual-wrap
  no-init path.

- Real-AWS-only signals: the four variants whose value IS the platform —
  esm (published layer zip artifact + ESM loader), sync-metrics (direct-API
  sink to the real intake), http-requests (_X_AMZN_TRACE_ID pass-through +
  real egress), status-code-500s (real API Gateway) — move to a dedicated
  integration-tests-residual suite in serverless-e2e-tests, which deploys
  against published/candidate layer ARNs and keeps the same snapshots and
  byte-identical normalization pipeline.

Deleted here: serverless.yml, the six top-level handlers, all 450 snapshots,
and scripts/run_integration_tests.sh (459 files). Kept: input_events/,
parse-json.js, and container/ — the local suite references the first two and
uses container/ as fixture; a new integration_tests/README.md documents this.

CI: the GitLab `integration test` job and its sign/publish `needs` entries
are removed (build-layer keeps CI_ENABLE_CONTAINER_IMAGE_BUILDS, which it
uses to docker-build the layer). CONTRIBUTING.md now points contributors at
the local suite.

Release-gate note: the per-pipeline AWS gate on sign/publish goes away. The
candidate-layer gate moves to the residual suite in serverless-e2e-tests —
manual until the e2e release-gate automation lands (migration roadmap), so
release runbooks should trigger it until then.
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