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 |
black box techniques
1. After completing testing , what whoulds you deliver to the client ?
What is 'Account Conditioning'?
What is pesticide paradox? How to overcome it?
How can I use bugzilla in my company to track a bug and to allow the client to see the bug report online throughbugzilla. Please explain in detail. I am really need this.
A defect which could have been removed during the initial stage is removed in a later stage. How does this affect cost?
can anyone give FULL DETAILS on ATM scenarios, test cases and test cases PURPOSES
how to excute testcases in regression testing time.
what is functional testing terminologies
how do you ensure by testing that the transactional refuilement or an application are met
There is only requirements document. You have 10 days and 8 resources to release the system.At the end of the 8th day u tell ur TL that system is ready for release. How will you proceed with the testing process or in other words what all approach you will follow once you get requirements
What is adhoc testing?when it can be done?