CONTRIBUTING.md

Contributing

Thank you for your interest and for taking the time to contribute to this project. If you feel insecure about how to start contributing, feel free to ask us on our Discord Server in the #open-source channel.

Code of conduct

Read our Code of Conduct before contributing.

How can I contribute?

There are many ways in which you can contribute to Test-at-scale.

👥 Join the community

  Join our Discord server.

🐞 Report a bug

  Report all issues through GitHub Issues and provide as much information as you can.

🛠 Create a feature request

  We welcome all feature requests, whether for new features or enhancements to existing features. File your feature request through GitHub Issues.

⚙️ Write code to fix a Bug / new Feature Request

  We welcome contributions that help make this repo bug-free & improve the test automation experience for our users. You can also find issues tagged Good First Issues. Check out the below sections to begin.

 

Writing Code

All submissions, including submissions by project members, require review. Before raising a pull request, ensure you have raised a corresponding issue and discussed a possible solution with a maintainer. This gives your pull request the highest chance of getting merged quickly. Join our Discord Server if you need any help.

Set up your branch to write code

We use Github Flow, so all code changes happen through pull requests. Learn more.

1. Please make sure there is an issue associated with the work that you're doing. If it doesn’t exist, create an issue.
2. If you're working on an issue, please comment that you are doing so to prevent duplicate work by others also.
3. Fork the repo and create a new branch from the dev branch.
4. Please name the branch as issue-[issue-number]-[issue-name(optional)] or feature-[feature-number]–[feature-name(optional)]. For example, if you are fixing Issue #205 name your branch as issue-205 or issue-205-selectbox-handling-changes
5. Squash your commits and refer to the issue using Fix #<issue-no> in the commit message, at the start.
6. Rebase dev with your branch and push your changes.
7. Raise a pull request against the staging branch of the main repository.

Committing code

The repository contains two important (protected) branches.

• main contains the code that is tested and released.
• dev contains recent developments under testing. This branch is set as the default branch, and all pull requests should be made against this branch.

Pull requests should be made against the dev branch. staging contains all of the new features and fixes that are under testing and ready to go out in the next release.

Commit & Create Pull Requests

1. Please make sure there is an issue associated with the work that you're doing. If it doesn’t exist, create an issue.
2. Squash your commits and refer to the issue using Fix #<issue-no> in the commit message, at the start.
3. Rebase dev with your branch and push your changes.
4. Once you are confident in your code changes, create a pull request in your fork to the dev branch in the LambdaTest/test-at-scale base repository.
5. Link the issue of the base repository in your Pull request description. Guide
6. Fill out the Pull Request Template completely within the body of the PR. If you feel some areas are not relevant add N/A but don’t delete those sections.

Commit messages

• The first line should be a summary of the changes, not exceeding 50 characters, followed by an optional body that has more details about the changes. Refer to this link for more information on writing good commit messages.

• Don't add a period/dot (.) at the end of the summary line.