File tree Expand file tree Collapse file tree 4 files changed +7
-7
lines changed
website_and_docs/content/documentation/webdriver/elements Expand file tree Collapse file tree 4 files changed +7
-7
lines changed Original file line number Diff line number Diff line change @@ -113,8 +113,8 @@ A nested lookup might not be the most effective location strategy since it requi
113
113
separate commands to be issued to the browser.
114
114
115
115
To improve the performance slightly, we can use either CSS or XPath to find this element in a single command.
116
- See the [ Locator strategy suggestions] (( {{< ref "/documentation/test_practices/encouraged/locators.md " >}}) ) in our
117
- [ Encouraged test practices] ((( {{< ref "/documentation/test_practices/encouraged" >}})) ) section.
116
+ See the [ Locator strategy suggestions] ({{< ref "/documentation/test_practices/encouraged/locators" >}}) in our
117
+ [ Encouraged test practices] ({{< ref "/documentation/test_practices/encouraged" >}}) section.
118
118
119
119
For this example, we'll use a CSS Selector:
120
120
Original file line number Diff line number Diff line change @@ -107,7 +107,7 @@ val fruit = fruits.findElement(By.id("tomatoes"))
107
107
ネストされたルックアップは、ブラウザに2つの別々のコマンドを発行する必要があるため、最も効果的なロケーション戦略ではない可能性があります。
108
108
109
109
パフォーマンスをわずかに向上させるために、CSSまたはXPathのいずれかを使用して、単一のコマンドでこの要素を見つけることができます。
110
- [ 推奨されるテストプラクティス] ((( {{< ref "/documentation/test_practices/encouraged" >}}))) の章で、[ ロケーター戦略] (( {{< ref "/documentation/test_practices/encouraged/locators.md " >}}) )の提案を参照してください。
110
+ [ 推奨されるテストプラクティス] ({{< ref "/documentation/test_practices/encouraged" >}})の章で、[ ロケーター戦略] ({{< ref "/documentation/test_practices/encouraged/locators" >}})の提案を参照してください。
111
111
112
112
この例では、CSSセレクターを使用します。
113
113
Original file line number Diff line number Diff line change @@ -114,8 +114,8 @@ A nested lookup might not be the most effective location strategy since it requi
114
114
separate commands to be issued to the browser.
115
115
116
116
To improve the performance slightly, we can use either CSS or XPath to find this element in a single command.
117
- See the [ Locator strategy suggestions] (( {{< ref "/documentation/test_practices/encouraged/locators.md " >}}) ) in our
118
- [ Encouraged test practices] ((( {{< ref "/documentation/test_practices/encouraged" >}})) ) section.
117
+ See the [ Locator strategy suggestions] ({{< ref "/documentation/test_practices/encouraged/locators" >}}) in our
118
+ [ Encouraged test practices] ({{< ref "/documentation/test_practices/encouraged" >}}) section.
119
119
120
120
For this example, we'll use a CSS Selector:
121
121
Original file line number Diff line number Diff line change @@ -114,8 +114,8 @@ A nested lookup might not be the most effective location strategy since it requi
114
114
separate commands to be issued to the browser.
115
115
116
116
To improve the performance slightly, we can use either CSS or XPath to find this element in a single command.
117
- See the [ Locator strategy suggestions] (( {{< ref "/documentation/test_practices/encouraged/locators.md " >}}) ) in our
118
- [ Encouraged test practices] ((( {{< ref "/documentation/test_practices/encouraged" >}})) ) section.
117
+ See the [ Locator strategy suggestions] ({{< ref "/documentation/test_practices/encouraged/locators" >}}) in our
118
+ [ Encouraged test practices] ({{< ref "/documentation/test_practices/encouraged" >}}) section.
119
119
120
120
For this example, we'll use a CSS Selector:
121
121
You can’t perform that action at this time.
0 commit comments