chore(i18n,docs): processed translations (#51264)
camperbot
GitHub
parent
be9e3aec93
commit
8e07ca93aa
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Issue Not Triaged
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Issue Not Triaged
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Issue Not Triaged
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Issue Not Triaged
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Issue Not Triaged
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Adding Comment About Newbie Mistakes
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Issue Not Triaged
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,100 +1,100 @@
|
|||
# How to add Playwright tests
|
||||
# Como adicionar testes do Playwright
|
||||
|
||||
## Installation:
|
||||
## Instalação:
|
||||
|
||||
To install and configure Playwright on your machine check out this [documentation](https://playwright.dev/docs/intro#installing-playwright)
|
||||
Para instalar e configurar o Playwright na sua máquina, confira a [documentação](https://playwright.dev/docs/intro#installing-playwright)
|
||||
|
||||
To learn how to write Playwright tests, or 'specs', please see Playwright's official [documentation](https://playwright.dev/docs/writing-tests).
|
||||
Para aprender a escrever testes do Playwright ou 'specs', confira a [documentação](https://playwright.dev/docs/writing-tests) oficial.
|
||||
|
||||
## Where to Add a Test
|
||||
## Onde adicionar um teste
|
||||
|
||||
- Playwright tests are in the `./e2e` directory.
|
||||
- Os testes do Playwright estão no diretório `./e2e`.
|
||||
|
||||
- Playwright test files are always with a `.spec.ts` extension.
|
||||
- Os arquivos de teste do Playwright têm sempre uma extensão `.spec.ts`.
|
||||
|
||||
## How to Run Tests
|
||||
## Como executar testes
|
||||
|
||||
|
||||
### 1. Ensure that MongoDB and Client Applications are Running
|
||||
### 1. Veja se as aplicações de client e do MongoDB estão em execução
|
||||
|
||||
- [Start MongoDB and seed the database](how-to-setup-freecodecamp-locally.md#step-3-start-mongodb-and-seed-the-database)
|
||||
- [Inicie o MongoDB e crie o banco de dados](how-to-setup-freecodecamp-locally.md#step-3-start-mongodb-and-seed-the-database)
|
||||
|
||||
- [Start the freeCodeCamp client application and API server](how-to-setup-freecodecamp-locally.md#step-4-start-the-freecodecamp-client-application-and-api-server)
|
||||
- [Inicie também a aplicação de client do freeCodeCamp e o servidor da API](how-to-setup-freecodecamp-locally.md#step-4-start-the-freecodecamp-client-application-and-api-server)
|
||||
|
||||
### 2. Run the Playwright Tests
|
||||
### 2. Execute os testes do Playwright
|
||||
|
||||
To run tests with Playwright check the following below
|
||||
Para executar testes com o Playwright, verifique o seguinte
|
||||
|
||||
- To run tests in UI helper mode:
|
||||
- Para executar testes no modo auxiliar de UI:
|
||||
|
||||
```console
|
||||
npx playwright test --ui
|
||||
```
|
||||
|
||||
- To run a single test:
|
||||
- Para executar um único teste:
|
||||
|
||||
```console
|
||||
npx playwright test <filename>
|
||||
npx playwright test <nome_do_arquivo>
|
||||
```
|
||||
|
||||
For example:
|
||||
Por exemplo:
|
||||
|
||||
```console
|
||||
npx playwright test landing-page.spec.ts
|
||||
```
|
||||
|
||||
- Run a set of test files in respective folders:
|
||||
- Para executar um conjunto de arquivos de teste nas respectivas pastas:
|
||||
|
||||
```console
|
||||
npx playwright test <pathToFolder1> <pathToFolder2>
|
||||
npx playwright test <caminho_da_pasta1> <caminho_da_pasta2>
|
||||
```
|
||||
|
||||
For example:
|
||||
Por exemplo:
|
||||
```console
|
||||
npx playwright test tests/todo-page/ tests/landing-page/
|
||||
```
|
||||
|
||||
- Run the test with the title:
|
||||
- Para executar o teste com o título:
|
||||
|
||||
```console
|
||||
npx playwright test -g <title>
|
||||
npx playwright test -g <título>
|
||||
```
|
||||
|
||||
For example:
|
||||
Por exemplo:
|
||||
```console
|
||||
npx playwright test -g "add a todo item"
|
||||
```
|
||||
|
||||
### 3. Debugging Tests
|
||||
### 3. Depuração dos testes
|
||||
|
||||
Since Playwright runs in Node.js, you can debug it with your debugger of choice e.g. using console.log or inside your IDE
|
||||
Como o Playwright é executado no Node.js, você pode depurá-lo com seu depurador preferido – por exemplo, usando console.log ou em seu IDE
|
||||
|
||||
- Debugging all tests:
|
||||
- Depuração de todos os testes:
|
||||
|
||||
```console
|
||||
npx playwright test --debug
|
||||
```
|
||||
|
||||
- Debugging one test file:
|
||||
- Depuração de um arquivo de teste:
|
||||
|
||||
```console
|
||||
npx playwright test example.spec.ts --debug
|
||||
```
|
||||
|
||||
### 4. Generate Test Reports
|
||||
### 4. Geração de relatórios de teste
|
||||
|
||||
The HTML Reporter shows you a full report of your tests allowing you to filter the report by browsers, passed tests, failed tests, skipped tests and flaky tests.
|
||||
O HTML Reporter mostra um relatório completo de seus testes, que permite filtrar o relatório por navegadores, testes que passaram, testes que falharam, testes ignorados e testes não confiáveis.
|
||||
|
||||
```console
|
||||
npx playwright show-report
|
||||
```
|
||||
|
||||
### 5. Troubleshooting
|
||||
### 5. Solução de problemas
|
||||
|
||||
Playwright is generally a solid bullet-proof tool. The contributor has already configured the tests to run on all OS machines, including majpr distributions of Windows, MacOS and Linux.
|
||||
O Playwright, geralmente, é uma ferramenta com pouquíssimas chances de erro. O colaborador já configurou os testes para serem executados em máquinas com todos os sistemas operacionais, incluindo as distribuições mais significativas do Windows, MacOS e Linux.
|
||||
|
||||
|
||||
- A common error seen in playwright is as follows:
|
||||
- Um erro comum visto no Playwright é o seguinte:
|
||||
|
||||
```console
|
||||
Error: page.goto: Could not connect: Connection refused
|
||||
|
|
@ -103,72 +103,72 @@ Playwright is generally a solid bullet-proof tool. The contributor has already c
|
|||
============================================================
|
||||
```
|
||||
|
||||
You can fix the above error with the following steps:
|
||||
Você pode corrigir o erro acima com os seguintes passos:
|
||||
|
||||
1. **Check the URL:** Ensure that the URL you're trying to navigate to is correct and properly formatted. Make sure there are no typos in the URL.
|
||||
1. **Verifique o URL:** confira se o URL que você está tentando navegar está certo e formatado corretamente. Certifique-se de que não há erros de digitação no URL.
|
||||
|
||||
2. **Server Status:** Check whether the server at the URL is running and accessible. You might encounter this error if the server is not running or is not accessible.
|
||||
2. **Status do servidor:** confira se o servidor no URL está em execução e acessível. Você pode encontrar esse erro se o servidor não estiver em execução ou se não estiver acessível.
|
||||
|
||||
3. **Port Availability:** Verify that the port mentioned in the URL (8000 in this case) is the correct port and is available for use. Make sure no other process is already using that port.
|
||||
3. **Disponibilidade da porta:** verifique se a porta mencionada no URL (8000, neste caso) é a porta correta e está disponível para uso. Certifique-se de que nenhum outro processo já esteja usando essa porta.
|
||||
|
||||
4. **Firewall or Security Software:** Sometimes, firewall or security software can block connections to specific ports. Check your firewall settings to ensure that the port is allowed.
|
||||
4. **Firewall ou software de segurança:** às vezes, firewalls ou software de segurança podem bloquear conexões em portas específicas. Verifique as configurações do firewall para garantir que a porta seja permitida.
|
||||
|
||||
5. **Network Connectivity:** Ensure that your system has a working network connection and can access external resources.
|
||||
5. **Conectividade de rede:** certifique-se de que seu sistema tenha uma conexão de rede ativa e possa acessar recursos externos.
|
||||
|
||||
- Another common error seen in playwright is as follows:
|
||||
- Outro erro comum visto no Playwright é o seguinte:
|
||||
|
||||
```console
|
||||
Protocol error (Network.getResponseBody): Request content was evicted from inspector cache
|
||||
```
|
||||
1. The network request was made using a method that does not include a response body, such as HEAD or CONNECT.
|
||||
2. The network request was made over a secure (HTTPS) connection, and the response body is not available for security reasons.
|
||||
3. The network request was made by a third-party resource (such as an advertisement or a tracking pixel) that is not controlled by the script.
|
||||
4. The network request was made by a script that has been paused or stopped before the response was received.
|
||||
1. A solicitação de rede foi feita usando um método que não inclui um corpo de resposta, como HEAD ou CONNECT.
|
||||
2. A solicitação de rede foi feita através de uma conexão segura (HTTPS) e o corpo da resposta não está disponível por razões de segurança.
|
||||
3. A solicitação de rede foi feita por um recurso de terceiros (como um anúncio ou um pixel de rastreamento) que não é controlado pelo script.
|
||||
4. A solicitação de rede foi feita por um script que foi pausado ou interrompido antes de a resposta ser recebida.
|
||||
|
||||
|
||||
|
||||
**For more insights on issues visit the official documentation.**
|
||||
**Para mais informações sobre essas questões, confira a documentação oficial.**
|
||||
|
||||
## Playwright-Gitpod Setup
|
||||
## Configuração do Playwright no Gitpod
|
||||
|
||||
### 1. Ensure Development Environment is Running
|
||||
### 1. Certifique-se que o ambiente de desenvolvimento está em execução
|
||||
|
||||
If starting the Gitpod environment did not automatically develop the environment:
|
||||
Se, ao iniciar o ambiente do Gitpod, o ambiente não foi desenvolvido automaticamente:
|
||||
|
||||
- Follow the [MongoDB installation guide](https://www.mongodb.com/basics/get-started).
|
||||
- Siga o [guia de instalação do MongoDB](https://www.mongodb.com/basics/get-started).
|
||||
|
||||
- Create the .env
|
||||
- Criar o arquivo .env
|
||||
```console
|
||||
cp sample.env .env
|
||||
```
|
||||
|
||||
- Create a config file.
|
||||
- Crie um arquivo de configuração.
|
||||
```console
|
||||
pnpm run create:config
|
||||
```
|
||||
|
||||
- Seed the database
|
||||
- Crie o banco de dados
|
||||
```console
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
- Develop the server and client
|
||||
- Desenvolva o servidor e o client
|
||||
```console
|
||||
pnpm run develop
|
||||
```
|
||||
|
||||
### 2. Install Playwright Build Tools
|
||||
### 2. Instale as ferramentas de compilação do Playwright
|
||||
|
||||
To install necessary dependencies for running Playwright run the following command:
|
||||
Para instalar as dependências necessárias para executar o Playwright, execute o seguinte comando:
|
||||
|
||||
```console
|
||||
pnpm run playwright:install-build-tools
|
||||
```
|
||||
|
||||
|
||||
### 3. Run the Playwright Tests on Gitpod
|
||||
### 3. Execute os testes do Playwright no Gitpod
|
||||
|
||||
To run all Playwright tests, run the following command:
|
||||
Para executar todos os testes do Playwright, execute o seguinte comando:
|
||||
|
||||
```console
|
||||
npx playwright test
|
||||
|
|
|
|||
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Adicionando comentário sobre erros de iniciante
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Issue não passou por triagem
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,100 +1,100 @@
|
|||
# How to add Playwright tests
|
||||
# Як додати тести Playwright
|
||||
|
||||
## Installation:
|
||||
## Встановлення:
|
||||
|
||||
To install and configure Playwright on your machine check out this [documentation](https://playwright.dev/docs/intro#installing-playwright)
|
||||
Щоб встановити та налаштувати Playwright на своїй машині, див. [документацію](https://playwright.dev/docs/intro#installing-playwright)
|
||||
|
||||
To learn how to write Playwright tests, or 'specs', please see Playwright's official [documentation](https://playwright.dev/docs/writing-tests).
|
||||
Щоб дізнатися, як писати тести Playwright, або «специфікації», зверніться до офіційної [документації Playwright](https://playwright.dev/docs/writing-tests).
|
||||
|
||||
## Where to Add a Test
|
||||
## Куди додати тест
|
||||
|
||||
- Playwright tests are in the `./e2e` directory.
|
||||
- Тести Playwright знаходяться в каталозі `./e2e`.
|
||||
|
||||
- Playwright test files are always with a `.spec.ts` extension.
|
||||
- Файли тестів Playwright завжди мають розширення `.spec.ts`.
|
||||
|
||||
## How to Run Tests
|
||||
## Як проводити тести
|
||||
|
||||
|
||||
### 1. Ensure that MongoDB and Client Applications are Running
|
||||
### 1. Переконайтеся, що MongoDB і клієнтські програми запущені
|
||||
|
||||
- [Start MongoDB and seed the database](how-to-setup-freecodecamp-locally.md#step-3-start-mongodb-and-seed-the-database)
|
||||
- [Запустіть MongoDB і заповнiть базу даних](how-to-setup-freecodecamp-locally.md#step-3-start-mongodb-and-seed-the-database)
|
||||
|
||||
- [Start the freeCodeCamp client application and API server](how-to-setup-freecodecamp-locally.md#step-4-start-the-freecodecamp-client-application-and-api-server)
|
||||
- [Запустіть клієнтський застосунок freeCodeCamp і сервер API](how-to-setup-freecodecamp-locally.md#step-4-start-the-freecodecamp-client-application-and-api-server)
|
||||
|
||||
### 2. Run the Playwright Tests
|
||||
### 2. Запустіть тести Playwright
|
||||
|
||||
To run tests with Playwright check the following below
|
||||
Щоб запустити тести Playwright, зверніть увагу на інформацію нижче
|
||||
|
||||
- To run tests in UI helper mode:
|
||||
- Щоб запустити тести в режимі помічника UI:
|
||||
|
||||
```console
|
||||
npx playwright test --ui
|
||||
```
|
||||
|
||||
- To run a single test:
|
||||
- Щоб запустити один тест:
|
||||
|
||||
```console
|
||||
npx playwright test <filename>
|
||||
```
|
||||
|
||||
For example:
|
||||
Наприклад:
|
||||
|
||||
```console
|
||||
npx playwright test landing-page.spec.ts
|
||||
```
|
||||
|
||||
- Run a set of test files in respective folders:
|
||||
- Щоб запустити набір файлів тестів у відповідних папках:
|
||||
|
||||
```console
|
||||
npx playwright test <pathToFolder1> <pathToFolder2>
|
||||
```
|
||||
|
||||
For example:
|
||||
Наприклад:
|
||||
```console
|
||||
npx playwright test tests/todo-page/ tests/landing-page/
|
||||
```
|
||||
|
||||
- Run the test with the title:
|
||||
- Щоб запустити тест із заголовком:
|
||||
|
||||
```console
|
||||
npx playwright test -g <title>
|
||||
```
|
||||
|
||||
For example:
|
||||
Наприклад:
|
||||
```console
|
||||
npx playwright test -g "add a todo item"
|
||||
```
|
||||
|
||||
### 3. Debugging Tests
|
||||
### 3. Налагодження тестів
|
||||
|
||||
Since Playwright runs in Node.js, you can debug it with your debugger of choice e.g. using console.log or inside your IDE
|
||||
Оскільки Playwright працює в Node.js, його можна налагодити за допомогою власного налагоджувача. Наприклад, використавши console.log або в IDE
|
||||
|
||||
- Debugging all tests:
|
||||
- Налагодження всіх тестів:
|
||||
|
||||
```console
|
||||
npx playwright test --debug
|
||||
```
|
||||
|
||||
- Debugging one test file:
|
||||
- Налагодження одного файлу тесту:
|
||||
|
||||
```console
|
||||
npx playwright test example.spec.ts --debug
|
||||
```
|
||||
|
||||
### 4. Generate Test Reports
|
||||
### 4. Формування звіту про тести
|
||||
|
||||
The HTML Reporter shows you a full report of your tests allowing you to filter the report by browsers, passed tests, failed tests, skipped tests and flaky tests.
|
||||
HTML Reporter надає повний звіт про ваші тести, що дає змогу фільтрувати звіт за браузерами, пройденими тестами, проваленими тестами, пропущеними тестами та ненадійними тестами.
|
||||
|
||||
```console
|
||||
npx playwright show-report
|
||||
```
|
||||
|
||||
### 5. Troubleshooting
|
||||
### 5. Розв’язання проблем розробки
|
||||
|
||||
Playwright is generally a solid bullet-proof tool. The contributor has already configured the tests to run on all OS machines, including majpr distributions of Windows, MacOS and Linux.
|
||||
Playwright, як правило, є інструментом з дуже малим шансом на помилку. Помічник вже налаштував тести для виконання на машинах з усіма операційними системами, включно з найважливішими дистрибутивами Windows, MacOS і Linux.
|
||||
|
||||
|
||||
- A common error seen in playwright is as follows:
|
||||
- Поширена помилка в Playwright виглядає так:
|
||||
|
||||
```console
|
||||
Error: page.goto: Could not connect: Connection refused
|
||||
|
|
@ -103,72 +103,72 @@ Playwright is generally a solid bullet-proof tool. The contributor has already c
|
|||
============================================================
|
||||
```
|
||||
|
||||
You can fix the above error with the following steps:
|
||||
Цю помилку можна виправити за допомогою таких кроків:
|
||||
|
||||
1. **Check the URL:** Ensure that the URL you're trying to navigate to is correct and properly formatted. Make sure there are no typos in the URL.
|
||||
1. **Перевірте URL:** переконайтесь, що URL, на який ви намагаєтесь перейти, правильний та відформатований. Переконайтесь, що в посиланні немає помилок.
|
||||
|
||||
2. **Server Status:** Check whether the server at the URL is running and accessible. You might encounter this error if the server is not running or is not accessible.
|
||||
2. **Стан сервера:** перевірте, чи сервер працює та доступний. Ви можете зіткнутися з цією помилкою, якщо сервер не працює або недоступний.
|
||||
|
||||
3. **Port Availability:** Verify that the port mentioned in the URL (8000 in this case) is the correct port and is available for use. Make sure no other process is already using that port.
|
||||
3. **Доступність порту:** переконайтесь, що порт, згаданий в URL (у цьому випадку 8000) правильний та доступний для використання. Переконайтеся, що жоден інший процес не використовує цей порт.
|
||||
|
||||
4. **Firewall or Security Software:** Sometimes, firewall or security software can block connections to specific ports. Check your firewall settings to ensure that the port is allowed.
|
||||
4. **Брандмауер та безпечне програмне забезпечення:** брандмауери та безпечне програмне забезпечення іноді можуть блокувати підключення до певних портів. Перевірте налаштування брандмауера, щоб переконатися, що порт дозволений.
|
||||
|
||||
5. **Network Connectivity:** Ensure that your system has a working network connection and can access external resources.
|
||||
5. **Підключення до мережі:** переконайтесь, що ваша система з’єднана з мережею та може отримати доступ до зовнішніх ресурсів.
|
||||
|
||||
- Another common error seen in playwright is as follows:
|
||||
- Ще одна поширена помилка в Playwright виглядає так:
|
||||
|
||||
```console
|
||||
Protocol error (Network.getResponseBody): Request content was evicted from inspector cache
|
||||
```
|
||||
1. The network request was made using a method that does not include a response body, such as HEAD or CONNECT.
|
||||
2. The network request was made over a secure (HTTPS) connection, and the response body is not available for security reasons.
|
||||
3. The network request was made by a third-party resource (such as an advertisement or a tracking pixel) that is not controlled by the script.
|
||||
4. The network request was made by a script that has been paused or stopped before the response was received.
|
||||
1. Мережевий запит було зроблено за допомогою методу, який не містить тіла відповіді (наприклад, HEAD або CONNECT).
|
||||
2. Мережевий запит було зроблено через безпечне з’єднання (HTTPS), а тіло відповіді недоступне з міркувань безпеки.
|
||||
3. Мережевий запит зроблено стороннім ресурсом (наприклад, рекламою чи пікселем відстеження), який не контролюється сценарієм.
|
||||
4. Мережевий запит було зроблено сценарієм, який було призупинено або зупинено до отримання відповіді.
|
||||
|
||||
|
||||
|
||||
**For more insights on issues visit the official documentation.**
|
||||
**Для отримання додаткової інформації відвідайте офіційну документацію.**
|
||||
|
||||
## Playwright-Gitpod Setup
|
||||
## Налаштування Playwright-Gitpod
|
||||
|
||||
### 1. Ensure Development Environment is Running
|
||||
### 1. Переконайтеся, що середовище розробки запущене
|
||||
|
||||
If starting the Gitpod environment did not automatically develop the environment:
|
||||
Якщо запуск середовища Gitpod не розробив середовище автоматично:
|
||||
|
||||
- Follow the [MongoDB installation guide](https://www.mongodb.com/basics/get-started).
|
||||
- Дотримуйтесь [посібнику з налаштування MongoDB](https://www.mongodb.com/basics/get-started).
|
||||
|
||||
- Create the .env
|
||||
- Створіть .env
|
||||
```console
|
||||
cp sample.env .env
|
||||
```
|
||||
|
||||
- Create a config file.
|
||||
- Створіть конфігураційний файл.
|
||||
```console
|
||||
pnpm run create:config
|
||||
```
|
||||
|
||||
- Seed the database
|
||||
- Заповніть базу даних
|
||||
```console
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
- Develop the server and client
|
||||
- Розробіть сервер та клієнта
|
||||
```console
|
||||
pnpm run develop
|
||||
```
|
||||
|
||||
### 2. Install Playwright Build Tools
|
||||
### 2. Встановіть інструменти збірки Playwright
|
||||
|
||||
To install necessary dependencies for running Playwright run the following command:
|
||||
Щоб встановити необхідні залежності для запуску Playwright, виконайте цю команду:
|
||||
|
||||
```console
|
||||
pnpm run playwright:install-build-tools
|
||||
```
|
||||
|
||||
|
||||
### 3. Run the Playwright Tests on Gitpod
|
||||
### 3. Запустіть тести Playwright на Gitpod
|
||||
|
||||
To run all Playwright tests, run the following command:
|
||||
Щоб запустити всі тести Playwright, виконайте цю команду:
|
||||
|
||||
```console
|
||||
npx playwright test
|
||||
|
|
|
|||
|
|
@ -129,40 +129,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
|
|||
## Додавання коментарів про помилки новачків
|
||||
|
||||
```markdown
|
||||
Hi there,
|
||||
Hello,
|
||||
|
||||
Thanks for creating this pull request.
|
||||
Firstly, thank you for submitting this pull request!
|
||||
|
||||
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
|
||||
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
|
||||
|
||||
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
|
||||
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
|
||||
|
||||
<details>
|
||||
<summary>Here are some examples (expand)</summary>
|
||||
<summary>**Friendly Pointers (click to expand)**</summary>
|
||||
|
||||
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
|
||||
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
|
||||
|
||||
Typos and formatting errors can break the tests.
|
||||
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
|
||||
|
||||
2. Use the correct way to link issues.
|
||||
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
|
||||
|
||||
Add the issue number only in the description of the PR by updating the `XXXXXX`. Не додавайте номери завдань будь-де.
|
||||
|
||||
4. Keep mentions and review requests to a minimum.
|
||||
|
||||
We understand you are excited about contributing, and our maintainers will get back to you when they can.
|
||||
|
||||
5. Do not work directly off your `main` branch.
|
||||
|
||||
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
|
||||
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
|
||||
|
||||
</details>
|
||||
|
||||
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
|
||||
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
|
||||
|
||||
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
|
||||
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
|
||||
|
||||
Happy Contributing.
|
||||
**Happy Contributing!** 🌟
|
||||
```
|
||||
|
||||
## Невідсортоване завдання
|
||||
|
|
@ -241,4 +233,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
|
|||
Issues labelled with `help wanted` or `first timers only` are open for contributions.
|
||||
|
||||
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
|
||||
```
|
||||
```
|
||||
|
|
|
|||
Loading…
Reference in New Issue