|
| 1 | +# Contributing to E2E CodeceptJS Boilerplate |
| 2 | + |
| 3 | +Thank you for your interest in contributing to the E2E CodeceptJS Boilerplate! This document outlines the process for contributing to the project, including setting up the development environment, coding standards, and submitting changes. |
| 4 | + |
| 5 | +## Table of Contents |
| 6 | +- [Code of Conduct](#code-of-conduct) |
| 7 | +- [Getting Started](#getting-started) |
| 8 | +- [Development Setup](#development-setup) |
| 9 | +- [Coding Standards](#coding-standards) |
| 10 | +- [Creating Issues](#creating-issues) |
| 11 | +- [Submitting Pull Requests](#submitting-pull-requests) |
| 12 | +- [Running Tests](#running-tests) |
| 13 | +- [Commit Messages](#commit-messages) |
| 14 | +- [Contact](#contact) |
| 15 | + |
| 16 | +## Code of Conduct |
| 17 | +Please follow our [Code of Conduct](CODE_OF_CONDUCT.md) to maintain a welcoming environment for all contributors. |
| 18 | + |
| 19 | +## Getting Started |
| 20 | +1. Fork the repository to your GitHub account. |
| 21 | +2. Clone your forked repository to your local machine: |
| 22 | + ```bash |
| 23 | + git clone https://github.com/your-username/e2e-codeceptjs-boilerplate.git |
| 24 | + ``` |
| 25 | +3. Create a new branch for your feature or bugfix: |
| 26 | + ```bash |
| 27 | + git checkout -b feature/your-feature-name |
| 28 | + ``` |
| 29 | + |
| 30 | +## Development Setup |
| 31 | +1. **Install Node.js** (version 14.x or higher recommended). |
| 32 | +2. Install project dependencies: |
| 33 | + ```bash |
| 34 | + npm install |
| 35 | + ``` |
| 36 | +3. Set up Playwright browsers: |
| 37 | + ```bash |
| 38 | + npx playwright install |
| 39 | + ``` |
| 40 | +4. Run the tests to ensure everything is set up correctly: |
| 41 | + ```bash |
| 42 | + npm run test |
| 43 | + ``` |
| 44 | + |
| 45 | +## Coding Standards |
| 46 | +- Follow the [Airbnb JavaScript Style Guide](https://github.com/airbnb/javascript). |
| 47 | +- Ensure your code passes ESLint checks before committing: |
| 48 | + ```bash |
| 49 | + npm run lint |
| 50 | + ``` |
| 51 | + |
| 52 | +## Creating Issues |
| 53 | +Before opening a new issue, search the existing issues to avoid duplicates. When creating a new issue, provide a detailed description, including steps to reproduce, expected behavior, and relevant screenshots. |
| 54 | + |
| 55 | +## Submitting Pull Requests |
| 56 | +1. Ensure your branch is up to date with the latest `main` branch: |
| 57 | + ```bash |
| 58 | + git fetch origin |
| 59 | + git checkout main |
| 60 | + git pull origin main |
| 61 | + ``` |
| 62 | +2. Push your branch to your fork: |
| 63 | + ```bash |
| 64 | + git push origin feature/your-feature-name |
| 65 | + ``` |
| 66 | +3. Open a pull request from your branch to the `main` branch of this repository. |
| 67 | +4. Ensure that your PR description clearly explains the changes and includes relevant issue references. |
| 68 | + |
| 69 | +## Running Tests |
| 70 | +- Run the complete test suite before submitting your PR: |
| 71 | + ```bash |
| 72 | + npm run test |
| 73 | + ``` |
| 74 | +- Generate Allure reports: |
| 75 | + ```bash |
| 76 | + npm run generate-allure-report-with-history |
| 77 | + ``` |
| 78 | + |
| 79 | +## Commit Messages |
| 80 | +Use the following format for commit messages: |
| 81 | +``` |
| 82 | +feat: Add new feature description |
| 83 | +fix: Correct bug in specific module |
| 84 | +docs: Update documentation |
| 85 | +style: Improve code formatting |
| 86 | +test: Add or update tests |
| 87 | +chore: Miscellaneous tasks |
| 88 | +``` |
| 89 | + |
| 90 | +## Contact |
| 91 | +For questions or help, open a discussion on GitHub or contact us at [dipenc245@gmail.com]. |
0 commit comments