Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit c0ed68f

Browse files
boris779sidsiddiqidiemol
committed
Regarding PR #163 (#178) [deploy site]
* Update on_test_automation.en.md A very small yet obvious grammatical fix to a sentence on this page. * Updated other languages to finish PR Co-authored-by: sidsiddiqi <2281928+sidsiddiqi@users.noreply.github.com> Co-authored-by: Diego Molina <diemol@users.noreply.github.com>
1 parent 7cb7cfb commit c0ed68f

File tree

6 files changed

+74
-74
lines changed

6 files changed

+74
-74
lines changed

‎docs_source_files/content/introduction/on_test_automation.de.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ and using the web browser only when you have absolutely no alternative,
4141
you can have many tests with minimal flake.
4242

4343
A distinct advantage of Selenium tests
44-
are their inherent ability to test all components of the application,
44+
is their inherent ability to test all components of the application,
4545
from backend to frontend, from a user's perspective.
4646
So in other words, whilst functional tests may be expensive to run,
4747
they also encompass large business-critical portions at one time.

‎docs_source_files/content/introduction/on_test_automation.en.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ and using the web browser only when you have absolutely no alternative,
3636
you can have many tests with minimal flake.
3737

3838
A distinct advantage of Selenium tests
39-
are their inherent ability to test all components of the application,
39+
is their inherent ability to test all components of the application,
4040
from backend to frontend, from a user's perspective.
4141
So in other words, whilst functional tests may be expensive to run,
4242
they also encompass large business-critical portions at one time.

‎docs_source_files/content/introduction/on_test_automation.fr.md‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -10,17 +10,17 @@ it by sending us pull requests!
1010
{{% /notice %}}
1111

1212
First, start by asking yourself whether or not you really need to use a browser.
13-
Odds are good that, at some point, if you're working on a complex web application,
13+
Odds are that, at some point, if you are working on a complex web application,
1414
you will need to open a browser and actually test it.
1515

1616
Functional end-user tests such as Selenium tests are expensive to run, however.
1717
Furthermore, they typically require substantial infrastructure
1818
to be in place to be run effectively.
19-
It's a good rule to always ask yourself if what you want to test
19+
It is a good rule to always ask yourself if what you want to test
2020
can be done using more lightweight test approaches such as unit tests
2121
or with a lower-level approach.
2222

23-
Once you have made the determination that you're in the web browser testing business,
23+
Once you have made the determination that you are in the web browser testing business,
2424
and you have your Selenium environment ready to begin writing tests,
2525
you will generally perform some combination of three steps:
2626

@@ -29,7 +29,7 @@ you will generally perform some combination of three steps:
2929
* Evaluate the results
3030

3131
You will want to keep these steps as short as possible;
32-
one to two operations should be enough much of the time.
32+
one or two operations should be enough most of the time.
3333
Browser automation has the reputation of being "flaky",
3434
but in reality, that is because users frequently demand too much of it.
3535
In later chapters, we will return to techniques you can use
@@ -42,7 +42,7 @@ and using the web browser only when you have absolutely no alternative,
4242
you can have many tests with minimal flake.
4343

4444
A distinct advantage of Selenium tests
45-
are their inherent ability to test all components of the application,
45+
is their inherent ability to test all components of the application,
4646
from backend to frontend, from a user's perspective.
4747
So in other words, whilst functional tests may be expensive to run,
4848
they also encompass large business-critical portions at one time.
@@ -51,7 +51,7 @@ they also encompass large business-critical portions at one time.
5151
### Testing requirements
5252

5353
As mentioned before, Selenium tests can be expensive to run.
54-
To what extent depends on the browser you're running the tests against,
54+
To what extent depends on the browser you are running the tests against,
5555
but historically browsers' behaviour has varied so much that it has often
5656
been a stated goal to cross-test against multiple browsers.
5757

@@ -67,7 +67,7 @@ will quickly become a non-trivial undertaking.
6767
Larry has written a web site which allows users to order their
6868
custom unicorns.
6969

70-
The general workflow (what we'll call the "happy path") is something
70+
The general workflow (what we will call the "happy path") is something
7171
like this:
7272

7373
* Create an account
@@ -80,17 +80,17 @@ like this:
8080
It would be tempting to write one grand Selenium script
8181
to perform all these operations–many will try.
8282
**Resist the temptation!**
83-
Doing so will result in a test that
83+
Doing so will result in a test that
8484
a) takes a long time,
8585
b) will be subject to some common issues around page rendering timing issues, and
8686
c) is such that if it fails,
87-
it won't give you a concise, "glanceable" method for diagnosing what went wrong.
87+
it will not give you a concise, "glanceable" method for diagnosing what went wrong.
8888

8989
The preferred strategy for testing this scenario would be
9090
to break it down to a series of independent, speedy tests,
9191
each of which has one "reason" to exist.
9292

93-
Let's pretend you want to test the second step:
93+
Let us pretend you want to test the second step:
9494
Configuring your unicorn.
9595
It will perform the following actions:
9696

@@ -110,11 +110,11 @@ Here you have some choices to make:
110110
taken into account before configuration begins?
111111

112112
Regardless of how you answer this question,
113-
the solution is to make it part of the "set up the data" portion of the test–
114-
if Larry has exposed an API that enables you (or anyone)
113+
the solution is to make it part of the "set up the data" portion of the test.
114+
If Larry has exposed an API that enables you (or anyone)
115115
to create and update user accounts,
116-
be sure to use that to answer this question–
117-
if possible, you want to launch the browser only after you have a user "in hand",
116+
be sure to use that to answer this question.
117+
If possible, you want to launch the browser only after you have a user "in hand",
118118
whose credentials you can just log in with.
119119

120120
If each test for each workflow begins with the creation of a user account,
@@ -241,7 +241,7 @@ Here is one way of doing this (continuing from the previous example):
241241
// with the browser in any way.
242242
Unicorn sparkles = new Unicorn("Sparkles", UnicornColors.PURPLE, UnicornAccessories.SUNGLASSES, UnicornAdornments.STAR_TATTOOS);
243243

244-
// Since we're already "on" the account page, we have to use it to get to the
244+
// Since we are already "on" the account page, we have to use it to get to the
245245
// actual place where you configure unicorns. Calling the "Add Unicorn" method
246246
// takes us there.
247247
AddUnicornPage addUnicornPage = accountPage.addUnicorn();
@@ -371,8 +371,8 @@ even if Larry decides next week that he no longer likes Ruby-on-Rails
371371
and decides to re-implement the entire site
372372
in the latest Haskell bindings with a Fortran front-end.
373373

374-
Your page objects will require some small maintenance in order
375-
to conform to the site redesign,
374+
Your page objects will require some small maintenance in order to
375+
conform to the site redesign,
376376
but these tests will remain the same.
377377
Taking this basic design,
378378
you will want to keep going through your workflows with the fewest browser-facing steps possible.

‎docs_source_files/content/introduction/on_test_automation.ja.md‎

Lines changed: 27 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,17 @@ weight: 2
99
{{% /notice %}}
1010

1111
First, start by asking yourself whether or not you really need to use a browser.
12-
Odds are good that, at some point, if you're working on a complex web application,
12+
Odds are that, at some point, if you are working on a complex web application,
1313
you will need to open a browser and actually test it.
1414

1515
Functional end-user tests such as Selenium tests are expensive to run, however.
1616
Furthermore, they typically require substantial infrastructure
1717
to be in place to be run effectively.
18-
It's a good rule to always ask yourself if what you want to test
18+
It is a good rule to always ask yourself if what you want to test
1919
can be done using more lightweight test approaches such as unit tests
2020
or with a lower-level approach.
2121

22-
Once you have made the determination that you're in the web browser testing business,
22+
Once you have made the determination that you are in the web browser testing business,
2323
and you have your Selenium environment ready to begin writing tests,
2424
you will generally perform some combination of three steps:
2525

@@ -28,7 +28,7 @@ you will generally perform some combination of three steps:
2828
* Evaluate the results
2929

3030
You will want to keep these steps as short as possible;
31-
one to two operations should be enough much of the time.
31+
one or two operations should be enough most of the time.
3232
Browser automation has the reputation of being "flaky",
3333
but in reality, that is because users frequently demand too much of it.
3434
In later chapters, we will return to techniques you can use
@@ -41,7 +41,7 @@ and using the web browser only when you have absolutely no alternative,
4141
you can have many tests with minimal flake.
4242

4343
A distinct advantage of Selenium tests
44-
are their inherent ability to test all components of the application,
44+
is their inherent ability to test all components of the application,
4545
from backend to frontend, from a user's perspective.
4646
So in other words, whilst functional tests may be expensive to run,
4747
they also encompass large business-critical portions at one time.
@@ -50,7 +50,7 @@ they also encompass large business-critical portions at one time.
5050
### Testing requirements
5151

5252
As mentioned before, Selenium tests can be expensive to run.
53-
To what extent depends on the browser you're running the tests against,
53+
To what extent depends on the browser you are running the tests against,
5454
but historically browsers' behaviour has varied so much that it has often
5555
been a stated goal to cross-test against multiple browsers.
5656

@@ -66,39 +66,39 @@ will quickly become a non-trivial undertaking.
6666
Larry has written a web site which allows users to order their
6767
custom unicorns.
6868

69-
The general workflow (what we'll call the "happy path") is something
69+
The general workflow (what we will call the "happy path") is something
7070
like this:
7171

7272
* Create an account
73-
* Configure their unicorn
74-
* Add her to the shopping cart
73+
* Configure the unicorn
74+
* Add it to the shopping cart
7575
* Check out and pay
76-
* Give feedback about their unicorn
76+
* Give feedback about the unicorn
7777

7878

7979
It would be tempting to write one grand Selenium script
8080
to perform all these operations–many will try.
8181
**Resist the temptation!**
82-
Doing so will result in a test that
82+
Doing so will result in a test that
8383
a) takes a long time,
8484
b) will be subject to some common issues around page rendering timing issues, and
85-
c) is such that if it fails,
86-
it won't give you a concise, "glanceable" method for diagnosing what went wrong.
85+
c) is such that if it fails,
86+
it will not give you a concise, "glanceable" method for diagnosing what went wrong.
8787

8888
The preferred strategy for testing this scenario would be
8989
to break it down to a series of independent, speedy tests,
9090
each of which has one "reason" to exist.
9191

92-
Let's pretend you want to test the second step:
92+
Let us pretend you want to test the second step:
9393
Configuring your unicorn.
9494
It will perform the following actions:
9595

9696
* Create an account
9797
* Configure a unicorn
9898

99-
Note that we're skipping the rest of these steps,
99+
Note that we are skipping the rest of these steps,
100100
we will test the rest of the workflow in other small, discrete test cases
101-
after we're done with this one.
101+
after we are done with this one.
102102

103103
To start, you need to create an account.
104104
Here you have some choices to make:
@@ -109,11 +109,11 @@ Here you have some choices to make:
109109
taken into account before configuration begins?
110110

111111
Regardless of how you answer this question,
112-
the solution is to make it part of the "set up the data" portion of the test–
113-
if Larry has exposed an API that enables you (or anyone)
112+
the solution is to make it part of the "set up the data" portion of the test.
113+
If Larry has exposed an API that enables you (or anyone)
114114
to create and update user accounts,
115-
be sure to use that to answer this question–
116-
if possible, you want to launch the browser only after you have a user "in hand",
115+
be sure to use that to answer this question.
116+
If possible, you want to launch the browser only after you have a user "in hand",
117117
whose credentials you can just log in with.
118118

119119
If each test for each workflow begins with the creation of a user account,
@@ -184,7 +184,7 @@ var user = userFactory.createCommonUser(); //This method is defined elsewhere.
184184
// Logging in on this site takes you to your personal "My Account" page, so the
185185
// AccountPage object is returned by the loginAs method, allowing you to then
186186
// perform actions from the AccountPage.
187-
var accountPage = loginAs(user.email, user.password);
187+
var accountPage = loginAs(user.email, user.password);
188188
{{< / code-panel >}}
189189
{{< code-panel language="kotlin" >}}
190190
// Create a user who has read-only permissions--they can configure a unicorn,
@@ -235,12 +235,12 @@ Here is one way of doing this (continuing from the previous example):
235235

236236
{{< code-tab >}}
237237
{{< code-panel language="java" >}}
238-
// The Unicorn is a top-level Object--it has attributes, which are set here.
238+
// The Unicorn is a top-level Object--it has attributes, which are set here.
239239
// This only stores the values; it does not fill out any web forms or interact
240240
// with the browser in any way.
241241
Unicorn sparkles = new Unicorn("Sparkles", UnicornColors.PURPLE, UnicornAccessories.SUNGLASSES, UnicornAdornments.STAR_TATTOOS);
242242

243-
// Since we're already "on" the account page, we have to use it to get to the
243+
// Since we are already "on" the account page, we have to use it to get to the
244244
// actual place where you configure unicorns. Calling the "Add Unicorn" method
245245
// takes us there.
246246
AddUnicornPage addUnicornPage = accountPage.addUnicorn();
@@ -322,12 +322,12 @@ unicornConfirmationPage = addUnicornPage.createUnicorn(sparkles)
322322
{{< / code-panel >}}
323323
{{< / code-tab >}}
324324

325-
Now that you've configured your unicorn,
325+
Now that you have configured your unicorn,
326326
you need to move on to step 3: making sure it actually worked.
327327

328328
{{< code-tab >}}
329329
{{< code-panel language="java" >}}
330-
// The exists() method from UnicornConfirmationPage will take the Sparkles
330+
// The exists() method from UnicornConfirmationPage will take the Sparkles
331331
// object--a specification of the attributes you want to see, and compare
332332
// them with the fields on the page.
333333
Assert.assertTrue("Sparkles should have been created, with all attributes intact", unicornConfirmationPage.exists(sparkles));
@@ -371,7 +371,7 @@ and decides to re-implement the entire site
371371
in the latest Haskell bindings with a Fortran front-end.
372372

373373
Your page objects will require some small maintenance in order to
374-
to conform to the site redesign,
374+
conform to the site redesign,
375375
but these tests will remain the same.
376376
Taking this basic design,
377377
you will want to keep going through your workflows with the fewest browser-facing steps possible.
@@ -390,6 +390,7 @@ and pre-configure a unicorn via the API or database.
390390
Then all you have to do is log in as the user, locate Sparkles,
391391
and add her to the cart.
392392

393+
393394
### To automate or not to automate?
394395

395396
Is automation always advantageous? When should one decide to automate test

‎docs_source_files/content/introduction/on_test_automation.ko.md‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ and using the web browser only when you have absolutely no alternative,
4242
you can have many tests with minimal flake.
4343

4444
A distinct advantage of Selenium tests
45-
are their inherent ability to test all components of the application,
45+
is their inherent ability to test all components of the application,
4646
from backend to frontend, from a user's perspective.
4747
So in other words, whilst functional tests may be expensive to run,
4848
they also encompass large business-critical portions at one time.
@@ -359,7 +359,6 @@ assert(unicornConfirmationPage.exists(sparkles), "Sparkles should have been crea
359359
// The exists() method from UnicornConfirmationPage will take the Sparkles
360360
// object--a specification of the attributes you want to see, and compare
361361
// them with the fields on the page.
362-
//CHECK Boris
363362
assertTrue("Sparkles should have been created, with all attributes intact", unicornConfirmationPage.exists(sparkles))
364363
{{< / code-panel >}}
365364
{{< / code-tab >}}
@@ -372,8 +371,8 @@ even if Larry decides next week that he no longer likes Ruby-on-Rails
372371
and decides to re-implement the entire site
373372
in the latest Haskell bindings with a Fortran front-end.
374373

375-
Your page objects will require some small maintenance in order
376-
to conform to the site redesign,
374+
Your page objects will require some small maintenance in order to
375+
conform to the site redesign,
377376
but these tests will remain the same.
378377
Taking this basic design,
379378
you will want to keep going through your workflows with the fewest browser-facing steps possible.
@@ -392,6 +391,7 @@ and pre-configure a unicorn via the API or database.
392391
Then all you have to do is log in as the user, locate Sparkles,
393392
and add her to the cart.
394393

394+
395395
### To automate or not to automate?
396396

397397
Is automation always advantageous? When should one decide to automate test
@@ -405,4 +405,3 @@ time to build test automation. For the short term, manual testing may be more
405405
effective. If an application has a very tight deadline, there is currently no
406406
test automation available, and it’s imperative that the testing gets done within
407407
that time frame, then manual testing is the best solution.
408-

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /