Quality Assurance

Code Reviews

Code reviews will be a prime focus of our development process throughout our projects. If you've read through the Teamwide Resources section, you should be familiar with our Git workflow. The general idea is that anytime you submit a Pull Request, you are indicating that your code is ready for production and has been fully tested and vetted. In the longterm, the code review process encourages that we all take the final effort to ensure our code is of the highest quality. It ensures that our project will be successful and professional.

My Pull Request was Rejected. Now What?

You may be upset if you submit code to the repository and it is rejected, but we ask that you understand the reasons why we promote code review as a tool for quality assurance. We want every contributor to our projects to have an opportunity to take part in creating software of the highest quality and professionalism. Code review is a cultural decision that encourages growth through peer review.

Just like you learn from the code review process during your Nanodegree, you will learn a lot from the code reviews that happen during your participation in collaborative projects. We ask that you take the suggestions from the code review to heart and use it as an opportunity to increase your skills by learning from your peers. If you have an issue with a code review, please bring it to the attention of your team leaders and we will try our best to make it right.

Testing

They say that at Google, they have 1 QA tester for every 10 software engineers. The reason for this is that Google encourages a culture of testing throughout the development process. Throughout the process of development, we will encourage functional unit testing. Every language and framework has its own testing tools, so we will leave it up to the teams to determine what tools they will be using.

Testing Resources

• Javascript - Testing in Depth
• Testing With React Components
• Testing with Rspec