Being in the software industry you may have often heard the term code review. However, the concept of code reviewing is often misunderstood. Often it is overlooked in the software development life cycle as people feel performing testing should suffice the validation process. And so, they tend to turn a blind eye towards the code reviewing process.

1. How Code Reviewing Can Help
With Quality Assurance?

2. What Is Code Review And Its Objective?
Code reviewing is a practice where
the source code is broken into small
pieces, which are inspected by the
supervisors or seniors in the team
to be carried out just before testing.
It is a process mostly followed in
Agile methodology.

3. Why Code Reviewing Is Inevitable?
Early Bug Detection: When bugs
are detected at a very early stage in
the development phase, it reduces
a lot of time during the testing
phase. The overall process becomes
a lot inexpensive. Although
nowadays, automation testing
reduces the testing effort and time
spent, still, there is no better gift
than the human nature of detecting
and correcting mistakes committed
by others.

4. Why Code Reviewing Is Inevitable?
Mentoring Juniors: When a fresher
joins a project, seniors may not
have much time to mentor or guide
the junior about the coding
practices or train them about how
they do their job. The ideal solution
in that scenario for a senior
developer is to spend at least 20-30
minutes in reviewing the code
written by the junior.

5. Why Code Reviewing Is Inevitable?
Age of Agile: Nowadays most
organizations follow Agile methodology
and require to deliver quality work in
time. Code review will enable the
organization to develop a quality
prototype, free from defects and
developed following the standard
protocols.

6. Why Code Reviewing Is Inevitable?
Team Cohesion: Frequent review discussion brings the team closer, makes
them aware of each other’s strength and weakness and saves them from
getting stuck in an isolated environment.

7. Can Code Reviewing And Testing Replace
One Another?
For starters, Code reviewing and
testing, both are best practices to be
included in a software development
life cycle. However, both are unique in
their own ways and must not be
confused. It would be wrong to think
that you don’t need code reviewing
because you have testing in your SDLC
or vice-versa.

8. Can Code Reviewing And Testing Replace
One Another?
Code review involves inspecting the
code which may or may not include
checking for bugs. It involves checking
whether the style of code is under
compliance by all policies, whether
there is any breach of security and
most importantly, whether the code
can be understood easily or not.

9. Can Code Reviewing And Testing Replace
One Another?
Testing, on the other hand, has several
categories. The main objective of
testing is not to check the code, but to
check whether the application works
perfectly or not. Testing involves
detecting whether there are any bugs
in different layers of the application,
whether the application satisfies all
the requirements of the stakeholders
and ensuring that the issues detected
are communicated to the concerned
team.

10. Can Code Reviewing And Testing Replace
One Another?
I’ll share my personal experience. Our
team was working on a large dynamic
web application. After the final testing
phase, the entire application was
satisfying every user requirements.
However, there was one problem – the
loading time.

11. How To Participate In Code Review As QA?
Code review is considered to be a part
of static testing, an activity to be
conducted mostly by quality analysts
to find out whether any bug can be
spotted earlier, before the testing
phase starts. If the testing team
actively participates in code review, it
saves a lot of time.

12. How To Participate In Code Review As QA?
You may wonder how to get started
with code review when you are into
testing and do not have any
experience with development. But the
fact is, code reviewing only requires
your observational skills, not your
coding proficiency. For starters, you
may start with automation scripts.

13. How To Participate In Code Review As QA?
Also, if someone from your team have
been reviewing codes, discuss or sit
with them and try to get an
understanding of how they are doing
the job. Check whether they are
looking at
● Log messages which are clearly
understandable
● Syntax errors
● Errors caused by spelling mistakes
● Naming conventions

14. Ways To Perform Code Review
Formal Code Review: It is a detailed process that requires you to collaborate with
multiple participants and work in multiple phases. This is the traditional process
where the team attends meetings and check the code line by line, traditionally
using printed copies. Inspections are thoroughly done and the method is found to
be effective in finding defects.

15. Ways To Perform Code Review
Lightweight Code Review: This process is also quite effective and requires less
effort that formal code review. Conducted as a part of normal development
procedures, there are 4 ways by which this review is carried out.
Over the Shoulder, Passing Emails, Pair Programming, Tool Assisted Review

16. Code Review Checklist For Selenium Automation Testing
Although there are certain best practices which we shall discuss later, that will
result in a flawless code review, if you are conducting automation testing with
Selenium WebDriver for cross browser testing of your website, there are certain
factors to check while reviewing your code.

17. Code Review – Best Practices To Follow
Know What You Are Looking For: Set up your goal before reviewing. Prepare a list
which may include coding style, structure, the complexity of logic, readability. In
short, include items which cannot be reviewed during automated testing and
requires human intervention.

18. Code Review – Best Practices To Follow
Build & Test Prior To Review: In the current age of continuous integration and
continuous delivery, it is ideal to build and test the code before manually reviewing
it. This ensures that the code is stable and saves a lot of time.

19. Code Review – Best Practices To Follow
Don’t Take Too Long To Review: As a part of code review best practices, you need
to ensure that you are not spending more than the average time in code review. It
will be better if you review the code in short breaks to ensure that your brain gets
the required interval and you can start again with a fresh mind.

20. Code Review – Best Practices To Follow
Your Review Must Not Hurt: Instead of being critical, be constructive in your
review. Ask questions instead of making statements. Also, praise the developer for
their job. Your feedback in the right tone must not hurt them, it should rather
inspire them to correct their mistakes and make sure it does not happen again.

21. I hope you now realize the relevance of code reviewing in the SDLC, along with its
distinction from testing. If you are a product manager then it is vital for you to
incorporate code reviewing process in your release cycle, in case it already isn’t. In
case it is incorporated, you need to organize the bandwidth and resources efficiently
and make sure that the participation is active from both developers as well as
testers.
www.lambdatest.com
CONCLUSION

22. HAPPY TESTING!!