Migrate lambda to run e2e tests to same location & infra stack as other lambdas

Open
#4,448 0 comments 1 reaction 2 assignees View on GitHub

@stephenhand is already working on this.

Since Jun 4, 2026.

  • #4449 by @copilot-swe-agent — open

Assessment

This issue has not been assessed yet.

Description

Description

Currently, to run our playwright E2E tests defined in /e2e-tests, we have a custom lambda defined in that directory

We should migrate the lambda logic out of this repo into the /lambdas directory, where we should reuse as much of the container and build configuration as possible to build a lambda that runs the e2e-tests in the same way it does now, passing the same parameters and configuration as the current one

We do NOT want to move the E2E test code itself into the lambdas directory, just move the lambda harness and have a container that pulls in the test code source from its current location

Additional context

Dominant language
TypeScript
Stars
12
Forks
10
Avg merge
1d 5h
Merged PRs (30d)
63

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from techmatters/flex-plugins

All issues in techmatters/flex-plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.