You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by gi...@apache.org on 2022/02/25 06:25:29 UTC
[dolphinscheduler-website] branch asf-site updated: Automated deployment: e43fba9f1f7f8ad1ac607a5078c766dff39cef33
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 65927bc Automated deployment: e43fba9f1f7f8ad1ac607a5078c766dff39cef33
65927bc is described below
commit 65927bc0d4bc5dbc87f03de0d6a69ad5224bd273
Author: github-actions[bot] <gi...@users.noreply.github.com>
AuthorDate: Fri Feb 25 06:25:24 2022 +0000
Automated deployment: e43fba9f1f7f8ad1ac607a5078c766dff39cef33
---
en-us/community/join/e2e-guide.html | 2 +-
en-us/community/join/e2e-guide.json | 2 +-
zh-cn/community/join/e2e-guide.html | 2 +-
zh-cn/community/join/e2e-guide.json | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/en-us/community/join/e2e-guide.html b/en-us/community/join/e2e-guide.html
index e32c57e..6563ff8 100644
--- a/en-us/community/join/e2e-guide.html
+++ b/en-us/community/join/e2e-guide.html
@@ -32,7 +32,7 @@
</ul>
<p><img src="/img/community/join/e2e/e2e-security.png" alt="e2e-security"></p>
<h3>How to write test code?</h3>
-<p>After taking up the corresponding task, the next step is to get to the crux of writing the code. Many partners may not be familiar with E2E test codes, so you can refer to this page: <a href="../../../development/zh-cn/e2e-test.md">e2e-test</a>.</p>
+<p>After taking up the corresponding task, the next step is to get to the crux of writing the code. Many partners may not be familiar with E2E test codes, so you can refer to this page: <a href="https://dolphinscheduler.apache.org/en-us/development/e2e-test.html">e2e-test</a>.</p>
<h3>How to submit a Pull Request?</h3>
<p>Participation in the open source community can take many forms, including issue, pull request and translation. To participate in the E2E testing process, contributors are first required to understand the simple process of submitting a pull request, see: <a href="../development/pull-request.md">Pull Request</a>.</p>
</div></section><footer class="footer-container"><div class="footer-body"><div><h3>About us</h3><h4>Do you need feedback? Please contact us through the following ways.</h4></div><div class="contact-container"><ul><li><a href="/en-us/community/development/subscribe.html"><img class="img-base" src="/img/emailgray.png"/><img class="img-change" src="/img/emailblue.png"/><p>Email List</p></a></li><li><a href="https://twitter.com/dolphinschedule"><img class="img-base" src="/img/twittergray.png [...]
diff --git a/en-us/community/join/e2e-guide.json b/en-us/community/join/e2e-guide.json
index 04d7285..a47ac00 100644
--- a/en-us/community/join/e2e-guide.json
+++ b/en-us/community/join/e2e-guide.json
@@ -1,6 +1,6 @@
{
"filename": "e2e-guide.md",
- "__html": "<h1>DolphinScheduler E2E Test Contribution Guide</h1>\n<p>The main purpose of E2E test is to verify the integration and data integrity of the system, and its components, by simulating real user scenarios. This makes it possible to extend the scope of testing and ensure the health and stability of the system. To a certain extent, the test workload and costs are reduced. In simple terms, E2E testing is about treating a program as a black box and simulating the access behaviour [...]
+ "__html": "<h1>DolphinScheduler E2E Test Contribution Guide</h1>\n<p>The main purpose of E2E test is to verify the integration and data integrity of the system, and its components, by simulating real user scenarios. This makes it possible to extend the scope of testing and ensure the health and stability of the system. To a certain extent, the test workload and costs are reduced. In simple terms, E2E testing is about treating a program as a black box and simulating the access behaviour [...]
"link": "/dist/en-us/community/join/e2e-guide.html",
"meta": {}
}
\ No newline at end of file
diff --git a/zh-cn/community/join/e2e-guide.html b/zh-cn/community/join/e2e-guide.html
index 228ef86..d7d3da7 100644
--- a/zh-cn/community/join/e2e-guide.html
+++ b/zh-cn/community/join/e2e-guide.html
@@ -32,7 +32,7 @@
</ul>
<p><img src="/img/community/join/e2e/e2e-security.png" alt="e2e-security"></p>
<h3>如何编写测试代码？</h3>
-<p>在认领对应的任务之后，下一步就进入到编写代码的关键。很多同学可能对于 E2E 测试代码并不是很熟悉，因此可以参考该页面：<a href="../../../development/zh-cn/e2e-test.md">e2e-test</a>。</p>
+<p>在认领对应的任务之后，下一步就进入到编写代码的关键。很多同学可能对于 E2E 测试代码并不是很熟悉，因此可以参考该页面：<a href="https://dolphinscheduler.apache.org/zh-cn/development/e2e-test.html">e2e-test</a>。</p>
<h3>如何提交 Pull Request ？</h3>
<p>参与开源社区的形式多种多样，其中不限于 issue、pull request 和翻译等等。在参与 E2E 测试的过程，首先要求贡献者了解简单的提交 pull request 的流程，可参考：<a href="../development/pull-request.md">Pull Request</a>。</p>
</div></section><footer class="footer-container"><div class="footer-body"><div><h3>联系我们</h3><h4>有问题需要反馈？请通过以下方式联系我们。</h4></div><div class="contact-container"><ul><li><a href="/zh-cn/community/development/subscribe.html"><img class="img-base" src="/img/emailgray.png"/><img class="img-change" src="/img/emailblue.png"/><p>邮件列表</p></a></li><li><a href="https://twitter.com/dolphinschedule"><img class="img-base" src="/img/twittergray.png"/><img class="img-change" src="/img/twitterblue.png"/><p [...]
diff --git a/zh-cn/community/join/e2e-guide.json b/zh-cn/community/join/e2e-guide.json
index ff68871..18fc7fb 100644
--- a/zh-cn/community/join/e2e-guide.json
+++ b/zh-cn/community/join/e2e-guide.json
@@ -1,6 +1,6 @@
{
"filename": "e2e-guide.md",
- "__html": "<h1>DolphinScheduler E2E 测试参与指南</h1>\n<p>E2E 测试的主要目的是通过模拟真实的用户场景，验证被测系统及其组件的集成性和数据完整性，从而可以扩展测试范围，确保系统的健康稳定，在一定程度上减少测试工作量和成本。简单来说，E2E 测试就是把程序当做黑盒子，以用户的视角对真实系统的访问行为进行仿真，对测试的输入（用户行为/模拟数据），看能否得到预期得到的结果。因此，社区决定为 DolphinScheduler 增加 E2E 自动化测试。</p>\n<p>当前社区的 E2E 测试尚未达到完全覆盖，因此编写此文档，目的在于引导更多的同学参与进来。</p>\n<h3>如何寻找对应的 issue ？</h3>\n<p>当前社区把 E2E 需要测试的页面已经列出相关的 issue，主要分为 Project Management、Resource Center、DataSource、Security Center 四个页面。</p>\n<p>贡献者可以通过 GitHub 然后搜索 <a h
ref=\"https://git [...]
+ "__html": "<h1>DolphinScheduler E2E 测试参与指南</h1>\n<p>E2E 测试的主要目的是通过模拟真实的用户场景，验证被测系统及其组件的集成性和数据完整性，从而可以扩展测试范围，确保系统的健康稳定，在一定程度上减少测试工作量和成本。简单来说，E2E 测试就是把程序当做黑盒子，以用户的视角对真实系统的访问行为进行仿真，对测试的输入（用户行为/模拟数据），看能否得到预期得到的结果。因此，社区决定为 DolphinScheduler 增加 E2E 自动化测试。</p>\n<p>当前社区的 E2E 测试尚未达到完全覆盖，因此编写此文档，目的在于引导更多的同学参与进来。</p>\n<h3>如何寻找对应的 issue ？</h3>\n<p>当前社区把 E2E 需要测试的页面已经列出相关的 issue，主要分为 Project Management、Resource Center、DataSource、Security Center 四个页面。</p>\n<p>贡献者可以通过 GitHub 然后搜索 <a h
ref=\"https://git [...]
"link": "/dist/zh-cn/community/join/e2e-guide.html",
"meta": {}
}
\ No newline at end of file