Real Time Manual Software Testing +Agile for beginners With Interview Question

Manual testing is the process of manually testing software for defects.Testing Method:  It follows two methods to validate an application. They are 1. Manual testing and 2. Automation testing.

Important of Testing:

In china A300 airbus crashed due to software bug - Apr 26 1994. Software bug can cause major problem. QA tester saves money , time.

Testing Method:  It follows two methods to validate an application. They are

1. Manual testing and
2. Automation testing.

Manual Testing:

In this scenario while performing operation on Application, QA engineer verify actual behavior of the system with respect to given expected results in test case documents.

Test case document: It is a document with user action and its expected result.

Example: Gmail login:

user action	expected	actual	status
username, password, sign in	inbox	inbox	pass/fail

Automation testing:

Automation testing performed using programming language, scripting language or third party tools like QTP. It is very fast.

Skill for Testers:

• Manual Testing concepts
• Any one of the Functional Automation tools
• Any one of the DEFECT REPORTING tools -HP-Quality Center/HP-ALM , JIRA, Visual task.
• Database Knowledge - SQL, Teradata, DB-2, MS-Access
• Domain Knowledge

               Example: Banking/Insurance/Finance/Healthcare/Retail/Telecom

Testing Methods

                     White Box Testing

                     Black Box Testing

                     Gray Box Testing

Testing Levels in SDLC ( Software Development Life Cycle)

                      UNIT Testing

                      Integrated Testing

                      System Testing

                      User Acceptance Testing

Testing Techniques

                   Adhoc Testing

                   Explanatory Testing

                   Re-Testing

                   Regression Testing

What is Testing

Validating An application is called Testing

Why to validate an Application?

To ensure that there are no Bugs in Application and Software/project/product Developed as per requirements.

• Software Testing Life Cycle (STLC)
   About Testing Plan document
                   Test Case Preparation
                   Test Case template
                   Tractability Matrix
                   Test Execution

What is a Bug:

A Error in programming /Fault/ Undefined coding which leads to /malfunction of An application Or Application which fails to give expected out put is nothing but its effected with a bug

What is bug?

Its nothing but a error in software coding

Manual Testing:

In This scenario while performing operation on Application,  Test engineer verify Actual Behavior of the system with Respect to Given Expected Results in Test case document.

Where As Automation Is Optional But Manual Testing will Be Performed On Very Application.

  Automation Testing:

Automating human Activates In order to Validate The Application. Automation Testing can be performed Using Programming Language, scripting language, or any other Third party tools like QTP. Rational Robot (IBM TOOL). QTP is an HP TOOL widely  used Automation TESTING Tool.

Roles and Responsibilities of Test Engineer:

1. Analyze the client Requirement BRS, FRS

2. Major test condition

3. Test case - test scritps (automation)

4. Execution

5. Bug Report to the development

6. Close

I) Analyze Application functionality using Requirement Documents Like BRS (Business Requirement Specification ),FRS (Functional Requirement Specifications)

II) Identifying Test Scenarios for allocated module: Test scenarios Describes A test condition

Lets Take Example of Facebook Home page to  Identify the Test Scenarios . Identify Test Scenarios For Gmail Home Page

Identify Test Scenarios For Facebook Home Page

.............................................

TS01:Login Validation

TS02:Cant access your account

TS30:Create Account

III) Preparing Test Cases For Manual Testing

What is Test case?

Test Case is a set of steps/sequence of steps with user action and subsequent response of the system .Test Cases are generally Derived from test scenarios.

Ex: Prepare Test case For gmail Login validation

IV) Creating automation Test scripts Note: If Possible

v) Executing Test Case and/or Automation Test Script Note: When Expected Result And Actual Result Are the Same then STATUS Will be Passed

Or Simply Test case is passed

VI) Defect Reporting

Defect reporting;

When Expected result And Actual Result not identical then that test cases said to be FAILED .This failed Test case will be Analyzed by test eng and Then it is forwarded to concern department to fix the problem

VII) Participation in RETESTING AND REGRESSION Testing Note: Topic ON RETESTING and REGRESSION Will be conducted in upcoming classes

The process is summarized as:

Analyze Application functionality using Requirement Documents Like FRS & BRS.

Identifying Test Scenarios.

Preparing Test Cases For Manual Testing.

Creating automation Test scripts.

Executing Test Case and/or Automation Test Script.

Defect Reporting.

Participation in RETESTING AND REGRESSION

SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

What is Software?

Set of instructions programs documented to perform particular task.

Software can be categorized in to TWO Types

• System Software
• Application Software

SYSTEM SOFTWARE: This S/W Provides interface to the System Components Like (Booting). System S/W also called as BIOS (basic i/p o/p system). Example: ALL Operating systems ,Windows, unix.

Application Software: Software which performs  Operations or functionalities. Based on Use inputs is called Application software. Generally application software developed based on User business needs. Ex: Msoffice ,QTP, Online Banking s/w, etc

Application Software divided into Two Types: (1.) Produced based, (2.)Project based.

1. Product Based: Developed Based on STANDARD Requirements. This product is developed For all worldwide Users and Who are related to specific product can buy this software from the product development company. Example: QTP, Team viewer , etc
2. Project Bases: Its Developed Based on Specific Client Requirement . After Developing this application it will be delivered to the client. Ex: Banking software, insurance, etc.

What is SDLC?

It is the process of developing software Product/Project to fulfill the client Requirement with in the specific cost and time.

In general it is also know as A method which is adopted by the organisation  to develop the Application with in the budget and time range

Its not mandatory the every organization/project/product should fallow same type of method, it depend on the type of company/project/product 

Phases of SDLC:

-----------------

REQUIRMENT COLLECTION --> BA collects requirement. use BRS. Eg. Bank to bank transfer money.

REQUIRMENT ANALYSIS --> SA, fuctionality of requirement, how it work, Use SRS. Eg. B2B transfer money needs user name, password, login,confirmation, trasation id

DESIGNING

CODING/IMPLEMENTING

TESTING

RELEASE & MAINTENANCE

PHASE I

REQUIRMENT COLLECTION

Business Analyst Collect requirements with interaction of client. BA collect requirement from client.

The collected Information will be Documented as

           BRS (Business Requirement Specification )

Or

             URS (User Requirement Specification)

Or

             CRS (Customer Requirement Specification )

           

 ....................sample of BRS........................

E-Banking

Business Requirements Specifications v1.0

Document Name	Version Number	Start Date	Prepared By	Reviewed By	Modified Date	Present Status
BRS-Bank/Rel1.0	1.0	mm/dd/yy	xxxx	xxxxx	mm/dd/yy	Completed

Introduction:

  Bank UK is a full service bank offering retail and corporate and investment banking services in the UK and Europe. The Bank delivers its products and services through five branches located in the UK and one branch in Antwerp, Belgium as well as through Internet and telephone banking. The Bank was incorporated in England and Wales on 11 February 2003 as a private company with the name   Bank UK Ltd. and on 30 October 2006 converted to being a public limited company. The Bank's registered office is 21 Knightsbridge, London SW1X 7LY. The Bank is regulated by the Financial Services Authority (the FSA) and is a member of the Financial Services Compensation Scheme established under the Financial Services and Markets Act 2000. The Bank has a long-term foreign currency credit rating of Baa1 from Moody's, which is one notch higher than the UK sovereign rating.

About   Bank

As at 30 September 2006, the Parent is UK's largest bank in the private sector with total consolidated assets of approximately US$ 61.5 billion and is the second largest company in UK including all public and private enterprises. The Parent and its subsidiaries offer not only comprehensive banking services in UK, but also life insurance, general insurance, asset management, investment banking and private equity/venture capital. The Parent has a presence, through its subsidiaries, branches and representative offices, in 16 countries in North America, the UK and Continental Europe, the Middle East, South Africa, South Asia and Hong Kong. In 2000, the Parent was the first UK banking company and the second bank from Asia to list on the New York Stock Exchange and currently has a financial strength rating of C- from Moody's Investors Service Limited (Moody's) and a long-term foreign currency credit rating of Baa2 from Moody's and BB+ from Standard & Poor's.

  Bank is UK's foremost technology bank and has pioneered Internet banking in UK.

KeyMouze Systems will design and develop the following key business modules:

  Bank is a web based and offers a full service such as personal, corporate and International Banking Services in the UK and Europe. The Bank delivers its products and services through five branches located in the UK and one branch in Antwerp, Belgium as well as through Internet.

The system would involve the following modules Admin, Banker, Personal, Corporate and International Banking Services But as part of the first release we would only concentrate on the following features.

Admin Tasks, Banker Tasks and Customer Tasks for personal banking. 

Admin

Admin Tasks:

This module allows admin to define and manage master data such as Branches, Roles, Users and Employee of the   Bank.

1.0 Branches:

Branches Feature allows admin to define a new branch for   Bank and also he can modify or delete any   Bank branches.

2.0 Roles

Roles feature allows admin to define a new role for   Bank and also he can modify or delete any   Bank roles.

3.0 Users:

Users feature allows admin to define a new user for any   Bank customers. He can modify or delete any user information.

4.0 Employees:

Employees feature allows admin to define a new employee basic information for any   Bank branch. He can modify or delete any employee information.

Banker

Banker’s Tasks

This module allows bankers to define and manage customers of his branch and also he can book receipts and payments.

5.0 Customers Registration

Customers feature allows him to define a new customer for his branch by filling registration form and sending it for the admin approval, and also he can modify or delete or view any customer information.

6.0 Receipts

Receipts feature allows him to book different kind of deposits from a customer such as cash deposits, cheque deposits, DD deposits and credit card payments etc.,

7.0 Payments

Payment feature allows him to book different payments made to customers such as Cash withdrawal, Cash withdrawal through cheques etc.

Customer

Personal Banking Customers Tasks

This Module allows the registered users to perform various activities such as Accounts Summary, Money Transfer, Smart Money Order, Online bill payments and Online request for cheque book etc.,

For present release only the mentioned key features only be constructed and the remaining features would be included in the upcoming releases.

8.0 Accounts Summary:

This feature should enable the user to generate their account summary reports, generating mini statements and detailed account statement for the specified period.

9.0 Money Transfer:

With  , Transferring funds from your   Bank Account is very simple. There are various options provided online for transferring funds.

With Funds Transfer on   Bank, you can

Forget about writing out & sending cheques/ DD's or pay orders to the payee.

Free yourself from the worry of payment instruments getting lost/misplaced in transit.

Transact from the comfort of your home or office through   Bank Internet Banking.

Transfer money to any   Bank account, anywhere in UK.

Transfer money to specified non-  Bank Accounts in over 100 cities across UK.

ECheques facility on  Bank.com is absolutely free of charge.

10.0 Smart Money Order:

Smart Money Order is a unique service that allows you to send a money order anytime and to any destination in UK.

Sending a Smart Money Order is very simple. Just login to  IBank.com and give the address of the person (receiver) and amount of money to be sent. You can then sit back & relax while your near & dear ones receive money conveniently at their door-step.

11.0 Bills Pay

  Bank has tied up with major organizations across the country to facilitate payment of bills for Utility Companies (Electricity and Telephone) Bills,   Bank credit card, Mobile Phone and Insurance Premium bills.

To pay your bills, all you need to do is complete a simple one time registration for each biller. You can also set up standing instructions online to pay your recurring bills, automatically.

12.0 Request for Cheque Book:

Thisfeature allows the valid user to place an online checkbook request.

High Level Business Requirements:

• Access banking, 24 hours a day, 7 days a week from anywhere in the world;
• View balances of accounts and transaction history;
• Transfer funds between own accounts;
• Transfer funds to any other bank account
• Ability to pay utility bills
• Printout and export transaction history to own computer;
• Request overseas payments (telegraphic transfers);
• Send and receive messages to and from the Bank;

Security features which allow businesses to designate initiator users and authoriser users.

....................................................................................................................................................................... 

SDLC PROCESS:

PHASE I  : REQUIRMENT COLLECTION

Business Analyst Collect requirements with interaction of client.The collected Information will be Documented as

            BRS (Business Requirement Specification )

Or         URS (User Requirement Specification)

OR        CRS (Customer Requirement Specification ) 

BRS is the First document prepared in SDLC Phase .This document will be quoted with Brief description of client business needs Like USERS, TYPE OF USERS, User Permissions, SERVICES. After preparation of BRS  doc Business Analyst will do/make Feasibility Study in Order to check whether project is Acceptable. If Project is Accepted Business Analyst will provide Intimation to client and Agreement will be made 

SLA (Service Level Agreement)

Basically SLA will be made between Company And Client.

PHASE II : REQUIRMENT ANALYSIS

In this Phase System Analyst will Study the BRS doc. And System Analyst  will prepare a detailed Functionality doc based on BRS. And the that document is Called as FRS.

FRS (Functional Requirement Specification ) Where as FRS document play a very important role in software development process. Its know that

A Good FRS document =Good project

FRS document contains all the specifications and  Functionalities of project

Lets have a look on Banking Project FRS document

PHASE III : DESIGNING

In this phase Design Architect will plan the programming language, scripting language ,Database Technology based on client Business needs/requirements

In this phase fallowing doc will prepare:

• GUI (Graphic User Interface) doc
• DB (Database ) doc
• Application Design doc

GUI: It describes application look and feel with dummy screens. This can be called “Prototype”.

DATABASE DESIGN: This document describes about database structure set of tables and rules implemented in database  

Application Design document :IT describes about application functionality with the help of HLD (High level document), LLD (Low level document )

PHASE IV : CODING/IMPLEMANTING

In this phase developers or programmers will write the programs. Based on designing documents to develop application. For windows based application developers use . Programming language like C#,C++,JAVA,.NET Visual Basics Etc .For web based generally they use scripting language like Asp.net, Php, Pearl,java scripting Etc,. Developer test code by White box testing.

PHASE V : TESTING

After Coding programs, Applications Available for Dynamic Testing. Initial Stage of testing performed by developers like Unit Testing/ Component Testing, Integration Testing by Using

(WBT) White Box Testing   - performed by Developer- testing source code

After unit and integration testing Application given to separate testing team where they validate Application using (system testing).

BBT (Black Box Testing): No need programming language. Participate tester.

After BBT we conduct UAT (User Acceptance test) to Know the client satisfaction . UAT - aplha testing -  completly control environment. Beta version- uncontrolled environment

PHASE VI : RELEASE AND MAINTENANCE

RELEASE

After System Testing And UAT, We deliver product to the Client. ITS also called as GO-LIVE And  changes can be made further upon request of Client is called maintenance NOTE: If Application No longer in use then it’s the end of SDLC.

SDLC CASE STUDY:

SDLC  MODEL:

Depending on complexity of functionality and need of client. We can use/adopt any one of the fallowing SDLC model.To develop application WATER FALL MODEL, ITERATIVE/ INCREMENTAL MODEL, PROTO TYPE MODEL, SPIRAL MODEL, RAD MODEL, V-MODEL, AGILE MODEL (scrum) .

WATERFALL MODEL:

This model is preferable for small Application, clear requirements and routine projects.

WATE FALL MODEL:

It contains All the SDLC phases Application developed in a linear Sequence  Water fall model

DISADVANTAGES:

There is no feed back between the phases. During Development process it wont allow any dynamic changes

ITERATIVE/INCREMENTAL MODEL

This model is preferred for big project and when requirements are not clear  In this model application develop in terms of increments (Modules).

V-MODEL (Excellent)

V stands for verification and validation . In general Organization prefer V-Model to develop the Application. Is the most proven model in SDLC.

In v-model Testing Activates starts parallel with the development activates and also they give same waitage for testing activates with respect to development

Disadvantage: it cant handle Dynamic changes

V MODEL: V Strands for Verification document and validation the application.

HLD /LLD = high level document and low level document.

WBT/BBT/UAT = white box testing and black box testing/ User Acceptance testing

BRS documents verify on UAT. FRS verify on BBT.

Verification: It's the process to check the correctness and complete necessary of the documents which prepared to develop the project

Verification is a Static testing: In general Verification Performed on documents like BRS, FRS, Design doc, test plan doc, Test Case etc

Verification techniques

• Peer Review
• Walk Through
• Inspections

Validation: After coding programs are available to execute, while executing we validate the applications to know whether its giving expected o/p or not. Validation is a Dynamic test approach. where as verification is a static approach.

For validation we use fallowing testing techniques

• Unit Testing - done by develper
• Integrated Testing - done by developer
• Functional Testing - application behavior
• Performance Testing
• Security Testing

AGILE METHODOLOGY:

i) customer satisfaction , ii) welcome changing requirements, iii) Deliver working software frequently, iv) work together, v) trust support, vi) face to face conversation, vii) working software, viii) sustainable development, ix) technical excellence, x) simplicity, xi) self-organization teams, xii) adjusts

Scrum  Model Overview:

Quality Management:

Quality management: Is a process of preventing the defects during development process and ensure there are no defects in final project

Quality management will have two teams: Quality control (QC), Quality Assurance (QA)

Quality Assurance:It’s a defect preventive Approach where they define, monitor and measure the strength of development process, QA team involves throughout life cycle

Quality Control: Qc team comes in to act only when project is built, Qc identifies the defects and make sure these defects has to be resolved before delivering the application to the Clint

• Exhaustive testing  - possible test
• Optimal testing  -

This methodologies are used to  derive best possible test cases in order to validate application

Testing methods

WBT (White Box Testing) - developer optimize the source code

BBT (Black Box Testing) - tester use for optimize test

GBT (Gray Box Testing)

Testing Methodologies:

Integration testing levels:

• Low level Integration testing
• High level integration testing 

1. Statement Coverage
2. loop Coverage
3. Path and Brach coverage
4. Boundary value analysis
5. Equivalence Class partition
6. Error Guessing

WBT: WBT techniques are used to validate source code of application In general its performed by developer

WBT Techniques:

1. Statement Coverage
2. loop Coverage
3. Path and Brach coverage

BBT: Without having and programming knowledge validating application functionality based on client requirement is called BBT. Using fallowing BBT techniques test eng derive test cases.

1. Boundary value analysis
2. Equivalence Class partition
3. Error Guessing

Testing Levels:

• Requirement Review
•    Design Review
•    Unit Testing - developer
•    Integration Testing - developer
•    System Testing - tester
•    User Acceptance Test

Developer develops the code as unit and test code as a source code test as a unit testing. and each unit combine with each other and test by developer as a integration testing.

Requirement review:  After preparation of FRS doc to check the correctness and completeness of documents we conduct reviews

Design Review: Design documents will be reviewed in this phase. Note: Requirement review and design review are static testing where they use verification techniques 

Unit Testing: It is also called as Component testing ,Testing on individual components is called unit testing,It is performed by the developers using WBT.

Integration Testing:  After unit testing in order to form the system we collect those components and verify inter phase between these components is called integration testing

Based on availability of components or modules we use fallowing approaches

• BIGBANG - wait until all the modules developed
• Incremental  -

Incremental

In this model we use temporary programs like Stubs & Drivers

In incremental approach we use fallowing techniques based on availability of modules

     i) TOP-DOWN

     ii) BOTTOM- UP

     iii) HYBRID/SANDWICH

Top down: we use STUB when sub-module is unavailable /under construction

Bottom up: We use Driver When main module is not Available/under construction

Integration testing levels:

• Low level integration testing (unit)
• High level integration testing(System)

System Testing: validating Application based on user / client Requirement and Expectation is called system testing

Generally in System testing we Validate two factors

• FUNCTIONAL TESTING
• NON FUNCTIONAL TESTING 

Functional Testing: functional testing is also called as Requirement testing

Functional factors can be validate manually or using functional Automation tools like

QTP             (Hp tool)

Winrunner     (Hp tool)

Silk                (Borland)

Rational robot (IBM)

Fallowing Factors are validated in Function testing

• Object Properties
• Error- Handling
• Input-Domain BVA/ECP
• Calculation
• Data Base**
• Links

Input Domain Coverage: Verify input objects with respect client expected data For input properties we use BBT Like

• Boundary value Analysis (BVA)
•  Equivalence Class partition (ECP)

Boundary value Analysis: This technique is used when there is a input in terms of range or size

BVA says there will be three possible conditions at each level to validate

where BVA input in range or size & in and around boundry

age : 18--80

min range 18

max range: 80

They are

               Minimum ===============valid

               Minimum -1==============Invalid

               Minimum +1==============Valid

               Maximum================valid

               Maximum -1==============valid

               Maximum +1==============Invalid

testdata

valid              invalid

18                        17

19                        81

80

79

......................................................next expample.......

Boundary value Analysis

bva

--------

where

input in range or size

in and around boundry

age : 18--80

min range 18

max rane 80

------------------------------------------------

min-------------18-------valid

min-1-----------17-------invalid

min+1-----------19-------valid[opt]

max------------80-------valid

max-1----------79-------valid[opt]

max+1----------81------invalid

------------------------------------------------------

testdata

valid invalid

18 17

19 79

80

79

------------------------------------------------------------

name edit box:

4 to 8char

min 4

max 8

-----------------------------

bva

min----4----valid

min-1--3-----invalid

min+1--5-----valid

max----8------valid

max-1--7------valid

max+1--9-----invalid

testdata

valid invalid

abc2 abc

kiran abcabc123

kiran123

kiran00

-------------------------------------------

mobile:

should be 10 dig

it shd sart with 9

min max

9000000000 9999999999

Equivalence class partitioning:

driving test data:

1. Alphanumeric only

2. Start with alphabet

3. Min of 6 Chars

4. Max of 40 Chars

bva ecp

--------

min---------6---valid

min-1-------5----invalid

min+-------7------valid

max--------40 valid

max-1------39 valid

max+1------41 invalid

bva ecp

valid invalid valid invalid

6 5 0-9 not starting with aplha

7 41 a-z spl char

40

39 start with alpha

* valid bva+valid ecp

*invalid bva+valid ecp

*valid bva+ invalid ecp

invalid bva+ invalid ecp

testdata

valid invalid

acvf12 akih2

kiran12 mnb@#$

kiran12345kumar12345kiran12345kumar12345 1bvgbnh [op]

kiran12345kumar12345kiran12345kumar1234 @cvcfvcfcvc@#$%nb125@cvcfvcfcvc@#$%nb1251

Functional testing directly deals with application behavior, user action.

Non Functional testing : Its also called as expectation testing Non functional testing techniques  

• GUI Testing - testing looking features, color,font
• Usability testing - user friendly testing
• Performance testing(istqb) - application load, stress, data volume testing
• Security testing - Authorization. access control, cookies, session id.
• Recovery testing
• Compatibility testing
• Configuration testing (h/w compatibility)
• Installation testing
• sanitation testing
• Competitive
  Different types of testing approach
• Sanity Test/smoke testing -application stable
• Ad-hoc testing (Informal) - No proper procedure
• L10N Testing - localization (support local language)
• i18N Testing - in-formalization
  Retesting and Regression:
• Retesting -
• Regression Testing -
  Software Life cycle:
• Test initiation
• Test planning
• Test design/test case design
• Test execution
• Defect reporting
• Test closure

Test Scenario:

High level of condition, it is easier tor write test cases.

Test case design:

writing test case:

A document with sequence of steps with user action and expected result.

Where: 

• Excel sheet,
• Quality center/ALM

..................

+ve     -ve

valid     invalid

Test Case: Example of Banking

Example of test case:

Example of test case:

Example of test case:

Gmail Test Case example:

Example test case: generating test data, BVA, ECP

invalid test data: it is combination of one valid and another invalid data ( see BVA,ECP)

How many ways test case can write:

1. testing with valid data
2. with invalid data
3. test reset
4. test mandatory field

Test cases is written below excel sheet:

Some test data from above scenario: -this is a one way to write test case dynamic. we are writting test case in one excel sheet and test case is another excel sheet. this is test data

Test cases with valid data:

Test case with invalid data:

Test case 3 with rest (few test data) and test case 4 mandatory field

Example of Test case of Banking:

another way of writting test case dyanamic: one is test data and other is test case.

Test number: number_projectname_module_submodule_functionality

Expected result: always use should

Actual result: had + v3

writing banking test cases from FRS ( by looking Flow diagram and use cases)

writing banking test cases from FRS ( by looking Flow diagram and use cases)

Flow diagram

Use cases:

..................................Lets start Test cases writing by using Banking FRS........................................................

FRS:

branches:

for invalid data:

Test cases: and test data are in separate excel sheet

test data with valid data

test cases with valid data

Mandatory does not need all data valid and invalid data. Only one valid test data is good for one field.

Alternative way of writing test cases in above scenario:

Introduction of Bug:

Bug can reports by using different reporting tools such as excel sheet, HP-QC Bugzilla, JIRA, Visual task board

Bug Reporting / Bug Life cycle

Severity - represents affect of bug. Its a impact of bug in application. eg. login fail. application has High severity

Priority - How fast your bug is defect time. Important of bug. eg. login fail- High priority

Example:.

1. logo is not display. Severity-low, priority-high. ( doesn't effect any functionality)

2. login fail application. Severity -High Priority -High
3. In application login, developer design logout instead of login button. but when user click on logout, its login the application. Severity- low , Priority - High ( UI errors, functionality is working)

Bug reporting:

use different tools: Excel, Bugzilla, Jira, HP -QC

Bug Life cycle:

New bug --> report to LEAD --> Analysis --> forward --> Development department --> Analysis --Accept/ Reject / Deferred --> Accept --> Assigned to Developer --> Fix --> Retesting and Regression --> Close --if there is still bug--> Reopen

Defect life cycle:

Defect reporting Tool BUGZILLA

File a bug in Bugzilla

Description:

• Steps to reproduce:
• step 1:
• step 2:
• Expected :
• Actually:
• and add a screenshot.

QA QUESTION for INTERVIEW

FAQ’s on Manual Testing

1. What is software testing?

 Testing is the process of evaluating a system or system component by manual or automated means to verify that it satisfies specified requirements”.

2. Importance of software testing?

 To deliver a bug free application to the customer (Error free superior product)

 To deliver more reliable S/w to customer (Quality Assurance to the client)

 To reduce the maintenance cost to customer

 Early finding defects which helps to reduce cost to fix those defects (cut-down cost)

 When defects are removed quality improves.

3. Why do we need specialist tester?

 Developers will not do systematic and complete testing.

 A developer assumes few things to be working fine as they are owners of the work.

4. What is software Quality?

 Quality from the customer view point is that the S/w should be fit for use and for producer point of view the S/w should meet customer requirement.

 Factors affecting the quality:

 Time

 Cost/budget

 Reliability

5. Explain Quality management process?

 Quality management is process of preventing defects in the S/w process to ensure that there are no defects in the final product, the whole quality process is divided into two parts:

1) Quality Assurance (QA)

2) Quality Control (QC)

6. What is Quality Assurance?

 It measures the quality of processes used to create a quality product.

 It is an activity that is based on process where we measure each process, identify any weakness and suggest improvement.

7. What is Quality Control?

 It is an activity that is based on product where we measure the product, identify any weakness and improve the product.

 QC is oriented towards detection of defects.

8 .Explain difference b/w QA VS QC

Quality Assurance (QA) Quality Control (QC)

It is process oriented

(producing the product) It is product oriented

Preventive approach Detective approach

Usually done through out the life cycle Usually done after products are built

Auditing, reviews are the examples Testing is a part of QC

9. Why do we need specialist Tester?

 Developers will not do systematic and complete testing.

 A developer assumes few things to be working fine as they are owners of the work.

10. Explain Testing Limitations

 We can only test against system requirements

 May not detect errors in the requirements

 Incomplete requirements may not lead to inadequate or incorrect testing.

 Exhaustive (total) testing is impossible in present scenario.

 Time and Budget constrains normally require very carefully planning of the testing effort.

 Test results are use to make business decisions for release dates.

11. Why Testing CANNOT Ensure Quality ?

Testing in itself cannot ensure the quality of software. All testing can do is give you a certain level of assurance (confidence) in the software. On its own, the only thing that testing proves is that under specific controlled conditions, the software functioned as expected by the test cases executed.

12. What is SDLC?

 SDLC: It is a process of developing a software project or product to fulfill the customer requirements within the specified cost and time.

13. What is Feasibility study?

 It is a process of analyzing feasibility factors to implement the project with respect to Technical, Schedule and financial aspects.

 Project Manager and senior team members carry out feasibility analysis.

 If feasibility of the project has any doubt the project will not be continue.

14. Common problems in SDLC?

 Poor Requirements:

 Unrealistic schedule:

 adequate testing:

 Miscommunications:

15. Explain some of SDLC Models?

 Based on the requirements and the needs of the customer there can be a specific model adopted in order to implement a S/w application

SDLC Models are:

 Waterfall Model

 Incremental Model

 Prototype Model

 Rapid Application Development (RAD) Model

 Spiral Model

 V-Model

 Agile Model

16. What is Agile Testing model?

 It is new Gen. SDLC Model.

 Agile testing involves testing from the customer perspective as early as possible.

 Testing early and often as code becomes available and stable enough from module/unit level testing.

17. Explain V-model? Advantage of V-model?

 ‘V’ stands for verification & validation. It is a suitable model for large scale companies to maintain testing process. This model defines co-existence relation between development process and testing process.

 The difference between other models and this model is that it has provided testing the same weight-age as other S/w development activities.

18.Explain Verification?

 In this process we say “Are we building the product right”?

 It is performed by reviewing the SRS Document, Design Document, Code to find any mistakes.

 It is consider as “Static” testing.

 Reviews, Walkthrough and Inspection are the examples of Verification Techniques.

19. Explain Verification Techniques?

a. Peer Review: It is informal meeting where the author provides the document to any one person to identify any mistakes.

b. Walkthrough: Semi-informal meeting where the participants comes to the meeting and author gives the presentation. In this case author himself is the presenter for explaining the project requirement.

It is planned meeting characterized by team of 2- people, led by author

Objective is to make other participants familiarize with the material and find any mistakes.

c. Inspection:

• Formal meeting characterized by individual preparation presentation prior to the meeting

• The meeting is led by the Moderator who assure that rules are been followed and review is effective. Inspector does review for the document been presented.

• Presenter is the reader other than the author.

• Recorder records the defect identified in the meeting.

20. Explain Validation process?

• In this process we say “Are we build the right product?

• It is the process of confirmation whether software meets customer requirements.

• It is performed by executing the application to find any defect

• It is consider as “DYNAMIC” testing or testing with execution of system.

• Unit testing, Integration testing, system testing and Acceptance testing are the examples of validation techniques.

21. what is Coding, Testing, Debugging and Bug fixing?

Coding:- Developing the programs for creating the application called as coding.

Testing: validating the application if all requirements are implemented or not

Debugging: the process of analyzing the code to identify the source of the error is called as debugging. Developers are responsible for Debugging.

 Bug Fixing: The process of correcting the bugs is called as Bug Fixing or bug resolving.

22. What is White Box Testing?

 It is based on knowledge of the internal logic of the application’s code.

 Tests are based on coverage of code, statements, branches, paths, conditions & loops.

 It is also called as Clear Box or Glass Box or Open Box or Structural Testing.

23. Disadvantages in WBT?

• Test cases creation starts after the coding and there is a delay in the process.

• WB testers will be rare and costly.

• It doesn’t ensure requirement coverage. because if any requirement is missing in the code WBT doesn’t identify such requirement.

• WBT is limited to a technology.

23. What is Black Box Testing?

 Black box testing is also called as functionality testing.

 Black box testing not based on any knowledge of internal design or code.

 Tests are based on requirements & functionality.

24. What is Gray box testing?

 This is just a combination of both black box and white box testing. Tester should have the knowledge of both the internal and externals of the function.

 Tester should have good knowledge of white box testing & complete knowledge of black box testing

 Grey box testing is especially important with web & internet applications, because the internet is built around loosely integrated components that connect via relatively well-defined interfaces.

25. Explain some of testing types?

 Functional Testing

- Integration Testing

- System Testing

- System-to-System Testing (for testing interfaces)

- Regression Testing

- Load Testing

- Performance Testing

- Stress Testing

Etc.

26. Explain levels of tests?

• Unit testing

• Module testing

• Integration testing

• System testing

• User acceptance testing

27. Explain Unit Testing?

 It is code oriented testing.

 Individual components are tested to ensure that they operate correctly. Each component is tested independently, without other system components.

28. Explain Module Testing?

 A module is a collection of dependent components such as an object class, an abstract data type or some looser collection of procedures and functions.

 A module encapsulates related components so it can be tested without other system modules.

29. Explain Integration testing?

 It is also called sub-system testing.

 It is Design oriented.

 This phase involves testing collections of modules, which have been integrated into sub-systems. Sub-systems may be independently designed and implemented. The most common problems, which arise in large software systems, are sub-systems interface mismatches. The sub-system test process should therefore concentrate on the detection of interface errors by rigorously exercising these interfaces

30. Explain Difference b/w stub & Driver?

Stub Driver

Called program Calling program

It returns values It accepts values

It is dummy program It is also dummy program

When sub module under construction. When main module (calling) under construction.

31. Explain system testing?

• The primary objective of system testing is to discover errors when the system is tested as a whole.

• System testing is also called as End – to – End testing.

• Tester is expected to test from login to logout by covering various business functionalities, conducted by test engineers. Depends on SRS.

32. What is acceptance testing?

It is to verify the system functionality and usability prior to the system being released to production.

• The acceptance test is the responsibility of the client/customer or project manager.

33. Explain Alpha test and Beta test?

• Alpha test: it is called as in-house acceptance testing. It is implemented in the development company. Conduct by client.

• Beta test: it is called as client(end) side acceptance testing. It is done by client at client/work environment.

34. What is Proto type?

• It is a sample application with out functionality.

• Which is used to demonstrate the application navigation and GUI to develop the application.

35. What is prototype testing?

• It is a very effective method for finding design errors at an early stage in product development, when functionalities are in basic form, or not yet implemented.

36. What elements will we cover in GUI testing?

• 1. Font size, colors, spellings(labels) etc

2. Every application should follow Microsoft rules like

2.1 Controls should be Initcap (i.e. every label should start with Capital letter )

2.2 OK or Cancel button should exist

2.3 Controls should not be overlapped

2.4 Controls should be aligned properly (left side alignment is mandatory but the right side is optional)

2.5 Controls should be visible

2.6 Short cut keys should be provided

2.7 System menu should exist (i.e. if u press Alt key + Space bar a menu will appear at the left most corner )

37. Explain Sanity testing?

• A quick and initial test to make sure the system can operate and process at least a minimal workload.

• It is a good idea to use a sanity test as entry criteria into feature testing, in order to ensure that the system is testable, and to avoid wasting time trying to test a system, which fails frequently.

38. What is performance testing?

• Performance testing verifies loads, volumes and response times, as defined by requirements. Although performance testing is a part of system testing, it can be regarded as a distinct level of testing.

39. What is recovery/error testing?

• Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

40. What is difference between load and stress testing?

• A. Load Testing: Load Testing is done in order to check when the application fails by increasing the number of users and keeping the system resources as constant.

• Stress Testing: Stress Testing is done in order to check when the application fails by reducing the system resources such as RAM, HDD etc. and keeping the number of users as constant.

41. What is security/penetration testing?

• Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage. This type of testing usually requires sophisticated testing techniques.

42. How do you conduct localization testing?

• A. This is one of the key factors considered during testing applications, which are operated across the globe. Various countries have their own formats of representing the data. Few examples are numeric format, date format and many more.

• In US the number is represented as 1,73,000.50

In Europe the same number is represented as 1.73.000, 50

43. How do you conduct I18N Testing?

• Internationalization (I18N) test Ideally, the set of tests performed on the original program prior to localization. Issues such as hard-coded strings, concatenation, character sets, encoding, and support for locales are examined.

44. What is Regression testing ?

• A: Regression Testing: Regression testing is done to ensure that enhancement, defect fixes or any other changes made to the software has not broken any existing functionality.
 

45. What is Retesting?

• When a developer resolves/fixes a defect on a modified build, then it would be sent to testing team for retesting that defect, to evaluate the bug fix work.

• Perform the retesting, If the defect is successfully resolved then the corresponding defect can be formally closed otherwise it should be properly fixed in the next build.

46. What is BVA?

• A: The purpose of boundary value analysis is to concentrate the testing effort on error prone areas by accurately pinpointing the boundaries of conditions

• Boundary conditions are:

• 1) Lower limit –1 =

• 2) Lower limit =

• 3) Lower limit +1 =

• 4) Upper limit –1 =

• 5) Upper limit =

• 6) Upper limit +1 =

47. What is ECP?

• Equivalence partitioning is a black-box testing method

• Divide the input domain of a program into classes of data

• Derive test cases based on these partitions.

• An equivalence class represents a set of valid or invalid states for input condition.

48. What's difference between client/server and Web Application?

• Client/server based is any application architecture where one server application and one or many client applications are involved like your mail server and MS outlook Express.

• Web Application is a kind that hosted on the web server and accessed over the internet or intranet.

49. What's difference between client/server and Web Application?

• Client/server based is any application architecture where one server application and one or many client applications are involved like your mail server and MS outlook Express.

• Web Application is a kind that hosted on the web server and accessed over the internet or intranet.

50. What is Mutation testing?

• Testing the application behavior when we introduce some known bugs.

• Our expected result will be user friendly error messages rather than technical error messages.

• Note: this can also be used for testing the completeness of the Test Cases.

51. What are the browser compatibility test elements?

• Client side scripting

• Frames

• Images

• Links

• Browser specific HTML tabs

• Cookies

52. What is SOAK testing?

• Extended stress testing is some times called as SOAK testing and it is used to analyze the memory leak.

53. What is Memory Leak?

• While running a application if the created variables or objects are not destroyed after their usage, those variables forms as garbage in the runtime memory and this is called Memory Leak.

• Memory Leaks to introduce poor performance or application crash.

• Memory leaks can be identify by using Bounds checker or rational purity.

54. Explain Response time, Execution time and Through put?

• Response time: the time from the request to the time when we get the 1st bit of response.

• Execution time: the time from the request to the time when we get the complete response.

• Through put: the amount of work done per second is called as through put. i.e. no. of requests process per second

55. What is DLL?

• A dynamic link library which maintains code as methods and which performs some actions.

• DLL cannot run on their own. DLL need to be called by another running exe or DLL.

56. What is kickoff meeting?

• An initial Project start up meeting from which the formal test activities are initiated.

57. What are the drawbacks in manual testing compared to Automation?

• Following are the drawbacks of manual testing,

• Time consuming

• Low reliability

• Human resources

• Inconsistent

58. How do you conduct KT sessions?

• In my company different KT sessions would be conducted starting after gathering requirements, SRS preparation,

• dev.team and testing team KT sessions with respect to client environment, domain etc.

• In most of KT will be coordinated by management team includes PM,PL,TL(Dev team),Test Lead.

59. Explain testing process? Or Explain STLC phases?

• Test initiation

• Test planning

• Test case design

• Test execution

• Defect Reporting and defect Tracking

• Test closure.

60. What is Test Strategy?

• The Test Strategy is the plan for how you are going to approach testing. It describes how you are going to approach the project to test.

61. What is cyclomatic complexity and function point?

• Using cyclomatic complexity techniques we can measure the complexity of requirements

• Using function point we can analyze the complexity of the requirement.

62. How do you plan the testing of an application when there was no-requirements or 
insufficient requirements are given?

• We plan the exploratory testing and we should start creating some of the documents during testing which can be helpful for future testing.

• Note: most of the exploratory test bugs may not be the real bugs.

63. How do you plan for testing?

• Test execution plan should be done based on the build that is delivered from the development team for testing.

• It consists of preparation of test sets ,setting up of test environment, identification of the resources and their respective tasks to be performed and the other related templates for reporting the status.

64. Difference b/w TP & TS

Test Plan

1. Project Specific

2. Dynamic Document, changes with the project release

3. The Test Plan, on the other hand, actually provides a

plan for the testing period itself. It includes who will

test what and when.

4. Uses test strategy to develop, at subsequently laters stages

5. Prepared by team lead to list out when to Test, What to Test, How to Test and Whom to Test?

Test Strategy

1. Organization Specific.

2. Static document, uniform for organization.

3. Details the testing infrastructure (types of testing, environment, acceptance criteria)

4. Generally fixed and prepared at the early stages of any project

5. Prepared by project manager to list out what tests to be applied

65. What is Test Setup environment?

• Test environment is the working environment where tests will be executed.

• The Testing Team may have their own Test Environment. Once the testing team certifies the system in Test Environment, it is migrated to the Production Environment

• Operating System

• Browsers

• Web Server and App Server

• Database (Oracle/DB2)

66. What are the testing metrics?

• There can be different levels of metrics:

1. Test Metrics:

2. Defect Metrics:

3. Resource Metrics:

67. What do you do if developer is repeatedly rejecting a bug?

• Discuss with team leader/discuss with developer

• Tester should setup a meeting with developer about the bug with required supporting documentation.

• If the issue not resolved in the discussion tester should initiate the discussion with

• If the issue is still persists a query will posted to client about the bug.

68. Can you provide status as closed for Duplicate and Rejected bugs?

• Duplicate and Rejected bugs may not be closed, Because closing such bugs will not allows to identify the actual bugs.

69. How many test cases you write in one day?

• On an average of 25 test cases a day

70. How many defects you find in one day?

• It depends on the application and the number of test cases executed in a day.

71. What is a release note?

• A release note is given to client along with the build when it is ready for the deployment. Release notes consists of the deployment details and also the known limitations of the build, if there are any critical errors that are still

• Not resolved and build is to be released, then those are also mentioned in the release notes.

72. What is Test Data?

• The data we need to supply on test cases which consists of customer expected data at the time of execution of test cases.

• We prepare test data generally in excel sheet based LLD,FRS/SRS.

73. What are the severity levels you give for a defect?

• We follow four levels of severity for a defect,

• Critical, High, Medium and low (cosmetic)

74. What are test scenarios?

• A. Test Scenarios are the end-to-end test cases prepared to test a realistic business flow with a specific pre-condition, Test Data Values and expected behavior.

75. How do you prepare test scenarios?

• The Test Scenarios are derived from Requirements documents/Use Case Documents based on the following factors

• Identify the multiple flows associated with a given event or a business scenario.

• Identify the multiple conditions associated with a given event.

• Identify the multiple data values required.

76. How are you tracking defects in your project?

• A: Using defect tracking tool (Quality Center)

77. To whom you report defects?

• A defect is generally reported to the test lead and lead will intern assign it to the development team, but at times the defect is assigned directly to the developer by the test engineer.

78. What is difference between severity and priority of a defect?

• Defect Severity represents how badly the functionality was failed and what serious impact it will have on the remaining system functionalities and also on the customer business.

• Defect Priority represents the importance of the defect and its resolution by the developers.

• The Severity and Priority levels are provided by the testers, The Severity levels should not be changed, but the priority levels can be changed by the Test Lead /Developers from one build to another based on the defects to be resolved.

79. What are the status for a Test Case?

1.NoRun

2.Not Completed

3.Passed

4.Failed

80. What are the status for defect?

Open:

Pending/deferred:

Fixed:

Rejected:

Reopen:

Closed:

81. How the Defect Density would contribute for the test exit criteria?

For the number of test cases being executed if the rate at which defects found have come done to a very low value and also saturated,

Hence an important input for test stop criteria.

82. Who will prepare a Test Summary Report?

• It is an exit report should be prepared by the test lead and communicate as a deliverable to the customer .It should include the following information

83. Who will prepare a Test Summary Report?

• It is an exit report should be prepared by the test lead and communicate as a deliverable to the customer .It should include the following information

84. What are the Test Deliverable?

• The following items will be delivered

• Test Plan

• Test Cases (Maintained in QC)

• Daily Test Execution Report

• Test Exit Report

• Defect Log (Maintained in QC)

• Traceability Matrix

• Project Metrics.

50 COMMON INTERVIEW QUESTIONS AND ANSWERS

Review these typical interview questions and think about how you would answer them. Read the questions listed; you will also find some strategy suggestions with it.

1. Tell me about yourself:

The most often asked question in interviews. You need to have a short statement prepared in your mind. Be careful that it does not sound rehearsed. Limit it to work-related items unless instructed otherwise. Talk about things you have done and jobs you have held that relate to the position you are interviewing for. Start with the item farthest back and work up to the present.

2. Why did you leave your last job?

Stay positive regardless of the circumstances. Never refer to a major problem with management and never speak ill of supervisors, co-workers or the organization. If you do, you will be the one looking bad. Keep smiling and talk about leaving for a positive reason such as an opportunity, a chance to do something special or other forward-looking reasons.
 

3. What experience do you have in this field?

Speak about specifics that relate to the position you are applying for. If you do not have specific experience, get as close as you can.

4. Do you consider yourself successful?

You should always answer yes and briefly explain why. A good explanation is that you have set goals, and you have met some and are on track to achieve the others.

5. What do co-workers say about you?

Be prepared with a quote or two from co-workers. Either a specific statement or a paraphrase will work. Jill Clark, a co-worker at Smith Company, always said I was the hardest worker she had ever known. It is as powerful as Jill having said it at the interview herself.

6. What do you know about this organization?

This question is one reason to do some research on the organization before the interview. Find out where they have been and where they are going. What are the current issues and who are the major players?

7. What have you done to improve your knowledge in the last year?

Try to include improvement activities that relate to the job. A wide variety of activities can be mentioned as positive self-improvement. Have some good ones handy to mention.

8. Are you applying for other jobs?

Be honest but do not spend a lot of time in this area. Keep the focus on this job and what you can do for this organization. Anything else is a distraction.

9. Why do you want to work for this organization?

This may take some thought and certainly, should be based on the research you have done on the organization. Sincerity is extremely important here and will easily be sensed. Relate it to your long-term career goals.

10. Do you know anyone who works for us?

Be aware of the policy on relatives working for the organization. This can affect your answer even though they asked about friends not relatives. Be careful to mention a friend only if they are well thought of.

11. What kind of salary do you need?

A loaded question. A nasty little game that you will probably lose if you answer first. So, do not answer it. Instead, say something like, That's a tough question. Can you tell me the range for this position? In most cases, the interviewer, taken off guard, will tell you. If not, say that it can depend on the details of the job. Then give a wide range.

12. Are you a team player?

You are, of course, a team player. Be sure to have examples ready. Specifics that show you often perform for the good of the team rather than for yourself are good evidence of your team attitude. Do not brag, just say it in a matter-of-fact tone. This is a key point.

13. How long would you expect to work for us if hired?

Specifics here are not good. Something like this should work: I'd like it to be a long time. Or As long as we both feel I'm doing a good job.

14. Have you ever had to fire anyone? How did you feel about that?

This is serious. Do not make light of it or in any way seem like you like to fire people. At the same time, you will do it when it is the right thing to do. When it comes to the organization versus the individual who has created a harmful situation, you will protect the organization. Remember firing is not the same as layoff or reduction in force.

15. What is your philosophy towards work?

The interviewer is not looking for a long or flowery dissertation here. Do you have strong feelings that the job gets done? Yes. That's the type of answer that works best here. Short and positive, showing a benefit to the organization.

16. If you had enough money to retire right now, would you?

Answer yes if you would. But since you need to work, this is the type of work you prefer. Do not say yes if you do not mean it.

17. Have you ever been asked to leave a position?

If you have not, say no. If you have, be honest, brief and avoid saying negative things about the people or organization involved.

18. Explain how you would be an asset to this organization

You should be anxious for this question. It gives you a chance to highlight your best points as they relate to the position being discussed. Give a little advance thought to this relationship.

19. Why should we hire you?

Point out how your assets meet what the organization needs. Do not mention any other candidates to make a comparison.

20. Tell me about a suggestion you have made

Have a good one ready. Be sure and use a suggestion that was accepted and was then considered successful. One related to the type of work applied for is a real plus.

21. What irritates you about co-workers?

This is a trap question. Think real hard but fail to come up with anything that irritates you. A short statement that you seem to get along with folks is great.

22. What is your greatest strength?

Numerous answers are good, just stay positive. A few good examples:

Your ability to prioritize, Your problem-solving skills, Your ability to work under pressure, Your ability to focus on projects, Your professional expertise, Your leadership skills, Your positive attitude

23. Tell me about your dream job.

Stay away from a specific job. You cannot win. If you say the job you are contending for is it, you strain credibility. If you say another job is it, you plant the suspicion that you will be dissatisfied with this position if hired. The best is to stay genetic and say something like: A job where I love the work, like the people, can contribute and can't wait to get to work.

24. Why do you think you would do well at this job?

Give several reasons and include skills, experience and interest.

25. What are you looking for in a job?

See answer # 23

26. What kind of person would you refuse to work with?

Do not be trivial. It would take disloyalty to the organization, violence or lawbreaking to get you to object. Minor objections will label you as a whiner.

27. What is more important to you: the money or the work?

Money is always important, but the work is the most important. There is no better answer.

28. What would your previous supervisor say your strongest point is?

There are numerous good possibilities:

Loyalty, Energy, Positive attitude, Leadership, Team player, Expertise, Initiative, Patience, Hard work, Creativity, Problem solver

29. Tell me about a problem you had with a supervisor

Biggest trap of all. This is a test to see if you will speak ill of your boss. If you fall for it and tell about a problem with a former boss, you may well below the interview right there. Stay positive and develop a poor memory about any trouble with a supervisor.

30. What has disappointed you about a job?

Don't get trivial or negative. Safe areas are few but can include:

Not enough of a challenge. You were laid off in a reduction Company did not win a contract, which would have given you more responsibility.

31. Tell me about your ability to work under pressure.

You may say that you thrive under certain types of pressure. Give an example that relates to the type of position applied for.

32. Do your skills match this job or another job more closely?

Probably this one. Do not give fuel to the suspicion that you may want another job more than this one.

33. What motivates you to do your best on the job?

This is a personal trait that only you can say, but good examples are:

Challenge, Achievement, Recognition

34. Are you willing to work overtime? Nights? Weekends?

This is up to you. Be totally honest.

35. How would you know you were successful on this job?

Several ways are good measures:

You set high standards for yourself and meet them. Your outcomes are a success.Your boss tell you that you are successful

36. Would you be willing to relocate if required?

You should be clear on this with your family prior to the interview if you think there is a chance it may come up. Do not say yes just to get the job if the real answer is no. This can create a lot of problems later on in your career. Be honest at this point and save yourself future grief.

37. Are you willing to put the interests of the organization ahead of your own?

This is a straight loyalty and dedication question. Do not worry about the deep ethical and philosophical implications. Just say yes.

38. Describe your management style.

Try to avoid labels. Some of the more common labels, like progressive, salesman or consensus, can have several meanings or descriptions depending on which management expert you listen to. The situational style is safe, because it says you will manage according to the situation, instead of one size fits all.

39. What have you learned from mistakes on the job?

Here you have to come up with something or you strain credibility. Make it small, well intentioned mistake with a positive lesson learned. An example would be working too far ahead of colleagues on a project and thus throwing coordination off.

40. Do you have any blind spots?

Trick question. If you know about blind spots, they are no longer blind spots. Do not reveal any personal areas of concern here. Let them do their own discovery on your bad points. Do not hand it to them.

41. If you were hiring a person for this job, what would you look for?

Be careful to mention traits that are needed and that you have.

42. Do you think you are overqualified for this position?

Regardless of your qualifications, state that you are very well qualified for the position.

43. How do you propose to compensate for your lack of experience?

First, if you have experience that the interviewer does not know about, bring that up: Then, point out (if true) that you are a hard working quick learner.

44. What qualities do you look for in a boss?

Be generic and positive. Safe qualities are knowledgeable, a sense of humor, fair, loyal to subordinates and holder of high standards. All bosses think they have these traits.

45. Tell me about a time when you helped resolve a dispute between others.

Pick a specific incident. Concentrate on your problem solving technique and not the dispute you settled.

46. What position do you prefer on a team working on a project?

Be honest. If you are comfortable in different roles, point that out.

47. Describe your work ethic.

Emphasize benefits to the organization. Things like, determination to get the job done and work hard but enjoy your work are good.

48. What has been your biggest professional disappointment?

Be sure that you refer to something that was beyond your control. Show acceptance and no negative feelings.

49. Tell me about the most fun you have had on the job.

Talk about having fun by accomplishing something for the organization.

50. Do you have any questions for me?

Always have some questions prepared. Questions prepared where you will be an asset to the organization are good. How soon will I be able to be productive? and What type of projects will I be able to assist on? are examples.