Back to Details

meticulous-test

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
To test a frontend change using Meticulous, follow the workflow below step by step, using the CLI commands as described.
Before starting, run the 
meticulous-cli-update
skill to ensure the Meticulous CLI is up to date — unless it has already run earlier in this conversation, in which case skip it.
如需使用Meticulous测试前端变更，请按照以下步骤逐步执行，使用下文所述的CLI命令。
开始前，请运行
meticulous-cli-update
技能确保Meticulous CLI为最新版本——除非在本次对话中已经运行过该命令，否则无需重复执行。

Step 1 -- Trigger Meticulous test run

步骤1 -- 触发Meticulous测试运行

If you are already given a test run id, then skip this step.
  1. If possible, find out what build artefact Meticulous expects by checking 
    .github/workflows/
    for one of the following steps: 
    • uses: alwaysmeticulous/report-diffs-action/upload-assets@v1
      - build assets
    • uses: alwaysmeticulous/report-diffs-action/upload-container@v1
      - docker image
  2. Build the frontend following the same instructions as used in the GitHub workflow.
  3. Upload the build artefact and trigger a Meticulous test run:
undefined
如果已提供测试运行ID，请跳过此步骤。
  1. 如有可能，通过检查
    .github/workflows/
    中的以下步骤之一，确定Meticulous所需的构建产物： 
    • uses: alwaysmeticulous/report-diffs-action/upload-assets@v1
      - 构建资源文件
    • uses: alwaysmeticulous/report-diffs-action/upload-container@v1
      - Docker镜像
  2. 按照GitHub工作流中使用的相同说明构建前端项目。
  3. 上传构建产物并触发Meticulous测试运行：
undefined

upload-assets

upload-assets

meticulous ci upload-assets --appDirectory <path-to-build> --repoDirectory <path-to-repo> --waitForTestRunToComplete
meticulous ci upload-assets --appDirectory <path-to-build> --repoDirectory <path-to-repo> --waitForTestRunToComplete

upload-container

upload-container

meticulous ci upload-container --localImageTag <image-tag> --repoDirectory <path-to-repo> --waitForTestRunToComplete

`--appDirectory` must point to the build output directory (e.g., `dist/` subfolder), whereas `--localImageTag` must point to the local Docker image tag. The `--repoDirectory` must point to the root of the git repository (e.g., `.`). The `--waitForTestRunToComplete` flag is required.

The command will finish with status `Failure` if visual differences have been detected. Note the `testRunId` from the output.
meticulous ci upload-container --localImageTag <image-tag> --repoDirectory <path-to-repo> --waitForTestRunToComplete

`--appDirectory`必须指向构建输出目录（例如`dist/`子文件夹），而`--localImageTag`必须指向本地Docker镜像标签。`--repoDirectory`必须指向git仓库的根目录（例如`.`）。`--waitForTestRunToComplete`参数为必填项。

如果检测到视觉差异，命令将以`Failure`状态结束。请记录输出结果中的`testRunId`。

Step 2 -- Review the visual changes

步骤2 -- 审核视觉变更

Follow the 
meticulous-review
skill, passing the 
testRunId
from Step 1. It fetches the diff summary, inspects representative screenshots / DOM diffs / timelines, and produces a final report classifying each visual change as intended or unintended.
遵循
meticulous-review
技能的流程，传入步骤1中获取的
testRunId
。该技能将获取差异摘要，检查代表性截图/DOM差异/时间线，并生成最终报告，将每个视觉变更分类为预期或非预期变更。