what is walkthrough?
Answers were Sorted based on User's Feedback
Answer / rama
Hi some body has written wrong walkthroughs are informal
reviews. In walkthroughs everybody will partcipate
testers,developers and technical writers.walkthrough will
conduct when ever necessary.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / ramprasad.s
Hi
review without preparations
everyday morning module lead speak with us for 5 to
10 minutes is walkthrough
sun_ramprasad@yahoo.com
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / mona
A: A walkthrough is an informal meeting for evaluation or
informational purposes. A walkthrough is also a process at
an abstract level. It’s the process of inspecting software
code by following paths through the code (as determined by
input conditions and choices made along the way). The
purpose of code walkthroughs is to ensure the code fits the
purpose. Walkthroughs also offer opportunities to assess an
individual’s or team’s competency.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / ram.polavarapu
reviews are going to conducted by the project manager
(or)team lead,read the documents and explain to the team members
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / mani
an informal meeting for evaluation or informational purposes
| Is This Answer Correct ? | 0 Yes | 0 No |
how can u differentiate intgration test cases with functional test cases
If anybody from banglore having the real time exp in manual testing with 3+ yrs exp and looking for change send your profile to vinodhanandhan@gmail.com
What exactly are semi-random test cases?
Give me some sertification courses in testing?
2.what are the various test appraoches that you are familier?
What is Defect Acceptance ?
Explain Boudary value testing and equivalence testing ?
What is the Difference between 2 tier and 3 tier Applications...Actually what is a tier.. Anybody can body can give accurate answer..Thanks in advance..........
What testing roles are standard on most testing projects? Categories: Software Testing
at what step sanity testing and smoke testing do?
If Tester found the bug in build 2.0.0 tester will assign it to developer but not get fixed in next build 2.0.1 then tester have to assign it again for every build if not get fixed upto build 2.0.7 or not? Same question is for version also?
how would one evaluate test effectiveness? if at all it is possible what type of metrics will be used to calculate effectiveness.