What is the Diff between Code Walk through & Code Review?
Answers were Sorted based on User's Feedback
Answer / varsha b
walk through is a informal review.In walk through author of
code actually lead the walkthrough and other participants
just review the code.
Code review can be formal or informal.If its informal then
is is known as peer review or walk through where as if its
formal then it is known as inspection.
reviews are static testing processes hence no code is
actually executed in review.
|Is This Answer Correct ?||17 Yes||3 No|
Code review and code walkthrough is a phase in the software
But in code review we schedule a meeting in which the
authors of code, developer of the code, and perhaps quality
assurance (QA) testers get together to review code. Meeting
time is given earlier along with code to be reviewed at that
time by moderator.
But in code walkthrough we will not schedule any meeting it
can happen at any time or can happen suddenly without any
intimation before hand. They will come to meeting room
straight away and discuss the topic.
For code review and code walkthing finding and correcting
errors at this stage is relatively inexpensive and tends to
reduce the more expensive process of handling, locating, and
fixing bugs during later stages of development or after
programs are delivered to users.
1.Reviewers read the code line by line and walkthrough might
not read line by line just a informal go through to check for:
For either code review or walkthrough these are the
following things we need to check
1. Flaws or potential flaws
2. Consistency with the overall program design
3. The quality of comments
4. Adherence to coding standards.
5. Existance, for the functionality implemented.
6. Clarity and Readability
7. Completness - e.g., User, Training, Reference, Table
Code review may be especially productive for identifying
HOpe this might give you all answer.
|Is This Answer Correct ?||10 Yes||1 No|
Answer / amar patil
Code walkthrough is informal process where code is executed
at any time. Author of code leads the code walkthrough
code review is formal process where review is done line by
line in the formal meeting of developers and QA engineers.
|Is This Answer Correct ?||5 Yes||0 No|
Answer / mehul
Code review is a phase in the software development process in which the authors of code, peer reviewers, and perhaps quality assurance (QA) testers get together to review code. Finding and correcting errors at this stage is relatively inexpensive and tends to reduce the more expensive process of handling, locating, and fixing bugs during later stages of development or after programs are delivered to users.
Reviewers read the code line by line to check for:
Flaws or potential flaws
Consistency with the overall program design
The quality of comments
Adherence to coding standards.
Code review may be especially productive for identifying security vulnerabilities. Specialized application programs are available that can help with this process. Automated code reviewing facilitates systematic testing of source code for potential trouble such as buffer overflows, race conditions, memory leakage, size violations, and duplicate statements. Code review is also commonly done to test the quality of patches.
An inspection is, most generally, an organized examination or formal evaluation exercise. It involves the measurements, tests, and gauges applied to certain characteristics in regard to an object or activity. The results are usually compared to specified requirements and standards for determining whether the item or activity is in line with these targets. Inspections are usually non-destructive.
Non-Destructive Examination (NDE) or Non-Destructive Testing (NDT) describe a number of technologies used to analyze materials for either inherent flaws or damage from use. Some common methods are visual, Liquid or Dye Penetrant, Magnetic Particle, Radiography, Ultrasonics, eddy Current, Acoustic Emission and Thermography. In addition, many non-destructive inspections can be performed by a precision scale, or when in motion, a checkweigher.
A surprise inspection tends to have different results than an announced inspection. Leaders seeking to discover how well lower echelons in their organization are typically doing sometimes drop in unannounced to see what is going on and what conditions are. When an inspection is scheduled in advance, it gives people a chance to cover up or fix mistakes. A surprise inspection, therefore, gives inspectors a better picture of the typical state of the inspected object than an announced inspection.
A walkthrough is a term describing the consideration of a process at an abstract level.
The term is often employed in the software industry (see software walkthrough) to describe the process of inspecting algorithms and source code by following paths through the algorithms or code as determined by input conditions and choices made along the way. The purpose of such code walkthroughs is generally to provide assurance of the fitness for purpose of the algorithm or code; and occasionally to assess the competence or output of an individual or team.
The term is employed in the theatrical and entertainment industry to describe a rehearsal where the major issues of choreography and interaction are practiced and resolved, prior to more formal "dress rehearsals".
The term is often used in the world of learning where a tutor/trainer will walk through the process for the first time. It is regarded as a literal walk through of the learning at the groups pace ensuring that everyone takes in the new knowledge and skills.
Something akin to walkthroughs are used in very many forms of human endeavour since the process is a thought experiment that seeks to determine the likely outcome(s) of an affair based on starting conditions and the effects of decisions taken.
|Is This Answer Correct ?||1 Yes||4 No|
What's the difference between Stress testing & Load testing
Explain Alpha Testing and Beta Testing
What r the different FUNCTIONAL testing techniques?
what is the difference b/w test scenario and test case? pls explain with one example the preparation of both? thanks in advance ................
What did your base your test cases?
What is difference between web based testing and windows based testing ?
functional testing and usability testing test cases for transfer funds...
What is good code?
What is integration testing?
How to test the functional specification?
I have 3 years of experience as a software manual tester. What can i study further for a career growth. Please advice if there is anything apart from automation testing
WHAT IS THE ANSWER FOR THE QUESTION "WHAT ARE YOUR ACHIEVEMENTS IN YOUR PREVIOUS COMAPANY"