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 2c239ad Automated deployment: 6bbcf7f9e85b6cabd452da4813e4a268ffb8346c
2c239ad is described below
commit 2c239ad8759b20d2f894d6c05b8b3d4cd9ee890d
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue Feb 8 12:00:37 2022 +0000
Automated deployment: 6bbcf7f9e85b6cabd452da4813e4a268ffb8346c
---
en-us/development/e2e-test.html | 2 +-
en-us/development/e2e-test.json | 2 +-
zh-cn/development/e2e-test.html | 2 +-
zh-cn/development/e2e-test.json | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/en-us/development/e2e-test.html b/en-us/development/e2e-test.html
index 29f4c73..0bada85 100644
--- a/en-us/development/e2e-test.html
+++ b/en-us/development/e2e-test.html
@@ -17,7 +17,7 @@
<p>In contrast, E2E test does not emphasize so much the need to cover all
usage scenarios, it focuses on whether a complete chain of operations can be
completed. For the web front-end, it is also concerned with the layout of the
interface and whether the content information meets expectations.</p>
<p>For example, E2E test of the login page is concerned with whether the user
is able to enter and log in normally, and whether the error message is
correctly displayed if the login fails. It is not a major concern whether input
that is not legal is processed.</p>
<h3>2. Selenium test framework</h3>
-<p><a href="(https://www.selenium.dev/)">Selenium</a> is an open source
testing tool for executing automated tests on a web browser. The framework uses
WebDriver to transform Web Service commands into browser native calls through
the browser's native components to complete operations. In simple words, it
simulates the browser and makes selection operations on the elements of the
page.</p>
+<p><a href="https://www.selenium.dev";>Selenium</a> is an open source testing
tool for executing automated tests on a web browser. The framework uses
WebDriver to transform Web Service commands into browser native calls through
the browser's native components to complete operations. In simple words, it
simulates the browser and makes selection operations on the elements of the
page.</p>
<p>A WebDriver is an API and protocol which defines a language-neutral
interface for controlling the behavior of a web browser. Every browser has a
specific WebDriver implementation, called a driver. The driver is the component
responsible for delegating to the browser and handling the communication with
Selenium and the browser.</p>
<p>The Selenium framework links all these components together through a
user-facing interface that allows transparent work with different browser
backends, enabling cross-browser and cross-platform automation.</p>
<h2>II. E2E Test</h2>
diff --git a/en-us/development/e2e-test.json b/en-us/development/e2e-test.json
index ad35c9c..ff9f7ff 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 "End to End", can be translated
as "end-to-end" 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 "End to End", can be translated
as "end-to-end" 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/development/e2e-test.html b/zh-cn/development/e2e-test.html
index 45960d0..b130330 100644
--- a/zh-cn/development/e2e-test.html
+++ b/zh-cn/development/e2e-test.html
@@ -17,7 +17,7 @@
<p>相对来说，E2E 测试并没有那么强调要覆盖全部使用场景，它关注的<strong>一个完整的操作链是否能够完成</strong>。对于 Web
前端来说，还关注<strong>界面布局、内容信息是否符合预期</strong>。</p>
<p>比如，登陆界面的 E2E
测试，关注用户是否能够正常输入，正常登录；登陆失败的话，是否能够正确显示错误信息。至于输入不合法的内容是否处理，并不是所关注的重点。</p>
<h3>2、Selenium 测试框架</h3>
-<p><a href="(https://www.selenium.dev/)">Selenium</a> 是一种开源测试工具，用于在 Web
浏览器上执行自动化测试。该框架使用 WebDriver 通过浏览器的原生组件，转化 Web Service 的命令为浏览器 native
的调用来完成操作。简单来说，就是模拟浏览器，对于页面的元素进行选择操作。</p>
+<p><a href="https://www.selenium.dev";>Selenium</a> 是一种开源测试工具，用于在 Web
浏览器上执行自动化测试。该框架使用 WebDriver 通过浏览器的原生组件，转化 Web Service 的命令为浏览器 native
的调用来完成操作。简单来说，就是模拟浏览器，对于页面的元素进行选择操作。</p>
<p>WebDriver 是一个 API 和协议，它定义了一个语言中立的接口，用于控制 web 浏览器的行为。 每个浏览器都有一个特定的 WebDriver
实现，称为驱动程序。驱动程序是负责委派给浏览器的组件，并处理与 Selenium 和浏览器之间的通信。</p>
<p>Selenium 框架通过一个面向用户的界面将所有这些部分连接在一起， 该界面允许透明地使用不同的浏览器后端， 从而实现跨浏览器和跨平台自动化。</p>
<h2>二、E2E 测试</h2>
diff --git a/zh-cn/development/e2e-test.json b/zh-cn/development/e2e-test.json
index 360d2af..17ea8b1 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
