Interview Questions for Manual Testing

Questions on Bug Life cycle
  1. What is a bug? What types of bugs do you know?
            Bug is a error during execution of the program. There are two types of bugs: syntax and logical 
2 What bug tracking system did you use?
            Again and again, it does not matter what bug tracking system you use if you made your homework and invented the name of such or mentioned a standard one. You may say you've used proprietary bug tracking system (works especially well if you previous company was this way or another dealing with databases) or you may say Test Director, Clarify, ClearCase, VisualTest, Bugzilla, QC etc
3.      What should be done after a bug is found?

The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. A variety of commercial problem-tracking/management software tools are available
The following are items to consider in the tracking process:

Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary.
·         Bug identifier (number, ID, etc.)
·         Current bug status (e.g., 'Released for Retest', 'New', etc.)
·         The application name or identifier and version
·         The function, module, feature, object, screen, etc. where the bug occurred
·         Environment specifics, system, platform, relevant hardware specifics
·         Test case name/number/identifier
·         One-line bug description
·         Full bug description
·         Description of steps needed to reproduce the bug if not covered by a test case or if the developer doesn't have easy access to the test case/test script/test tool
·         Names and/or descriptions of file/data/messages/etc. used in test
·         File excerpts/error messages/log file excerpts/screen shots/test tool logs that would be helpful in finding the cause of the problem
·         Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common)
·         Was the bug reproducible?
·         Tester name
·         Test date
·         Bug reporting date
·         Name of developer/group/organization the problem is assigned to
·         Description of problem cause
·         Description of fix
·         Code section/file/module/class/method that was fixed
·         Date of fix
·         Application version that contains the fix
·         Tester responsible for retest
·         Retest date
·         Retest results
·         Regression testing requirements
·         Tester responsible for regression tests
·         Regression testing results 

A reporting or tracking process should enable notification of appropriate personnel at various stages. For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers

4.      What if the software is so buggy it can't be tested at all?

             In this situation the best way is to have test engineers go through the process of reporting whatever bugs or problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules and indicates deeper problems in the software development process, such as insufficient unit testing, insufficient integration testing, poor design, improper build or release procedures, managers should be notified and provided with some documentation as evidence of the problem.

5.      If a bug has high severity then usually that is treated as high priority,then why do priority given by test engineers/project managers and severity given by testers?
            High severity bugs affects the end users ....testers tests an application with the users point of view, hence it is given as high severity. High priority is given to the bugs which affects the production. Project managers assign a high priority based on production point of view.
6.      what is meant by Priority and severity?
Priority means "Importance of the defect w.r.t  customer requirement"
 This is assigned by the Developer.
 This is to say how soon the bug as to be fixed in the main code, so that it pass the basic requirement.
Severity means "Seriousness of the defect w.r.t functionality"
 This is assigned by the Test Engineer
This is to say how badly it is affecting the other modules of the build or release.
7.      When a bug is found what is the 1st action?
               Report it in bug tracking tool.
8.      What is best bug in your current proj? Which you found??
               It’s your project. You should know it
9.      What is the bug base do you use in your comp.?
               The interviewer was asking about Bug tracking tool that you use...
10.  Give an example of high priority and low severity, low priority and high severity?
               In user interface bugs we are giving low severity
Ex: 1) Improper right alignments (low priority)
    2) Spelling mistakes (high priority)
In calculation bug we are giving high severity
Ex: 1) final output is wrong (low priority)
    2) Dependent outputs are wrong (high priority)
11.  Daily how many bugs will you find and what types are they?
The Bugs I find in a Day could be User Interface defect Bug, boundary related, Database Related,
Error Handling defect, calculation defect Load conditions, hardware failures, Compatibility related.
12.  What are the differences between these three words Error, Defect and Bug?
Error: The deviation from the required logic, syntax or standards/ethics is called as error.
There are three types of error. They are:
Syntax error (This is due to deviation from the syntax of the language what supposed to follow). 
Logical error (This is due to deviation from the logic of the program what supposed to follow) 
Execution error (This is generally happens when you are executing the same program, that time you
 get it.) 
Defect: When an error found by the test engineer (testing department) then it is called defect
Bug: if the defect is agreed by the developer then it converts into bug, which has to fix by the developer or post point to next version.
13.  If the client identified some bugs to whom did he reported?
He will report to the Project Manager. Project Manager will arrange a meeting with all the leads 
(Dev. Manager, Test Lead and Requirement Manager) then raise a Change Request and then, 
identify which all the screens are going to be impacted by the bug. They will take the code and 
correct it and send it to the Testing Team.

14.  What are the main bugs which were identified by you and in that how many are considered
 as real bugs?
If you take one screen, let’s say, it has got 50 Test conditions, out of which, I have identified 5 defects
 which are failed.
 I should give the description defect, severity and defect classification. All the defects will be 
Defect Classification are:
GRP       :              Graphical Representation
LOG       :              Logical Error
DSN       :              Design Error
STD        :              Standard Error
TST         :              Wrong Test case
TYP        :              Typographical Error (Cosmotic Error)

15.  Define Defect Life Cycle
Defect life cycle includes reporting a new bug to closing a bug. It has below stages:

About Bugzilla
What is Bugzilla?
Bugzilla is a bug tracking tool or issue tracking tool.
What is the use of Bugzilla?
Bugzilla is a centralized location to keep all the bugs. More than none person can access and see the bugs. And it will give the entire change history such who as reported to whom, who has changed the status etc.
How do enter a bug in Bugzilla?
To enter a bug, through "Enter a new bug" link from the main Bugzilla page. This will take you to a product selection screen.
What happens once enter a bug?
After you enter a bug, mail is sent both to you and the QA department. A member of the QA department will verify that they can reproduce your bug.
How do search a bug?
To search a bug, through "Query" link from the main Bugzilla page.
How do submit aattachement?
The new Bugzilla system supports the attachment of patches, test cases, and various other forms of file types directly from the bug report screen. Just click on "Create an attachment"
Are cookies required in Bugzilla?
How can you view your assigned bugs?
We can view the assigned bugs though “My Bugs” link.
How can you generate bug report?
We can generate bug report through “Report” link.
When Bugzilla was released?
Bugzilla was released in 1998.
Which language was written Bugzilla first time?
Bugzilla was originally written in "TCL".
Who developed the Bugzilla?
Terry Weissman
Which language Bugzilla written?
What are the Bugzilla fields?
Bugzilla have 11 fields. They are Product, Component, Version, Platform, OS, Priority, Severity, Assigned To, URL, Summary and Description.
How can you edit your account in Bugzilla?
We can use "User Preferences" link.
How can you add new Product in Bugzilla?
We can use "Product" link for adding new product.
How can you add Components of product in Bugzilla?
We can use "Components" link for adding components in Bugzilla.
How can edit version of any product in Bugzilla?
We can use "Edit Versions" link.