Skip to content

Commit d29144c

Browse files
mmerrellmmerrell
authored
Updating Applicability section of the grid docs (#1139)
* Updating Applicability section of the grid docs * Copying comments to all lang files [deploy site]
1 parent 04d522a commit d29144c

File tree

5 files changed

+145
-125
lines changed

5 files changed

+145
-125
lines changed

‎website_and_docs/content/documentation/grid/applicability.en.md

+37-43
Original file line numberDiff line numberDiff line change
@@ -1,52 +1,46 @@
11
---
2-
title: "When to Use a Grid"
3-
linkTitle: "Applicability"
2+
title: "When to Use Grid"
3+
linkTitle: "When to Use Grid"
44
weight: 4
55
description: >
6-
Is Grid the right tool for you?
6+
Is Grid right for you?
77
aliases: [
88
"/documentation/en/grid/when_to_use_grid/",
99
"/documentation/grid/when_to_use_grid"
1010
]
1111
---
1212

13-
Generally speaking, there’s two reasons why you might want to use Grid.
14-
15-
* To run your tests against multiple browsers, multiple versions of browser,
16-
and browsers running on different operating systems.
17-
* To reduce the time it takes for the test suite to complete a test pass.
18-
19-
Grid is used to speed up the execution of a test pass by using
20-
multiple machines to run tests in parallel. For example, if you have a suite of
21-
100 tests, but you set up Grid to support 4 different machines (VMs or
22-
separate physical machines) to run those tests, your test suite will complete
23-
in (roughly) one-fourth the time as it would if you ran your tests sequentially
24-
on a single machine. For large test suites, and long-running test suite such as
25-
those performing large amounts of data-validation, this can be a significant
26-
time-saver. Some test suites can take hours to run. Another reason to boost the
27-
time spent running the suite is to shorten the turnaround time for test results
28-
after developers check-in code for the AUT. Increasingly software teams
29-
practicing Agile software development want test feedback as immediately as
30-
possible as opposed to wait overnight for an overnight test pass.
31-
32-
Grid is also used to support running tests against multiple runtime
33-
environments, specifically, against different browsers at the same time. For
34-
example, a ‘grid’ of virtual machines can be setup with each supporting a
35-
different browser that the application to be tested must support. So, machine 1
36-
has Internet Explorer 8, machine 2, Internet Explorer 9, machine 3 the latest
37-
Chrome, and machine 4 the latest Firefox. When the test suite is run,
38-
Selenium-Grid receives each test-browser combination and assigns each test to
39-
run against its required browser.
40-
41-
In addition, one can have a grid of all the same browser, type and version. For
42-
instance, one could have a grid of 4 machines each running 3 instances of
43-
Firefox 70, allowing for a ‘server-farm’ (in a sense) of available Firefox
44-
instances. When the suite runs, each test is passed to Grid which
45-
assigns the test to the next available Firefox instance. In this manner one
46-
gets test pass where conceivably 12 tests are all running at the same time in
47-
parallel, significantly reducing the time required to complete a test pass.
48-
49-
Grid is very flexible. These two examples can be combined to allow
50-
multiple instances of each browser type and version. A configuration such as
51-
this would provide both, parallel execution for fast test pass completion and
52-
support for multiple browser types and versions simultaneously.
13+
When would you use a Selenium Grid?
14+
15+
* To run your tests in parallel, against different browser types, browser versions, operating systems
16+
* To reduce the time needed to execute a test suite
17+
18+
Selenium Grid runs test suites in parallel against multiple machines (called Nodes).
19+
For large and long-running test suites, this can save minutes, hours, or perhaps days.
20+
This shortens the turnaround time for test results as your application under test (AUT)
21+
changes.
22+
23+
Grid can run tests (in parallel) against multiple different browsers, and it can
24+
run against multiple instances of the same browser. As an example, let's imagine
25+
a Grid with six Nodes. The first machine has Firefox's latest version,
26+
the second has Firefox "latest minus one", the third gets the latest Chrome, and
27+
the remaining three machines are Mac Minis, which allows for three tests to run in
28+
parallel on the latest version of Safari.
29+
30+
Execution time can be expressed as a simple formula:
31+
32+
```Number of Tests * Average Test Time / Number of Nodes = Total Execution Time```
33+
34+
15 * 45s / 1 = 11m 15s // Without Grid
35+
15 * 45s / 5 = 2m 15s // Grid with 5 Nodes
36+
15 * 45s / 15 = 45s // Grid with 15 Nodes
37+
100 * 120s / 15 = 13m 20s // Would take over 3 hours without Grid
38+
39+
As the test suite is executing, the Grid allocates the tests to run against these
40+
browsers as configured in the tests.
41+
42+
A configuration such as this can greatly speed up the execution time of even the largest Selenium test suites.
43+
44+
Selenium Grid is a completely native part of the Selenium project, and is maintained in parallel by the same team
45+
of committers who work in the core Selenium development. Recognizing the importance of test execution speed, Grid
46+
has been a critical part of the Selenium project since the earliest days.

‎website_and_docs/content/documentation/grid/applicability.ja.md

+32-21
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "グリッドを使用する場合"
33
linkTitle: "グリッドを使用する場合"
44
weight: 4
55
description: >
6-
Is Grid the right tool for you?
6+
Is Grid right for you?
77
aliases: [
88
"/documentation/ja/grid/when_to_use_grid/",
99
"/ja/documentation/grid/when_to_use_grid"
@@ -13,33 +13,44 @@ aliases: [
1313
{{% pageinfo color="warning" %}}
1414
<p class="lead">
1515
<i class="fas fa-language display-4"></i>
16-
Page being translated from
17-
English to Japanese. Do you speak Japanese? Help us to translate
16+
Page being translated from English to Japanese.
17+
Do you speak Japanese? Help us to translate
1818
it by sending us pull requests!
1919
</p>
2020
{{% /pageinfo %}}
2121

2222

23-
一般的に、グリッドを使用する理由は2つあります。
23+
When would you use a Selenium Grid?
2424

25-
* 複数のブラウザー、複数のバージョンのブラウザー、および異なるオペレーティングシステムで実行されているブラウザーに対してテストを実行するため。
26-
* テストスイートがテストがパスするのに完了するのにかかる時間を短縮するため。
25+
* To run your tests in parallel, against different browser types, browser versions, operating systems
26+
* To reduce the time needed to execute a test suite
2727

28-
グリッドは、複数のマシンを使用してテストを並行して実行することにより、テストパスの実行を高速化するために使用されます。
29-
たとえば、100個のテストスイートがあり、それらのテストを実行するために4つの異なるマシン（VMまたは個別の物理マシン）をサポートするようにグリッドをセットアップした場合、テストスイートは単一のマシンでテストを連続して実行した場合と比較して（およそ）4分の1の時間で完了します。
30-
大規模なテストスイート、および大量のデータ検証を実行するような長時間実行されるテストスイートの場合、これは大幅な時間の節約になります。
31-
一部のテストスイートの実行には数時間かかる場合があります。 スイートの実行に費やす時間を増やすもう1つの理由は、開発者がAUTのコードをチェックインした後のテスト結果の所要時間を短縮することです。
32-
アジャイルソフトウェア開発を実践しているソフトウェアチームは、一晩テストパスを一晩待つのではなく、できるだけ早くテストフィードバックを求めています。
28+
Selenium Grid runs test suites in parallel against multiple machines (called Nodes).
29+
For large and long-running test suites, this can save minutes, hours, or perhaps days.
30+
This shortens the turnaround time for test results as your application under test (AUT)
31+
changes.
3332

34-
グリッドは、複数のランタイム環境、特に異なるブラウザーに対して同時に実行するテストをサポートするためにも使用されます。
35-
たとえば、仮想マシンの"グリッド"は、テスト対象のアプリケーションがサポートする必要がある異なるブラウザーをサポートするようにセットアップできます。
36-
したがって、マシン1にはInternet Explorer 8、マシン2、Internet Explorer 9、マシン3は最新のChrome、マシン4は最新のFirefoxを持っています。
37-
テストスイートが実行されると、Selenium-Gridは各テストブラウザーの組み合わせを受け取り、必要なブラウザーに対して実行する各テストを割り当てます。
33+
Grid can run tests (in parallel) against multiple different browsers, and it can
34+
run against multiple instances of the same browser. As an example, let's imagine
35+
a Grid with six Nodes. The first machine has Firefox's latest version,
36+
the second has Firefox "latest minus one", the third gets the latest Chrome, and
37+
the remaining three machines are Mac Minis, which allows for three tests to run in
38+
parallel on the latest version of Safari.
3839

39-
さらに、すべて同じブラウザ、タイプ、およびバージョンのグリッドを持つことができます。
40-
たとえば、それぞれがFirefox 70の3つのインスタンスを実行する4台のマシンのグリッドを持つことができ、利用可能なFirefoxインスタンスの"ある意味"での"サーバーファーム"を可能にします。
41-
スイートが実行されると、各テストはグリッドに渡され、グリッドは次に利用可能なFirefoxインスタンスにテストを割り当てます。 この方法で、おそらく12のテストがすべて同時に並行して実行されるテストパスを取得し、テストパスの完了に必要な時間を大幅に短縮します。
40+
Execution time can be expressed as a simple formula:
4241

43-
グリッドは非常に柔軟です。
44-
これらの2つの例を組み合わせて、各ブラウザタイプとバージョンの複数のインスタンスを許可することができます。
45-
このような構成では、迅速にテストがパスすることを完了するための並列実行と、複数のブラウザタイプおよびバージョンの同時サポートの両方が提供されます。
42+
```Number of Tests * Average Test Time / Number of Nodes = Total Execution Time```
43+
44+
15 * 45s / 1 = 11m 15s // Without Grid
45+
15 * 45s / 5 = 2m 15s // Grid with 5 Nodes
46+
15 * 45s / 15 = 45s // Grid with 15 Nodes
47+
100 * 120s / 15 = 13m 20s // Would take over 3 hours without Grid
48+
49+
As the test suite is executing, the Grid allocates the tests to run against these
50+
browsers as configured in the tests.
51+
52+
A configuration such as this can greatly speed up the execution time of even the largest Selenium test suites.
53+
54+
Selenium Grid is a completely native part of the Selenium project, and is maintained in parallel by the same team
55+
of committers who work in the core Selenium development. Recognizing the importance of test execution speed, Grid
56+
has been a critical part of the Selenium project since the earliest days.

‎website_and_docs/content/documentation/grid/applicability.pt-br.md

+37-42
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Quando usar a Grid"
33
linkTitle: "Quando usar a Grid"
44
weight: 4
55
description: >
6-
Is Grid the right tool for you?
6+
Is Grid right for you?
77
aliases: [
88
"/documentation/pt-br/grid/when_to_use_grid/",
99
"/pt-br/documentation/grid/when_to_use_grid"
@@ -13,48 +13,43 @@ aliases: [
1313
{{% pageinfo color="warning" %}}
1414
<p class="lead">
1515
<i class="fas fa-language display-4"></i>
16-
Page being translated from
17-
English to Portuguese. Do you speak Portuguese? Help us to translate
16+
Page being translated from English to Portuguese.
17+
Do you speak Portuguese? Help us to translate
1818
it by sending us pull requests!
1919
</p>
2020
{{% /pageinfo %}}
2121

22-
De modo geral, há dois motivos pelos quais você pode querer usar a Grid.
23-
24-
* Para executar seus testes em vários navegadores, várias versões de navegador,
25-
e navegadores executados em diferentes sistemas operacionais.
26-
* Para reduzir o tempo que leva para o conjunto de testes concluir uma aprovação no teste.
27-
28-
A Grid é usada para acelerar a execução dos testes usando
29-
várias máquinas para executar testes em paralelo. Por exemplo, se você tiver um conjunto de
30-
100 testes, mas você configurou o Grid para suportar 4 máquinas diferentes (VMs ou
31-
máquinas físicas separadas) para executar esses testes, seu conjunto de testes será concluído
32-
em (aproximadamente) um quarto do tempo, do que se você executasse seus testes sequencialmente
33-
em uma única máquina. Para grandes conjuntos de testes e conjuntos de testes de longa duração, como
34-
aqueles que realizam grandes quantidades de validação de dados, isso pode ser um
35-
economizador de tempo significativo. Alguns conjuntos de testes podem levar horas para serem executados.
36-
Outro motivo para impulsionar o tempo gasto na execução do pacote é para encurtar o tempo de resposta para os resultados do teste
37-
após o código de check-in dos desenvolvedores para o AUT. Cada vez mais equipes de software
38-
praticando o desenvolvimento de software Agile desejam testar o feedback tão imediatamente quanto
39-
possível, em oposição a esperar durante a noite para uma aprovação no teste durante a noite.
40-
41-
A Grid também é usada para suportar testes em execução em vários
42-
ambientes de runtime, especificamente, em diferentes navegadores ao mesmo tempo. Por
43-
exemplo, uma ‘Grid’ de máquinas virtuais pode ser configurada com cada uma suportando um
44-
navegador diferente que o aplicativo a ser testado deve suportar. Então, máquina 1
45-
tem Internet Explorer 8, máquina 2, Internet Explorer 9, máquina 3, o mais recente
46-
Chrome e máquina 4 com o Firefox mais recente. Quando o conjunto de testes é executado,
47-
o Selenium Grid recebe cada combinação de navegador de teste e atribui cada teste a um navegador necessário.
48-
49-
Além disso, pode-se ter uma Grid do mesmo navegador, tipo e versão. Por
50-
exemplo, pode-se ter uma Grid de 4 máquinas, cada uma executando 3 instâncias de
51-
Firefox 70, permitindo um ‘server-farm’ (em certo sentido) de Firefox.
52-
Quando o pacote é executado, cada teste é passado para o Grid que
53-
atribui o teste à próxima instância disponível do Firefox. Desta maneira um
54-
obtém aprovação em que, concebivelmente, 12 testes estão sendo executados ao mesmo tempo em
55-
paralelo, reduzindo significativamente o tempo necessário para concluir os testes.
56-
57-
A Grid é muito flexível. Esses dois exemplos podem ser combinados para permitir
58-
várias instâncias de cada tipo e versão de navegador. Uma configuração como
59-
essa forneceria execução paralela para conclusão rápida de testes e
60-
suporte para vários tipos e versões de navegador simultaneamente.
22+
When would you use a Selenium Grid?
23+
24+
* To run your tests in parallel, against different browser types, browser versions, operating systems
25+
* To reduce the time needed to execute a test suite
26+
27+
Selenium Grid runs test suites in parallel against multiple machines (called Nodes).
28+
For large and long-running test suites, this can save minutes, hours, or perhaps days.
29+
This shortens the turnaround time for test results as your application under test (AUT)
30+
changes.
31+
32+
Grid can run tests (in parallel) against multiple different browsers, and it can
33+
run against multiple instances of the same browser. As an example, let's imagine
34+
a Grid with six Nodes. The first machine has Firefox's latest version,
35+
the second has Firefox "latest minus one", the third gets the latest Chrome, and
36+
the remaining three machines are Mac Minis, which allows for three tests to run in
37+
parallel on the latest version of Safari.
38+
39+
Execution time can be expressed as a simple formula:
40+
41+
```Number of Tests * Average Test Time / Number of Nodes = Total Execution Time```
42+
43+
15 * 45s / 1 = 11m 15s // Without Grid
44+
15 * 45s / 5 = 2m 15s // Grid with 5 Nodes
45+
15 * 45s / 15 = 45s // Grid with 15 Nodes
46+
100 * 120s / 15 = 13m 20s // Would take over 3 hours without Grid
47+
48+
As the test suite is executing, the Grid allocates the tests to run against these
49+
browsers as configured in the tests.
50+
51+
A configuration such as this can greatly speed up the execution time of even the largest Selenium test suites.
52+
53+
Selenium Grid is a completely native part of the Selenium project, and is maintained in parallel by the same team
54+
of committers who work in the core Selenium development. Recognizing the importance of test execution speed, Grid
55+
has been a critical part of the Selenium project since the earliest days.

0 commit comments

Comments
 (0)