A propos de cette documentation

Cette documentation, tout comme le code lui-même, est maintenue à 100% par des volontaires de la communauté Selenium. Beaucoup font partie des utilisateurs de la première heure, mais encore plus sont des utilisateurs récents, et ont donné de leur temps pour améliorer l’accueil des nouveaux utilisateurs.

Si vous rencontrez un problème avec la documentation, nous souhaitons le savoir ! La meilleure façon de communiquer un problème est de visiter https://github.com/seleniumhq/seleniumhq.github.io/issues et de vérifier si ce problème a déjà été remonté. Si ce n’est pas le cas, n’hésitez pas à ouvrir une nouvel issue !

De nombreux membre de la communauté fréquentent le canal Libera Libera.chat. N’hésitez pas à passer et poser vos questions. Si vous recevez de l’aide et pensez que cela devrait faire partie de la documentation, votre contribution sera plus que bienvenue ! Nous pouvons mettre à jour cette documentation, mais c’est beaucoup plus facile pour tout le monde lorsque nous recevons des contributions venant de nouvelles personnes.

1 - Copyright et attributions

Copyright, contributions and all attributions for the different projects under the Selenium umbrella.

Page being translated from English to French. Do you speak French? Help us to translate it by sending us pull requests!

The Documentation of Selenium

Every effort has been made to make this documentation as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an “as-is” basis. The authors and the publisher shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book. No patent liability is assumed with respect to the use of the information contained herein.

Attributions

Thanks to:

Selenium Main Repository

5118 commits
3352 commits
2440 commits
1464 commits
1298 commits
1175 commits
1162 commits
1125 commits
599 commits
492 commits
473 commits
420 commits
373 commits
326 commits
289 commits
225 commits
205 commits
200 commits
191 commits
179 commits
153 commits
147 commits
138 commits
137 commits
133 commits
115 commits
109 commits
108 commits
94 commits
90 commits
89 commits
66 commits
63 commits
49 commits
48 commits
46 commits
44 commits
44 commits
42 commits
41 commits
40 commits
36 commits
32 commits
30 commits
28 commits
27 commits
25 commits
22 commits
20 commits
20 commits
20 commits
19 commits
16 commits
14 commits
12 commits
12 commits
12 commits
12 commits
11 commits
11 commits
10 commits
10 commits
9 commits
9 commits
9 commits
9 commits
8 commits
7 commits
7 commits
7 commits
7 commits
7 commits
7 commits
6 commits
6 commits
6 commits
5 commits
5 commits
5 commits
5 commits
5 commits
5 commits
5 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits

Selenium IDE

2445 commits
607 commits
88 commits
51 commits
36 commits
36 commits
34 commits
15 commits
15 commits
12 commits
11 commits
5 commits
3 commits
3 commits
3 commits
2 commits
2 commits
2 commits
2 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits

Docker Selenium

401 commits
133 commits
53 commits
53 commits
50 commits
24 commits
8 commits
5 commits
5 commits
5 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
4 commits
3 commits
3 commits
3 commits
3 commits
3 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits

Selenium Website & Docs

415 commits
380 commits
323 commits
71 commits
32 commits
30 commits
28 commits
25 commits
21 commits
20 commits
18 commits
17 commits
17 commits
12 commits
10 commits
8 commits
8 commits
6 commits
6 commits
6 commits
5 commits
5 commits
5 commits
4 commits
4 commits
4 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
3 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits

Previous Selenium Website

417 commits
91 commits
89 commits
79 commits
63 commits
59 commits
40 commits
40 commits
36 commits
26 commits
24 commits
22 commits
21 commits
21 commits
19 commits
17 commits
14 commits
12 commits
11 commits
11 commits
10 commits
7 commits
6 commits
5 commits
5 commits
5 commits
5 commits
5 commits
5 commits
3 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits

Previous Documentation Rewrite Project

197 commits
105 commits
54 commits
30 commits
27 commits
25 commits
21 commits
17 commits
16 commits
12 commits
12 commits
12 commits
12 commits
8 commits
7 commits
6 commits
6 commits
6 commits
6 commits
5 commits
5 commits
5 commits
4 commits
4 commits
4 commits
4 commits
3 commits
3 commits
3 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
2 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits
1 commits

Third-Party software used by Selenium documentation project:

SoftwareVersionLicense
Hugov0.83.1Apache 2.0
DocsyApache 2.0

License

All code and documentation originating from the Selenium project is licensed under the Apache 2.0 license, with the Software Freedom Conservancy as the copyright holder.

The license is included here for convenience, but you can also find it on the Apache Foundation’s websites:

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

2 - Contributing to the Selenium Site & Documentation

Selenium est un gros projet logiciel, son site et sa documentation sont essentiels comprendre comment les choses fonctionnent et apprendre des moyens efficaces d’exploiter son potentiel.

Ce projet contient à la fois le site et la documentation de Selenium. C’est un effort continu (qui ne vise aucune version spécifique) pour fournir des informations mises à jour sur la façon d’utiliser efficacement le sélénium, impliqués et comment contribuer au sélénium.

Les contributions vers le site et les documents suivent le processus décrit dans la section ci-dessous sur les contributions.

Le projet Selenium accueille les contributions de tous. Il y a un plusieurs façons d’aider:

Signaler un problème

Lorsque vous signalez un nouveau problème ou commentez un problème existant, veuillez assurez-vous que les discussions sont liées à des problèmes techniques concrets avec le Logiciel Selenium, son site et / ou sa documentation.

Tous les composants Selenium changent assez rapidement au fil du temps, donc cela peut rendre la documentation obsolète. Si vous trouvez cela être le cas, comme mentionné, ne doutez pas de créer un problème pour cela. Il est également possible que vous sachiez comment mettre à jour documentation, merci de nous envoyer une pull request avec les informations changements.

Si vous n’êtes pas sûr que ce que vous avez trouvé soit un problème ou non, Si vous n’êtes pas sûr que ce que vous avez trouvé soit un problème ou non, veuillez demander par les canaux de communication décrits à https://selenium.dev/support.

Contributions

Le projet Selenium accueille de nouveaux contributeurs. Les individus qui font des contributions importantes et précieuses au fil du temps sont faites Committers et donné un accès de validation au projet.

Ce guide vous guidera tout au long du processus de contribution.

Step 1: Fork

Fork le projet sur Github et vérifiez votre copie localement.

% git clone git@github.com:seleniumhq/seleniumhq.github.io.git
% cd seleniumhq.github.io

Dependencies: Hugo

We use Hugo and the Docsy theme to build and render the site. You will need the “extended” Sass/SCSS version of the Hugo binary to work on this site. We recommend to use Hugo 0.83.1 or higher.

Please follow the Install Hugo instructions from Docsy.

Step 2: Branch

Créez une branche de fonctionnalité et lancez le piratage:

% git checkout -b my-feature-branch

Nous pratiquons le développement basé sur HEAD, ce qui signifie que tous les changements sont appliqués directement sur le dessus du maître.

Step 3: Faire des changements

The repository contains the site and docs. Before jumping into making changes, please initialize the submodules and install the needed dependencies (see commands below). To make changes to the site, work on the website_and_docs directory. To see a live preview of your changes, run hugo server on the site’s root directory.

% git submodule update --init --recursive
% cd website_and_docs
% npm install
% hugo server

Capitalisation des titres

Il faut éviter la capitalisation du titre, comme A Very Fine Heading, et optez plutôt pour un titre très fin. Capitalisation gratuite ou casse de titre, montrent souvent un malentendu - ou un mépris pour - conventions orthographiques. Nous préférons ce que l’on appelle le “cas de peine”, avec un seul capital initial pour démarrer les en-têtes.

Longueur de la ligne

Lors de la modification de la source de la documentation, qui est écrit en HTML simple, limitez la longueur de vos lignes à environ 72 caractères.

Certains d’entre nous vont encore plus loin et utiliser ce qu’on appelle semantic linefeeds, qui est une technique par laquelle les lignes source HTML, qui ne sont pas lus par le public, sont divisés à des “ruptures naturelles” dans la prose. En d’autres termes, les phrases sont divisées aux pauses naturelles entre les clauses. Au lieu de s’embêter avec les lignes de chaque paragraphe de sorte qu’ils se terminent tous près de la marge droite, les sauts de ligne peuvent être ajoutés n’importe où qu’il y a une rupture entre les idées.

Cela peut rendre les différences très faciles à lire lors de la collaboration via git, mais ce n’est pas quelque chose que nous imposons aux contributeurs d’utiliser.

Traduits

Les documents sont traduits en plusieurs langues et les traductions sont basées sur le contenu anglais. Lorsque vous modifiez un fichier, assurez-vous de changements dans tous les autres fichiers traduits également. Cela peut différer selon sur le changement, par exemple:

  • Si vous ajoutez un exemple de code au fichier browser_manipulation.en.md, ajoutez-le également à browser_manipulation.es.md, browser_manipulation.ef.md, browser_manipulation.ja.md, et tous les autres fichiers traduits.
  • Si vous trouvez une traduction qui peut être améliorée, ne modifiez que la traduction fichier.
  • Si vous ajoutez une nouvelle traduction linguistique, ajoutez les nouveaux fichiers avec le suffixe approprié. Il n’est pas nécessaire de tout traduire pour soumettre un PR, cela peut être fait de manière itérative. N’oubliez pas de vérifier certaines configurations nécessaires dans le fichier config.toml.
  • Si vous apportez des modifications au texte dans la version anglaise, remplacez la même section dans les fichiers traduits avec votre modification (oui, en anglais), et ajoutez ce qui suit remarquez en haut du fichier.
{{% pageinfo color="warning" %}}
<p class="lead">
   <i class="fas fa-language display-4"></i> 
   Page being translated from 
   English to {LANGUAGE}. Do you speak {LANGUAGE}? Help us to translate
   it by sending us pull requests!
</p>
{{% /pageinfo %}}

Step 4: Commit

Assurez-vous d’abord que git connaît votre nom et votre adresse e-mail:

% git config --global user.name 'Santa Claus'
% git config --global user.email 'santa@example.com'

Il est important d’écrire de bons messages de validation. Un message de validation devrait décrire ce qui a changé, pourquoi et les problèmes de référence résolus (si tout). Suivez ces directives lorsque vous en rédigez une:

  1. La première ligne doit contenir environ 50 caractères ou moins et contenir un     brève description du changement.
  2. Laissez la deuxième ligne vierge.
  3. Enveloppez toutes les autres lignes sur 72 colonnes.
  4. Incluez Fixes #N, où N est le numéro de problème du commit     corrections, le cas échéant.

Un bon message de validation peut ressembler à ceci:

explain commit normatively in one line

Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc.

The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about
72 characters or so. That way `git log` will show things
nicely even when it is indented.

Fixes #141

La première ligne doit être significative car c’est ce que les gens voient lorsqu’ils exécutez git shortlog ou git log --oneline.

Step 5: Rebase

Utilisez git rebase (et non git merge) pour synchroniser votre travail de temps en temps.

% git fetch upstream
% git rebase upstream/trunk

Step 6: Test

N’oubliez pas de exécuter le serveur local, avec cela, vous pouvez être sûr que vos modifications n’ont rien cassé.

Step 7: Push

% git push origin my-feature-branch

Accédez à _https://github.com/yourusername/seleniumhq.github.io.git_ et appuyez sur la Pull Request et remplissez le formulaire. Indiquez s’il vous plait que vous avez signé le CLA (voir l’étape 7).

Les demandes d’extraction sont généralement examinées en quelques jours. S’il y a commentaires à adresser, appliquez vos modifications dans les nouveaux commits (de préférence fixups) et pousser à la même chose branche.

Step 8: Integration

Lorsque la révision du code est terminée, un committer prendra votre PR et l’intégrer dans la branche principale du référentiel. Parce que nous aimons garder un histoire linéaire sur la branche principale, nous allons normalement écraser et rebaser l’historique de votre succursale.

Communication

Tous les détails sur la façon de communiquer avec les contributeurs du projet et la communauté dans son ensemble se trouve sur https://selenium.dev/support