Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Document the opt-in browser tests (template #157)

已关闭
#232 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
55/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
docker, github-actions, gitlab, php, playwright

调研方向

Start with the template's e2e/README.md and e2e/run.sh, then tests/fixtures.ts, to confirm the variable, job names, and env vars. Add the CWA_CI_E2E_ENABLED entry to content/6.deployment/4.variables.md, and cover the GitLab browser tests job, the GitHub browser-tests.yml workflow, and local runs in content/6.deployment/3.ci-cd.md. Done when those pages match the template and cover the fixtures, logIn(page), and GCLOUD_API_ENDPOINT.

由索引模型根据 Issue 内容生成。

描述

Template change in components-web-app 3fd2c01 / 8c36f8c (Unreleased, next release after 2.0.0-alpha.33).

New: opt-in Playwright browser tests that gate deploys (e2e/ in the template; the template's e2e/README.md has the details).

  • CI variable: CWA_CI_E2E_ENABLED ("true" turns them on). It goes on content/6.deployment/4.variables.md, with the other CWA_CI_* switches.
  • CI/CD page (content/6.deployment/3.ci-cd.md):
    • GitLab's browser tests job, which review, staging, canary and production wait for;
    • GitHub's reusable browser-tests.yml, called from ci.yml and production.yml;
    • the report artifacts (14 days).
  • Local use: build the two prod images, then E2E_PHP_IMAGE=… E2E_APP_IMAGE=… sh e2e/run.sh, with E2E_ARGS to run part of the suite and E2E_KEEP_STACK=true to keep the stack.
  • Writing project tests:
    • import from tests/fixtures.ts, which fails a test on a 405, 406 or 415 API write;
    • logIn(page);
    • one database, tests run one at a time;
    • wait for saves to settle before publishing (cwa-nuxt-module#394).
  • New optional php env: GCLOUD_API_ENDPOINT, a Cloud Storage emulator endpoint used by the tests. Empty uses Google, as on every deploy.
主要语言
Vue
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

components-web-app/docs 的其他 Issue

查看 components-web-app/docs 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。