This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new cc9f6d2  Automated deployment: 1c2d0c59b8300df6336d46888868366e7b53f740
cc9f6d2 is described below

commit cc9f6d236b700b72ee3a5b8b099d42185f208f92
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Apr 1 07:12:12 2022 +0000

    Automated deployment: 1c2d0c59b8300df6336d46888868366e7b53f740
---
 en-us/community/team.html       | 25 +++++++++++++++++++++++++
 en-us/community/team.json       |  2 +-
 en-us/development/e2e-test.html |  3 +--
 en-us/development/e2e-test.json |  2 +-
 zh-cn/community/team.html       | 25 +++++++++++++++++++++++++
 zh-cn/community/team.json       |  2 +-
 zh-cn/development/e2e-test.html |  3 +--
 zh-cn/development/e2e-test.json |  2 +-
 8 files changed, 56 insertions(+), 8 deletions(-)

diff --git a/en-us/community/team.html b/en-us/community/team.html
index 4d0f0db..2bdbcc2 100644
--- a/en-us/community/team.html
+++ b/en-us/community/team.html
@@ -224,6 +224,31 @@
 <td>songjian</td>
 <td><a href="https://github.com/songjianet";>@songjianet</a></td>
 </tr>
+<tr>
+<td>Zhaohe Sun</td>
+<td>zixi0825</td>
+<td><a href="https://github.com/zixi0825";>@zixi0825</a></td>
+</tr>
+<tr>
+<td>Tianqi Yan</td>
+<td>tianqiyan</td>
+<td><a href="https://github.com/Tianqi-Dotes";>@Tianqi-Dotes</a></td>
+</tr>
+<tr>
+<td>Dongkai Liu</td>
+<td>liudongkai</td>
+<td><a href="https://github.com/devosend";>@devosend</a></td>
+</tr>
+<tr>
+<td>Hua Jiang</td>
+<td>huajiang</td>
+<td><a href="https://github.com/calvinjiang";>@calvinjiang</a></td>
+</tr>
+<tr>
+<td>Zihao Xiang</td>
+<td>zihaoxiang</td>
+<td><a href="https://github.com/SbloodyS";>@SbloodyS</a></td>
+</tr>
 </tbody>
 </table>
 <h2>Contributors</h2>
diff --git a/en-us/community/team.json b/en-us/community/team.json
index 8866fa8..355b94e 100644
--- a/en-us/community/team.json
+++ b/en-us/community/team.json
@@ -1,6 +1,6 @@
 {
   "filename": "team.md",
-  "__html": "<h1>DolphinScheduler Team</h1>\n<p>The DolphinScheduler team is 
comprised of Members and Contributors. Members have direct access to the source 
of DolphinScheduler project and actively evolve the code-base. Contributors 
improve the project through submission of patches and suggestions to the 
Members. The number of Contributors to the project is unbounded. All 
contributions to DolphinScheduler are greatly appreciated, whether for trivial 
cleanups, big new features or other ma [...]
+  "__html": "<h1>DolphinScheduler Team</h1>\n<p>The DolphinScheduler team is 
comprised of Members and Contributors. Members have direct access to the source 
of DolphinScheduler project and actively evolve the code-base. Contributors 
improve the project through submission of patches and suggestions to the 
Members. The number of Contributors to the project is unbounded. All 
contributions to DolphinScheduler are greatly appreciated, whether for trivial 
cleanups, big new features or other ma [...]
   "link": "/dist/en-us/community/team.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/en-us/development/e2e-test.html b/en-us/development/e2e-test.html
index 5cd8fa9..dd07066 100644
--- a/en-us/development/e2e-test.html
+++ b/en-us/development/e2e-test.html
@@ -153,8 +153,7 @@
 <p><a 
href="https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/cases";>https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/cases</a></p>
 <h2>III. Supplements</h2>
 <p>When running E2E tests locally, First, you need to start the local service, 
you can refer to this page:
-[development-environment-setup](<a 
href="https://dolphinscheduler.apache";>https://dolphinscheduler.apache</a>.
-org/en-us/development/development-environment-setup.html)</p>
+<a 
href="https://dolphinscheduler.apache.org/en-us/development/development-environment-setup.html";>development-environment-setup</a></p>
 <p>When running E2E tests locally, the <code>-Dlocal=true</code> parameter can 
be configured to connect locally and facilitate changes to the UI.</p>
 <p>When running E2E tests with <code>M1</code> chip, you can use 
<code>-Dm1_chip=true</code> parameter to configure containers supported by
 <code>ARM64</code>.</p>
diff --git a/en-us/development/e2e-test.json b/en-us/development/e2e-test.json
index ce924fd..8adfdd1 100644
--- a/en-us/development/e2e-test.json
+++ b/en-us/development/e2e-test.json
@@ -1,6 +1,6 @@
 {
   "filename": "e2e-test.md",
-  "__html": "<h1>DolphinScheduler E2E Automation Test</h1>\n<h2>I. Preparatory 
knowledge</h2>\n<h3>1. The difference between E2E Test and Unit 
Test</h3>\n<p>E2E, which stands for &quot;End to End&quot;, can be translated 
as &quot;end-to-end&quot; testing. It imitates the user, starting from a 
certain entry point and progressively performing actions until a certain job is 
completed. And unit tests are different, the latter usually requires testing 
parameters, types and parameter values, t [...]
+  "__html": "<h1>DolphinScheduler E2E Automation Test</h1>\n<h2>I. Preparatory 
knowledge</h2>\n<h3>1. The difference between E2E Test and Unit 
Test</h3>\n<p>E2E, which stands for &quot;End to End&quot;, can be translated 
as &quot;end-to-end&quot; testing. It imitates the user, starting from a 
certain entry point and progressively performing actions until a certain job is 
completed. And unit tests are different, the latter usually requires testing 
parameters, types and parameter values, t [...]
   "link": "/dist/en-us/development/e2e-test.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/zh-cn/community/team.html b/zh-cn/community/team.html
index 54b55da..990be85 100644
--- a/zh-cn/community/team.html
+++ b/zh-cn/community/team.html
@@ -225,6 +225,31 @@
 <td>songjian</td>
 <td><a href="https://github.com/songjianet";>@songjianet</a></td>
 </tr>
+<tr>
+<td>Zhaohe Sun</td>
+<td>zixi0825</td>
+<td><a href="https://github.com/zixi0825";>@zixi0825</a></td>
+</tr>
+<tr>
+<td>Tianqi Yan</td>
+<td>tianqiyan</td>
+<td><a href="https://github.com/Tianqi-Dotes";>@Tianqi-Dotes</a></td>
+</tr>
+<tr>
+<td>Dongkai Liu</td>
+<td>liudongkai</td>
+<td><a href="https://github.com/devosend";>@devosend</a></td>
+</tr>
+<tr>
+<td>Hua Jiang</td>
+<td>huajiang</td>
+<td><a href="https://github.com/calvinjiang";>@calvinjiang</a></td>
+</tr>
+<tr>
+<td>Zihao Xiang</td>
+<td>zihaoxiang</td>
+<td><a href="https://github.com/SbloodyS";>@SbloodyS</a></td>
+</tr>
 </tbody>
 </table>
 <h2>贡献者</h2>
diff --git a/zh-cn/community/team.json b/zh-cn/community/team.json
index be479fc..cbd69e8 100644
--- a/zh-cn/community/team.json
+++ b/zh-cn/community/team.json
@@ -1,6 +1,6 @@
 {
   "filename": "team.md",
-  "__html": "<h1>DolphinScheduler 团队</h1>\n<p>DolphinScheduler 团队由成员和贡献者组成。 
成员可以直接访问 DolphinScheduler 项目的源代码并积极地开发代码库。 贡献者通过向成员提交补丁和建议来改善项目。 该项目的贡献者数量是无限的。 
无论是琐碎的清理工作,重要的新功能还是其他重大的奖励,对 DolphinScheduler 
所做的所有贡献都将受到极大的赞赏。</p>\n<h2>成员</h2>\n<h3>PMC</h3>\n<table>\n<thead>\n<tr>\n<th>Public
 Name</th>\n<th>Apache ID</th>\n<th>GitHub 
ID</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Furkan 
Kamaci</td>\n<td>kamaci</td>\n<td><a 
href=\"https://github.com/kamaci\";>@kamaci</a></td>\n</tr>\n<tr>\n<td>Gang [...]
+  "__html": "<h1>DolphinScheduler 团队</h1>\n<p>DolphinScheduler 团队由成员和贡献者组成。 
成员可以直接访问 DolphinScheduler 项目的源代码并积极地开发代码库。 贡献者通过向成员提交补丁和建议来改善项目。 该项目的贡献者数量是无限的。 
无论是琐碎的清理工作,重要的新功能还是其他重大的奖励,对 DolphinScheduler 
所做的所有贡献都将受到极大的赞赏。</p>\n<h2>成员</h2>\n<h3>PMC</h3>\n<table>\n<thead>\n<tr>\n<th>Public
 Name</th>\n<th>Apache ID</th>\n<th>GitHub 
ID</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Furkan 
Kamaci</td>\n<td>kamaci</td>\n<td><a 
href=\"https://github.com/kamaci\";>@kamaci</a></td>\n</tr>\n<tr>\n<td>Gang [...]
   "link": "/dist/zh-cn/community/team.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/zh-cn/development/e2e-test.html b/zh-cn/development/e2e-test.html
index b601f99..66b2c8d 100644
--- a/zh-cn/development/e2e-test.html
+++ b/zh-cn/development/e2e-test.html
@@ -152,8 +152,7 @@
 <p>其余的都是类似的情况,可参考具体的源码来理解。</p>
 <p><a 
href="https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/cases";>https://github.com/apache/dolphinscheduler/tree/dev/dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/cases</a></p>
 <h2>三、补充</h2>
-<p>在本地运行的时候,首先需要启动相应的本地服务,可以参考该页面: [环境搭建](<a 
href="https://dolphinscheduler.apache";>https://dolphinscheduler.apache</a>.
-org/zh-cn/development/development-environment-setup.html)</p>
+<p>在本地运行的时候,首先需要启动相应的本地服务,可以参考该页面: <a 
href="https://dolphinscheduler.apache.org/zh-cn/development/development-environment-setup.html";>环境搭建</a></p>
 <p>在本地运行 E2E 测试的时候,可以配置 <code>-Dlocal=true</code> 参数,用于连接本地,方便对于 UI 界面的更改。</p>
 <p>如果是<code>M1</code>芯片的机器,可以使用<code>-Dm1_chip=true</code> 
参数,用于配置使用<code>ARM64</code>支持的容器。</p>
 <p><img src="../../img/e2e-test/Dlocal.png" alt="Dlocal"></p>
diff --git a/zh-cn/development/e2e-test.json b/zh-cn/development/e2e-test.json
index 1b7c513..6d81f58 100644
--- a/zh-cn/development/e2e-test.json
+++ b/zh-cn/development/e2e-test.json
@@ -1,6 +1,6 @@
 {
   "filename": "e2e-test.md",
-  "__html": "<h1>DolphinScheduler — E2E 
自动化测试</h1>\n<h2>一、前置知识:</h2>\n<h3>1、E2E 测试与单元测试的区别</h3>\n<p>E2E,是“End to 
End”的缩写,可以翻译成“端到端”测试。它模仿用户,从某个入口开始,逐步执行操作,直到完成某项工作。与单元测试不同,后者通常需要测试参数、参数类型、参数值、参数数量、返回值、抛出错误等,目的在于保证特定函数能够在任何情况下都稳定可靠完成工作。单元测试假定只要所有函数都正常工作,那么整个产品就能正常工作。</p>\n<p>相对来说,E2E
 测试并没有那么强调要覆盖全部使用场景,它关注的<strong>一个完整的操作链是否能够完成</strong>。对于 Web 
前端来说,还关注<strong>界面布局、内容信息是否符合预期</strong>。</p>\n<p>比如,登陆界面的 E2E 
测试,关注用户是否能够正常输入,正常登录;登陆失败的�
 �,是否能够正确显示错误信息。至于输入不合法的内容是否处理,并不是所关注的重点。</p>\n<h3>2、Selen [...]
+  "__html": "<h1>DolphinScheduler — E2E 
自动化测试</h1>\n<h2>一、前置知识:</h2>\n<h3>1、E2E 测试与单元测试的区别</h3>\n<p>E2E,是“End to 
End”的缩写,可以翻译成“端到端”测试。它模仿用户,从某个入口开始,逐步执行操作,直到完成某项工作。与单元测试不同,后者通常需要测试参数、参数类型、参数值、参数数量、返回值、抛出错误等,目的在于保证特定函数能够在任何情况下都稳定可靠完成工作。单元测试假定只要所有函数都正常工作,那么整个产品就能正常工作。</p>\n<p>相对来说,E2E
 测试并没有那么强调要覆盖全部使用场景,它关注的<strong>一个完整的操作链是否能够完成</strong>。对于 Web 
前端来说,还关注<strong>界面布局、内容信息是否符合预期</strong>。</p>\n<p>比如,登陆界面的 E2E 
测试,关注用户是否能够正常输入,正常登录;登陆失败的�
 �,是否能够正确显示错误信息。至于输入不合法的内容是否处理,并不是所关注的重点。</p>\n<h3>2、Selen [...]
   "link": "/dist/zh-cn/development/e2e-test.html",
   "meta": {}
 }
\ No newline at end of file

Reply via email to