diff --git a/docs/image/1-intro.md b/docs/image/1-intro.md
index 2865e0e11..aabfd2ad4 100644
--- a/docs/image/1-intro.md
+++ b/docs/image/1-intro.md
@@ -21,4 +21,4 @@ Docker 镜像是一个可执行的软件包，它包含运行应用程序所需
- 支持快速上传和管理现有镜像
- 可在平台内直接使用托管的镜像
-- 与平台[自动化服务](../workflow/action/1-quickstart.md)和[批量测试](../simandtests/regression/1-intro.md)等功能无缝集成
+- 与平台[自动化服务](../workflow/action/1-quickstart.md)和[批量测试](../sim-and-tests/regression/1-intro.md)等功能无缝集成
diff --git a/docs/simandtests/_category_.json b/docs/sim-and-tests/_category_.json
similarity index 100%
rename from docs/simandtests/_category_.json
rename to docs/sim-and-tests/_category_.json
diff --git a/docs/sim-and-tests/regression/1-intro.md b/docs/sim-and-tests/regression/1-intro.md
new file mode 100644
index 000000000..210ff1cd0
--- /dev/null
+++ b/docs/sim-and-tests/regression/1-intro.md
@@ -0,0 +1,89 @@
+---
+sidebar_position: 1
+---
+
+# 关于批量测试
+
+批量测试是一种并行执行多个测试任务的自动化解决方案，主要用于回归测试、仿真测试等大规模测试场景。平台提供完整的测试资源管理能力，支持镜像、数据集、测试套件与测试程序的统一管理，可在项目中一站式完成测试执行、状态监控及结果分析。
+
+## 基本信息
+### 概念说明
+
+| 名称 | 说明 |
+| --- | --- |
+| 镜像 | 运行批量测试的虚拟环境 |
+| 测试套件 | 一组相关联的测试用例集合，通常针对特定功能或场景进行测试 |
+| 测试程序 | 为执行测试用例而编写的一系列代码和相关依赖 |
+| 测试用例 | 运行批量测试过程中执行的具体任务，通常从相应的测试报告中解析出 |
+
+批量测试任务的执行流程如下：
+1. 选择测试套件，将其预设的镜像作为测试环境
+2. 将测试程序、测试数据（[记录](../../collaboration/record/1-quick-start-record.md)）和测试套件的配置参数导入测试环境
+3. 系统为测试套件关联的每条记录创建独立的子测试任务
+4. 所有子测试任务完成后，系统自动汇总结果并生成测试报告
+
+### 系统目录
+批量测试支持的目录结构如下：
+| 名称 | 目录 |
+| -------- | -------------- |
+| 测试程序 | /cos/bundles |
+| 记录 | /cos/files |
+| Artifact | /cos/artifacts |
+| 测试输出 | /cos/outputs |
+
+## 批量测试界面
+### 批量测试列表页
+
+
+
+- **测试序号**：测试的唯一标识，依次递增，点击后可查看详情
+- **测试时间**：测试开始的时间，鼠标悬停可查看具体时间
+- **测试状态**：测试的当前状态，包括队列中、运行中、已完成、无结果。其中：
+ - 「已完成」表示测试已完成（不表示测试用例的执行成功与否）
+ - 「无结果」表示测试未解析出结果，查看[如何输出测试结果](./6-status-and-output.md)
+- **测试套件名称**：测试所选的测试套件名称，详见[测试套件](./3-config-management.md)
+- **测试程序种类、版本**：测试所选的测试程序种类与版本，详见[测试程序](./4-test-bundle-management.md)
+- **测试进度**：一个测试包含多个子测试任务，鼠标悬停可查看具体进度
+- **测试通过率**：测试通过的数量占总数的比例。
+ - 计算公式：1 个测试套件用于计算通过率的数值 = 测试套件解析出的用例数 × 关联记录数
+- **测试时长**：测试总时长
+- **操作**：
+ - 取消运行
+ - 重新运行批量测试
+ - 下载 Artifacts
+ - 下载测试输出
+
+### 批量测试详情页
+- **测试报告**：展示测试的运行时长、测试数量、测试通过率、测试结果等信息
+
+ 
+
+ - 测试套件解析出的测试用例：1 个测试套件可解析出多条用例，每条用例有对应的执行结果
+ - 点击测试用例名称可查看具体结果
+
+- **测试进度**：展示每个子测试任务的执行状态，可在子测试任务详情中查看对应的执行日志、Artifact 与测试输出
+- **Artifacts**：测试过程中生成的结果文件，如测试报告
+- **测试输出**：测试过程中生成的需要可视化的文件，如 ROSbag
+
+## 使用流程概览
+进入项目的「批量测试」页面，根据提示创建一个批量测试：
+
+
+
+1. 准备测试环境与数据
+
+ - 准备运行批量测试的 [Docker 镜像](../../image/1-intro.md)
+ - 将镜像推送至公开平台或[刻行时空镜像仓库](../../image/3-push-image.md)
+ - 将测试数据上传到项目中并按[记录](../../collaboration/record/1-quick-start-record.md)存储
+
+2. 配置测试内容
+
+ - 在「[测试套件管理](./3-config-management.md)」页面设置测试套件和相应配置参数
+ - 在「[测试程序管理](./4-test-bundle-management.md)」页面上传被测程序
+
+3. 执行与监控
+ - 在「[运行批量测试](./5-run.md)」弹框中，选择测试程序版本与测试套件
+ - 启动批量测试
+ - 实时监控测试进度并[查看测试结果](./6-status-and-output.md#查看测试结果)
+
+详情请参见后续章节。
diff --git a/docs/sim-and-tests/regression/3-config-management.md b/docs/sim-and-tests/regression/3-config-management.md
new file mode 100644
index 000000000..73c41e473
--- /dev/null
+++ b/docs/sim-and-tests/regression/3-config-management.md
@@ -0,0 +1,167 @@
+---
+sidebar_position: 3
+---
+
+# 测试套件
+## 简介
+测试套件是一组相关联的测试用例集合，提供统一的配置管理界面，支持设置测试名称、运行环境（镜像）、测试数据（记录）等参数，实现测试用例的标准化管理。
+
+
+
+## 管理测试套件
+### 前提条件
+1. 请确保已将测试数据按[记录](../../collaboration/record/1-quick-start-record.md)存储，并给每条记录打上了标签
+
+ 
+
+2. 请确保已准备好测试环境（镜像），并将其推送至公开平台或[刻行时空镜像仓库](../../image/1-intro.md)。
+ 推荐在镜像中定义测试用例：
+ - 测试用例（testcase）支持解析，详见[定义测试结果](./6-status-and-output.md#定义测试结果)
+ - 批量测试的输入与输出目录，详见[系统目录](./1-intro.md#系统目录)
+
+### 创建测试套件
+1. 在项目左侧边栏，选择「批量测试」，点击按钮进入「测试套件管理」页面：
+
+ - 首次编辑测试套件
+
+ 
+
+ - 非首次编辑测试套件
+
+ 
+
+2. 点击【编辑】，进入测试套件编辑页面：
+
+ 
+ 
+
+3. 填写测试套件名称、运行环境、测试数据等信息：
+
+ ```yaml
+ # 示例文件
+
+ # 版本号，当前支持的版本为"1"
+ version: '1'
+
+ # 测试名称为 workflow name
+ name: 'workflow name'
+
+ # 一个 job 由一个或多个测试套件组成，这些测试套件可以并行测试
+ jobs:
+ # 第一个测试套件的名称为"test-1"
+ - name: 'test-1'
+ # 测试类型为"generic"
+ type: 'generic'
+
+ # 镜像地址
+ images:
+ # 根据测试类型，输入镜像地址
+ base: cr.coscene.cn/coscene-hello/position:v1.0.0
+
+ # 关联记录
+ records:
+ # 该测试套件的关联记录标签为"sample"
+ labels:
+ - 'sample'
+
+ # 该测试套件的运行命令
+ parameters:
+ script:
+ - /bin/sh
+ - -c
+ - 'echo hello'
+
+ # 测试套件"test-1"的消息通知模板
+ notifications:
+ # 通知到钉钉群
+ - dingTalkBot:
+
+ # 第二个测试套件的名称为"test-2"
+ - name: 'test-2'
+
+ # 控制何时自动触发该测试
+ on:
+ # 当上传测试程序时，满足以下条件则会触发
+ bundlePush:
+ # 条件：测试程序种类为"test"
+ category:
+ - test
+ ```
+
+ - **version**：版本号，当前支持的版本为`'1'`。
+ - **name**：测试名称
+ - **jobs**：测试套件列表
+ - **name**：测试套件名称
+ - **type**：测试类型，当前支持的类型为`'generic'`
+ - **images**：测试套件运行的镜像，支持使用刻行时空镜像仓库或公开平台的镜像
+ - **records**：运行该测试套件时使用的记录，通过标签关联记录
+ - **parameters**：运行该测试套件时使用的参数
+ - **notifications**：测试套件运行完成后发送的消息通知模版
+ - **on**：自动触发测试
+ - **bundlePush**：当上传测试程序时，其「种类」满足条件则会触发
+
+ 具体格式详见 [配置文件格式与样例](./9-yaml-sample.md)。
+
+4. 点击【保存】，保存测试套件配置文件。
+
+ 
+
+### 上传、下载与编辑
+> 测试套件的配置文件为 cos.yaml，支持直接上传、下载与编辑。
+
+1. 在项目左侧边栏，选择「批量测试」，点击按钮进入「测试套件管理」页面：
+
+ 
+
+2. 上传、下载或直接编辑配置文件：
+
+ 
+
+3. 点击【保存】，保存测试套件配置文件。
+
+ 
+
+### 查看
+配置文件校验通过后，测试套件管理页面将展示解析结果，包括测试套件的基本信息、运行环境、数据关联及触发条件等配置详情。
+
+- 测试名称与测试套件名称
+
+ 
+
+- 测试类型与镜像
+
+ 
+
+- 关联记录
+
+ 
+
+- 关联触发条件
+
+ 
+
+- 通知模板样式
+
+ 
+
+### 使用
+在运行批量测试时，可选择测试套件，系统将根据测试套件配置信息运行测试。
+.default})
+
+## 了解更多
+- [配置文件格式与样例](./9-yaml-sample.md)
+- [测试程序](./4-test-bundle-management.md)
+- [管理测试结果](./6-status-and-output.md)
+- [运行批量测试](./5-run.md)
+
+## 常见问题
+1. **问：无法保存测试套件，提示”记录错误:标签不存在:sample“**
+
+ 答：请检查名为「sample」的测试套件，是否存在错误的标签，如标签不存在或书写错误。此处仅支持使用已存在的标签。了解[如何给记录添加标签](../../collaboration/record/3-manage-records.md#编辑)
+
+2. **问：无法保存测试套件，提示”请检查 yaml 文件格式“**
+
+ 答：请检查测试套件配置文件格式是否正确，如配置文件格式错误，可参考[配置文件格式与样例](./9-yaml-sample.md)
+
+
+
diff --git a/docs/sim-and-tests/regression/4-test-bundle-management.md b/docs/sim-and-tests/regression/4-test-bundle-management.md
new file mode 100644
index 000000000..1b6a2b69b
--- /dev/null
+++ b/docs/sim-and-tests/regression/4-test-bundle-management.md
@@ -0,0 +1,59 @@
+---
+sidebar_position: 4
+---
+
+# 测试程序
+## 简介
+测试程序是被测试的代码文件，可以是一个.deb 格式的文件或.zip /.tgz /.tar.gz 格式的压缩文件。
+
+
+
+## 管理测试程序
+### 上传测试程序
+1. 在项目左侧边栏，选择「批量测试」，点击按钮进入「测试程序管理」页面：
+
+- 首次上传测试程序
+
+ 
+
+- 非首次上传测试程序
+
+ 
+
+2. 点击【上传测试程序】：
+
+ 
+
+3. 上传测试程序，填写测试种类与版本：
+
+ .default})
+
+ - **测试程序种类**：自定义输入种类信息，或选择已有的测试种类。
+
+ - **测试程序版本**：自定义输入版本信息，如`v0.1`
+
+ 测试种类与版本信息可用于自动触发测试。详见[配置文件格式与样例-自动触发测试](./9-yaml-sample.md#auto-triggering)
+
+4. 上传测试程序后，列表「状态」栏显示为「活跃」，即表示该测试程序上传成功：
+
+ 
+
+### 下载
+1. 在项目左侧边栏，选择「批量测试」，点击按钮进入「测试程序管理」页面：
+
+ 
+
+2. 点击列表中测试程序的「下载」按钮，即可下载测试程序：
+
+ 
+
+### 使用
+在运行批量测试时，可选择特定版本的测试程序执行测试任务。可以通过测试程序的序号、种类、版本号来识别所需的测试程序。
+
+.default})
+
+## 了解更多
+- [运行批量测试](./5-run.md)
+- [配置文件格式与样例](./9-yaml-sample.md)
+- [管理测试结果](./6-status-and-output.md)
+- [测试套件](./3-config-management.md)
\ No newline at end of file
diff --git a/docs/sim-and-tests/regression/5-run.md b/docs/sim-and-tests/regression/5-run.md
new file mode 100644
index 000000000..a02793b80
--- /dev/null
+++ b/docs/sim-and-tests/regression/5-run.md
@@ -0,0 +1,144 @@
+---
+sidebar_position: 5
+---
+
+# 运行批量测试
+
+> 了解如何运行批量测试，包括手动触发、自动触发、以及使用命令行在本地运行批量测试等。
+
+## 前提条件
+1. 已创建[测试套件](./3-config-management.md)
+2. 已上传[测试程序](./4-test-bundle-management.md)
+
+## 手动运行
+
+1. 在项目左侧边栏，选择「批量测试」，点击【运行批量测试】按钮
+
+- 首次运行批量测试
+
+ 
+
+- 非首次运行批量测试
+
+ 
+
+2. 在运行批量测试弹框中，选择测试程序、测试套件后，点击【确定】，运行批量测试。
+
+
+
+3. 系统会为每个测试套件关联的记录创建独立的测试任务。例如，当一个测试套件关联了 10 条记录时，系统会创建 10 个子任务，每个任务会使用选定的测试程序和测试套件配置，对单条记录进行测试。
+
+ 
+
+4. 运行完成后，在测试列表中可查看其运行结果。详见[管理测试结果](./6-status-and-output.md)。
+
+ 
+
+## 自动触发
+当上传的「测试程序」满足测试套件中[预设的触发条件](./9-yaml-sample.md#auto-triggering)时，系统会自动执行相关的测试套件。
+
+查看测试套件的自动触发条件：
+1. 进入「批量测试-测试套件管理」页面，找到带有「关联触发条件」标识的测试套件：
+
+ 
+
+2. 点击【查看触发条件】，查看该测试套件的具体触发规则：
+
+ .default})
+
+## 本地运行
+除了使用 Web 界面，平台支持通过命令行工具（CLI）在本地运行批量测试。以下是详细的配置和使用说明。
+
+### 下载与配置
+
+1. 输入命令以下载所需文件，各操作系统对应命令如下：
+
+- Linux
+
+ ```bash
+ curl https://coscene-artifacts-production.oss-cn-hangzhou.aliyuncs.com/cos/linux/amd64/latest/cos -o cos
+ ```
+
+- macOS
+
+ ```bash
+ curl https://coscene-artifacts-production.oss-cn-hangzhou.aliyuncs.com/cos/darwin/amd64/latest/cos -o cos
+ ```
+
+2. 通过以下命令进行配置：
+
+ ```bash
+ # 给 cos 可执行权限
+ chmod +x cos
+
+ # 创建配置目录
+ mkdir $HOME/.cos
+
+ # 创建配置文件
+ cat << EOF > $HOME/.cos/config.yaml
+ platform:
+ endpoint: ${YOUR_DOMAIN}
+ accessToken: ${YOUR_TOKEN}
+ project: ${ORG_SLUG}/${PROJECT_SLUG}
+ EOF
+
+ # 验证配置
+ cos config list
+ ```
+
+ 其中各参数说明如下：
+
+ - **`endpoint`**
+
+ `${YOUR_DOMAIN}` 需替换成实际的网站地址。如下图的网址，`${YOUR_DOMAIN}` 为 `api.coscene.cn`
+
+ 
+
+ - **`accessToken`**
+
+ `${YOUR_TOKEN}` 的获取步骤如下所示：
+
+ 
+
+ .default})
+
+ .default})
+
+ - **`project`**
+
+ `ORG_SLUG` 和 `PROJECT_SLUG` 需根据实际替换：
+
+ 
+
+### 运行
+以下是常用的命令行示例，展示了不同场景下如何运行批量测试：
+
+```bash
+# 使用最新的测试程序运行项目下所有批量测试
+cos test run
+
+# 只用本地的配置文件 cos.yaml 运行批量测试
+cos test run --test-config cos.yaml
+
+# 使用最新的测试程序，对项目下名称为 sample-test-suite 的测试套件运行批量测试
+cos test run -t sample-test-suite
+
+# 使用指定的记录 定位采集数据 运行批量测试
+cos test run -r 定位采集数据
+
+# 使用标签为 v0.0.1 的测试程序，对项目下所有测试套件运行批量测试
+cos test run --bundle-tag v0.0.1
+
+# 使用种类为 sample-test-bundle 的测试程序，对项目下所有测试套件运行批量测试
+cos test run --bundle-category sample-test-bundle
+
+# 上传 bundle.zip 并运行批量测试
+cos test run -b bundle.zip
+```
+
+## 了解更多
+- [如何输出测试结果](./6-status-and-output.md)
+- [如何查看运行信息](./6-status-and-output.md#查看运行进度与产物)
+- [管理测试套件](./3-config-management.md)
+- [管理测试程序](./4-test-bundle-management.md)
+- [自动触发测试](./9-yaml-sample.md#auto-triggering)
\ No newline at end of file
diff --git a/docs/sim-and-tests/regression/6-status-and-output.md b/docs/sim-and-tests/regression/6-status-and-output.md
new file mode 100644
index 000000000..bce36d9e3
--- /dev/null
+++ b/docs/sim-and-tests/regression/6-status-and-output.md
@@ -0,0 +1,178 @@
+---
+sidebar_position: 6
+---
+
+# 管理测试结果
+批量测试支持全面的测试结果管理能力，包括测试用例解析、运行状态追踪、日志收集及产物管理等。平台提供标准化的结果解析引擎，可视化的报告展示，以及丰富的数据分析功能。
+
+## 定义测试结果
+### 定义测试报告
+批量测试支持解析 JUnit XML 格式的文件。 在 [Artifact](./1-intro.md#系统目录) 中输出测试结果文件，系统会自动解析并展示测试结果。示例如下：
+- 在每条记录运行测试的 Artifacts 中输出 .xml 文件：
+
+ 
+
+- 系统会自动解析并展示测试报告：
+
+ 
+
+创建 JUnit XML 格式文件的方法有两种：
+- 在代码中使用 `pytest` 库的 `pytest_junit` 插件
+- 在配置文件中使用命令输出 xml 文件。详见 [配置文件格式与样例-输出测试结果文件](../regression/9-yaml-sample.md#save-artifacts)。
+
+支持解析的测试结果文件示例如下:
+> 其中结果数据到 JUnit XML 格式的映射请参考 [JUnit Mapping](https://www.ibm.com/docs/en/developer-for-zos/14.1?topic=formats-junit-xml-format#junitschema__table_junitmap)
+
+```xml
+
+
+
+
+
+ WARNING: Use a program name that matches the source file name
+ Category: COBOL Code Review – Naming Conventions
+ File: /project/PROGRAM.cbl
+ Line: 2
+
+
+
+
+```
+
+### 定义输出图表
+JUnit XML 格式的测试结果文件中，支持添加以 "cos\_" 为前缀的自定义属性（如 `cos_customer_name`），系统会自动解析这些属性及其对应的指标值，并生成可视化图表（柱状图、箱线图）。
+
+当前支持的数据类型为：布尔类型、浮点类型。在测试代码文件中输出图表的示例如下：
+
+```python
+ def test_romeo(record_xml_attribute):
+
+ for i in (1, 2, 3):
+ rand_float = random.uniform(1, 100)
+ record_xml_attribute("cos_test_romeo_val" + str(i), rand_float)
+ for i in (1, 2, 3):
+ rand_bool = random.choice([True, False])
+ record_xml_attribute("cos_test_romeo_bool" + str(i), rand_bool)
+
+ assert __count('romeo') > 0
+```
+
+系统会自动解析并生成可视化图表：
+
+
+
+
+### 自定义输出文件
+测试过程中生成的文件可输出至以下目录：
+- Artifact：/cos/artifacts
+- 测试输出：/cos/outputs
+
+ 
+
+文件预览与播放支持：
+- 「Artifacts」目录下的文件仅支持预览
+- 「测试输出」目录下的文件支持预览与播放。其中，ROSbag 文件播放时将自动进入「影子模式」，与原始记录进行同步对比播放
+
+### 创建一刻
+批量测试支持在关键时间点（如机器偏移量异常、设备故障等）创建一刻，便于后续快速定位和分析问题。一刻可以：
+- 标记重要的时间点
+- 记录问题发生的具体时刻
+- 提取关键片段用于分析
+
+使用批量测试环境中内置的 `cos` 命令行工具来创建一刻，具体命令如下：
+
+```yaml
+/cos/bins/cos moment create \
+ --display-name "急停" \ # moment 名字
+ --description "机器急停" \ # moment 描述
+ --trigger-time 1532402940 \ # moment 触发时间
+ --duration 10 \ # moment 持续时长
+ --customized-fields '{"key1": "value1"}' # moment 自定义字段
+```
+
+在可视化页面查看一刻，参见[一刻](../../viz/5-create-moment-viz.md)
+
+## 查看测试结果
+批量测试列表页展示所有测试的执行历史，包括测试状态、进度等信息。点击测试序号可进入详情页查看完整信息：
+
+ 
+
+### 查看运行进度与产物
+1. 在批量测试详情页的「进度」栏中，可查看所有子测试任务的运行状态与执行进度：
+
+ 
+
+2. 点击子测试任务的标题，查看其详情页面:
+
+ 
+
+3. 在子测试任务详情页，可查看子测试任务的运行状态、进度、运行日志、测试产物等信息：
+ - **记录**：点击记录名称，查看记录详情
+ - **步骤**：点击步骤名称，查看运行日志
+ - **Artifacts**：查看或下载测试过程中生成的结果文件，如测试报告
+ - **测试输出**：播放测试过程中生成的需要可视化的文件，如 ROSbag 文件
+
+ 
+
+4. 在批量测试详情页的「Artifacts」中，可查看与下载该批量测试的所有 Artifacts。文件层级如下：
+
+ ```plaintext
+ 所有 Artifacts
+ ├── 测试套件 A
+ │ ├── 记录 1
+ │ │ ├── report.xml
+ │ │ └── ...
+ │ └── 记录 2
+ │ └── ...
+ └── 测试套件 B
+ └── ...
+ ```
+
+ 
+
+4. 在批量测试详情页的「测试输出」中，可查看与下载该批量测试的所有测试输出。文件层级如下：
+
+ ```plaintext
+ 所有测试输出
+ ├── 测试套件 A
+ │ ├── 记录 1
+ │ │ ├── test.bag
+ │ │ └── ...
+ │ └── 记录 2
+ │ └── ...
+ └── 测试套件 B
+ └── ...
+ ```
+
+### 查看测试报告
+当批量测试运行完成后，在「测试报告」中可查看测试套件运行结果统计，包括运行信息以及各测试套件运行解析出的测试用例等:
+
+
+
+点击单个测试用例名称，可查看该测试用例的运行报告，包括各测试详情列表和输出图表等：
+
+
+
+点击页面右上角的「查看历史数据」，可以查看该测试用例的历史结果数据统计，包括测试的运行结果矩阵、指标统计图等：
+
+
+
+
+
+### 播放影子模式
+若测试输出中有 ROSbag 文件，则可与原记录进行对比播放。
+
+1. 在测试详情页的「测试输出」栏，选择对应的记录层级，点击右上角的「影子模式」按钮进入可视化界面：
+
+ 
+
+2. 测试输出文件将与原记录中的文件一起在可视化界面中对比播放。
+
+ 
+
+## 了解更多
+- [测试程序](./4-test-bundle-management.md)
+- [测试套件](./3-config-management.md)
+- [运行批量测试](./5-run.md)
+- [记录](../../collaboration/record/1-quick-start-record.md)
+- [可视化](../../viz/1-about-viz.md)
\ No newline at end of file
diff --git a/docs/simandtests/regression/9-yaml-sample.md b/docs/sim-and-tests/regression/9-yaml-sample.md
similarity index 90%
rename from docs/simandtests/regression/9-yaml-sample.md
rename to docs/sim-and-tests/regression/9-yaml-sample.md
index e4f4084a1..375194710 100644
--- a/docs/simandtests/regression/9-yaml-sample.md
+++ b/docs/sim-and-tests/regression/9-yaml-sample.md
@@ -3,12 +3,9 @@ sidebar_position: 9
---
# 配置文件格式与样例
+本章节介绍测试套件配置文件（cos.yaml）的语法规则和使用示例，帮助你快速配置和管理测试套件。
-> 你可以通过本章节的内容了解批量测试配置文件的书写规则；同时本章节会提供样例文件以供参考。
-
-
-
-支持解析的配置文件为 yaml 或 yml 类型文件，且名称必须为 **cos.yaml** 或 **cos.yml**。你可以直接复制，或 点击此处下载 示例配置文件并进行修改。其基本结构如下：
+系统支持解析 YAML 格式的配置文件，其文件名必须为 **cos.yaml** 或 **cos.yml**。你可以下载示例配置文件进行修改，或参考下方示例创建：
## 自定义测试套件 {#customize-testing-bundle}
@@ -122,7 +119,7 @@ parameters:
## 自动触发测试 {#auto-triggering}
-设置自动触发测试的条件，目前支持：上传的测试包「种类」或「标签」符合预设条件时，自动触发批量测试
+设置自动触发测试的条件，目前支持：上传的测试程序「种类」或「版本」符合预设条件时，自动触发批量测试
```yaml
on:
@@ -137,23 +134,23 @@ on:
用于控制何时自动触发测试
-- **bundlePush：设置上传测试包触发**
+- **bundlePush：设置上传测试程序触发**
- 当上传测试包时，满足条件则会自动触发测试
+ 当上传测试程序时，满足条件则会自动触发测试
-- **category：测试包种类**
+- **category：测试程序种类**
- 用于指定触发测试的测试包种类名称
+ 用于指定触发测试的测试程序种类名称
-- **tag：测试包标签**
+- **tag：测试程序版本**
- 用于指定触发测试的测试包标签名称
+ 用于指定触发测试的测试程序版本名称
**备注：**
1. 没有 on 或者只有 on 时，不会自动触发批量测试
-2. 有且仅有 bundlePush 时，任意的测试包上传都会自动触发批量测试
-3. 有 category 或者 tag 时， 只有符合预设条件的测试包会自动触发批量测试
+2. 有且仅有 bundlePush 时，任意的测试程序上传都会自动触发批量测试
+3. 有 category 或者 tag 时， 只有符合预设条件的测试程序会自动触发批量测试
@@ -294,7 +291,7 @@ jobs:
**备注：**
1. 参考资料：[Django-syntax like templating-language](https://github.com/flosch/pongo2)
-2. 刻行自定义 filter
+2. 刻行时空自定义 filter
a. `formatByOffset:"$offset"`
diff --git a/docs/simandtests/regression/_2-image-management.md b/docs/sim-and-tests/regression/_2-image-management.md
similarity index 100%
rename from docs/simandtests/regression/_2-image-management.md
rename to docs/sim-and-tests/regression/_2-image-management.md
diff --git a/docs/simandtests/regression/_category_.json b/docs/sim-and-tests/regression/_category_.json
similarity index 100%
rename from docs/simandtests/regression/_category_.json
rename to docs/sim-and-tests/regression/_category_.json
diff --git a/docs/simandtests/regression/img/4-8-regression-intro.png b/docs/sim-and-tests/regression/img/4-8-regression-intro.png
similarity index 100%
rename from docs/simandtests/regression/img/4-8-regression-intro.png
rename to docs/sim-and-tests/regression/img/4-8-regression-intro.png
diff --git a/docs/sim-and-tests/regression/img/artifacts_1.png b/docs/sim-and-tests/regression/img/artifacts_1.png
new file mode 100644
index 000000000..0d004b7d7
Binary files /dev/null and b/docs/sim-and-tests/regression/img/artifacts_1.png differ
diff --git a/docs/sim-and-tests/regression/img/cli_1.png b/docs/sim-and-tests/regression/img/cli_1.png
new file mode 100644
index 000000000..deb434196
Binary files /dev/null and b/docs/sim-and-tests/regression/img/cli_1.png differ
diff --git a/docs/sim-and-tests/regression/img/cli_2.png b/docs/sim-and-tests/regression/img/cli_2.png
new file mode 100644
index 000000000..f570dfd72
Binary files /dev/null and b/docs/sim-and-tests/regression/img/cli_2.png differ
diff --git a/docs/sim-and-tests/regression/img/cli_3.png b/docs/sim-and-tests/regression/img/cli_3.png
new file mode 100644
index 000000000..20e6c2849
Binary files /dev/null and b/docs/sim-and-tests/regression/img/cli_3.png differ
diff --git a/docs/sim-and-tests/regression/img/cli_4.png b/docs/sim-and-tests/regression/img/cli_4.png
new file mode 100644
index 000000000..9151f6a7a
Binary files /dev/null and b/docs/sim-and-tests/regression/img/cli_4.png differ
diff --git a/docs/sim-and-tests/regression/img/cli_5.png b/docs/sim-and-tests/regression/img/cli_5.png
new file mode 100644
index 000000000..799b9e2bf
Binary files /dev/null and b/docs/sim-and-tests/regression/img/cli_5.png differ
diff --git a/docs/sim-and-tests/regression/img/regression-detail_1.png b/docs/sim-and-tests/regression/img/regression-detail_1.png
new file mode 100644
index 000000000..1b54b54d7
Binary files /dev/null and b/docs/sim-and-tests/regression/img/regression-detail_1.png differ
diff --git a/docs/sim-and-tests/regression/img/regression-list.png b/docs/sim-and-tests/regression/img/regression-list.png
new file mode 100644
index 000000000..7ad4f5bad
Binary files /dev/null and b/docs/sim-and-tests/regression/img/regression-list.png differ
diff --git a/docs/sim-and-tests/regression/img/regression-list_1.png b/docs/sim-and-tests/regression/img/regression-list_1.png
new file mode 100644
index 000000000..7529621bb
Binary files /dev/null and b/docs/sim-and-tests/regression/img/regression-list_1.png differ
diff --git a/docs/simandtests/regression/img/report-2.png b/docs/sim-and-tests/regression/img/report-2.png
similarity index 100%
rename from docs/simandtests/regression/img/report-2.png
rename to docs/sim-and-tests/regression/img/report-2.png
diff --git a/docs/sim-and-tests/regression/img/report-3.png b/docs/sim-and-tests/regression/img/report-3.png
new file mode 100644
index 000000000..872fddb23
Binary files /dev/null and b/docs/sim-and-tests/regression/img/report-3.png differ
diff --git a/docs/simandtests/regression/img/report-4.png b/docs/sim-and-tests/regression/img/report-4.png
similarity index 100%
rename from docs/simandtests/regression/img/report-4.png
rename to docs/sim-and-tests/regression/img/report-4.png
diff --git a/docs/sim-and-tests/regression/img/report_1.png b/docs/sim-and-tests/regression/img/report_1.png
new file mode 100644
index 000000000..dae37cd51
Binary files /dev/null and b/docs/sim-and-tests/regression/img/report_1.png differ
diff --git a/docs/sim-and-tests/regression/img/result_1.png b/docs/sim-and-tests/regression/img/result_1.png
new file mode 100644
index 000000000..8bd0e1527
Binary files /dev/null and b/docs/sim-and-tests/regression/img/result_1.png differ
diff --git a/docs/sim-and-tests/regression/img/result_2.png b/docs/sim-and-tests/regression/img/result_2.png
new file mode 100644
index 000000000..2a0806cdc
Binary files /dev/null and b/docs/sim-and-tests/regression/img/result_2.png differ
diff --git a/docs/sim-and-tests/regression/img/result_3.png b/docs/sim-and-tests/regression/img/result_3.png
new file mode 100644
index 000000000..89c42ac75
Binary files /dev/null and b/docs/sim-and-tests/regression/img/result_3.png differ
diff --git a/docs/sim-and-tests/regression/img/result_4.png b/docs/sim-and-tests/regression/img/result_4.png
new file mode 100644
index 000000000..6cd2a4592
Binary files /dev/null and b/docs/sim-and-tests/regression/img/result_4.png differ
diff --git a/docs/sim-and-tests/regression/img/run_1.png b/docs/sim-and-tests/regression/img/run_1.png
new file mode 100644
index 000000000..851d03096
Binary files /dev/null and b/docs/sim-and-tests/regression/img/run_1.png differ
diff --git a/docs/sim-and-tests/regression/img/run_2.png b/docs/sim-and-tests/regression/img/run_2.png
new file mode 100644
index 000000000..f47e93c22
Binary files /dev/null and b/docs/sim-and-tests/regression/img/run_2.png differ
diff --git a/docs/sim-and-tests/regression/img/run_3.png b/docs/sim-and-tests/regression/img/run_3.png
new file mode 100644
index 000000000..5d4143d75
Binary files /dev/null and b/docs/sim-and-tests/regression/img/run_3.png differ
diff --git a/docs/sim-and-tests/regression/img/run_4.png b/docs/sim-and-tests/regression/img/run_4.png
new file mode 100644
index 000000000..d881baab2
Binary files /dev/null and b/docs/sim-and-tests/regression/img/run_4.png differ
diff --git a/docs/sim-and-tests/regression/img/run_5.png b/docs/sim-and-tests/regression/img/run_5.png
new file mode 100644
index 000000000..ee72d82b4
Binary files /dev/null and b/docs/sim-and-tests/regression/img/run_5.png differ
diff --git a/docs/sim-and-tests/regression/img/shadow-mode_1.png b/docs/sim-and-tests/regression/img/shadow-mode_1.png
new file mode 100644
index 000000000..ec95dffe9
Binary files /dev/null and b/docs/sim-and-tests/regression/img/shadow-mode_1.png differ
diff --git a/docs/sim-and-tests/regression/img/shadow-mode_2.png b/docs/sim-and-tests/regression/img/shadow-mode_2.png
new file mode 100644
index 000000000..9dbb8d663
Binary files /dev/null and b/docs/sim-and-tests/regression/img/shadow-mode_2.png differ
diff --git a/docs/sim-and-tests/regression/img/status_1.png b/docs/sim-and-tests/regression/img/status_1.png
new file mode 100644
index 000000000..148557698
Binary files /dev/null and b/docs/sim-and-tests/regression/img/status_1.png differ
diff --git a/docs/sim-and-tests/regression/img/status_2.png b/docs/sim-and-tests/regression/img/status_2.png
new file mode 100644
index 000000000..c9af5ef75
Binary files /dev/null and b/docs/sim-and-tests/regression/img/status_2.png differ
diff --git a/docs/sim-and-tests/regression/img/status_3.png b/docs/sim-and-tests/regression/img/status_3.png
new file mode 100644
index 000000000..5256e15d3
Binary files /dev/null and b/docs/sim-and-tests/regression/img/status_3.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_1.png b/docs/sim-and-tests/regression/img/test-suite_1.png
new file mode 100644
index 000000000..fd3d9127a
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_1.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_10.png b/docs/sim-and-tests/regression/img/test-suite_10.png
new file mode 100644
index 000000000..be00e6501
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_10.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_11.png b/docs/sim-and-tests/regression/img/test-suite_11.png
new file mode 100644
index 000000000..446a6c1cd
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_11.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_12.png b/docs/sim-and-tests/regression/img/test-suite_12.png
new file mode 100644
index 000000000..2f79b607f
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_12.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_13.png b/docs/sim-and-tests/regression/img/test-suite_13.png
new file mode 100644
index 000000000..34dbcd2a4
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_13.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_14.png b/docs/sim-and-tests/regression/img/test-suite_14.png
new file mode 100644
index 000000000..77368e619
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_14.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_2.png b/docs/sim-and-tests/regression/img/test-suite_2.png
new file mode 100644
index 000000000..9c03f5a73
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_2.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_3.png b/docs/sim-and-tests/regression/img/test-suite_3.png
new file mode 100644
index 000000000..791faf8d0
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_3.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_4.png b/docs/sim-and-tests/regression/img/test-suite_4.png
new file mode 100644
index 000000000..5306728d7
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_4.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_5.png b/docs/sim-and-tests/regression/img/test-suite_5.png
new file mode 100644
index 000000000..2e857b724
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_5.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_6.png b/docs/sim-and-tests/regression/img/test-suite_6.png
new file mode 100644
index 000000000..91a52a896
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_6.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_7.png b/docs/sim-and-tests/regression/img/test-suite_7.png
new file mode 100644
index 000000000..f3874b370
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_7.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_8.png b/docs/sim-and-tests/regression/img/test-suite_8.png
new file mode 100644
index 000000000..73f987639
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_8.png differ
diff --git a/docs/sim-and-tests/regression/img/test-suite_9.png b/docs/sim-and-tests/regression/img/test-suite_9.png
new file mode 100644
index 000000000..6094536af
Binary files /dev/null and b/docs/sim-and-tests/regression/img/test-suite_9.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_1.png b/docs/sim-and-tests/regression/img/testbundle_1.png
new file mode 100644
index 000000000..cf79dd7d7
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_1.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_2.png b/docs/sim-and-tests/regression/img/testbundle_2.png
new file mode 100644
index 000000000..1d55041df
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_2.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_3.png b/docs/sim-and-tests/regression/img/testbundle_3.png
new file mode 100644
index 000000000..b05c2327e
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_3.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_4.png b/docs/sim-and-tests/regression/img/testbundle_4.png
new file mode 100644
index 000000000..1f8fb1567
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_4.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_5.png b/docs/sim-and-tests/regression/img/testbundle_5.png
new file mode 100644
index 000000000..20e7807fc
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_5.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_6.png b/docs/sim-and-tests/regression/img/testbundle_6.png
new file mode 100644
index 000000000..015798bb0
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_6.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_7.png b/docs/sim-and-tests/regression/img/testbundle_7.png
new file mode 100644
index 000000000..59ca01421
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_7.png differ
diff --git a/docs/sim-and-tests/regression/img/testbundle_8.png b/docs/sim-and-tests/regression/img/testbundle_8.png
new file mode 100644
index 000000000..9c2ef5c1e
Binary files /dev/null and b/docs/sim-and-tests/regression/img/testbundle_8.png differ
diff --git a/docs/simandtests/regression/1-intro.md b/docs/simandtests/regression/1-intro.md
deleted file mode 100644
index b99c8efac..000000000
--- a/docs/simandtests/regression/1-intro.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-sidebar_position: 1
----
-
-# 关于批量测试
-
-批量测试旨在以产品化的方式满足用户对于大规模测试的需求，应用场景包括回归测试、仿真测试等。
-
-用户可以在刻行时空平台上传并管理相关镜像、测试数据、测试套件与测试包，在项目范围内运行批量测试、监控进度并获取测试结果。
-
-
-
-## 基本概念
-
-| 概念名称 | 说明 |
-| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 配置文件
(Config File) | 由用户编写的、指定批量测试运行所需参数的一个文件
_用户需要在运行批量测试前在项目中通过配置文件进行测试的配置，用户可以上传或在线编辑配置文件_ |
-| 镜像
(Image) | 运行批量测试的虚拟环境
_用户可以在刻行平台推送镜像至当前组织并进行管理，在运行批量测试时需要指定使用的镜像版本_ |
-| 测试套件
(Test Suite) | 通常是针对相同或相似测试场景的一组测试，在批量测试中一次性批量执行
_用户可以在刻行平台通过配置文件上传测试套件至当前项目中并进行管理_ |
-| 测试包
(Test Bundle) | 通常是为执行测试用例而编写的一系列代码和相关依赖等
_用户可以在刻行平台上传测试包至当前项目，指定其种类与标签以进行版本管理；在运行批量测试时需要选择测试包版本_ |
-| 测试用例
(Test Case) | 运行批量测试过程中执行的具体任务，通常从相应的测试报告中解析出
_用户可以在批量测试运行完毕后，在结果报告中查看测试报告解析出的测试用例详情与执行结果_ |
-
-
-
-## 使用流程概览
-
-点击进入项目的「批量测试」页面，根据页面提示创建一个批量测试：
-
-
-
-以下步骤概述为你提供了使用批量测试功能的一个基本流程：
-
-1. 准备测试环境
-
- - 准备批量测试环境的 Docker 镜像
- - 将镜像推送至公开平台或[刻行时空镜像仓库](../../image/3-push-image.md)
- - 将测试数据上传到刻行项目中并按「记录」存储
-
-2. 配置测试内容
-
- - 在「测试套件管理」页面上传或编辑配置文件
- - 设置测试套件和相应配置参数
- - 在「测试包管理」页面上传测试包文件
-
-3. 执行与监控
- - 在「批量测试」页面选择运行参数（测试包版本、测试套件等）
- - 启动批量测试（可通过界面或命令行方式）
- - 实时监控测试进度并查看测试结果
-
-更多具体步骤请参见后续章节的详细说明。
diff --git a/docs/simandtests/regression/3-config-management.md b/docs/simandtests/regression/3-config-management.md
deleted file mode 100644
index 1573b5619..000000000
--- a/docs/simandtests/regression/3-config-management.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-sidebar_position: 3
----
-
-# 管理测试配置
-
-> 了解配置文件的编写与上传/编辑，以及查看解析出的测试套件信息。
-
-## 1. 准备配置文件
-
-配置文件为一个名称为 cos.yaml 或 cos.yml 的文件，其具体格式与规则请参见 [配置文件格式与样例](../regression/9-yaml-sample.md)。
-
-
-
-## 2. 上传与编辑配置文件
-
-1. 点击进入「批量测试」-「测试套件管理」页面：
-
-- 首次上传测试套件
-
- 
-
-- 非首次上传测试套件
-
- 
-
-
-
-2. 直接从本地选择配置文件上传或者在线编写配置文件：
-
-
-
-
-
-你可以在「批量测试-测试套件管理」页面右上角点击下载/编辑/上传配置文件
-
-
-
-
-
-其中你可以点击「编辑」在线编辑配置文件，在修改配置文件内容后点击「保存编辑」以更新配置文件：
-
-
-
-
-
-## 3. 查看测试套件信息
-
-格式与内容符合规范的配置文件解析完毕后，测试套件管理页面会显示解析出的测试套件及相关信息。
-
-你可以点击某些列内容查看详细信息，例如你可以点击「测试类型与镜像」列查看与复制镜像地址，点击「查看触发条件」查看该测试套件对应的自动触发条件，点击「查看通知配置」查看该测试套件对应的通知模版内容等：
-
-
-
-
diff --git a/docs/simandtests/regression/4-test-bundle-management.md b/docs/simandtests/regression/4-test-bundle-management.md
deleted file mode 100644
index cada46c40..000000000
--- a/docs/simandtests/regression/4-test-bundle-management.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-sidebar_position: 4
----
-
-# 管理测试包
-
-> 了解测试包文件内容示例，查看如何将测试包上传至刻行平台并进行相应版本管理。
-
-## 1. 准备测试包文件
-
-测试代码文件为一个 .deb 格式的文件或 .zip / .tgz / .tar.gz 格式的压缩文件。
-
-你可以 点击此处下载 示例测试包文件。
-
-
-
-## 2. 上传测试包文件
-
-1. 点击进入「批量测试」-「测试包管理」页面：
-
-- 首次上传测试包
-
- 
-
-- 非首次上传测试包
-
- 
-
-
-
-2. 点击右上角「上传测试包」：
-
-
-
-
-
-3. 选择测试包上传：
-
-
-
-
-
-4. 测试包列表「状态」栏显示「活跃」，即代表该测试包上传成功：
-
-
-
-
diff --git a/docs/simandtests/regression/5-run.md b/docs/simandtests/regression/5-run.md
deleted file mode 100644
index a26c2951a..000000000
--- a/docs/simandtests/regression/5-run.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-sidebar_position: 5
----
-
-# 运行批量测试
-
-> 了解如何运行批量测试，包括在网站上指定相关条件后触发、通过配置文件指定自动触发条件，以及使用命令行在本地运行批量测试等。
-
-## 网页端运行批量测试
-
-1. 点击进入「批量测试」页面：
-
-- 首次运行批量测试
-
- 
-
-- 非首次运行批量测试
-
- 
-
-
-
-2. 选择测试包版本和需要执行的测试套件后，点击「确定」运行批量测试，会使用符合条件的关联记录作为测试数据执测试套件：
-
- 
-
-
-
-## 自动触发批量测试
-
-上传的测试包种类或标签符配置文件中的预设条件时，测试包完成上传后会自动触发批量测试，使用该测试包文件执行符合条件的全部测试套件。
-
-你可以在配置文件中的「on」字段对测试套件设置自动触发条件，具体格式与规则请参见 [配置文件格式与样例-自动触发测试](../regression/9-yaml-sample.md#auto-triggering)。
-
-在「批量测试-测试套件管理」页面中，对于配置了自动触发条件的测试套件，其「关联触发条件」列会显示「查看触发条件」按钮：
-
-
-
-你可以点击「查看触发条件」按钮，查看该测试套件自动触发对应的测试包条件：
-
-
-
-
-
-## 本地运行批量测试
-
-你可以使用命令行，按照以下说明在本地运行批量测试。
-
-### 下载与配置
-
-1. 输入命令以下载所需文件，各操作系统对应命令如下：
-
-- Linux
-
- ```bash
- curl https://coscene-artifacts-production.oss-cn-hangzhou.aliyuncs.com/cos/linux/amd64/latest/cos -o cos
- ```
-
-- macOS
-
- ```bash
- curl https://coscene-artifacts-production.oss-cn-hangzhou.aliyuncs.com/cos/darwin/amd64/latest/cos -o cos
- ```
-
-2. 通过以下命令进行配置：
-
- ```bash
- # 给 cos 可执行权限
- chmod +x cos
-
- # 创建配置目录
- mkdir $HOME/.cos
-
- # 创建配置文件
- cat << EOF > $HOME/.cos/config.yaml
- platform:
- endpoint: ${YOUR_DOMAIN}
- accessToken: ${YOUR_TOKEN}
- project: ${ORG_SLUG}/${PROJECT_SLUG}
- EOF
-
- # 验证配置
- cos config list
- ```
-
- 其中各参数说明如下：
-
- - `endpoint` 中 `${YOUR_DOMAIN}` 需替换成实际的网站地址。如下图的网址，`${YOUR_DOMAIN}` 为 `api.coscene.cn`
-
- 
-
- - `accessToken` 中 `${YOUR_TOKEN}` 的获取步骤如下所示：
-
- 
-
- 
-
- 
-
- - `project` 中 `ORG_SLUG` 和 `PROJECT_SLUG` 需根据实际替换：
-
- 
-
-
-
-### 运行
-
-你可以参考以下命令示例运行批量测试：
-
-```bash
-# 使用最新的测试包运行项目下所有批量测试
-cos test run
-
-# 只用本地的配置文件 cos.yaml 运行批量测试
-cos test run --test-config cos.yaml
-
-# 使用最新的测试包，对项目下名称为 gazebo 的测试套件运行批量测试
-cos test run -t gezebo
-
-# 使用指定的记录 定位采集数据 运行批量测试
-cos test run -r 定位采集数据
-
-# 使用标签为 v0.0.1 的测试包，对项目下所有测试套件运行批量测试
-cos test run --bundle-tag v0.0.1
-
-# 使用种类为 Gazebo 的测试包，对项目下所有测试套件运行批量测试
-cos test run --bundle-category Gazebo
-
-# 上传 bundle.zip 并运行批量测试
-cos test run -b bundle.zip
-```
-
-
diff --git a/docs/simandtests/regression/6-status-and-output.md b/docs/simandtests/regression/6-status-and-output.md
deleted file mode 100644
index 0f71f654d..000000000
--- a/docs/simandtests/regression/6-status-and-output.md
+++ /dev/null
@@ -1,132 +0,0 @@
----
-sidebar_position: 6
----
-
-# 输出结果与查看运行信息
-
-> 了解如何自定义输出的测试结果，如何查看批量测试与其中单个测试的进度与运行产物，以及如何在可视化界面下播放影子模式以对比输出等
-
-## 输出测试结果
-
-你可以通过配置文件和测试代码等自定义输出的测试结果，目前支持输出可解析的结果文件与输出图表。
-
-### 输出可解析的结果文件
-
-批量测试支持解析 JUnit XML 格式的结果文件。你可以在配置文件中的「script」参数中使用以下命令在 `path` 处创建一个 XML 格式的结果文件：
-
-```bash
-pytest --junitxml=path
-```
-
-具体示例请参见 [配置文件格式与样例-输出测试结果文件](../regression/9-yaml-sample.md#save-artifacts)。
-
-支持解析的 JUnit XML 格式的结果文件示例如下，其中结果数据到 JUnit XML 格式的映射请参考 [JUnit Mapping](https://www.ibm.com/docs/en/developer-for-zos/14.1?topic=formats-junit-xml-format#junitschema__table_junitmap)：
-
-```xml
-
-
-
-
-
- WARNING: Use a program name that matches the source file name
- Category: COBOL Code Review – Naming Conventions
- File: /project/PROGRAM.cbl
- Line: 2
-
-
-
-
-```
-
-### 输出图表
-
-你可以在测试报告中增加以 "cos\_" 开头的自定义属性，例如`cos_customer_name`，这些自定义属性将与默认指标一起上传到刻行，刻行会对这些自定义属性进行收集和分析，以及将其作为维度对指标进行分组、排序和过滤展示等。
-
-你可以在镜像中的相关测试代码文件中使用以 "cos\_" 开头的自定义图名，以在测试结果中输出图表，其示例格式如下：
-
-```python
- def test_romeo(record_xml_attribute):
-
- for i in (1, 2, 3):
- rand_float = random.uniform(1, 100)
- record_xml_attribute("cos_test_romeo_val" + str(i), rand_float)
- for i in (1, 2, 3):
- rand_bool = random.choice([True, False])
- record_xml_attribute("cos_test_romeo_bool" + str(i), rand_bool)
-
- assert __count('romeo') > 0
-```
-
-### 输出影子模式文件
-
-> 输出文件至指定目录作为测试输出，其中的.bag文件可与原记录中的文件在可视化界面中对比播放。
-
-你可以配置文件的「script」字段中使用命令将文件输出到 `/cos/outputs` 目录下作为测试输出，具体示例请参见 [配置文件格式与样例-输出影子模式文件](../regression/9-yaml-sample.md#generate-shadow-mode)。
-
-测试输出将展示在测试详情页的「测试输出」栏，按照对应测试套件与记录分级展示。
-
-
-
-
-
-## 查看运行进度与产物
-
-1. 在批量测试页面的列表中，会展示项目内运行过的批量测试及信息，你可以点击某个批量测试序号以查看其详情页面：
-
- 
-
-2. 在批量测试详情页中，「进度」Tab会展示该批量测试的运行进度和其中所有单个测试的运行状态：
-
- 
-
- 你可以点击某个测试标题以查看其详情页面:
-
- 
-
- 点击「步骤」中的单个步骤标题，可以查看其运行日志、步骤详情和运行产物：
-
- 
-
- 你可以在单个步骤的「Artifact」中，查看与下载该步骤的运行产物：
-
- 
-
- 单个测试详情页的「Artifacts」中，可以查看与下载此测试的所有运行产物：
-
- 
-
-3. 你可以在批量测试详情页的「Artifacts」Tab 中，查看与下载该批量测试的所有运行产物：
-
- 
-
-
-
-## 查看运行结果
-
-当批量测试运行完成后，你可以点击批量测试详情页中的「测试报告」Tab 查看测试套件运行结果统计，包括运行信息以及各测试套件运行解析出的测试用例等:
-
-
-
-你可以点击单个测试用例名称，查看该测试用例的运行报告，包括各测试详情列表和输出图表等：
-
-
-
-点击页面右上角的「查看历史数据」，可以查看该测试用例的历史结果数据统计，包括测试的运行结果矩阵、指标统计图等：
-
-
-
-
-
-
-
-## 播放影子模式
-
-测试输出中包含.bag 文件的记录支持影子模式；点击测试详情页的「测试输出」栏中对应记录测试输出列表上方，或者单个测试详情页右上角的「影子模式」按钮进入可视化界面：
-
-
-
-
-
-测试输出文件将与原记录中的文件一起在可视化界面中对比播放。
-
-
diff --git a/docs/simandtests/regression/7-advanced.md b/docs/simandtests/regression/7-advanced.md
deleted file mode 100644
index b2d6e4985..000000000
--- a/docs/simandtests/regression/7-advanced.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-sidebar_position: 7
----
-
-# 更多功能
-
-> 你可以通过本章节的内容了解其他批量测试中涉及的内容，包括接收消息通知、创建一刻等。
-
-
-
-## 接收消息通知
-
-你可以在上传的配置文件中的「notifications」字段，设置在钉钉中接收测试套件运行相关信息，你可以使用自定义的模板规定接受的内容信息。
-
-具体示例请参见 [配置文件格式与样例-消息通知](../regression/9-yaml-sample.md#notifications) 章节。
-
-在「批量测试-测试套件管理」页面中，对于配置了消息通知的测试套件，其「通知」列会显示「查看通知」按钮：
-
-
-
-你可以点击「查看通知」按钮，查看该其消息模版内容：
-
-
-
-
-
-## 创建一刻
-
-批量测试的运行环境集成了 `cos` 命令行工具，可以在程序中运行以下命令创建一刻：
-
-```yaml
-/cos/bins/cos moment create \
- --display-name "急停" \ # moment 名字
- --description "机器急停" \ # moment 描述
- --trigger-time 1532402940 \ # moment 触发时间
- --duration 10 \ # moment 持续时长
- --customized-fields '{"key1": "value1"}' # moment 自定义字段
-```
-
-
diff --git a/docs/simandtests/regression/8-system-directory.md b/docs/simandtests/regression/8-system-directory.md
deleted file mode 100644
index 7e5f93d4c..000000000
--- a/docs/simandtests/regression/8-system-directory.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-sidebar_position: 8
----
-
-# 系统目录概览
-
-| 名称 | 目录 |
-| -------- | -------------- |
-| 测试包 | /cos/bundles |
-| 记录 | /cos/files |
-| Artifact | /cos/artifacts |
-| 测试输出 | /cos/outputs |
diff --git a/docs/simandtests/regression/img/artifacts-1.png b/docs/simandtests/regression/img/artifacts-1.png
deleted file mode 100644
index 3b2223714..000000000
Binary files a/docs/simandtests/regression/img/artifacts-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/auto-trigger-1.png b/docs/simandtests/regression/img/auto-trigger-1.png
deleted file mode 100644
index 5bbafcab2..000000000
Binary files a/docs/simandtests/regression/img/auto-trigger-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/auto-trigger-2.png b/docs/simandtests/regression/img/auto-trigger-2.png
deleted file mode 100644
index 16ba85692..000000000
Binary files a/docs/simandtests/regression/img/auto-trigger-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/bundle-management.png b/docs/simandtests/regression/img/bundle-management.png
deleted file mode 100644
index f70f9fb04..000000000
Binary files a/docs/simandtests/regression/img/bundle-management.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/bundle-status.png b/docs/simandtests/regression/img/bundle-status.png
deleted file mode 100644
index f55adf05c..000000000
Binary files a/docs/simandtests/regression/img/bundle-status.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/choose-bundle.png b/docs/simandtests/regression/img/choose-bundle.png
deleted file mode 100644
index f9c82ff64..000000000
Binary files a/docs/simandtests/regression/img/choose-bundle.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/cli-1.png b/docs/simandtests/regression/img/cli-1.png
deleted file mode 100644
index af243775e..000000000
Binary files a/docs/simandtests/regression/img/cli-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/cli-2.png b/docs/simandtests/regression/img/cli-2.png
deleted file mode 100644
index 404c1b497..000000000
Binary files a/docs/simandtests/regression/img/cli-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/cli-3.png b/docs/simandtests/regression/img/cli-3.png
deleted file mode 100644
index 1e1a4a241..000000000
Binary files a/docs/simandtests/regression/img/cli-3.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/cli-4.png b/docs/simandtests/regression/img/cli-4.png
deleted file mode 100644
index b53c42a8a..000000000
Binary files a/docs/simandtests/regression/img/cli-4.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/cli-5.png b/docs/simandtests/regression/img/cli-5.png
deleted file mode 100644
index 9ce7ad3c1..000000000
Binary files a/docs/simandtests/regression/img/cli-5.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/goto-config-1.png b/docs/simandtests/regression/img/goto-config-1.png
deleted file mode 100644
index 5bb176315..000000000
Binary files a/docs/simandtests/regression/img/goto-config-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/goto-config-2.png b/docs/simandtests/regression/img/goto-config-2.png
deleted file mode 100644
index b39b5b7e1..000000000
Binary files a/docs/simandtests/regression/img/goto-config-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/goto-step.png b/docs/simandtests/regression/img/goto-step.png
deleted file mode 100644
index ac0ca4884..000000000
Binary files a/docs/simandtests/regression/img/goto-step.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/goto-test-bundle-1.png b/docs/simandtests/regression/img/goto-test-bundle-1.png
deleted file mode 100644
index c5e4f1472..000000000
Binary files a/docs/simandtests/regression/img/goto-test-bundle-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/goto-test-bundle-2.png b/docs/simandtests/regression/img/goto-test-bundle-2.png
deleted file mode 100644
index 92e419ab2..000000000
Binary files a/docs/simandtests/regression/img/goto-test-bundle-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/goto-workflow.png b/docs/simandtests/regression/img/goto-workflow.png
deleted file mode 100644
index 1e7533a14..000000000
Binary files a/docs/simandtests/regression/img/goto-workflow.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/manage-config.png b/docs/simandtests/regression/img/manage-config.png
deleted file mode 100644
index cbab131d4..000000000
Binary files a/docs/simandtests/regression/img/manage-config.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/notification-1.png b/docs/simandtests/regression/img/notification-1.png
deleted file mode 100644
index 69b1116a1..000000000
Binary files a/docs/simandtests/regression/img/notification-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/notification-2.png b/docs/simandtests/regression/img/notification-2.png
deleted file mode 100644
index bed0e447e..000000000
Binary files a/docs/simandtests/regression/img/notification-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/report-1.png b/docs/simandtests/regression/img/report-1.png
deleted file mode 100644
index 5c749813a..000000000
Binary files a/docs/simandtests/regression/img/report-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/report-3.png b/docs/simandtests/regression/img/report-3.png
deleted file mode 100644
index 1d10b766f..000000000
Binary files a/docs/simandtests/regression/img/report-3.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/run-1.png b/docs/simandtests/regression/img/run-1.png
deleted file mode 100644
index b541a3ec4..000000000
Binary files a/docs/simandtests/regression/img/run-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/run-2.png b/docs/simandtests/regression/img/run-2.png
deleted file mode 100644
index b14efbf40..000000000
Binary files a/docs/simandtests/regression/img/run-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/run-wfrun.png b/docs/simandtests/regression/img/run-wfrun.png
deleted file mode 100644
index 77b04bf08..000000000
Binary files a/docs/simandtests/regression/img/run-wfrun.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/shadow-mode-1.png b/docs/simandtests/regression/img/shadow-mode-1.png
deleted file mode 100644
index 8287f648b..000000000
Binary files a/docs/simandtests/regression/img/shadow-mode-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/shadow-mode-2.png b/docs/simandtests/regression/img/shadow-mode-2.png
deleted file mode 100644
index e026b55ed..000000000
Binary files a/docs/simandtests/regression/img/shadow-mode-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/shadow-mode-3.png b/docs/simandtests/regression/img/shadow-mode-3.png
deleted file mode 100644
index 0d371e0a4..000000000
Binary files a/docs/simandtests/regression/img/shadow-mode-3.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/shadow-mode-4.png b/docs/simandtests/regression/img/shadow-mode-4.png
deleted file mode 100644
index 424b7023e..000000000
Binary files a/docs/simandtests/regression/img/shadow-mode-4.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/status-1.png b/docs/simandtests/regression/img/status-1.png
deleted file mode 100644
index 31be8df24..000000000
Binary files a/docs/simandtests/regression/img/status-1.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/status-2.png b/docs/simandtests/regression/img/status-2.png
deleted file mode 100644
index de2bc641f..000000000
Binary files a/docs/simandtests/regression/img/status-2.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/status-3.png b/docs/simandtests/regression/img/status-3.png
deleted file mode 100644
index f89cbac88..000000000
Binary files a/docs/simandtests/regression/img/status-3.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/status-4.png b/docs/simandtests/regression/img/status-4.png
deleted file mode 100644
index 2f7b7d0bd..000000000
Binary files a/docs/simandtests/regression/img/status-4.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/test-suite-info.png b/docs/simandtests/regression/img/test-suite-info.png
deleted file mode 100644
index ce8929c05..000000000
Binary files a/docs/simandtests/regression/img/test-suite-info.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/update-config.png b/docs/simandtests/regression/img/update-config.png
deleted file mode 100644
index 46abbb75e..000000000
Binary files a/docs/simandtests/regression/img/update-config.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/upload-config.png b/docs/simandtests/regression/img/upload-config.png
deleted file mode 100644
index 34b2cbacd..000000000
Binary files a/docs/simandtests/regression/img/upload-config.png and /dev/null differ
diff --git a/docs/simandtests/regression/img/upload-test-bundle.png b/docs/simandtests/regression/img/upload-test-bundle.png
deleted file mode 100644
index f935749bf..000000000
Binary files a/docs/simandtests/regression/img/upload-test-bundle.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/image/1-intro.md b/i18n/en/docusaurus-plugin-content-docs/current/image/1-intro.md
index b3f39bc9d..49cbeb12f 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/image/1-intro.md
+++ b/i18n/en/docusaurus-plugin-content-docs/current/image/1-intro.md
@@ -24,4 +24,4 @@ Docker images are typically built from a base image and customized through a Doc
# About coScene Image Registry
-The coScene platform provides a private image registry, eliminating the need for users to set up their own. Users can quickly upload existing images to the coScene image registry, enabling immediate use of these images on the coScene platform to build business processes and improve development efficiency. The coScene image registry is supported in features such as [Automation](../workflow/action/1-quickstart.md) and [Batch Testing](../simandtests/regression/1-intro.md).
+The coScene platform provides a private image registry, eliminating the need for users to set up their own. Users can quickly upload existing images to the coScene image registry, enabling immediate use of these images on the coScene platform to build business processes and improve development efficiency. The coScene image registry is supported in features such as [Automation](../workflow/action/1-quickstart.md) and [Batch Testing](../sim-and-tests/regression/1-intro.md).
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/_category_.json
similarity index 100%
rename from i18n/en/docusaurus-plugin-content-docs/current/simandtests/_category_.json
rename to i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/_category_.json
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/1-intro.md b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/1-intro.md
new file mode 100644
index 000000000..e1f67e2ec
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/1-intro.md
@@ -0,0 +1,89 @@
+---
+sidebar_position: 1
+---
+
+# About Cloud Test
+
+Batch testing is an automated solution for parallel execution of multiple test tasks, primarily used in large-scale testing scenarios such as regression testing and simulation testing. The platform provides comprehensive test resource management capabilities, supporting unified management of images, datasets, test suites, and test bundles, enabling one-stop test execution, status monitoring, and result analysis within projects.
+
+## Basic Information
+### Key Concepts
+
+| Name | Description |
+| --- | --- |
+| Image | Virtual environment for running batch tests |
+| Test Suite | A collection of related test cases, typically testing specific functions or scenarios |
+| Test Bundle | A series of code and related dependencies written to execute test cases |
+| Test Case | Specific tasks executed during batch testing, usually parsed from corresponding test reports |
+
+The execution flow of batch testing tasks is as follows:
+1. Select a test suite and use its preset image as the test environment
+2. Import test bundles, test data ([records](../../collaboration/record/1-quick-start-record.md)), and test suite configuration parameters into the test environment
+3. The system creates independent sub-test tasks for each record associated with the test suite
+4. After all sub-test tasks are completed, the system automatically aggregates results and generates test reports
+
+### System Directories
+Batch testing supports the following directory structure:
+| Name | Directory |
+| -------- | -------------- |
+| Test Bundle | /cos/bundles |
+| Records | /cos/files |
+| Artifact | /cos/artifacts |
+| Test Output | /cos/outputs |
+
+## Batch Testing Interface
+### Batch Testing List Page
+
+
+
+- **Test serial number**: Unique identifier for tests, incrementing sequentially, click to view details
+- **Test time**: Test start time, hover to view specific time
+- **Test status**: Current test status, including queued, running, completed, no results. Where:
+ - "Completed" indicates the test is finished (regardless of test case execution success)
+ - "No Results" indicates no results were parsed, see [how to output test results](./6-status-and-output.md)
+- **Test suite name**: Name of the selected test suite, see [Test Suite](./3-config-management.md)
+- **Test bundle category, version**: Selected test bundle category and version, see [Test Bundle](./4-test-bundle-management.md)
+- **Test progress**: One test contains multiple sub-test tasks, hover to view specific progress
+- **Test pass rate**: Ratio of passed tests to total tests.
+ - Calculation formula: Values used for calculating pass rate per test suite = Number of parsed cases × Number of associated records
+- **Test duration**: Total test duration
+- **Actions**:
+ - Cancel Running
+ - Re-run Regression
+ - Download Artifacts
+ - Download test outputs
+
+### Batch Testing Details Page
+- **Regression Report**: Displays test duration, test count, pass rate, test results, and other information
+
+ 
+
+ - Test cases parsed from test suite: One test suite can parse multiple cases, each with corresponding execution results
+ - Click test case name to view specific results
+
+- **Test Progress**: Shows execution status of each sub-test task, view corresponding execution logs, Artifacts, and test outputs in sub-test task details
+- **Artifacts**: Result files generated during testing, such as test reports
+- **Test Output**: Files needing visualization generated during testing, such as ROSbag
+
+## Usage Process Overview
+Enter the project's "Batch Testing" page and create a batch test following the prompts:
+
+
+
+1. Prepare Test Environment and Data
+
+ - Prepare [Docker image](../../image/1-intro.md) for running batch tests
+ - Push image to public platform or [coScene Image Registry](../../image/3-push-image.md)
+ - Upload test data to project and store as [records](../../collaboration/record/1-quick-start-record.md)
+
+2. Configure Test Content
+
+ - Set up test suites and corresponding configuration parameters on the "[Test Suite Management](./3-config-management.md)" page
+ - Upload test programs on the "[Test Bundle Management](./4-test-bundle-management.md)" page
+
+3. Execute and Monitor
+ - Select test bundle version and test suite in the "[Run a Cloud Test](./5-run.md)" dialog
+ - Start batch test
+ - Monitor test progress in real-time and [view test results](./6-status-and-output.md#viewing-test-results)
+
+For details, please refer to the following chapters.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/3-config-management.md b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/3-config-management.md
new file mode 100644
index 000000000..5559f70af
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/3-config-management.md
@@ -0,0 +1,160 @@
+---
+sidebar_position: 3
+---
+
+# Test Suite
+## Introduction
+A test suite is a collection of related test cases that provides a unified configuration management interface. It supports setting test names, runtime environments (images), test data (records), and other parameters to achieve standardized management of test cases.
+
+
+
+## Managing Test Suites
+### Prerequisites
+1. Ensure that test data has been stored as [records](../../collaboration/record/1-quick-start-record.md) and each record has been labeled
+
+ 
+
+2. Ensure that the test environment (image) is ready and has been pushed to a public platform or [coScene Image Registry](../../image/1-intro.md).
+ It is recommended to define test cases in the image:
+ - Test cases support parsing, see [Defining Test Results](./6-status-and-output.md#defining-test-results)
+ - Input and output directories for batch testing, see [System Directories](./1-intro.md#system-directories)
+
+### Creating Test Suites
+1. In the project's left sidebar, select "Testing" and click to enter the "Test Suite Management" page:
+
+ - First time editing test suite
+
+ 
+
+ - Subsequent editing of test suite
+
+ 
+
+2. Click [Edit] to enter the test suite editing page:
+
+ 
+ 
+
+3. Fill in the test suite name, runtime environment, test data, and other information:
+
+ ```yaml
+ # Example file
+
+ # Version number, currently supported version is "1"
+ version: '1'
+
+ # Test name is workflow name
+ name: 'workflow name'
+
+ # A job consists of one or more test suites that can be tested in parallel
+ jobs:
+ # First test suite named "test-1"
+ - name: 'test-1'
+ # Test type is "generic"
+ type: 'generic'
+
+ # Image address
+ images:
+ # Enter image address according to test type
+ base: /coscene-hello/position:v1.0.0
+
+ # Associated records
+ records:
+ # This test suite's associated record label is "sample"
+ labels:
+ - 'sample'
+
+ # Run commands for this test suite
+ parameters:
+ script:
+ - /bin/sh
+ - -c
+ - 'echo hello'
+
+ # Message notification template for test suite "test-1"
+ notifications:
+ # Notify to DingTalk group
+ - dingTalkBot:
+
+ # Second test suite named "test-2"
+ - name: 'test-2'
+
+ # Control when to automatically trigger this test
+ on:
+ # Trigger when uploading test bundle that meets the following conditions
+ bundlePush:
+ # Condition: test bundle category is "test"
+ category:
+ - test
+ ```
+
+ - **version**: Version number, currently supported version is `'1'`
+ - **name**: Test name
+ - **jobs**: List of test suites
+ - **name**: Test suite name
+ - **type**: Test type, currently supported type is `'generic'`
+ - **images**: Images for running test suite, supports using coScene Image Registry or public platform images
+ - **records**: Records used when running this test suite, associated through labels
+ - **parameters**: Parameters used when running this test suite
+ - **notifications**: Message notification template sent after test suite completion
+ - **on**: Automatic test triggering
+ - **bundlePush**: Triggers when uploading test bundle whose "category" meets conditions
+
+ For specific format details, see [Configuration Yaml Sample](./9-yaml-sample.md).
+
+4. Click [Save] to save the test suite configuration file.
+
+ 
+
+### Upload, Download, and Edit
+> The test suite configuration file is cos.yaml, supporting direct upload, download, and editing.
+
+1. In the project's left sidebar, select "Testing" and click to enter the "Test Suite Management" page:
+
+ 
+
+2. Upload, download, or directly edit the configuration file:
+
+ 
+
+3. Click [Save] to save the test suite configuration file.
+
+ 
+
+### View
+After configuration file validation passes, the test suite management page will display the parsing results, including basic information, runtime environment, data associations, and trigger conditions of the test suite.
+
+- Test name and test suite name
+
+ 
+
+- Test type and image
+
+ 
+
+- Associated records
+
+ 
+
+- Associated trigger conditions
+
+ 
+
+### Usage
+When running batch tests, you can select a test suite, and the system will run tests according to the test suite configuration information.
+
+
+## Learn More
+- [Configuration Yaml Sample](./9-yaml-sample.md)
+- [Test Bundle](./4-test-bundle-management.md)
+- [Managing Test Results](./6-status-and-output.md)
+- [Run a Cloud Test](./5-run.md)
+
+## FAQ
+1. **Q: Cannot save test suite, error message "Record error: Label does not exist: sample"**
+
+ A: Please check if the test suite named "sample" has incorrect labels, such as non-existent or incorrectly written labels. Only existing labels are supported here. Learn [how to add labels to records](../../collaboration/record/3-manage-records.md#edit)
+
+2. **Q: Cannot save test suite, error message "Please check yaml file format"**
+
+ A: Please check if the test suite configuration file format is correct. If the configuration file format is incorrect, refer to [Configuration Yaml Sample](./9-yaml-sample.md)
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/4-test-bundle-management.md b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/4-test-bundle-management.md
new file mode 100644
index 000000000..3357aa0f8
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/4-test-bundle-management.md
@@ -0,0 +1,59 @@
+---
+sidebar_position: 4
+---
+
+# Test Bundle
+## Introduction
+A test bundle is the code file being tested, which can be a .deb format file or a compressed file in .zip/.tgz/.tar.gz format.
+
+
+
+## Managing Test Bundles
+### Upload Test Bundle
+1. In the project's left sidebar, select "Testing" and click to enter the "Test Bundle Management" page:
+
+- First time uploading test bundle
+
+ 
+
+- Subsequent uploads of test bundle
+
+ 
+
+2. Click [Upload Test Bundle]:
+
+ 
+
+3. Upload test bundle, fill in test category and version:
+
+ .default})
+
+ - **Test Bundle Category**: Enter custom category information or select from existing test categories.
+
+ - **Test Bundle Version**: Enter custom version information, such as `v0.1`
+
+ Test category and version information can be used for automatic test triggering. See [Configuration Yaml Sample - Auto-Triggering Tests](./9-yaml-sample.md#auto-triggering)
+
+4. After uploading the test bundle, when the "Status" column in the list shows "Active", it indicates that the test bundle has been successfully uploaded:
+
+ 
+
+### Download
+1. In the project's left sidebar, select "Testing" and click to enter the "Test Bundle Management" page:
+
+ 
+
+2. Click the "Download" button for the test bundle in the list to download it:
+
+ 
+
+### Usage
+When running batch tests, you can select a specific version of the test bundle to execute test tasks. Test bundles can be identified by their sequence number, category, and version number.
+
+.default})
+
+## Learn More
+- [Run a Cloud Test](./5-run.md)
+- [Configuration Yaml Sample](./9-yaml-sample.md)
+- [Managing Test Results](./6-status-and-output.md)
+- [Test Suite](./3-config-management.md)
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/5-run.md b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/5-run.md
new file mode 100644
index 000000000..5d39fde47
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/5-run.md
@@ -0,0 +1,54 @@
+---
+sidebar_position: 5
+---
+
+# Run a Cloud Test
+
+> Learn how to run batch tests, including manual triggering and automatic triggering.
+
+## Prerequisites
+1. Created [Test Suite](./3-config-management.md)
+2. Uploaded [Test Bundle](./4-test-bundle-management.md)
+
+## Manual Execution
+
+1. In the project's left sidebar, select "Testing" and click the [Run Batch Test] button
+
+- First time running batch test
+
+ 
+
+- Subsequent runs of batch test
+
+ 
+
+2. In the Run Batch Test dialog, select the test bundle and test suite, then click [Confirm] to run the batch test.
+
+
+
+3. The system will create independent test tasks for each record associated with the test suites. For example, when a test suite is associated with 10 records, the system will create 10 sub-tasks, each using the selected test bundle and test suite configuration to test a single record.
+
+ 
+
+4. After completion, you can view the test results in the test list. See [Managing Test Results](./6-status-and-output.md) for details.
+
+ 
+
+## Automatic Triggering
+When the uploaded "Test Bundle" meets the [preset trigger conditions](./9-yaml-sample.md#auto-triggering) in the test suite, the system will automatically execute the relevant test suites.
+
+To view the automatic trigger conditions for a test suite:
+1. Go to the "Testing - Test Suite Management" page and find the test suite with "Associated Trigger Conditions" indicator:
+
+ 
+
+2. Click [View Trigger Conditions] to see the specific trigger rules for that test suite:
+
+
+
+## Learn More
+- [How to Output Test Results](./6-status-and-output.md)
+- [How to View Run Information](./6-status-and-output.md#viewing-test-results)
+- [Managing Test Suites](./3-config-management.md)
+- [Managing Test Bundles](./4-test-bundle-management.md)
+- [Automatic Test Triggering](./9-yaml-sample.md#auto-triggering)
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/6-status-and-output.md b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/6-status-and-output.md
new file mode 100644
index 000000000..5605778d4
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/6-status-and-output.md
@@ -0,0 +1,175 @@
+---
+sidebar_position: 6
+---
+
+# Test Metadata and Test Results
+Batch testing provides comprehensive test result management capabilities, including test case parsing, run status tracking, log collection, and artifact management. The platform offers standardized result parsing engines, visualized report displays, and rich data analysis functions.
+
+## Defining Test Results
+### Defining Test Reports
+Batch testing supports parsing JUnit XML format files. Output test result files in [Artifacts](./1-intro.md#system-directories), and the system will automatically parse and display the test results. Examples:
+- Output .xml files in the Artifacts of each record's test run:
+
+ 
+
+- The system will automatically parse and display the test report:
+
+ 
+
+There are two methods to create JUnit XML format files:
+- Use the `pytest_junit` plugin of the `pytest` library in your code
+- Use commands in the configuration file to output xml files. See [Configuration Yaml Sample - Output Test Result Files](../regression/9-yaml-sample.md#save-artifacts).
+
+Example of supported test result file:
+> For mapping of result data to JUnit XML format, refer to [JUnit Mapping](https://www.ibm.com/docs/en/developer-for-zos/14.1?topic=formats-junit-xml-format#junitschema__table_junitmap)
+
+```xml
+
+
+
+
+
+ WARNING: Use a program name that matches the source file name
+ Category: COBOL Code Review – Naming Conventions
+ File: /project/PROGRAM.cbl
+ Line: 2
+
+
+
+
+```
+
+### Defining Output Charts
+In JUnit XML format test result files, you can add custom attributes prefixed with "cos_" (e.g., `cos_customer_name`). The system will automatically parse these attributes and their corresponding metric values to generate visualization charts (bar charts, box plots).
+
+Currently supported data types are: boolean and float. Here's an example of outputting charts in the test code file:
+
+```python
+def test_romeo(record_xml_attribute):
+ for i in (1, 2, 3):
+ rand_float = random.uniform(1, 100)
+ record_xml_attribute("cos_test_romeo_val" + str(i), rand_float)
+ for i in (1, 2, 3):
+ rand_bool = random.choice([True, False])
+ record_xml_attribute("cos_test_romeo_bool" + str(i), rand_bool)
+
+ assert __count('romeo') > 0
+```
+
+### Custom Output Files
+Files generated during testing can be output to the following directories:
+
+- Artifacts: /cos/artifacts
+- Test Output: /cos/outputs
+
+File preview and playback support:
+
+
+
+- Files in the "Artifacts" directory only support preview
+- Files in the "Outputs" directory support both preview and playback. ROSbag files will automatically enter "Shadow Mode" during playback for synchronized comparison with the original record
+
+### Creating Moments
+Batch testing supports creating moments at key time points (such as when machine offset is abnormal or device failures occur) for quick problem location and analysis later. Moments can:
+
+- Mark important time points
+- Record when problems occur
+- Extract key segments for analysis
+
+Use the built-in `cos` command line tool in the batch testing environment to create moments. The specific command is:
+
+```
+/cos/bins/cos moment create \
+ --display-name "Emergency Stop" \ # moment name
+ --description "Machine emergency stop" \ # moment description
+ --trigger-time 1532402940 \ # moment trigger time
+ --duration 10 \ # moment duration
+ --customized-fields '{"key1": "value1"}' # moment custom fields
+```
+
+To view moments in the visualization page, see [Moments](../../viz/5-create-moment-viz.md)
+
+## Viewing Test Results
+The batch testing list page displays the execution history of all tests, including test status, progress, and other information. Click on the test sequence number to view complete information on the details page:
+
+ 
+
+### Viewing Progress and Artifacts
+1. In the "Progress" section of the batch test details page, you can view the running status and execution progress of all subtasks:
+
+ 
+
+2. Click on the subtitle of a subtask to view its details page:
+
+ 
+
+3. On the subtask details page, you can view the running status, progress, execution logs, test artifacts, and other information:
+ - **Records**: Click on the record name to view record details
+ - **Steps**: Click on the step name to view execution logs
+ - **Artifacts**: View or download result files generated during testing, such as test reports
+ - **Outputs**: Play files that need visualization, such as ROSbag files
+
+ 
+
+4. In the "Artifacts" section of the batch test details page, you can view and download all Artifacts for this batch test. The file hierarchy is as follows:
+
+ ```plaintext
+ All Artifacts
+ ├── Test Suite A
+ │ ├── Record 1
+ │ │ ├── report.xml
+ │ │ └── ...
+ │ └── Record 2
+ │ └── ...
+ └── Test Suite B
+ └── ...
+ ```
+
+ 
+
+4. In the "Test Output" section of the batch test details page, you can view and download all test outputs for this batch test. The file hierarchy is as follows:
+
+ ```plaintext
+ All Test Outputs
+ ├── Test Suite A
+ │ ├── Record 1
+ │ │ ├── test.bag
+ │ │ └── ...
+ │ └── Record 2
+ │ └── ...
+ └── Test Suite B
+ └── ...
+ ```
+
+### Viewing Test Reports
+After the batch test is completed, you can view test suite execution result statistics in the "Test Report" section, including running information and test cases parsed from each test suite:
+
+
+
+Click on an individual test case name to view its execution report, including test detail lists and output charts:
+
+
+
+Click "View History" in the upper right corner to view historical result statistics for this test case, including test result matrix and metric statistics charts:
+
+
+
+
+
+### Playing Shadow Mode
+If there are ROSbag files in the test output, they can be played back in comparison with the original record.
+
+1. In the "Test Output" section of the test details page, select the corresponding record level and click the "Shadow Mode" button in the upper right corner to enter the visualization interface:
+
+ 
+
+2. The test output files will be played back together with the files from the original record in the visualization interface.
+
+ 
+
+## Learn More
+- [Test Bundle](./4-test-bundle-management.md)
+- [Test Suites](./3-config-management.md)
+- [Run a Cloud Test](./5-run.md)
+- [Records](../../collaboration/record/1-quick-start-record.md)
+- [Visualization](../../viz/1-about-viz.md)
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/9-yaml-sample.md b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/9-yaml-sample.md
similarity index 94%
rename from i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/9-yaml-sample.md
rename to i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/9-yaml-sample.md
index 86bbbc1da..0bd6d5b2a 100644
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/9-yaml-sample.md
+++ b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/9-yaml-sample.md
@@ -3,12 +3,9 @@ sidebar_position: 9
---
# Configuration Yaml Example
+This chapter introduces the syntax rules and usage examples of the test suite configuration file (cos.yaml), helping you quickly configure and manage test suites.
-> Through this section, you can understand the writing rules of batch testing configuration files; this section will also provide sample files for reference.
-
-
-
-Supported configuration files are of the type yaml or yml, and the name must be **cos.yaml** or **cos.yml**. You can copy directly or click here to download the sample configuration file and make modifications. Its basic structure is as follows:
+The system supports parsing YAML format configuration files, and the file name must be **cos.yaml** or **cos.yml**. You can create one by referring to the examples below:
## Customize Testing Suite {#customize-testing-bundle}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/_2-image-management.md b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/_2-image-management.md
similarity index 100%
rename from i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/_2-image-management.md
rename to i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/_2-image-management.md
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/_category_.json
similarity index 100%
rename from i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/_category_.json
rename to i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/_category_.json
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/4-8-regression-intro.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/4-8-regression-intro.png
similarity index 100%
rename from i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/4-8-regression-intro.png
rename to i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/4-8-regression-intro.png
diff --git a/docs/simandtests/regression/img/artifacts-2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/artifacts-2.png
similarity index 100%
rename from docs/simandtests/regression/img/artifacts-2.png
rename to i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/artifacts-2.png
diff --git a/docs/simandtests/regression/img/artifacts-3.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/artifacts-3.png
similarity index 100%
rename from docs/simandtests/regression/img/artifacts-3.png
rename to i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/artifacts-3.png
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/artifacts_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/artifacts_1.png
new file mode 100644
index 000000000..0d92fb25d
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/artifacts_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-detail_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-detail_1.png
new file mode 100644
index 000000000..74ad19f6f
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-detail_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-intro.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-intro.png
new file mode 100644
index 000000000..f662fb9d3
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-intro.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-list.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-list.png
new file mode 100644
index 000000000..f63180ce7
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-list.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-list_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-list_1.png
new file mode 100644
index 000000000..b1cf4f619
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/regression-list_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_1.png
new file mode 100644
index 000000000..7e99669e6
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_2.png
new file mode 100644
index 000000000..ffbdb8c82
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_3.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_3.png
new file mode 100644
index 000000000..572ded7b4
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/report_3.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_1.png
new file mode 100644
index 000000000..c0f7aad31
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_2.png
new file mode 100644
index 000000000..ba5bc1a47
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_3.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_3.png
new file mode 100644
index 000000000..42ee69b7e
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/result_3.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_1.png
new file mode 100644
index 000000000..c74844962
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_2.png
new file mode 100644
index 000000000..8d32b8d1c
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_3.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_3.png
new file mode 100644
index 000000000..eb23e3703
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_3.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_4.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_4.png
new file mode 100644
index 000000000..3450cf190
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_4.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_5.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_5.png
new file mode 100644
index 000000000..3960a91f9
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/run_5.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/shadow-mode_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/shadow-mode_1.png
new file mode 100644
index 000000000..06f95502b
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/shadow-mode_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/shadow-mode_2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/shadow-mode_2.png
new file mode 100644
index 000000000..0cd67ee9f
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/shadow-mode_2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/status_2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/status_2.png
new file mode 100644
index 000000000..e67502e5d
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/status_2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/status_3.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/status_3.png
new file mode 100644
index 000000000..c25bc9ad6
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/status_3.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_1.png
new file mode 100644
index 000000000..ea123fdf6
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_2.png
new file mode 100644
index 000000000..ab85958ba
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_3.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_3.png
new file mode 100644
index 000000000..9793d06bf
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_3.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_4.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_4.png
new file mode 100644
index 000000000..c9f460c4d
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_4.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_5.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_5.png
new file mode 100644
index 000000000..0fbcab51b
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_5.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_6.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_6.png
new file mode 100644
index 000000000..ae1f990af
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_6.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_7.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_7.png
new file mode 100644
index 000000000..2b50485e0
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_7.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_8.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_8.png
new file mode 100644
index 000000000..fd3eccf6d
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-bundle_8.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_1.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_1.png
new file mode 100644
index 000000000..cd695c2bf
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_10.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_10.png
new file mode 100644
index 000000000..8a2b02af5
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_10.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_11.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_11.png
new file mode 100644
index 000000000..1349ba2c5
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_11.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_12.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_12.png
new file mode 100644
index 000000000..df10349fa
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_12.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_14.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_14.png
new file mode 100644
index 000000000..305b20eb8
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_14.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_2.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_2.png
new file mode 100644
index 000000000..d6e39477b
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_3.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_3.png
new file mode 100644
index 000000000..734b44200
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_3.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_4.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_4.png
new file mode 100644
index 000000000..3d6ebe6d9
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_4.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_5.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_5.png
new file mode 100644
index 000000000..76a21e7e6
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_5.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_6.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_6.png
new file mode 100644
index 000000000..917b557f6
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_6.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_7.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_7.png
new file mode 100644
index 000000000..55f6983b1
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_7.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_8.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_8.png
new file mode 100644
index 000000000..72d7c7c85
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_8.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_9.png b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_9.png
new file mode 100644
index 000000000..a91008afe
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs/current/sim-and-tests/regression/img/test-suite_9.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/1-intro.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/1-intro.md
deleted file mode 100644
index 75d7cf380..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/1-intro.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-sidebar_position: 1
----
-
-# About Cloud Test
-
-Batch testing aims to meet users' needs for large-scale testing in a productized manner, with application scenarios including regression testing, simulation testing, etc.
-
-Users can upload and manage relevant images, test data, test suites, and test packages on the coScene platform, run batch tests within the project scope, monitor progress, and obtain test results.
-
-
-
-## Basic Concepts
-
-| Concept Name | Description |
-| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
-| Configuration File | A file written by the user specifying the parameters required for batch test execution. It is uploaded or edited online before testing. |
-| Image | The virtual environment for running batch tests. Users push images to the platform and specify the image version during testing. |
-| Test Suite | Typically a set of tests for similar scenarios, executed in batch during batch testing. Users upload test suites using a configuration file. |
-| Test Bundle | Typically a series of codes and related dependencies written for executing test cases. Users upload test bundles to manage its versions. |
-| Test Case | The specific task executed during the batch test, usually parsed from the corresponding test report. |
-
-
-
-## Overview of the Usage Process
-
-Click to enter the project's "Batch Testing" page and create a batch test according to the page prompts:
-
-
-
-The following step-by-step overview provides you with a basic process for using the batch testing feature:
-
-1. Upload test data to the coScene project and store it as a record.
-2. Ensure the organization has the appropriate available image or push images to the coScene platform.
-3. Upload or edit the configuration file online on the "Test Suite Management" page to obtain the test suite and corresponding configuration parameters.
-4. Upload the test package file on the "Test Package Management" page to generate a test package version; if the uploaded test package meets the test suite association trigger condition, it will automatically trigger a batch test.
-5. On the "Batch Testing" page, click the button and select run parameters (test package version, test suite, etc.) to run the batch test; or run the batch test directly from the command line locally.
-6. Click on the batch test to view the progress and test results.
-
-For more detailed steps, please refer to the detailed explanations in the following chapters.
-
-
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/2-image-management.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/2-image-management.md
deleted file mode 100644
index 895766cda..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/2-image-management.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-sidebar_position: 2
----
-
-# Image Management
-
-> Learn how to configure image files, push images to the coScene platform, and manage them.
-
-## 1. Prepare Image Files
-
-**1. Run Docker**
-
-**2. Configure the Image**
-
-Create a new folder containing the dockerfile and related test code.
-
-- Sample dockerfile:
-
-```
-FROM ubuntu:latest
-
-RUN apt update -y
-RUN apt upgrade -y
-RUN apt install -y python3 unzip python-is-python3
-RUN apt install -y python3-pip
-RUN pip install pytest
-copy tests.py /tests.py
-```
-
-- Sample test code:
-
-```
-import os
-import subprocess
-import tempfile
-
-BUNDLE_DIR = '/cos/bundles'
-DATA_DIR = '/cos/files'
-ARTEFACT_DIR = '/cos/artifacts'
-
-def __count(word):
-with tempfile.TemporaryDirectory() as d:
-print(d)
-os.system('unzip %s/\*.zip -d %s' % (BUNDLE_DIR, d))
-
- cmd = [d + '/count', word , DATA_DIR, ARTEFACT_DIR]
- print('RUNNING TEST COMMAND')
- print(cmd)
- proc = subprocess.run(cmd, text=True, capture_output=True)
- print('COMMAND RETURN CODE IS: ' + str(proc.returncode))
- output = proc.stdout
- print('COMMAND OUTPUT IS: ' + output)
- return int(output)
-
-def test_romeo():
-assert __count('romeo') > 0
-```
-
-- If you need to output graphic test reports in the final test results, please refer to the [Output Test Results](../regression/6-status-and-output.md#output-charts) section.
-
-**3. Build the Image**
-
-Once the image file is ready, open the terminal, navigate to the corresponding folder, and execute the command to build the image. The commands for different operating systems are as follows (please replace the image address part as needed):
-
-- Linux:
-
-```
-docker build -f dockerfile -t cr.coscene.cn/coscene-lark/image:latest .
-```
-
-- macOS:
-
-```
-docker build -f dockerfile -t cr.coscene.cn/coscene-lark/image:latest --platform linux/amd64 .
-```
-
-
-
-## 2. Push the Image
-
-Log in to the coScene platform. In "My Settings - Security - Access coScene Container Image Repository", click "Generate Access Command" to obtain access rights to the coScene container image repository:
-
-
-
-
-
-Copy the above command and execute it in the terminal to log in and push the image to the coScene platform.
-
-
-
-## 3. View the Organization Image List
-
-In the "My - Organization Management - Images" page, you can view the image list within the current organization:
-
-
-
-Click on the image name to display all versions of that image. You can click the "Copy" button to copy the full image address:
-
-
-
-
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/3-config-management.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/3-config-management.md
deleted file mode 100644
index 6bff9e0e4..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/3-config-management.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-sidebar_position: 3
----
-
-# Configuration Management
-
-> Learn about writing, uploading/editing configuration files, and viewing parsed test suite information.
-
-## 1. Prepare Configuration File
-
-The configuration file is named either `cos.yaml` or `cos.yml`. For its specific format and rules, please refer to [Configuration File Format and Samples](../regression/9-yaml-sample.md).
-
-
-
-## 2. Upload and Edit Configuration File
-
-On the "Batch Testing - Test Suite Management" page within the project, you can directly select and upload a configuration file from your local device or write one online:
-
-
-
-
-
-You can click on the top right corner of the "Batch Testing - Test Suite Management" page to download/edit/upload configuration files.
-
-
-
-
-
-You can click "Edit" to edit the configuration file online. After modifying the content of the configuration file, click "Save Edits" to update it:
-
-
-
-
-
-## 3. View Test Suite Information
-
-After parsing a configuration file that adheres to the format and content standards, the test suite management page will display the parsed test suites and related information.
-
-You can click on some column content to view detailed information. For example, you can click on the "Test Type and Image" column to view and copy the image address, click "View Trigger Conditions" to view the automatic trigger conditions for that test suite, click "View Notification Configuration" to view the notification template content for that test suite, and more:
-
-
-
-
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/4-test-bundle-management.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/4-test-bundle-management.md
deleted file mode 100644
index 47b60c6bb..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/4-test-bundle-management.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-sidebar_position: 4
----
-
-# Test Bundle Management
-
-> Understand the sample content of the test bundle file, and see how to upload the test bundle to the coScene platform and manage its versions.
-
-## 1. Prepare Test Bundle File
-
-The test code file is a .deb format file or a .zip / .tgz / .tar.gz format compressed file.
-
-You can click here to download a sample test bundle file.
-
-
-
-## 2. Upload Test Bundle File
-
-1. Click to enter the "Batch Testing" - "Test Bundle Management" page:
-
-
-
-
-
-2. Click on the top right "Upload Test Bundle":
-
-
-
-
-
-3. Choose bundle:
-
-
-
-
-
-4. The "Status" column in the test bundle list shows "Active", which means the test bundle has been successfully uploaded:
-
-
-
-
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/5-run.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/5-run.md
deleted file mode 100644
index 6b51fb67a..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/5-run.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
-sidebar_position: 5
----
-
-# Run a Cloud Test
-
-> Learn how to execute batch tests, including triggering them on the website by specifying related conditions, automatically triggering through configuration files, and running batch tests locally using the command line.
-
-## Running Batch Tests via Web Interface
-
-1. On the "Batch Tests" page, click the "Run Batch Test" button in the top right corner:
-
- 
-
-2. After selecting the test package version and the test suites to be executed, click "Confirm" to run the batch tests. The associated records that meet the conditions will be used as test data to execute the test suites:
-
- 
-
-
-
-## Automatically Trigger Batch Tests
-
-When the uploaded test package type or tag meets the preset conditions in the configuration file, the batch test will be automatically triggered upon completion of the test package upload. The full test suite that meets the conditions will be executed using that test package file.
-
-You can set automatic trigger conditions for test suites in the "on" field of the configuration file. For the specific format and rules, please refer to [Configuration File Format and Sample - Automatic Test Triggering](../regression/9-yaml-sample.md#auto-triggering).
-
-On the "Batch Tests - Test Suite Management" page, for test suites with automatic trigger conditions configured, the "Associated Trigger Conditions" column will display the "View Trigger Conditions" button:
-
-
-
-You can click the "View Trigger Conditions" button to view the test package conditions that automatically trigger the test suite:
-
-
-
-
-
-## Running Batch Tests Locally
-
-You can use the command line to run batch tests locally, following the instructions below.
-
-### Download and Configuration
-
-1. Enter the command to download the required files. The corresponding commands for different operating systems are:
-
-- Linux
-
- ```
- curl https://coscene-artifacts-production.oss-cn-hangzhou.aliyuncs.com/cos/linux/amd64/latest/cos -o cos
- ```
-
-- macOS
-
- ```
- curl https://coscene-artifacts-production.oss-cn-hangzhou.aliyuncs.com/cos/darwin/amd64/latest/cos -o cos
- ```
-
-2. Configure using the following commands:
-
- ```
-
- # Grant execute permission to cos
-
- chmod +x cos
-
- # Create configuration directory
-
- mkdir $HOME/.cos
-
- # Create a configuration file
-
- cat << EOF > $HOME/.cos/config.yaml
- platform:
- endpoint: ${YOUR_DOMAIN}
- accessToken: ${YOUR_TOKEN}
- project: ${ORG_SLUG}/${PROJECT_SLUG}
- EOF
-
- # Verify configuration
-
- cos config list
- ```
-
- Explanation of parameters:
-
- - Replace `${YOUR_DOMAIN}` in `endpoint` with the actual website address:
-
- 
-
- - Steps to obtain `${YOUR_TOKEN}` in `accessToken`:
-
- 
-
- 
-
- 
-
- - Replace `ORG_SLUG` and `PROJECT_SLUG` in `project` according to reality:
-
- 
-
-
-
-### Execution
-
-You can refer to the following command examples to run batch tests:
-
-```
-
-# Use the latest test package to run all batch tests in the project
-
-cos test run
-
-# Only use the local configuration file cos.yaml to run batch tests
-
-cos test run --test-config cos.yaml
-
-# Use the latest test package to run the batch test named gazebo in the project
-
-cos test run -t gezebo
-
-# Use the specified record "Positioning Collection Data" to run batch tests
-
-cos test run -r 定位采集数据
-
-# Use the test package with the tag v0.0.1 to run all test suites in the project
-
-cos test run --bundle-tag v0.0.1
-
-# Use the test package of category Gazebo to run all test suites in the project
-
-cos test run --bundle-category Gazebo
-
-# Upload bundle.zip and run batch tests
-
-cos test run -b bundle.zip
-```
-
-
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/6-status-and-output.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/6-status-and-output.md
deleted file mode 100644
index 99de77e97..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/6-status-and-output.md
+++ /dev/null
@@ -1,132 +0,0 @@
----
-sidebar_position: 6
----
-
-# Test Metadata and Test Results
-
-> Learn how to customize output test results, how to view the progress and output of batch tests and individual tests within them, and how to play shadow mode in the visualization interface for comparison.
-
-## Output Test Results
-
-You can customize the output of test results through configuration files, test codes, etc. Currently, outputting parsable result files and charts are supported.
-
-### Output Parsable Result Files
-
-Batch tests support parsing JUnit XML format result files. You can use the following command in the `script` parameter of the configuration file to create an XML format result file at `path`:
-
-```bash
-pytest --junitxml=path
-```
-
-For an example, see [Configuration File Format and Samples - Outputting Test Result Files](... /8-regression/9-yaml-sample.md#Output test result file).
-
-Examples of result files in JUnit XML format that support parsing are as follows, where the mapping of result data to JUnit XML format is described in [JUnit Mapping](https://www.ibm.com/docs/en/developer-for-zos/14.1?topic=formats- junit-xml-format#junitschema\_\_table_junitmap):
-
-```xml
-
-
-
-
-
- WARNING: Use a program name that matches the source file name
- Category: COBOL Code Review – Naming Conventions
- File: /project/PROGRAM.cbl
- Line: 2
-
-
-
-
-```
-
-### Output charts
-
-You can add custom attributes starting with "cos\_" in the test report, e.g. `cos_customer_name`. These custom attributes will be uploaded together with the default metrics to carve line, which collects and analyzes these custom attributes, as well as grouping, sorting, and filtering metrics to display as dimensions, etc.
-
-You can use a custom chart name starting with "cos\_" in the relevant test code file in the image to output the chart in the test results in the sample format below:
-
-```python
- def test_romeo(record_xml_attribute):
-
- for i in (1, 2, 3):
- rand_float = random.uniform(1, 100)
- record_xml_attribute("cos_test_romeo_val" + str(i), rand_float)
- for i in (1, 2, 3):
- rand_bool = random.choice([True, False])
- record_xml_attribute("cos_test_romeo_bool" + str(i), rand_bool)
-
- assert __count('romeo') > 0
-```
-
-### Generate Shadow Mode Artifacts
-
-> Output files to the specified directory as test output, where the .bag files can be compared with the files in the original record to be played in the visualization interface.
-
-You can configure the "script" field in the file to use commands to output files to the `/cos/outputs` directory as test output. For specific examples, please refer to [Configuration File Format and Examples - Output Shadow Mode Files](../regression/9-yaml-sample.md#generate-shadow-mode)
-
-Test outputs will be displayed in the "Test Output" column of the test details page, displayed hierarchically according to the corresponding test suite and record.
-
-
-
-
-
-## View Running Progress and Artifacts
-
-1. In the list on the batch test page, it will display the batch tests and information that have been run within the project. You can click on a batch test number to view its details page:
-
- 
-
-2. In the batch test details page, the "Progress" Tab will display the running progress of this batch test and the running status of all individual tests within it:
-
- 
-
- You can click on a test title to view its details page:
-
- 
-
- Clicking on the title of an individual step in "Steps" will allow you to view its running log, step details, and running artifacts:
-
- 
-
- You can view and download the running artifacts of the individual step in "Artifact":
-
- 
-
- In the "Artifacts" section of the individual test details page, you can view and download all the running artifacts of this test:
-
- 
-
-3. In the "Artifacts" Tab of the batch test details page, you can view and download all the running artifacts of this batch test:
-
- 
-
-
-
-## View Running Results
-
-After the batch test is completed, you can click on the "Test Report" Tab in the batch test details page to view the test suite running results statistics, including running information and test cases analyzed from each test suite:
-
-
-
-You can click on the name of a single test case to view its running report, which includes the test details list and output charts, etc:
-
-
-
-Click on the "View Historical Data" in the top right corner of the page to view the historical result data statistics for the test case, including the test running results matrix, metric statistics chart, etc:
-
-
-
-
-
-
-
-## Play Shadow Mode
-
-Test outputs containing .bag files support shadow mode. Click on the "Test Output" column in the test details page corresponding to the test output list above, or the "Shadow Mode" button in the top right corner of the single test details page to enter the visualization interface:
-
-
-
-
-
-The test output files will be played back in comparison with the files in the original record in the visualization interface.
-
-
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/7-advanced.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/7-advanced.md
deleted file mode 100644
index 2390c8d09..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/7-advanced.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-sidebar_position: 7
----
-
-# Advanced
-
-> Through this section, you can understand other content involved in batch tests, including receiving message notifications and creating moments.
-
-
-
-## Receive Message Notifications
-
-You can set up in the uploaded configuration file's "notifications" field to receive information related to the execution of test suites in DingTalk. You can use a custom template to define the content of the received information.
-
-For specific examples, please refer to the [Configuration File Format and Sample - Message Notification](../regression/9-yaml-sample.md#notifications) section.
-
-On the "Batch Tests - Test Suite Management" page, for test suites that have message notifications configured, the "Notification" column will display the "View Notification" button:
-
-
-
-You can click the "View Notification" button to see the content of its message template:
-
-
-
-
-
-## Create a Moment
-
-The running environment of batch tests integrates the `cos` command-line tool. You can run the following command within the program to create a moment:
-
-```yaml
-/cos/bins/cos moment create \
- --display-name "Emergency Stop" \ # moment name
- --description "Machine emergency stop" \ # moment description
- --trigger-time 1532402940 \ # moment trigger time
- --duration 10 \ # moment duration
- --customized-fields '{"key1": "value1"}' # moment custom fields
-```
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/8-system-directory.md b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/8-system-directory.md
deleted file mode 100644
index 6290e8cfc..000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/8-system-directory.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-sidebar_position: 8
----
-
-# Reserved Directories
-
-| Name | Directory |
-| ----------- | -------------- |
-| Test Bundle | /cos/bundles |
-| Record | /cos/files |
-| Artifact | /cos/artifacts |
-| Test Output | /cos/outputs |
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-1.png
deleted file mode 100644
index 3b2223714..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-2.png
deleted file mode 100644
index 50f5850d2..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-3.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-3.png
deleted file mode 100644
index 32edf7630..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/artifacts-3.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/auto-trigger-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/auto-trigger-1.png
deleted file mode 100644
index 5bbafcab2..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/auto-trigger-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/auto-trigger-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/auto-trigger-2.png
deleted file mode 100644
index 16ba85692..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/auto-trigger-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/bundle-management.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/bundle-management.png
deleted file mode 100644
index f70f9fb04..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/bundle-management.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/bundle-status.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/bundle-status.png
deleted file mode 100644
index f55adf05c..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/bundle-status.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/choose-bundle.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/choose-bundle.png
deleted file mode 100644
index f9c82ff64..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/choose-bundle.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-1.png
deleted file mode 100644
index af243775e..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-2.png
deleted file mode 100644
index 404c1b497..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-3.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-3.png
deleted file mode 100644
index 1e1a4a241..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-3.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-4.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-4.png
deleted file mode 100644
index b53c42a8a..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-4.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-5.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-5.png
deleted file mode 100644
index 9ce7ad3c1..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/cli-5.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-config-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-config-1.png
deleted file mode 100644
index 5bb176315..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-config-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-config-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-config-2.png
deleted file mode 100644
index b39b5b7e1..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-config-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-step.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-step.png
deleted file mode 100644
index ac0ca4884..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-step.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-test-bundle-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-test-bundle-1.png
deleted file mode 100644
index c5e4f1472..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-test-bundle-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-test-bundle-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-test-bundle-2.png
deleted file mode 100644
index 92e419ab2..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-test-bundle-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-workflow.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-workflow.png
deleted file mode 100644
index 1e7533a14..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/goto-workflow.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/manage-config.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/manage-config.png
deleted file mode 100644
index cbab131d4..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/manage-config.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/notification-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/notification-1.png
deleted file mode 100644
index 69b1116a1..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/notification-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/notification-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/notification-2.png
deleted file mode 100644
index bed0e447e..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/notification-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/regression.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/regression.png
deleted file mode 100644
index 498dbcc3e..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/regression.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-1.png
deleted file mode 100644
index 5c749813a..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-2.png
deleted file mode 100644
index 05c680ff1..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-3.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-3.png
deleted file mode 100644
index 1d10b766f..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-3.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-4.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-4.png
deleted file mode 100644
index 111047482..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/report-4.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-1.png
deleted file mode 100644
index b541a3ec4..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-2.png
deleted file mode 100644
index b14efbf40..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-wfrun.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-wfrun.png
deleted file mode 100644
index 77b04bf08..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/run-wfrun.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-1.png
deleted file mode 100644
index 8287f648b..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-2.png
deleted file mode 100644
index e026b55ed..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-3.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-3.png
deleted file mode 100644
index 0d371e0a4..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-3.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-4.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-4.png
deleted file mode 100644
index 424b7023e..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/shadow-mode-4.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-1.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-1.png
deleted file mode 100644
index 31be8df24..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-1.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-2.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-2.png
deleted file mode 100644
index de2bc641f..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-2.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-3.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-3.png
deleted file mode 100644
index f89cbac88..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-3.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-4.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-4.png
deleted file mode 100644
index 2f7b7d0bd..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/status-4.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/test-suite-info.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/test-suite-info.png
deleted file mode 100644
index ce8929c05..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/test-suite-info.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/update-config.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/update-config.png
deleted file mode 100644
index 46abbb75e..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/update-config.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/upload-config.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/upload-config.png
deleted file mode 100644
index 34b2cbacd..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/upload-config.png and /dev/null differ
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/upload-test-bundle.png b/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/upload-test-bundle.png
deleted file mode 100644
index f935749bf..000000000
Binary files a/i18n/en/docusaurus-plugin-content-docs/current/simandtests/regression/img/upload-test-bundle.png and /dev/null differ