This repository has been archived by the owner on Mar 20, 2024. It is now read-only.
docs(guide): french translation of the testing configuration guide #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ClementVidal
changed the title
ClementVidal
changed the title
| - write a test plan in code | ||
| - écire un plan de test dans le code |
There was a problem hiding this comment.
écrire*
écrire un plan de test en code ?
écrire le code d'un plan de test ?
coder un plan de test ?
|
|
||
| It’s a big agenda. Fortunately, you can learn a little bit at a time and put each lesson to use. | ||
| C'est un gros agenda. Heureusement, vous pouvez apprendre petit à petit et mettre chaque leçon en pratique. |
There was a problem hiding this comment.
un "vaste programme" plutot qu'un "gros agenda" ?
| :marked | ||
| The Unit Testing chapters build upon each other. We recommend reading them in order. | ||
|
|
||
| Chaque châpitre sur les tests unitaires se base sur le précédent. Nous recommendons de les lires dans l'ordre. |
| We're also assuming that you're already comfortable with basic Angular 2 concepts and the tools | ||
| we introduced in the [QuickStart](../quickstart.html) and | ||
| the [Tour of Heroes](../tutorial/) tutorial | ||
| such as <code>npm</code>, <code>gulp</code>, and <code>lite-server</code>. | ||
|
|
||
| Nous nous attendons à ce que vous soyez déja habitué aux concepts basiques d'Angular 2 et aux outils | ||
| que nous avons présentés dans le [Démarrage rapide]](../quickstart.html) et le | ||
| tutoriel [Tour des héros](../tutorial/) comme <code>npm</code>, <code>gulp</code>, and <code>lite-server</code>. |
| The description should be sufficient to identify the tested application part and its source file. Almost any convention will do as long as you and your team follow it consistently and are never confused. | ||
|
|
||
| La description doit être suffisante pour identifier la partie testée et son fichier source. Presque toutes les conventions feront l'affaire, temps que vous et votre équipe les suivez correctements et que vous n' êtes jamais perdus. |
There was a problem hiding this comment.
temps que
=> tant que
correctement
sans 's'
| **Create** a new file, ** `hero.spec.ts` ** in `app` next to `hero.ts`. | ||
|
|
||
| **Créez** un nouveau fichié, ** `hero.spec.ts` ** dans `app` à coté de `hero.ts`. |
| Notice the ".spec" suffix in the test file's filename, appended to the name of the file holding the application part we're testing. | ||
|
|
||
| Notez le ".spec" suffixe dans le nom du fichier de test, ajouté au nom du fichier contenant la partie de l'application que nous testons. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for submitting this PR...
Please check if the PR fulfills these requirements
Please provide the issue number?
issue #21
Did you finish translating the whole issue?
What kind of change does this PR introduce? (check one with "x")
Other information: