After tests are running- what next?
The first step in getting started on Automated Testing is to start running automation locally. After getting set up, the next big step is to make your first pull request. It may feel like a big leap, but if you have gotten as far as running tests successfully – then making changes is just the next step forward.
In order to make a good pull request, it’s important to get to know the project code. You can choose any of the projects listed on our Projects page. All of our projects are available for contributor work, but if you’re looking for a suggestion the mcom-tests project is a good place to start working.
Open up all of the folders and files in the project – and take a look around! You’ll see all of the styles and formatting we use in each of the tests. Feel free to review our Style guide on automation.
Keep an eye out for the “Community” label on GitHub tests! We are introducing this new label to mark Issues that are good for beginners.
When you see this label, it signifies that these tasks are oriented towards contributors who are just getting involved with automation. There are Community tasks in each of the projects listed on the Projects page.
Community tests are just for you!
1) Open up any of our automation projects, and look at the Issues. Look for the bright purple tag that signifies Community tasks. Open the task and see if anyone is working on it. If no one is assigned- then it’s free for you to pick up!
2) Follow the steps in the Issue, making your changes and then submitting the pull request for review.
* If you need a little help creating your first pull request, the best place to go is GitHub. Here is a link to documents reviewing how to use and create pull requests. If you’ve gotten as far as running tests locally, you are most of the way there!
3) After you have had your pull request merged, make sure to go ahead and Claim your Badge!
Our team loves to see contributors branching out and testing new skills. We’re hoping you’ll make the leap to getting more involved with our projects!
Luke wrote on :