Files
34eeb6e5ec Cherry pick #37570 to release-11.8 (#37732)
* E2E/Playwright: Add testcontainers to playwright-lib (#37570)

* add testcontainers to playwright-lib

* include retry mechanism for transient failures

* - Introduced a new command `testcontainers:up` in package.json to run Playwright tests with Testcontainers.
- Created a standalone Playwright configuration file `playwright.testcontainers-up.config.ts` for managing Testcontainers.
- Added a no-op test `testcontainers_up.spec.ts` to ensure the Testcontainers stack is up during the test run.
- Implemented a global setup script `testcontainers_up_global_setup.ts` to start and stop the Testcontainers stack.
- Updated dependencies in package.json, including adding `chalk` for logging.

* fix package-lock

* fix tsc and restore waiting for all migrations to complete

---------

Co-authored-by: Mattermost Build <[email protected]>

* fix(e2e): remove obsolete CRT intro modal dismiss from uiClickSidebarItem

The CRT tutorial modal was removed in MM-66470; dismissing
#genericModalLabel races and flakes MM-T4261_3.

Co-authored-by: sabril <[email protected]>

* fix(e2e): sync Playwright navigations to live testcontainers baseURL

After restartMattermostContainer remaps the host port, relative page.goto
must follow testConfig.baseURL rather than the worker-start config value.

Co-authored-by: sabril <[email protected]>

* fix(e2e): restore eslint-disable for axe empty fixture pattern

Co-authored-by: sabril <[email protected]>

* fix(e2e): ignore webhook assets in eslint; prettier README

Co-authored-by: sabril <[email protected]>

* ci(e2e): fully adopt test-system-io and lighten Playwright services

Port #37413: drop the dual v1/v2 dispatch path, promote the test-system-io
templates to the canonical names, and remove legacy calculate-results / AWS
artifact upload plumbing.

For Playwright testcontainers on this release, leave optional sidecars
(openldap, keycloak, elasticsearch, opensearch, minio, azurite, webhook)
off by default and remove the related service-specific specs that are not
part of the older suite.

Co-authored-by: sabril <[email protected]>

* style(e2e): prettier stack.ts after optional webhook change

Co-authored-by: sabril <[email protected]>

* test(e2e): align testcontainers feature flags with release docker-compose

Mirror MM_FEATUREFLAGS_* from e2e-tests/.ci/server.generate.sh for each
release, dropping flags that do not exist in that release's FeatureFlags
struct (or were never enabled in the compose stack).

Co-authored-by: sabril <[email protected]>

* e2e(playwright): omit unset Testcontainers env keys; align release docs

When optional webhook/sidecars are off, .env.testcontainers no longer
writes PW_*=undefined. Docs match empty DEFAULT_TESTCONTAINERS_SERVICES.

Co-authored-by: sabril <[email protected]>

* e2e(playwright): prettier-format lib/README.md table

Fixes CI npm run check (prettier) failures from the services table edit.

Co-authored-by: sabril <[email protected]>

---------

Co-authored-by: Mattermost Build <[email protected]>

Co-authored-by: sabril <[email protected]>

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-29 18:07:27 +02:00
..

Playwright E2E Test Scripts

This directory contains utility scripts for the Playwright E2E test suite.

Test Documentation Format Linter

The lint-test-docs.js script verifies that all spec files follow the required documentation format:

  • JSDoc with @objective and @precondition tags
  • Proper test title with MM-T ID (e.g., MM-T1234)
  • Tag for feature categorization (e.g., {tag: '@feature_name'})
  • Action comments (e.g., // # Action)
  • Verification comments (e.g., // * Verification)

Usage

# Run the linter directly
node script/lint-test-docs.js

# Or use the npm script
npm run lint:test-docs

Integration with CI

The linter is also integrated with the main check command, which is typically run before committing changes:

npm run check

This will run ESLint, Prettier, TypeScript type checking, and the test documentation format linter.

Requirements

All spec files should follow this format:

/**
 * @objective Clear description of what the test verifies
 *
 * @precondition
 * Special setup or conditions required for the test
 * Note: Only include for non-default requirements
 */
test('descriptive test title', {tag: '@feature_tag'}, async ({pw}) => {
    // # Initialize setup and login
    const {user} = await pw.initSetup();
    const {channelsPage} = await pw.testBrowser.login(user);

    // # Navigate to channel and post a message
    await channelsPage.goto();
    await channelsPage.postMessage('Test message');

    // * Verify message appears in the channel
    const lastPost = await channelsPage.getLastPost();
    await expect(lastPost.body).toContainText('Test message');
});

This ensures consistency across all test files and makes it easier to understand the purpose and requirements of each test.