seleniumhq / docs Goto Github PK

A sample nodeconfig file for server version 3.x.x (>= beta4) can be seen at https://github.com/SeleniumHQ/selenium/blob/master/java/server/src/org/openqa/grid/common/defaults/DefaultNodeWebDriver.json

"https://github.com/SeleniumHQ/selenium/blob/master/java/server/src/org/openqa/grid/common/defaults/DefaultNodeWebDriver.json" <- is broken, where can we find the default node web driver for the newest verion?

Please use Selenium 3 in the docs.

The code still references Selenium 2, even in the installation page, e.g.:
https://seleniumhq.github.io/docs/install.html#selenium_installation

Thank you.

The link should include the entire section title. Currently, instead of linking with the text "Working with Select elements", it says only "Working with".

1. Add <code class=xml> to XML example snippets.
2. Text > SELENIUM INSTALLATION: depends on browsers you want to run your [...] > add 'the' before 'browsers'
3. Text > USING BROWSER SPECIFIC JAR: run tests in only a specific browser > swap 'in' and 'only'
4. Text > USING BROWSER SPECIFIC JAR: Rephrase to reflect that Firefox is not mandatory (Add 'for example').
5. Text: Remove That's all and you are ready to driver your tests in Firefox. line; as it does not add value and the sentence that follows it about Chrome is more important.
6. Text: In a similar manner
7. Text: Slightly rephrase Chrome's capability sentence to be similar to Firefox's one.
8. Text: The link to download the selenium-server-standalone JAR does not redirect correctly due to it having https at the beginning of it.
9. Text: Capitalize 'Selenium' in selenium-server-standalone jar is never uploaded,[...], under USING STANDALONE JAR.

Would be nice to migrate the docs to using Jekyll. It will allow non-technical users to be able to contribute to the docs and will reduce the reliance on javascript, which will improve page loading, and also enable viewing when javascript is disabled. Also uses liquid for templates.

Steps to re-produce this issue:

• Go to "https://seleniumhq.github.io/docs/guidelines.html#fresh_browser_per_test"/
• Now go to bottom
• Last Table of contents "Fresh browser per test " is not showing at the bottom.
  

In http://docs.seleniumhq.org/docs/03_webdriver.jsp#fetching-a-page there is:

Dependent on several factors, including the OS/Browser combination, WebDriver may or may not wait for the page to load. In some circumstances, WebDriver may return control before the page has finished, or even started, loading. To ensure robustness, you need to wait for the element(s) to exist in the page using Explicit and Implicit Waits.

It says it is dependent on several factors and circumstances, but which ones? It would be much better to provide some examples, because the code right above uses driver.get("http://www.google.com"); without waiting for the elements to exist in the page (except the part after element.submit();).

So it means that driver.get("http://www.google.com"); is not robust enough in the code provided? Why not?

You could add the desired documentation in the Explicit and Implicit Waits link, to prevent unnecessary verbosity inside the paragraph. If that's the case you could put a for more information regarding some factors and circumstances that might make WebDriver return control early, check Explicit and Implicit Waits.

what is hq stand for in SeleniumHQ?

Steps to reproduce:
1.Load the https://seleniumhq.github.io/docs/index.html Url
2. Click on the Annual conference link.

3.below page is shown to the user.

Page rendering error: Character # disappears

https://seleniumhq.github.io/docs/site/en/selenium_installation/installing_selenium_libraries/#c

## C#

Error rendering

this should be on the page somewhere (probaby the header)

At http://docs.seleniumhq.org/docs/03_webdriver.jsp#firefox-driver the link:

(see the source to see which ones)

Is invalid.

my initial thought is we need separate ones for each client language binding and then also each browser needs a section on what you may need to download / configure to run with it. Thoughts? :)

needed to log this as a placeholder for a google code issue.
https://code.google.com/p/selenium/issues/detail?id=8327

Based on a conversation on IRC...

[excerpt]
"is there much need for Selenium Grid if you have an api that the front end is tapping into with html/js? it sounds it's for load testing in which case i heard something like jboss is more appropriate?"
...
"oh. if the only two browsers we plan to support are chrome/firefox can you picture any need for it?"
[/excerpt]

Might be a nice enhancement to eventually have a section that includes a questionnaire that will help someone decide whether they need a grid.

Example:

1. Do you need to run tests on different browsers?
2. Will you need dedicated computers to run the tests?

I was wondering if you would be interested to move to Jekyll since it's natively supported by Github Pages. It would make easier the redaction of new articles and future maintenance of the site.

Tell me if you're interested so I start the work on my forked version of the repository.

Hi Team,

https://seleniumhq.github.io/docs/grid.html
in Cons:
Limited power
Certain third party libraries have limitations that prevent them from being used in conjuction with Grid.

"conjuction" should be "conjunction".

The Selenium RC page is blank. We ought to cover the basics here, with a small recommendation anyone starting fresh to use WebDriver.

In step 3, the following line is Assert.assertTrue("Sparkles should have been created, with all attributes intact", unicornConfirmationPage.exists(sparkles);.
It needs a closing parenthesis at the end to close the Assert.assertTrue() statement.

The link "drivers section" links to 404 page - https://github.com/SeleniumHQ/selenium-docs/blob/master/Different%20Drivers%20and%20Requirements

In http://docs.seleniumhq.org/docs/03_webdriver.jsp#cookies, it says:

If you are trying to preset cookies before you start interacting with a site and your homepage is large / takes a while to load an alternative is to find a smaller page on the site, typically the 404 page is small (http://example.com/some404page)

A more concise explanation would be:

If you are trying to preset cookies before you start interacting with a site and your homepage is large or it takes a while to load**,** an alternative is to find a smaller page on the site**. T**ypically the site's 404 page is small enough (http://example.com/some404page)

Hi i am experiencing the same problem like user Lorelehy on Google groups, therefore i used his/hers post.

I can not access the documentation of web driver.
http://www.seleniumhq.org/docs/03_webdriver.jsp
Error: Server Error
The server encountered an error and could not complete your request.
Please try again in 30 seconds.

The documentation is also not available in GitHub.
Thank you for the help you can give me.

I ask you kindly to fix the documentation.

BR,

Stephan

As shared by @cgoldberg:
https://labs.detectify.com/2017/10/06/guest-blog-dont-leave-your-grid-wide-open/

We could probably add this to the selenium grid setup section.

We want the code examples in the documentation to be available in multiple languages. If we annotate the containers for the code with the language we can implement a folding technique similar to the one found in the existing, official Selenium documentation.

Suggestion for annotation:

<pre class=py><code>…</code></pre>
<pre class=js><code>…</code></pre>
…

This entails writing a bit of JavaScript code to do the language selection, and some CSS to do the styling and folding of the containers.

Direct links to headings do not work on first load, but do once the page is loaded in the tab.

The Worst Practices page has an empty section to add some open source performance testing recommendations. These should be identified and added.

The table of contents has a fixed position relative to the user's viewport, but on smaller resolution screen, when viewing a page with a large number of headings (like webdriver ) some of the contents can be obscured by the browser fold. It would be handy if you could scroll the table of contents to reveal the complete contents.

Here are some links to pages and grammatical issues that are on them:

Page 1:
1. Under "DRIVER REQUIREMENTS":
(a) In the 2nd paragraph, there's "detalis".
(b) Under "Chromium/Chrome": in the 2nd paragraph, "that makes up" needs to be changed to "make up".
(c) Under "Opera (Presto-based)": in the 1st paragraph, there needs to be a period after "server JAR".
2. Under "WAITS" -> "Explicit waiting":
(a) In the last sentence of the 1st paragraph:
-There's "falsy".
-The 2nd occurrence of "keep" needs to be removed.
(b) In the 1st sentence of the 4th paragraph, there's "truthy".

Page 2
1. Under "PROS AND CONS": in the first paragraph, "suite" needs to be changed to "suit".
2. Under "ROLLING YOUR OWN GRID": under "Quick start", there's the following line:
"Step 1: Start the ub"

At http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp#explicit-and-implicit-waits there is this part:

Waiting is having the automated task execution elapse a certain amount of time before continuing with the next step. You should choose to use Explicit Waits or Implicit Waits. Mixing both will cause unintended consequences, namely waits sleeping for the maximum time even if the element is available or condition is true.

The last part is not clear what it means (highlighted):

Mixing both will cause unintended consequences, namely waits sleeping for the maximum time even if the element is available or condition is true.

It would be much clearer if it is written as:

Mixing both will cause unintended consequences, like sleeping for the maximum time even if the element is available or condition is true.

The warning below may be already saying what the last paragraph sentence means:

WARNING: Do not mix implicit and explicit waits. Doing so can cause unpredictable wait times. For example setting an implicit wait of 10s and an explicit wait of 15 seconds, could cause a timeout to occur after 20 seconds.

So this change might be unnecessary (the offending paragraph sentence could be removed).

I use:
Firefox 52
Selenium 3.8.1
geckodriver 0.16.0
Windows Vista

Code (for example):
ActionChains(driver).key_down(Keys.CONTROL).send_keys("t").key_up(Keys.CONTROL).perform()
driver.switch_to_window(driver.window_handles[-1])
driver.get(url)

Sometimes, Firefox can open new tab, but it stops and can not further navigate to the targeted website. In rest cases, Firefox can perform the task successfully.
What is the problem? Can anyone help?

Would you consider translating this document into multiple languages?

是否考虑将本文档翻译为多国语言？

There are many testers in China who are not good at English.

在**有很多测试人员英语不好。

In the best practices page there is a paragraph named "Fresh Browser Per Test".
In this paragraph it's explained "at least start a new WebDriver for each test".
If a new WebDriver is started after each test, few seconds (maybe 20 or 30 seconds) will be used for start the browser and quit the browser. This process increases hugely the time necessary to execute all the tests.
I understand the interest to start a fresh browser for each tests but the total time necessary for execute all the tests will hugely increase. am I wrong?

Thanks.

Into docs/docs_source_files/content/webdriver the file:

understanding_the_componets.nl.md

has a mistake.

If you visit this page, the language selector only has Nederlands.

I'm going to leave it fixed on a branch.

Note1: I am not sure if this is the correct repository to create this issue, if it is not please point me to the correct resource.
Note 2: I am a total newbie in using selenium. This is the first time I get my hands into the docs so I will be creating issues regarding anything that I think should be documented for clarity.

In http://docs.seleniumhq.org/docs/03_webdriver.jsp#chapter03-reference, more specifically in the "Java" section, there is some dependencies examples in maven:

The below example is pretty intuitive. It is supposed to work as the main dependency for java.

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>2.44.0</version>
</dependency>

The next dependency though is also pretty clear. It means you should add some kind of "driver" dependency for each browser.

<dependency>
  <groupId>com.opera</groupId>
   <artifactId>operadriver</artifactId>
</dependency>

The problem is that it should contain not only one example of a driver, but the reference to all supported driver artifacts groupIds and artifactIds. This page is supposed to be the first resource to be viewed by a developer after all.

Why is that? You may be asking.

Well, I could look on maven central for "com.google" groupId and "chromedriver" artifactId, but it wouldnt mean I would get the correct and supported artifact. There are cases where people uploaded artifacts using a package but that wasn't the official version of that artifact, that is why the official docs should mention every supported driver, and if it is already mentioned somewhere, it should mention in this specific section to make it clear which drivers are supported.

If the artifacts are mentioned elsewhere: Put the relevant links on this page.
If the artifacts are not mentioned elsewhere: Create the artifacts references page and put the relevant links on this page.

I hope this is useful to help the documentation to become better.

(Last note: I am creating an issue instead of a pull request because I believe I don't have enough context of the overall documentation to be able to enhance it in a proper way).

As version numbers change from time to time, it would be handy if we replaced the version number in example pom files and jars with the latest version number automatically. Do we have an endpoint that would work for this purpose? Something like http://selenium-release.storage.googleapis.com/latest.html ?

Alternatively we could add a class to the current download page, and do an GET request and scrape the latest version number off of the page and add it to a cookie, but that seems kind of hacky. Any opinions?

Code would be a much more readable if syntax was highlighted.

f.ex
http://prismjs.com/
https://highlightjs.org/
could be used

Will it make sense to have a section for selenium docker in this documentation?

This link is https://seleniumhq.github.io/docs/site even when you choose other language. And it will redir to https://seleniumhq.github.io/docs/site/en/.

Here are some grammatical issues that are on this page:

• Under "One interface to rule them all": in the 3rd last sentence:
  • (a) The 2nd comma needs to be removed.
  • (b) The 3rd comma needs to be changed to a period.
  • (c) The initial letter of "what" needs to be made uppercase.
• Under "History": in the 1st sentence, there needs to be "was" between "1" and "released".

https://seleniumhq.github.io/docs/site/zh-cn/

The source code is:

Selenium 的核心是 _[WebDriver]({{< ref "/webdriver/_index.md" >}})_，这是一个编写指令集的接口，可以在许多浏览器中互换运行。
这里有一个最简单的说明：

compare to en:

At the core of Selenium is _[WebDriver]({{< ref "/webdriver/_index.md" >}})_, 
an interface to write instruction sets that can be run interchangeably in many 
browsers. Here is one of the simplest instructions you can make:

I think the issue is caused by ，.

In the third paragraph in this section there is a a link to the Command Reference. The server referenced (release.seleniumhq.org) is down (it does not respond to pings) so the Selenium command reference is not accessible.

The SELENIUM REMOTE CONTROL TO WEBDRIVER MIGRATION page is blank.

Looking for some additional hints and tips to write this up - I'll be starting with:
Migrating the herd - How Salesforce is migrating 35,000 Selenium RC tests @ Selenium Conf 14

This should make clear how to send a PR to improve the docs, and also what to considere regarding the different translations of the docs.
Also include a PR template that will mention the main bullet points and a link to the CONTRIBUTING.md doc.

Hi Team,

In the below description of web driver, there is a small spelling mistake.
"The" is spelled as he in the below paragraph of webdriver.

WEBDRIVER

Hence you are testing he same application which you push live.

Kindly correct the above spelling.

(Haven't checked in any other browsers)

Firefox:

Chrome:

We are hitting the GitHub public API quota when the contributors page is being generated, this causes builds to break and people who send PRs get an error when their PR is actually completely valid.