Basic Questions asked in any Software Testing Interview June 3, 2008
Posted by kiranjoglekar in : General Interview Questions , trackback1. What is Testing?
Testing is a process of finding the bugs or defects in the software,
reporting it & making sure that the bugs are fixed by the development.
Once the development fixes the reported bugs, again Testing team is
responsible to verfiy the fixes & making sure that the new fix has not
broken any previously working functionality of the product.
2. What is a Defect or a Bug?
A defect or a bug is a mistake in the software considering the details
mentioned in the specification document. So if some feature or
functionality of a Software is varying from what it is supposed to be
with regard to its expectations mentioned in the Specification
documents then it is considered as a bug or a Defect.
3. What will you do when you find a Defect in the product that
you are Testing ?
Generally when we find a bug or defect we report it following the bug
logging process or Defect Reporting. But it is also the job of a
Testing Engineer to make sure it is a real product bug & not any setup
or testcase issue before filing a Defect Report or Bug Logging.
4. How do you log a bug & what software you use for this
process?
We use Bugzilla which is an opensource software for logging bug. While
logging a bug we need to give detailed information about the whole
steps when we encountered a bug or defect.
5. Describe in detail what you should do after Finding the Bug?
Write the bug report just when you are sure that you have found a bug,
not after the end of test or at the end of the day. It might be
possible that you might miss out on many crucial points if you are
delaying the write up for bug filing. Put necessary time to diagnose
the defect you are reporting. Think of the possible causes. You might
land up uncovering more defects if there are any. Mention your
discoveries in your bug report. The programmers will only be happy
seeing that you have made their job easier. Take some time off before
reading your bug report. You might feel like re-writing it.
6. What are the factors you consider while writing Defect
Summary or Bug Synopsis ?
The summary of the bug report is the readers first glance with your
bug report. The fate of your bug heavily depends on how well you
compress yet describe the summary of your bug report. The rule is
that every bug should have a one line summary some reporting
softwares call it as Bug Synopsis. A good summary will not be more
than 50 to 60 characters.
Keep reading for more common Testing Questions & Their Answers.
Comments»
no comments yet - be the first?