Contents

1. What is Acceptance Testing?............................................................................ .............6

2. What is Accessibility Testing?................................................................... ....................6
3. What is Ad Hoc Testing?............................................................................................. ....6
4. What is Agile Testing?................................................................................. ...................6
5. What is Application Binary Interface (ABI)?............................... ...............................6
6. What is Application Programming Interface (API)?................................... ...............6
7. What is Automated Software Quality (ASQ)?.................................... .........................6
8. What is Automated Testing?...................................................................................... ....6
9. What is Backus-Naur Form?............................................................... ...........................6
10. What is Basic Block?........................................................................................ .............6
11. What is Basis Path Testing?............................................................. ...........................6
12. What is Basis Set?................................................................................................... ......6
13. What is Baseline?.............................................................................................. ............7
14. What you will do during the first day of job?...........................................................7
15. What is Beta Testing?............................................................................................ .......7
16. What is Binary Portability Testing?.............................................................. ..............7
17. What is Black Box Testing?......................................................................................... .7
18. What is Bottom Up Testing?...................................................................... ..................7
19. What is Boundary Testing?............................................................................... ...........7
20. What is Bug?.................................................................................................... ..............7
20. What is Defect?................................................................................ .............................7
21. What is Boundary Value Analysis?.................................................... .........................7
22. What is Branch Testing?.................................................................. ............................7
23. What is Breadth Testing?..................................................................................... ........7
24. What is CAST?.......................................................................................................... ......7
25. What is Capture/Replay Tool?.......................................................... ..........................8
26. What is CMM?................................................................................................................ .8
27. What is Cause Effect Graph?........................................................... ............................8
28. What is Code Complete?................................................................ ..............................8
29. What is Code Coverage?............................................................................................. ..8
30. What is Code Inspection?.................................................................... ........................8
31. What is Code Walkthrough?................................................................. .......................8
32. What is Coding?........................................................................................................ .....8
33. What is Compatibility Testing?....................................................... ............................8
34. What is Component?.............................................................................................. .......8
2
35. What is Component Testing?................................................................................. ......8
36. What is Concurrency Testing?.............................................................................. .......8
37. What is Conformance Testing?.................................................................................... 9
38. What is Context Driven Testing?.................................................. ..............................9
39. What is Conversion Testing?.................................................................... ...................9
40. What is Cyclomatic Complexity?................................................................... ..............9
41. What is Data Dictionary?............................................................... ..............................9
42. What is Data Flow Diagram?................................................................ .......................9
43. What is Data Driven Testing?.......................................................................... ............9
44. What is Debugging?............................................................................................. .........9
45. What is Defect?................................................................................ .............................9
46. What is Dependency Testing?............................................................... ......................9
47. What is Depth Testing?.......................................................................... ......................9
48. What is Dynamic Testing?........................................................................................... .9
49. What is Emulator?................................................................................................ .........9
50. What is Endurance Testing?................................................................. .....................10
51. What is End-to-End testing?.............................................................................. ........10
52. What is Equivalence Class?....................................................................................... .10
53. What is Equivalence Partitioning?................................................................ ............10
54. What is Exhaustive Testing?..................................................... ................................10
55. What is Functional Decomposition?................................................. ........................10
55. What is Functional Testing?.......................................................... ............................10
56. What is Glass Box Testing?.................................................................................... ....10
57. What is Gorilla Testing?....................................................................... ......................10
58. What is Gray Box Testing?............................................................................... ..........10
59. What is High Order Tests?.................................................................... .....................10
60. What is Independent Test Group (ITG)?............................................... ..................11
61. What is Inspection?.................................................................................... ................11
62. What is Integration Testing?.................................................................................. ...11
63. What is Installation Testing?.......................................................... ..........................11
64. What is Load Testing?...................................................................... ..........................11
65. What is Localization Testing?.............................................................................. ......11
66. What is Loop Testing?........................................................................ ........................11
67. What is Metric?.................................................................................................. ..........11
68. What is Monkey Testing?...................................................................... .....................11
69. What is Negative Testing?..................................................................... ....................11
70. What is Path Testing?........................................................................................... ......11
71. What is Performance Testing?.......................................................... ........................11
3
72. What is Positive Testing?................................................................................... ........12
73. What is Quality Assurance?........................................................................ ...............12
74. What is Quality Audit?....................................................................................... .........12
75. What is Quality Circle?....................................................................... ........................12
76. What is Quality Control?................................................................... .........................12
77. What is Quality Management?.................................................... ..............................12
78. What is Quality Policy?.......................................................................................... .....12
79. What is Quality System?...................................................................... ......................12
80. What is Race Condition?............................................................. ...............................12
81. What is Ramp Testing?......................................................................................... ......12
82. What is Recovery Testing?......................................................................................... 12
83. What is Regression Testing?.............................................................. .......................12
84. What is Release Candidate?.......................................................... ............................12
85. What is Sanity Testing?......................................................................................... .....13
86. What is Scalability Testing?..................................................................................... ..13
87. What is Security Testing?................................................................. .........................13
88. What is Smoke Testing?................................................................................. ............13
89. What is Soak Testing?........................................................................... .....................13
90. What is Software Requirements Specification?.................................................. ....13
91. What is Software Testing?............................................................................... ..........13
92. What is Static Analysis?............................................................................. ................13
93. What is Static Analyzer?................................................................... .........................13
94. What is Static Testing?.......................................................................................... .....13
95. What is Storage Testing?.......................................................................... .................13
96. What is Stress Testing?....................................................................................... .......14
97. What is Structural Testing?.................................................................... ...................14
98. What is System Testing?................................................................................... .........14
99. What is Testability?.......................................................................... ..........................14
100. What is Testing?...................................................................................................... ..14
101. What is Test Bed?........................................................................... ..........................14
102. What is Test Case?.............................................................................................. ......14
103. What is Test Driver?.............................................................................. ...................14
104. What is Test Environment?.................................................................................... ..14
105. What is Test First Design?........................................................................ ...............14
106. What is Test Harness?........................................................................................ ......15
107. What is Test Plan?........................................................................... .........................15
108. What is Test Procedure?......................................................................... .................15
109. What is Test Script?............................................................................................ ......15
4
110. What is Test Specification?........................................................ .............................15
111. What is Test Suite?..................................................................................... ..............15
112. What is Test Tools?............................................................................................... ....15
113. What is Thread Testing?................................................................... .......................15
114. What is Top Down Testing?....................................................................... ..............15
115. What is Total Quality Management?............................................ ..........................15
116. What is Traceability Matrix?............................................................................... .....15
117. What is Usability Testing?.................................................................. .....................15
118. What is Use Case?.............................................................................................. .......16
119. What is Unit Testing?........................................................................ .......................16
120. What is Validation?.......................................................................................... .........16
121. What is Verification?........................................................................ ........................16
122. What is White Box Testing?..................................................... ...............................16
123. What is Workflow Testing?.................................................................................... ..16
124. What's the difference between load and stress testing ?...................................16
125. What's the difference between QA and testing?....................................... ...........16
126. What is the best tester to developer ratio?................................. .........................17
127. How can new Software QA processes be introduced in an existing organization?
.......................................................................................................................................... ....17
128. What are 5 common problems in the software development process?............17
FAST ,RELIABLE,COMPREHENSIVE,REUSABLE..................................................... .................27
1. The choice of automation tool for certain technologies 2. Wrong set of test automated. .27
Font issues, alignment issues............................................................................................ ....29
Please submit Your Suggestion to our forum http://forum.qabricks.com.............................29
Software Quality Assurance Interview Questions only (1)................................ .........30
Software Quality Assurance Interview Questions only (2)................................ .........30
Software Quality Assurance Interview Questions only (3)................................ .........31
Software Quality Assurance Interview Questions only (4)................................ .........32
Software Quality Assurance Interview Questions only (5)................................ .........33
Software Quality Assurance Interview Questions only (6)................................ .........34
Software Quality Assurance Interview Questions only (7)................................ .........35
. N/A - I would be new to creating test plans or test cases.......................................... ....35
. Tests give confidence that the program meets its specifications....................................35
. Tests can discover that some code is missing........................................ ........................36
Software Quality Assurance Interview Questions only (8)................................ .........36
. Regression................................................................................................................ ......36
Software Quality Assurance Interview Questions only (9)................................ .........37
Software Quality Assurance Interview Questions only 10)........................................38

5
Software Quality Assurance Interview Questions only (11)..................................... ..39

1. What is Acceptance Testing?

Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to
validate the software meets a set of agreed acceptance criteria.
2. What is Accessibility Testing?
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).
3. What is Ad Hoc Testing?
A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include
negative testing as well. See also Monkey Testing.
4. What is Agile Testing?
Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a
test-first design paradigm. See also Test Driven Development.
5. What is Application Binary Interface (ABI)?
A specification defining requirements for portability of applications in binary forms across different system platforms and
environments.
6. What is Application Programming Interface (API)?
A formalized set of software calls and routines that can be referenced by an application program in order to access
supporting system or network services.
7. What is Automated Software Quality (ASQ)?
The use of software tools, such as automated testing tools, to improve software quality.
8. What is Automated Testing?
Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API,
etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes,
the setting up of test preconditions, and other test control and test reporting functions.
9. What is Backus-Naur Form?
A meta language used to formally describe the syntax of a language.
10. What is Basic Block?
A sequence of one or more consecutive, executable statements containing no branches.
11. What is Basis Path Testing?
A white box test case design technique that uses the algorithmic flow of the program to design tests.
12. What is Basis Set?
The set of tests derived using basis path testing.

6
13. What is Baseline?
The point at which some deliverable produced during the software engineering process is put under formal change control.
14. What you will do during the first day of job?
What would you like to do five years from now?
15. What is Beta Testing?
Testing of a re-release of a software product conducted by customers.
16. What is Binary Portability Testing?
Testing an executable application for portability across system platforms and environments, usually for conformation to an
ABI specification
17. What is Black Box Testing?
Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is
to test how well the component conforms to the published requirements for the component.
18. What is Bottom Up Testing?
An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of
higher level components. The process is repeated until the component at the top of the hierarchy is tested.
19. What is Boundary Testing?
Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).
20. What is Bug?
A fault in a program which causes the program to perform in an unintended or unanticipated manner.
20. What is Defect?
If software misses some feature or function from what is there in requirement it is called as defect.
21. What is Boundary Value Analysis?
BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by
the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would
include negative 101 and positive 1001.
22. What is Branch Testing?
Testing in which all branches in the program source code are tested at least once.
23. What is Breadth Testing?
A test suite that exercises the full functionality of a product but does not test features in detail.
24. What is CAST?
Computer Aided Software Testing.
25. What is Capture/Replay Tool?
A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to
reproduce the test at a later time. Most commonly applied to GUI test tools.
26. What is CMM?
The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes
of an organization and for identifying the key practices that are required to increase the maturity of these processes.
27. What is Cause Effect Graph?
A graphical representation of inputs and the associated outputs effects which can be used to design test cases.
28. What is Code Complete?
Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the
Functional Specifications have been implemented
29. What is Code Coverage?
An analysis method that determines which parts of the software have been executed (covered) by the test case suite and
which parts have not been executed and therefore may require additional attention.

7
30. What is Code Inspection?
A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the
program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its
compliance with coding standards.
31. What is Code Walkthrough?
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program
variables is manually monitored, to analyze the programmer's logic and assumptions.
32. What is Coding?
The generation of source code.
33. What is Compatibility Testing?
Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers,
Operating Systems, or hardware.
34. What is Component?
A minimal software item for which a separate specification is available.
35. What is Component Testing?
Testing of individual software components (Unit Testing).
36. What is Concurrency Testing?
Multi-user testing geared towards determining the effects of accessing the same application code, module or database
records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
37. What is Conformance Testing?
The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing
conformance to a formal standard.
38. What is Context Driven Testing?
The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of
testing opportunities in light of the potential information revealed and the value of that information to the organization right
now.
39. What is Conversion Testing?
Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
40. What is Cyclomatic Complexity?
A measure of the logical complexity of an algorithm, used in white-box testing
41. What is Data Dictionary?
A database that contains definitions of all data items defined during analysis.
42. What is Data Flow Diagram?
A modeling notation that represents a functional decomposition of a system.
43. What is Data Driven Testing?
Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or
spreadsheet. A common technique in Automated Testing.
44. What is Debugging?
The process of finding and removing the causes of software failures.
45. What is Defect?
Nonconformance to requirements or functional / program specification
46. What is Dependency Testing?
Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper
functionality.
47. What is Depth Testing?
A test that exercises a feature of a product in full detail.
48. What is Dynamic Testing?

8
Testing software through executing it. See also Static Testing.
49. What is Emulator?
A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.
50. What is Endurance Testing?
Checks for memory leaks or other problems that may occur with prolonged execution
51. What is End-to-End testing?
Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database,
using network communications, or interacting with other hardware, applications, or systems if appropriate.
52. What is Equivalence Class?
A portion of a component's input or output domains for which the component's behavior is assumed to be the same from the
component's specification.
53. What is Equivalence Partitioning?
A test case design technique for a component in which test cases are designed to execute representatives from equivalence
classes.
54. What is Exhaustive Testing?
Testing which covers all combinations of input values and preconditions for an element of the software under test.
55. What is Functional Decomposition?
A technique used during planning, analysis and design; creates a functional hierarchy for the software.
54. What is Functional Specification?
A document that describes in detail the characteristics of the product with regard to its intended features.
55. What is Functional Testing?
Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores
the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected
inputs and execution conditions. or Black Box Testing.
56. What is Glass Box Testing?
A synonym for White Box Testing.
57. What is Gorilla Testing?
Testing one particular module, functionality heavily.
58. What is Gray Box Testing?
A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but
using some knowledge of its internal workings.
59. What is High Order Tests?
Black-box tests conducted once the software has been integrated.

9
60. What is Independent Test Group (ITG)?
A group of people whose primary responsibility is software testing,
61. What is Inspection?
A group review quality improvement process for written material. It consists of two aspects; product (document itself)
improvement and process improvement (of both document production and inspection).
62. What is Integration Testing?
Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and
functional testing. This type of testing is especially relevant to client/server and distributed systems.
63. What is Installation Testing?
Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality.
Events can include shortage of disk space, unexpected loss of communication, or power out conditions.
64. What is Load Testing?
See Performance Testing.
65. What is Localization Testing?
This term refers to making software specifically designed for a specific locality.
66. What is Loop Testing?
A white box testing technique that exercises program loops.
67. What is Metric?
A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric
should be a real objective measurement of something such as number of bugs per lines of code.
68. What is Monkey Testing?
Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not
crash out.
69. What is Negative Testing?
Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.
70. What is Path Testing?
Testing in which all paths in the program source code are tested at least once
71. What is Performance Testing?
Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this
is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

10
72. What is Positive Testing?
Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.
73. What is Quality Assurance?
All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and
quality needed and expected by the customer.
74. What is Quality Audit?
A systematic and independent examination to determine whether quality activities and related results comply with planned
arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.
75. What is Quality Circle?
A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the
quality of outputs of a process and to the correction of problems or to the improvement of quality.
76. What is Quality Control?
The operational techniques and the activities used to fulfill and verify requirements of quality.
77. What is Quality Management?
That aspect of the overall management function that determines and implements the quality policy.
78. What is Quality Policy?
The overall intentions and direction of an organization as regards quality as formally expressed by top management.
79. What is Quality System?
The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.
80. What is Race Condition?
A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no
mechanism used by either to moderate simultaneous access.
81. What is Ramp Testing?
Continuously raising an input signal until the system breaks down.
82. What is Recovery Testing?
Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can
include shortage of disk space, unexpected loss of communication, or power out conditions
83. What is Regression Testing?
Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as
a result of the changes made.
84. What is Release Candidate?
A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs
(which ideally should be removed before the final version is released).
85. What is Sanity Testing?
Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.
86. What is Scalability Testing?
Performance testing focused on ensuring the application under test gracefully handles increases in work load.
87. What is Security Testing?
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can
access the functions available to their security level.
88. What is Smoke Testing?
A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of
turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
89. What is Soak Testing?

11
Running a system at high load for a prolonged period of time. For example, running several times more transactions in an
entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large
number of transactions have been executed.
90. What is Software Requirements Specification?
A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements
for software/
91. What is Software Testing?
A set of activities conducted with the intent of finding errors in software.
92. What is Static Analysis?
Analysis of a program carried out without executing the program
93. What is Static Analyzer?
A tool that carries out static analysis.
94. What is Static Testing?
Analysis of a program carried out without executing the program.
95. What is Storage Testing?
Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to
prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

12
96. What is Stress Testing?
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the
load under which it fails and how. Often this is performance testing using a very high level of simulated load.
97. What is Structural Testing?
Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.
98. What is System Testing?
Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.
99. What is Testability?
The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to
determine whether those criteria have been met.
100. What is Testing?
The process of exercising software to verify that it satisfies specified requirements and to detect errors. The process of
analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate
the features of the software item (Ref. IEEE Std 829). The process of operating a system or component under specified
conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. What
is Test Automation? It is the same as Automated Testing
101. What is Test Bed?
An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the
product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s)
to be used.
102. What is Test Case?
Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of
information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of
inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular
program path or to verify compliance with a specific requirement. Test Driven Development? Testing methodology associated
with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to
eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of
lines of test code to the size of the production code.
103. What is Test Driver?
A program or test tool used to execute a tests. Also known as a Test Harness.
104. What is Test Environment?
The hardware and software environment in which tests will be run, and any other software with which the software under test
interacts when under test including stubs and test drivers.
105. What is Test First Design?
Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write
any production code until they have first written a unit test.

13
106. What is Test Harness?
A program or test tool used to execute a tests. Also known as a Test Driver.
107. What is Test Plan?
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the
features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning
108. What is Test Procedure?
A document providing detailed instructions for the execution of one or more test cases.
109. What is Test Script?
Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.
110. What is Test Specification?
A document specifying the test approach for a software feature or combination or features and the inputs, predicted results
and execution conditions for the associated tests.
111. What is Test Suite?
A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to
organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a
high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.
112. What is Test Tools?
Computer programs used in the testing of a system, a component of the system, or its documentation.
113. What is Thread Testing?
A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the
requirements, as opposed to the integration of components by successively lower levels.
114. What is Top Down Testing?
An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level
components being simulated by stubs. Tested components are then used to test lower level components. The process is
repeated until the lowest level components have been tested
115. What is Total Quality Management?
A company commitment to develop a process that achieves high quality product and customer satisfaction.
116. What is Traceability Matrix?
A document showing the relationship between Test Requirements and Test Cases.
117. What is Usability Testing?
Testing the ease with which users can learn and use a product.

14
118. What is Use Case?
The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software
as an end-user would conduct their day-to-day activities.
119. What is Unit Testing?
Testing of individual software components.
120. What is Validation?
The process of evaluating software at the end of the software development process to ensure compliance with software
requirements. The techniques for validation is testing, inspection and reviewing.
121. What is Verification?
The process of determining whether of not the products of a given phase of the software development cycle meet the
implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques
for verification are testing, inspection and reviewing.
122. What is White Box Testing?
Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch
Testing and Path Testing. Also known as Structural Testing and Glass Box Testing. Contrast with Black Box Testing.

White box testing is used to test the internal logic of the code.for ex checking whether the path has been executed once,
checking whether the branches has been executed at least once .....Used to check the structure of the code.
123. What is Workflow Testing?
Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user
124. What's the difference between load and stress testing ?
• One of the most common, but unfortunate misuse of terminology is treating “load testing” and “stress testing” as
synonymous. The consequence of this ignorant semantic abuse is usually that the system is neither properly “load
tested” nor subjected to a meaningful stress test.
• Stress testing is subjecting a system to an unreasonable load while denying it the resources (e.g., RAM, disc, mips,
interrupts, etc.) needed to process that load. The idea is to stress a system to the breaking point in order to find bugs
that will make that break potentially harmful. The system is not expected to process the overload without adequate
resources, but to behave (e.g., fail) in a decent manner (e.g., not corrupting or losing data). Bugs and failure modes
discovered under stress testing may or may not be repaired depending on the application, the failure mode,
consequences, etc. The load (incoming transaction stream) in stress testing is often deliberately distorted so as to force
the system into resource depletion.
• Load testing is subjecting a system to a statistically representative (usually) load. The two main reasons for using such
loads is in support of software reliability testing and in performance testing. The term 'load testing' by itself is too vague
and imprecise to warrant use. For example, do you mean representative load,' 'overload,' 'high load,' etc. In performance
testing, load is varied from a minimum (zero) to the maximum level the system can sustain without running out of
resources or having, transactions >suffer (application-specific) excessive delay.
• A third use of the term is as a test whose objective is to determine the maximum sustainable load the system can
handle. In this usage, 'load testing' is merely testing at the highest transaction arrival rate in performance testing.
125. What's the difference between QA and testing?
QA is more a preventive thing, ensuring quality in the company and therefore the product rather than just testing the product
for software bugs?
TESTING means 'quality control'
QUALITY CONTROL measures the quality of a product
QUALITY ASSURANCE measures the quality of processes used to create a quality product.
126. What is the best tester to developer ratio?
Reported tester: developer ratios range from 10:1 to 1:10. There's no simple answer. It depends on so many things, Amount
of reused code, number and type of interfaces, platform, quality goals, etc.
It also can depend on the development model. The more specs, the less testers. The roles can play a big part also. Does QA
own beta? Do you include process auditors or planning activities?
These figures can all vary very widely depending on how you define 'tester' and 'developer'. In some organizations, a 'tester'
is anyone who happens to be testing software at the time -- such as their own. In other organizations, a 'tester' is only a
member of an independent test group.
It is better to ask about the test labor content than it is to ask about the tester/developer ratio. The test labor content, across
15
most applications is generally accepted as 50%, when people do honest accounting. For life-critical software, this can go up
to 80%
127. How can new Software QA processes be introduced in an existing organization?
- A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives
or property) projects, serious management buy-in is required and a formalized QA process is necessary.
- Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time
process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand.
- For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects.
A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among
customers, managers, developers, and testers.
- In all cases the most value for effort will be in requirements management processes, with a goal of clear, complete, testable
requirement specifications or expectations.
128. What are 5 common problems in the software development process?
1. poor requirements - if requirements are unclear, incomplete, too general, or not testable, there will be problems.
2. unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.
3. inadequate testing - no one will know whether or not the program is any good until the customer complains or systems
crash.
4. featuritis - requests to pile on new features after development is underway; extremely common.
5. miscommunication - if developers don't know what's needed or customer's have erroneous expectations, problems are
guaranteed.
129. What are 5 common solutions to software development problems?
1. solid requirements - clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players.
Use prototypes to help nail down requirements.
2. realistic schedules - allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation;
personnel should be able to complete the project without burning out.
3. adequate testing - start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing.
4. stick to initial requirements as much as possible - be prepared to defend against changes and additions once development
has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in
related schedule changes. If possible, use rapid prototyping during the design phase so that customers can see what to
expect. This will provide them a higher comfort level with their requirements decisions and minimize changes later on.
5. communication - require walkthroughs and inspections when appropriate; make extensive use of group communication
tools - e-mail, groupware, networked bug-tracking tools and change management tools, intranet capabilities, etc.; insure that
documentation is available and up-to-date - preferably electronic, not paper; promote teamwork and cooperation; use
prototypes early on so that customers' expectations are clarified
130. What is 'good code'?
'Good code' is code that works, is bug free, and is readable and maintainable. Some organizations have coding 'standards'
that all developers are supposed to adhere to, but everyone has different ideas about what's best, or what is too many or too
few rules. There are also various theories and metrics, such as McCabe Complexity metrics. It should be kept in mind that
excessive use of standards and rules can stifle productivity and creativity. 'Peer reviews', 'buddy checks' code analysis tools,
etc. can be used to check for problems and enforce standards.
For C and C++ coding, here are some typical ideas to consider in setting rules/standards; these may or may not apply to a
particular situation:
- minimize or eliminate use of global variables.
- use descriptive function and method names - use both upper and lower case, avoid abbreviations, use as many characters
as necessary to be adequately descriptive (use of more than 20 characters is not out of line); be consistent in naming
conventions.
- use descriptive variable names - use both upper and lower case, avoid abbreviations, use as many characters as
necessary to be adequately descriptive (use of more than 20 characters is not out of line); be consistent in naming
conventions.
- function and method sizes should be minimized; less than 100 lines of code is good, less than 50 lines is preferable.
- function descriptions should be clearly spelled out in comments preceding a function's code.
- organize code for readability.
- use whitespace generously - vertically and horizontally
- each line of code should contain 70 characters max.
- one code statement per line.
- coding style should be consistent through a program (eg, use of brackets, indentations, naming conventions, etc.)
- in adding comments, err on the side of too many rather than too few comments; a common rule of thumb is that there
should be at least as many lines of comments (including header blocks) as lines of code.
- no matter how small, an application should include documentaion of the overall program function and flow (even a few
paragraphs is better than nothing); or if possible a separate flow chart and detailed program documentation.
- make extensive use of error handling procedures and status and error logging.
- for C++, to minimize complexity and increase maintainability, avoid too many levels of inheritance in class heirarchies
16
(relative to the size and complexity of the application). Minimize use of multiple inheritance, and minimize use of operator
overloading (note that the Java programming language eliminates multiple inheritance and operator overloading.)
- for C++, keep class methods small, less than 50 lines of code per method is preferable.
- for C++, make liberal use of exception handlers
131. What is 'good design'?
'Design' could refer to many things, but often refers to 'functional design' or 'internal design'. Good internal design is indicated
by software code whose overall structure is clear, understandable, easily modifiable, and maintainable; is robust with
sufficient error-handling and status logging capability; and works correctly when implemented. Good functional design is
indicated by an application whose functionality can be traced back to customer and end-user requirements. For programs
that have a user interface, it's often a good idea to assume that the end user will have little computer knowledge and may not
read a user manual or even the on-line help; some common rules-of-thumb include:
- the program should act in a way that least surprises the user
- it should always be evident to the user what can be done next and how to exit
- the program shouldn't let the users do something stupid without warning them.
132. What makes a good test engineer?
A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for
quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers,
and an ability to communicate with both technical (developers) and non-technical (customers, management) people is useful.
Previous software development experience can be helpful as it provides a deeper understanding of the software
development process, gives the tester an appreciation for the developers' point of view, and reduce the learning curve in
automated test tool programming. Judgment skills are needed to assess high-risk areas of an application on which to focus
testing efforts when time is limited
133. What makes a good Software QA engineer?
The same qualities a good tester has are useful for a QA engineer. Additionally, they must be able to understand the entire
software development process and how it can fit into the business approach and goals of the organization. Communication
skills and the ability to understand various sides of issues are important. In organizations in the early stages of implementing
QA processes, patience and diplomacy are especially needed. An ability to find problems as well as to see 'what's missing' is
important for inspections and reviews.
134. What makes a good QA or Test manager?
A good QA, test, or QA/Test(combined) manager should:
- be familiar with the software development process
- be able to maintain enthusiasm of their team and promote a positive atmosphere, despite what is a somewhat 'negative'
process (e.g., looking for or preventing problems)
- be able to promote teamwork to increase productivity
- be able to promote cooperation between software, test, and QA engineers
- have the diplomatic skills needed to promote improvements in QA processes
-have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or QA processes are not
being adhered to
- have people judgment skills for hiring and keeping skilled personnel
- be able to communicate with technical and non-technical people, engineers, managers, and customers.
- be able to run meetings and keep them focused
135. What's the role of documentation in QA?
Critical. (Note that documentation can be electronic, not necessarily paper.) QA practices should be documented such that
they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test
cases, bug reports, user manuals, etc. should all be documented. There should ideally be a system for easily finding and
obtaining documents and determining what documentation will have a particular piece of information. Change management
for documentation should be used if possible.
136. What's the big deal about 'requirements'?
One of the most reliable methods of insuring problems, or failure, in a complex software project is to have poorly documented
requirements specifications. Requirements are the details describing an application's externally-perceived functionality and
properties. Requirements should be clear, complete, reasonably detailed, cohesive, attainable, and testable. A non-testable
requirement would be, for example, 'user-friendly' (too subjective). A testable requirement would be something like 'the user
must enter their previously-assigned password to access the application'. Determining and organizing requirements details in
a useful and efficient way can be a difficult effort; different methods are available depending on the particular project. Many
books are available that describe various approaches to this task.
Care should be taken to involve ALL of a project's significant 'customers' in the requirements process. 'Customers' could be
in-house personnel or out, and could include end-users, customer acceptance testers, customer contract officers, customer
management, future software maintenance engineers, salespeople, etc. Anyone who could later derail the project if their
expectations aren't met should be included if possible.
Organizations vary considerably in their handling of requirements specifications. Ideally, the requirements are spelled out in a
17
document with statements such as 'The product shall.....'. 'Design' specifications should not be confused with 'requirements';
design specifications should be traceable back to the requirements.
In some organizations requirements may end up in high level project plans, functional specification documents, in design
documents, or in other documents at various levels of detail. No matter what they are called, some type of documentation
with detailed requirements will be needed by testers in order to properly plan and execute tests. Without such documentation,
there will be no clear-cut way to determine if a software application is performing correctly
137. What steps are needed to develop and run software tests?
The following are some of the steps to consider:
- Obtain requirements, functional design, and internal design specifications and other necessary documents
- Obtain budget and schedule requirements
- Determine project-related personnel and their responsibilities, reporting requirements, required standards and processes
(such as release processes, change processes, etc.)
- Identify application's higher-risk aspects, set priorities, and determine scope and limitations of tests
- Determine test approaches and methods - unit, integration, functional, system, load, usability tests, etc.
- Determine test environment requirements (hardware, software, communications, etc.)
-Determine testware requirements (record/playback tools, coverage analyzers, test tracking, problem/bug tracking, etc.)
- Determine test input data requirements
- Identify tasks, those responsible for tasks, and labor requirements
- Set schedule estimates, timelines, milestones
- Determine input equivalence classes, boundary value analyses, error classes
- Prepare test plan document and have needed reviews/approvals
- Write test cases
- Have needed reviews/inspections/approvals of test cases
- Prepare test environment and testware, obtain needed user manuals/reference documents/configuration guides/installation
guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data
- Obtain and install software releases
- Perform tests
- Evaluate and report results
- Track problems/bugs and fixes
- Retest as needed
- Maintain and update test plans, test cases, test environment, and testware through life cycle

18
138. What is 'configuration management'?
Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation,
problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes.
139. What if the software is so buggy it can't really be tested at all?
The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type 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 or insufficient integration testing, poor
design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as
evidence of the problem
140. How can it be known when to stop testing?
This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent
environment, that complete testing can never be done. Common factors in deciding when to stop are:
- Deadlines (release deadlines, testing deadlines, etc.)
- Test cases completed with certain percentage passed
- Test budget depleted
- Coverage of code/functionality/requirements reaches a specified point
- Bug rate falls below a certain level
- Beta or alpha testing period ends
141. What if there isn't enough time for thorough testing?
Use risk analysis to determine where testing should be focused.
Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every
dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This
requires judgment skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations
can include:
- Which functionality is most important to the project's intended purpose?
- Which functionality is most visible to the user?
- Which functionality has the largest safety impact?
- Which functionality has the largest financial impact on users?
- Which aspects of the application are most important to the customer?
- Which aspects of the application can be tested early in the development cycle?
- Which parts of the code are most complex, and thus most subject to errors?
- Which parts of the application were developed in rush or panic mode?
- Which aspects of similar/related previous projects caused problems?
- Which aspects of similar/related previous projects had large maintenance expenses?
- Which parts of the requirements and design are unclear or poorly thought out?
- What do the developers think are the highest-risk aspects of the application?
- What kinds of problems would cause the worst publicity?
- What kinds of problems would cause the most customer service complaints?
- What kinds of tests could easily cover multiple functionalities?
- Which tests will have the best high-risk-coverage to time-required ratio?
142. What can be done if requirements are changing continuously?
A common problem and a major headache.
- Work with the project's stakeholders early on to understand how requirements might change so that alternate test plans and
strategies can be worked out in advance, if possible.
- It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the
application from scratch.
- If the code is well-commented and well-documented this makes changes easier for the developers.
- Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes.
- The project's initial schedule should allow for some extra time commensurate with the possibility of changes.
- Try to move new requirements to a 'Phase 2' version of an application, while using the original requirements for the 'Phase
1' version.
- Negotiate to allow only easily-implemented new requirements into the project, while moving more difficult new requirements
into future versions of the application.
- Be sure that customers and management understand the scheduling impacts, inherent risks, and costs of significant
requirements changes. Then let management or the customers (not the developers or testers) decide if the changes are
warranted - after all, that's their job.
- Balance the effort put into setting up automated testing with the expected effort required to re-do them to deal with changes.

- Try to design some flexibility into automated test scripts.

19
- Focus initial automated testing on application aspects that are most likely to remain unchanged.
- Devote appropriate effort to risk analysis of changes to minimize regression testing needs.
- Design some flexibility into test cases (this is not easily done; the best bet might be to minimize the detail in the test cases,
or set up only higher-level generic-type test plans)
- Focus less on detailed test plans and test cases and more on ad hoc testing (with an understanding of the added risk that
this entails).
143. What if the project isn't big enough to justify extensive testing?
Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis
is again needed and the same considerations as described previously in 'What if there isn't enough time for thorough
testing?' apply. The tester might then do ad hoc testing, or write up a limited test plan based on the risk analysis.
144. What if the application has functionality that wasn't in the requirements?
It may take serious effort to determine if an application has significant unexpected or hidden functionality, and it would
indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the
application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the
designer or the customer. If not removed, design information will be needed to determine added testing needs or regression
testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality.
If the functionality only effects areas such as minor improvements in the user interface, for example, it may not be a
significant risk.
145. How can Software QA processes be implemented without stifling productivity?
By implementing QA processes slowly over time, using consensus to reach agreement on processes, and adjusting and
experimenting as an organization grows and matures, productivity will be improved instead of stifled. Problem prevention will
lessen the need for problem detection, panics and burn-out will decrease, and there will be improved focus and less wasted
effort. At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote
computer-based processes and automated tracking and reporting, minimize time required in meetings, and promote training
as part of the QA process. However, no one - especially talented technical types - likes rules or bureaucracy, and in the short
run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but
less time will be required for late-night bug-fixing and calming of irate customers.
146. What if an organization is growing so fast that fixed QA processes are impossible?
This is a common problem in the software industry, especially in new technology areas. There is no easy solution in this
situation, other than:
- Hire good people
- Management should 'ruthlessly prioritize' quality issues and maintain focus on the customer
- Everyone in the organization should be clear on what 'quality' means to the customer
147. How does a client/server environment affect testing?
Client/server applications can be quite complex due to the multiple dependencies among clients, data communications,
hardware, and servers. Thus testing requirements can be extensive. When time is limited (as it usually is) the focus should
be on integration and system testing. Additionally, load/stress/performance testing may be useful in determining client/server
application limitations and capabilities. There are commercial tools to assist with such testing.
148.How can World Wide Web sites be tested?
Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to
the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web
pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts,
database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of
servers and browsers, various versions of each, small but sometimes significant differences between them, variations in
connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for
web sites can become a major ongoing effort. Other considerations might include:
- What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required
under such loads (such as web server response time, database query response times). What kinds of tools will be needed for
performance testing (such as web load testing tools, other tools already in house that can be adapted, web robot
downloading tools, etc.)?
- Who is the target audience? What kind of browsers will they be using? What kind of connection speeds will they by using?
Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide
variety of connection speeds and browser types)?
- What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations,
applets, etc. load and run)?
- Will down time for server and content maintenance/upgrades be allowed? how much?
- What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it expected to do? How can it be
tested?
- How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant
connection requirements and testing?
20
- What processes will be required to manage updates to the web site's content, and what are the requirements for
maintaining, tracking, and controlling page content, graphics, links, etc.?
- Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers?
- Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site??
- How will internal and external links be validated and updated? how often?
- Can testing be done on the production system, or will a separate test system be required? How are browser caching,
variations in browser option settings, dial-up connection variability's, and real-world internet 'traffic congestion' problems to be
accounted for in testing?
- How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the
system and do they require testing?
- How are cgi programs, applets, java scripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested?
- Pages should be 3-5 screens max unless content is tightly focused on a single topic. If larger, provide internal links within
the page.
- The page layouts and design elements should be consistent throughout a site, so that it's clear to the user that they're still
within a site.
- Pages should be as browser-independent as possible, or pages should be provided or generated based on the browser-
type.
- All pages should have links external to the page; there should be no dead-end pages.
- The page owner, revision date, and a link to a contact person or organization should be included on each page
149. How is testing affected by object-oriented designs?
Well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to
requirements. While there will be little affect on black box testing (where an understanding of the internal design of the
application is unnecessary), white-box testing can be oriented to the application's objects. If the application was well-
designed this can simplify test design.
150. What is Extreme Programming and what's it got to do with testing?
Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable
requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained'.
Testing ('extreme testing') is a core aspect of Extreme Programming. Programmers are expected to write unit and functional
test code first - before the application is developed. Test code is under source control along with the rest of the code.
Customers are expected to be an integral part of the project team and to help developed scenarios for acceptance/black box
testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development
iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements
documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected.
151. Will automated testing tools make testing easier?
- Possibly. For small projects, the time needed to learn and implement them may not be worth it. For larger projects, or on-
going long-term projects they can be valuable.
- A common type of automated tool is the 'record/playback' type. For example, a tester could click through all combinations of
menu choices, dialog box choices, buttons, etc. in an application GUI and have them 'recorded' and the results logged by a
tool. The 'recording' is typically in the form of text based on a scripting language that is interpretable by the testing tool. If new
buttons are added, or some underlying code in the application is changed, etc. the application can then be retested by just
'playing back' the 'recorded' actions, and comparing the logging results to check effects of the changes. The problem with
such tools is that if there are continual changes to the system being tested, the 'recordings' may have to be changed so much
that it becomes very time-consuming to continuously update the scripts. Additionally, interpretation of results (screens, data,
logs, etc.) can be a difficult task. Note that there are record/playback tools for text-based interfaces also, and for all types of
platforms.
- Other automated tools can include:
code analyzers - monitor code complexity, adherence to standards, etc.
coverage analyzers - these tools check which parts of the code have been exercised by a test, and may be oriented to code
statement coverage, condition coverage, path coverage, etc.
memory analyzers - such as bounds-checkers and leak detectors.
load/performance test tools - for testing client/server and web applications under various load levels.
web test tools - to check that links are valid, HTML code usage is correct, client-side and server-side programs work, a web
site's interactions are secure.
other tools - for test case management, documentation management, bug reporting, and configuration management.
151. What's the difference between black box and white box testing?
Black-box and white-box are test design methods. Black-box test design treats the system as a “black-box”, so it doesn't
explicitly use knowledge of the internal structure. Black-box test design is usually described as focusing on testing functional
requirements. Synonyms for black-box include: behavioral, functional, opaque-box, and closed-box. White-box test design
allows one to peek inside the “box”, and it focuses specifically on using internal knowledge of the software to guide the
selection of test data. Synonyms for white-box include: structural, glass-box and clear-box.
While black-box and white-box are terms that are still in popular use, many people prefer the terms 'behavioral' and
'structural'. Behavioral test design is slightly different from black-box test design because the use of internal knowledge isn't
21
strictly forbidden, but it's still discouraged. In practice, it hasn't proven useful to use a single test design method. One has to
use a mixture of different methods so that they aren't hindered by the limitations of a particular one. Some call this 'gray-box'
or 'translucent-box' test design, but others wish we'd stop talking about boxes altogether.
It is important to understand that these methods are used during the test design phase, and their influence is hard to see in
the tests once they're implemented. Note that any level of testing (unit testing, system testing, etc.) can use any test design
methods. Unit testing is usually associated with structural test design, but this is because testers usually don't have well-
defined requirements at the unit level to validate.
152. What kinds of testing should be considered?
Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and
functionality.
White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code
statements, branches, paths, conditions.
Unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the
programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily
done unless the application has a well-designed architecture with tight code; may require developing test driver modules or
test harnesses.
incremental integration testing - continuous testing of an application as new functionality is added; requires that various
aspects of an application's functionality be independent enough to work separately before all parts of the program are
completed, or that test drivers be developed as needed; done by programmers or by testers.
Integration testing - testing of combined parts of an application to determine if they function together correctly. The 'parts'
can be code modules, individual applications, client and server applications on a network, etc. This type of testing is
especially relevant to client/server and distributed systems. functional testing - black-box type testing geared to functional
requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers
shouldn't check that their code works before releasing it (which of course applies to any stage of testing.) system testing -
black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
End-to-end testing - similar to system testing; the 'macro' end of the test scale; involves testing of a complete application
environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or
interacting with other hardware, applications, or systems if appropriate.
Sanity testing or smoke testing - typically an initial testing effort to determine if a new software version is performing well
enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging
down systems to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further
testing in its current state.
Regression testing - re-testing after fixes or modifications of the software or its environment. It can be difficult to determine
how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially
useful for this type of testing.
acceptance testing - final testing based on specifications of the end-user or customer, or based on use by end-
users/customers over some limited period of time.
Load testing - testing an application under heavy loads, such as testing of a web site under a range of loads to determine at
what point the system's response time degrades or fails.
stress testing - term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as
system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large
numerical values, large complex queries to a database system, etc. performance testing - term often used interchangeably
with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements
documentation or QA or Test Plans.
usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or
customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and
testers are usually not appropriate as usability testers.
install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes. recovery testing - testing how well a
system recovers from crashes, hardware failures, or other catastrophic problems.
Failover testing - typically used interchangeably with 'recovery testing'
Security testing - testing how well the system protects against unauthorized internal or external access, willful damage, etc;
may require sophisticated testing techniques.
Compatibility testing - testing how well software performs in a particular hardware/software/operating system/network/etc.
environment.
exploratory testing - often taken to mean a creative, informal software test that is not based on formal test plans or test
cases; testers may be learning the software as they test it. ad-hoc testing - similar to exploratory testing, but often taken to
mean that the testers have significant understanding of the software before testing it.
Context-driven testing - testing driven by an understanding of the environment, culture, and intended use of software. For
example, the testing approach for life-critical medical equipment software would be completely different than that for a low-
cost computer game.
User acceptance testing - determining if software is satisfactory to an end-user or customer. comparison testing -
comparing software weaknesses and strengths to competing products. alpha testing - testing of an application when
development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by
end-users or others, not by programmers or testers.
Beta testing - testing when development and testing are essentially completed and final bugs and problems need to be
22
found before final release. Typically done by end-users or others, not by programmers or testers. mutation testing - a method
for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and
retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large
computational resources
151. Why is it often hard for management to get serious about quality assurance?
Solving problems is a high-visibility process; preventing problems is low-visibility.
This is illustrated by an old parable:
In ancient China there was a family of healers, one of whom was known throughout the land and employed as a physician to
a great lord. The physician was asked which of his family was the most skillful healer. He replied, "I tend to the sick and dying
with drastic and dramatic treatments, and on occasion someone is cured and my name gets out among the lords."
"My elder brother cures sickness when it just begins to take root, and his skills are known among the local peasants and
neighbors."
"My eldest brother is able to sense the spirit of sickness and eradicate it before it takes form. His name is unknown outside
our home."
152. Why does software have bugs?
1. Miscommunication or no communication - as to specifics of what an application should or shouldn't do (the application's
requirements).
2. Software complexity - the complexity of current software applications can be difficult to comprehend for anyone without
experience in modern-day software development. Multi-tiered applications, client-server and distributed applications, data
communications, enormous relational databases, and sheer size of applications have all contributed to the exponential
growth in software/system complexity. programming errors - programmers, like anyone else, can make mistakes.
3. Changing requirements (whether documented or undocumented) - the end-user may not understand the effects of
changes, or may understand and request them anyway - redesign, rescheduling of engineers, effects on other projects, work
already completed that may have to be redone or thrown out, hardware requirements that may be affected, etc. If there are
many minor changes or any major changes, known and unknown dependencies among parts of the project are likely to
interact and cause problems, and the complexity of coordinating changes may result in errors. Enthusiasm of engineering
staff may be affected. In some fast-changing business environments, continuously modified requirements may be a fact of
life. In this case, management must understand the resulting risks, and QA and test engineers must adapt and plan for
continuous extensive testing to keep the inevitable bugs from running out of control.
3. Poorly documented code - it's tough to maintain and modify code that is badly written or poorly documented; the result is
bugs. In many organizations management provides no incentive for programmers to document their code or write clear,
understandable, maintainable code. In fact, it's usually the opposite: they get points mostly for quickly turning out code, and
there's job security if nobody else can understand it ('if it was hard to write, it should be hard to read').
4. software development tools - visual tools, class libraries, compilers, scripting tools, etc. often introduce their own bugs or
are poorly documented, resulting in added bugs.
153. How can new Software QA processes be introduced in an existing organization?
A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives or
property) projects, serious management buy-in is required and a formalized QA process is necessary.
Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time
process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand.
For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects. A
lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among
customers, managers, developers, and testers.
The most value for effort will often be in
(a) requirements management processes, with a goal of clear, complete, testable requirement specifications embodied in
requirements or design documentation, or in 'agile'-type environments extensive continuous coordination with end-users,
(b) design inspections and code inspections, and
(c) post-mortems/retrospectives.
154. how do the companies expect the defect reporting to be communicated by the tester to the development team.
Can the excel sheet template be used for defect reporting. If so what are the common fields that are to be included ?
who assigns the priority and severity of the defect
To report bugs in excel:
Sno. Module Screen/ Section Issue detail Severity
Prioriety Issue status

this is how to report bugs in excel sheet and also set filters on the Columns attributes.

But most of the companies use the share point process of reporting bugs In this when the project came for testing a module
wise detail of project is inserted to the defect managment system they are using. It contains following field
1. Date
2. Issue brief
3. Issue discription(used for developer to regenerate the issue)
23
4. Issue status( active, resolved, on hold, suspend and not able to regenerate)
5. Assign to (Names of members allocated to project)
6. Prioriety(High, medium and low)
7. severity (Major, medium and low)
155. What are the tables in testplans and testcases?
Test plan is a document that contains the scope, approach, test design and test strategies. It includes the following:-
1. Test case identifier
2. Scope
3.Features to be tested
4. Features not to be tested.
5. Test strategy.
6. Test Approach
7. Test Deliverables
8. Responsibilities.
9 Staffing and Training
10.Risk and Contingencies
11. Approval

While A test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to
confirm its functionality/behavior to certain set of inputs.
156. What are the table contents in testplans and test cases?
Test Plan is a document which is prepared with the details of the testing priority. A test Plan generally includes:

1. Objective of Testing
2. Scope of Testing
3. Reason for testing
4. Timeframe
5. Environment
6. Entrance and exit criteria
7. Risk factors involved
8. Deliverables
157. What automating testing tools are you familiar with?
Win Runner , Load runner, QTP , Silk Performer, Test director, Rational robot, QA run.
158. How did you use automating testing tools in your job?
1. For regression testing
2. Criteria to decide the condition of a particular build
3. Describe some problem that you had with automating testing tool.

The problem of win runner identifying the third party controls like infragistics control.
159. How do you plan test automation?
1. Prepare the automation Test plan
2. Identify the scenario
3. Record the scenario
4. Enhance the scripts by inserting check points and Conditional Loops
5. Incorporated Error Handler
6. Debug the script
7. Fix the issue
8. Rerun the script and report the result.
160. Can test automation improve test effectiveness?

Yes, Automating a test makes the test process:

1.Fast
2.Reliable
3. Repeatable
4.Programmable
5.Reusable
6.Comprehensive
6. What is data - driven automation?

Testing the functionality with more test cases becomes laborious as the functionality grows. For multiple sets of data (test
24
cases), you can execute the test once in which you can figure out for which data it has failed and for which data, the test has
passed. This feature is available in the WinRunner with the data driven test where the data can be taken from an excel sheet
or notepad.
161. What are the main attributes of test automation?
software test automation attributes :
Maintainability - the effort needed to update the test automation suites for each new release
Reliability - the accuracy and repeatability of the test automation
Flexibility - the ease of working with all the different kinds of automation test ware
Efficiency - the total cost related to the effort needed for the automation
Portability - the ability of the automated test to run on different environments
Robustness - the effectiveness of automation on an unstable or rapidly changing system
Usability - the extent to which automation can be used by different types of users

162. Does automation replace manual testing?

There can be some functionality which cannot be tested in an automated tool so we may have to do it manually. therefore
manual testing can never be replaced. (We can write the scripts for negative testing also but it is hectic task).When we talk
about real environment we do negative testing manually.
163. How will you choose a tool for test automation?
choosing of a tool defends on many things ...
1. Application to be tested
2. Test environment
3. Scope and limitation of the tool.
4. Feature of the tool.
5. Cost of the tool.
6. Whether the tool is compatible with your application which means tool should be able to interact with your application
7. Ease of use
164. How you will evaluate the tool for test automation?
We need to concentrate on the features of the tools and how this could be benficial for our project. The additional new
features and the enhancements of the features will also help.
165. What are main benefits of test automation?
FAST ,RELIABLE,COMPREHENSIVE,REUSABLE
166. What could go wrong with test automation?
1. The choice of automation tool for certain technologies 2. Wrong set of test automated
167. How you will describe testing activities?
Testing activities start from the elaboration phase. The various testing activities are preparing the test plan, Preparing test
cases, Execute the test case, Log teh bug, validate the bug & take appropriate action for the bug, Automate the test cases.
168. What testing activities you may want to automate?
Automate all the high priority test cases which needs to be executed as a part of regression testing for each build cycle.
169. Describe common problems of test automation.
The common problems are:
1. Maintenance of the old script when there is a feature change or enhancement
2. The change in technology of the application will affect the old scripts
170. What types of scripting techniques for test automation do you know?
5 types of scripting techniques:
Linear
Structured
Shared
Data Driven
Key Driven
171. What are principles of good testing scripts for automation?
1. Proper code guiding standards
2. Standard format for defining functions, exception handler etc
3. Comments for functions
4. Proper error handling mechanisms
25
5. The appropriate synchronization techniques
18. What tools are available for support of testing during software development life cycle?

Testing tools for regression and load/stress testing for regression testing like, QTP, load runner, rational robot, win runner,
silk, test complete, Astra are available in the market. -For defect tracking Bug Zilla, Test Runner are available.
172. Can the activities of test case design be automated?
As I know it, test case design is about formulating the steps to be carried out to verify something about the application under
test. And this cannot be automated. However, I agree that the process of putting the test results into the excel sheet.
173. What are the limitations of automating software testing?
Hard-to-create environments like “out of memory”, “invalid input/reply”, and “corrupt registry entries” make applications
behave poorly and existing automated tools can’t force these condition - they simply test your application in “normal”
environment
174. What skills needed to be a good test automator?
1.Good Logic for programming.
2. Analytical sklls.
3.Pessimestic in Nature.
175. How to find that tools work well with your existing system?
1. Discuss with the support officials
2. Download the trial version of the tool and evaluate
3. Get suggestions from people who are working on the tool
176. Describe some problem that you had with automating testing tool
1. The inability of win runner to identify the third party control like infragistics controls
2. The change of the location of the table object will cause object not found error.
3. The inability of the win runner to execute the script against multiple languages
177. What are the main attributes of test automation?
Maintainability, Reliability, Flexibility, Efficiency, Portability, Robustness, and Usability - these are the main attributes in test
automation.
178. What testing activities you may want to automate in a project?
Testing tools can be used for :
* Sanity tests (which is repeated on every build),
* stress/Load test's simulate a large no of users, which is manually impossible) &
* Regression tests (which are done after every code change)
179. How to find that tools work well with your existing system?
To find this, select the suite of tests which are most important for your application. First run them with automated tool. Next
subject the same tests to careful manual testing. If the results are coinciding you can say your testing tool has been
performing.
180. How will you test the field that generates auto numbers of AUT when we click the button 'NEW" in the
application?
We can create a textile in a certain location, and update the auto generated value each time we run the test and compare the
currently generated value with the previous one will be one solution.
181. How will you evaluate the fields in the application under test using automation tool?
We can use Verification points (rational Robot) to validate the fields .Ex. Using object data ,object data properties VP we can
validate fields
182. Can we perform the test of single application at the same time using different tools on the same machine?
No. The Testing Tools will be in the ambiguity to determine which browser is opened by which tool.
183. Difference between Web application Testing and Client Server Testing. State the different types for Web
application Testing and Client Server Testing types?
which win runner 7.2 version compatible with internet explorer, firefox, n.n
184. What is 'configuration management'?
Configuration management is a process to control and document any changes made during the life of a project. Revision
control, Change Control, and Release Control are important aspects of Configuration Management.
185. How to test the Web applications?

26
The basic difference in web testing is here we have to test for URL's coverage and links coverage. Using Win Runner we can
conduct web testing. But we have to make sure that Web test option is selected in "Add in Manager". Using WR we cannot
test XML objects.
186. What are the problems encountered during the testing the application compatibility on different browsers and
on different operating systems
Font issues, alignment issues
188. How exactly the testing the application compatibility on different browsers and on different operating systems
is done
Please submit Your Suggestion to our forum http://forum.qabricks.com
189. How testing is proceeded when SRS or any other document is not given?
If SRS is not there we can perform Exploratory testing. In Exploratory testing the basic module is executed and depending on
its results, the next plan is executed
190. How do we test for severe memory leakages ?
By using Endurance Testing . Endurance Testing means checking for memory leaks or other problems that may occur with
prolonged execution.
191. What is the difference between quality assurance and testing?
Quality assurance involves the entire software development process and testing involves operation of a system or application
to evaluate the results under certain conditions. QA is oriented to prevention and Testing is oriented to detection.
192. Why does software have bugs?
1.miscommunication
2.programming errors
3.time pressures.
4.changing requirements
5.software complexity
193. What is memory leaks and buffer overflows ?
Memory leaks means incomplete deal location - are bugs that happen very often. Buffer overflow means data sent as input to
the server that overflows the boundaries of the input area, thus causing the server to misbehave. Buffer overflows can be
used.
194. what are the major differences between stress testing ,load testing ,Volume testing?
Stress testing means increasing the load ,and checking the performance at each level. Load testing means at a time giving
more load by the expectation and checking the performance at that level. Volume testing means first we have to apply initial.
Software Quality Assurance Interview Questions only (1)
• What automating testing tools are you familiar with?
• How did you use automating testing tools in your job?
• Describe some problem that you had with automating testing tool.
• How do you plan test automation?
• Can test automation improve test effectiveness?
• What is data - driven automation?
• What are the main attributes of test automation?
• Does automation replace manual testing?
• How will you choose a tool for test automation?
• How you will evaluate the tool for test automation?
• What are main benefits of test automation?
• What could go wrong with test automation?
• How you will describe testing activities?
• What testing activities you may want to automate?
• Are regression tests required or do you feel there is a better use for resources?

27
• Our software designers use UML for modeling applications. Based on their use cases, we would like to plan a test
strategy. Do you agree with this approach or would this mean more effort for the testers.
• Tell me about a difficult time you had at work and how you worked through it.
• Give me an example of something you tried at work but did not work out so you had to go at things another way.
• How can one file compare future dated output files from a program which has change, against the baseline run which
used current date for input. The client does not want to mask dates on the output files to allow compares
• Tell me about the worst boss you've ever had.
• What are your greatest weaknesses?
• What are your strengths?
• What is a successful product?
• What do you like about Windows?
• What is good code?
• What are basic, core, practices for a QA specialist?
• What do you like about QA?
• What has not worked well in your previous QA experience and what would you change?
• you will begin to improve the QA process?
• What is the difference between QA and QC?
• What is UML and how to use it for testing?
• What is CMMI?
• What do you like about computers?
• Do you have a favourite QA book? More than one? Which ones? And why.
• What is the responsibility of programmers vs QA?
• What are the properties of a good requirement?
• How to do test if we have minimal or no documentation about the product
Software Quality Assurance Interview Questions only (2)
• What are all the basic elements in a defect report?
• Is an "A fast database retrieval rate" a testable requirement?
• What is software quality assurance?
• What is the value of a testing group? How do you justify your work and budget?
• What is the role of the test group vis-à-vis documentation, tech support, and so forth?
• How much interaction with users should testers have, and why?
• How should you learn about problems discovered in the field, and what should you learn from those problems?
• What are the roles of glass-box and black-box testing tools?
• What issues come up in test automation, and how do you manage them?
• What development model should programmers and the test group use?
• How do you get programmers to build testability support into their code?
• What is the role of a bug tracking system?
• What are the key challenges of testing?
• Have you ever completely tested any part of a product? How?
• Have you done exploratory or specification-driven testing?

28
 • Should every business test its software the same way?
• Discuss the economics of automation and the role of metrics in testing.
• Describe components of a typical test plan, such as tools for interactive products and for database products, as well
as cause-and-effect graphs and data-flow diagrams.
• When have you had to focus on data integrity?
• What are some of the typical bugs you encountered in your last assignment?
• How do you prioritize testing tasks within a project?
• How do you develop a test plan and schedule? Describe bottom-up and top-down approaches.
• When should you begin test planning?
• When should you begin testing?
• Do you know of metrics that help you estimate the size of the testing effort?
• How do you scope out the size of the testing effort?
• How many hours a week should a tester work?
• How should your staff be managed? How about your overtime?
• How do you estimate staff requirements?
• What do you do (with the project tasks) when the schedule fails?
• How do you handle conflict with programmers?
• How do you know when the product is tested well enough?
• What characteristics would you seek in a candidate for test-group manager?
• What do you think the role of test-group manager should be? Relative to senior management? Relative to other
technical groups in the company? Relative to your staff?
• How do your characteristics compare to the profile of the ideal manager that you just described?
• How does your preferred work style work with the ideal test-manager role that you just described? What is different
between the way you work and the role you described?
• Who should you hire in a testing group and why?
• What is the role of metrics in comparing staff performance in human resources management?
• How do you estimate staff requirements?
• What do you do (with the project staff) when the schedule fails?
• Describe some staff conflicts youÂ’ve handled.
• Why did you ever become involved in QA/testing?
• What is the difference between testing and Quality Assurance?
• What was a problem you had in your previous assignment (testing if possible)? How did you resolve it?
• What are two of your strengths that you will bring to our QA/testing team?
Software Quality Assurance Interview Questions only (3)
• What do you like most about Quality Assurance/Testing?
• What do you like least about Quality Assurance/Testing?
• What is the Waterfall Development Method and do you agree with all the steps?
• What is the V-Model Development Method and do you agree with this model?
• What is a "Good Tester"?
• Could you tell me two things you did in your previous assignment (QA/Testing related hopefully) that you are proud
of?

29
 • List 5 words that best describe your strengths.
• What are two of your weaknesses?
• What methodologies have you used to develop test cases?
• In an application currently in production, one module of code is being modified. Is it necessary to re- test the whole
application or is it enough to just test functionality associated with that module?
• How do you go about going into a new organization? How do you assimilate?
• Define the following and explain their usefulness: Change Management, Configuration Management, Version
Control, and Defect Tracking.
• What is ISO 9000? Have you ever been in an ISO shop?
• When are you done testing?
• What is the difference between a test strategy and a test plan?
• What is ISO 9003? Why is it important
• What are ISO standards? Why are they important?
• What is IEEE 829? (This standard is important for Software Test Documentation-Why?)
• What is IEEE? Why is it important?
• Do you support automated testing? Why?
• We have a testing assignment that is time-driven. Do you think automated tests are the best solution?
• What is your experience with change control? Our development team has only 10 members. Do you think managing
change is such a big deal for us?
• Are reusable test cases a big plus of automated testing and explain why.
• Can you build a good audit trail using Compuware's QACenter products. Explain why.
• How important is Change Management in today's computing environments?
• Do you think tools are required for managing change. Explain and please list some tools/practices which can help
you managing change.
• We believe in ad-hoc software processes for projects. Do you agree with this? Please explain your answer.
• When is a good time for system testing?
Software Quality Assurance Interview Questions only (4)
• How would you categorize the severity of defects?
• Where do you imagine you will be spending the bulk of your time?
• When do you know you have tested enough?
• What types of documents would you need for QA, QC, and Testing?
• What did you include in a test plan?
• Describe any bug you remember.
• What is the purpose of the testing?
• What do you like (not like) in this job?
• What is quality assurance?
• What is the difference between QA and testing?
• How do you scope, organize, and execute a test project?
• What is the role of QA in a development project?
• What is the role of QA in a company that produces software?
• Define quality for me as you understand it

30
 • Describe to me the difference between validation and verification.
• Describe to me what you see as a process. Not a particular process, just the basics of having a process.
• Describe to me when you would consider employing a failure mode and effect analysis.
• Describe to me the Software Development Life Cycle as you would define it.
• What are the properties of a good requirement?
• How do you differentiate the roles of Quality Assurance Manager and Project Manager?
• Tell me about any quality efforts you have overseen or implemented. Describe some of the challenges you faced
and how you overcame them.
• How do you deal with environments that are hostile to quality change efforts?
• In general, how do you see automation fitting into the overall process of testing?
• How do you promote the concept of phase containment and defect prevention?
• If you come onboard, give me a general idea of what your first overall tasks will be as far as starting a quality effort.
• What kinds of testing have you done?
• Have you ever created a test plan?
• Have you ever written test cases or did you just execute those written by others?
• What did your base your test cases?
• You are the test manager starting on system testing. The development team says that due to a change in the
requirements, they will be able to deliver the system for SQA 5 days past the deadline. You cannot change the
resources (work hours, days, or test tools). What steps will you take to be able to finish the testing in time?
• Your company is about to roll out an e-commerce application. It’s not possible to test the application on all types of
browsers on all platforms and operating systems. What steps would you take in the testing environment to reduce
the business risks and commercial risks?
• In your organization, testers are delivering code for system testing without performing unit testing. Give an example
of test policy:
○ Policy statement
○ Methodology
○ Measurement
• Testers in your organization are performing tests on the deliverables even after significant defects have been found.
This has resulted in unnecessary testing of little value, because re-testing needs to be done after defects have been
rectified. You are going to update the test plan with recommendations on when to halt testing. Wwhat
recommendations are you going to make?

• How do you measure:

Test Effectiveness
Test Efficiency
• You found out the senior testers are making more mistakes then junior testers; you need to communicate this
aspect to the senior tester. Also, you don’t want to lose this tester. How should one go about constructive criticism?
• You are assigned to be the test lead for a new program that will automate take-offs and landings at an airport. How
would you write a test strategy for this new program?
Software Quality Assurance Interview Questions only (5)
• What are the properties of a good requirement?
• Ho to do test if we have minimal or no documentation about the product?
• What are all the basic elements in a defect report?
• Is an "A fast database retrieval rate" a testable requirement?
• What is software quality assurance?
• What is the value of a testing group? How do you justify your work and budget?
31
• What is the role of the test group vis- is documentation, tech support, and so forth?
• How much interaction with users should testers have, and why?
• How should you learn about problems discovered in the field, and what should you learn from those problems?
• What are the roles of glass-box and black-box testing tools?
• What issues come up in test automation, and how do you manage them?
• What development model should programmers and the test group use?
• How do you get programmers to build testability support into their code?
• What is the role of a bug tracking system?
• What are the key challenges of testing?
• Have you ever completely tested any part of a product? How?
• Have you done exploratory or specification-driven testing?
• Should every business test its software the same way?
• Discuss the economics of automation and the role of metrics in testing.
• Describe components of a typical test plan, such as tools for interactive products and for database products, as well
as cause-and-effect graphs and data-flow diagrams.
• When have you had to focus on data integrity?
• What are some of the typical bugs you encountered in your last assignment?
• How do you prioritize testing tasks within a project?
• How do you develop a test plan and schedule? Describe bottom-up and top-down approaches.
• When should you begin test planning?
• When should you begin testing?
• Do you know of metrics that help you estimate the size of the testing effort?
• How do you scope out the size of the testing effort?
• How many hours a week should a tester work?
• How should your staff be managed? How about your overtime?
• How do you estimate staff requirements?
• What do you do (with the project tasks) when the schedule fails?
• How do you handle conflict with programmers?
• How do you know when the product is tested well enough?
• What characteristics would you seek in a candidate for test-group manager?
• What do you think the role of test-group manager should be? Relative to senior management? Relative to other
technical groups in the company? Relative to your staff?
• How do your characteristics compare to the profile of the ideal manager that you just described?
• How does your preferred work style work with the ideal test-manager role that you just described? What is different
between the way you work and the role you described?
• Who should you hire in a testing group and why?
• What is the role of metrics in comparing staff performance in human resources management?
• How do you estimate staff requirements?
• What do you do (with the project staff) when the schedule fails?
• Describe some staff conflicts you?ve handled.
• Is automation (or testing) a label for other problems?
32
 • Are testers trying to use automation to prove their prowess?
• Can testability features be added to the product code?
• Do testers and developers work cooperatively and with mutual respect?
• Is automation is developed on an iterative basis?
• Have you defined the requirements and success criteria for automation?
• Are you open to different concepts of what test automation can mean?
• Is test automation lead by someone with an understanding of both programming and testing?
Software Quality Assurance Interview Questions only (6)
• What are the benefits of creating multiple actions within any virtual user script?
• How you used Win Runner in your project?
• Explain Win Runner testing process?
• What is contained in the GUI map in Win Runner?
• How does Win Runner recognize objects on the application?
• Have you created test scripts and what is contained in the test scripts in Win Runner?
• How does Win Runner evaluate test results?
• Have you performed debugging of the scripts in Win Runner?
• How do you run your test scripts in Win Runner ?
• How do you analyze results and report the defects in Win Runner?
• What is the use of Test Director software in Win Runner?
• Have you integrated your automated scripts from Test Director in Win Runner?
• What is the purpose of loading Win Runner Add-Ins?
• What is meant by the logical name of the object in Win Runner?
• If the object does not have a name then what will be the logical name in Win Runner?
• What is the different between GUI map and GUI map files in Win Runner?
• How do you view the contents of the GUI map in Win Runner?
• When you create GUI map do you record all the objects of specific objects in Win Runner?
• What is load testing?
• What is Performance testing?
• Explain the Load testing process? Load Runner Version 7.2
• When do you do load and performance Testing?
• What are the components of Load Runner?
• What Component of Load Runner would you use to record a Script?
• When do you do load and performance Testing?
• What are the components of Load Runner?
• What Component of Load Runner would you use to play Back the script in multi user mode?
• What is a rendezvous point about Load Runner?
• What is a scenario about Load Runner?
• Explain the recording mode for web Vuser script about Load Runner?
• Why do you create parameters about Load Runner?
• What is correlation Load Runner? Explain the difference between automatic correlation and manual correlation?
33
 • How do you find out where correlation is required Load Runner? Give few examples from your projects?
• Where do you set automatic correlation options about Load Runner?
1. When do you disable log in Virtual User Generator, When do you choose standard and extended logs about Load
Runner?
2. What is a function to capture dynamic values in the web Vuser script about Load Runner?
3. How do you debug a Load Runner script?
4. How do you write user defined functions in Load Runner?
5. What are the changes you can make in run-time settings about Load Runner?
6. Where do you set Iteration for Vuser testing about Load Runner?
7. How do you perform functional testing under load about Load Runner?
8. What is Ramp up? How do you set this about Load Runner?
9. What is the advantage of running the Vuser as thread? about Load Runner
10. If you want to stop the execution of your script on error about Load Runner, how do you do that?
11. What is the relation between Response Time and Throughput about Load Runner?
12. Explain the Configuration of your systems about Load Runner?
13. How do you identify the performance bottlenecks about Load Runner?
14. How did you find database related issues about Load Runner?
15. What is the difference between Overlay graph and Correlate graph? about Load Runner
16. How did you plan the Load? What are the Criteria about Load Runner?
17. What does vuser_init action contain about Load Runner?
18. What does vuser_end action contain about Load Runner?
Software Quality Assurance Interview Questions only (7)
1. Who should be involved in each level of testing? What should be their responsibilities?
a. You have more verifiable QA experience testing:
b. Java APIs
c. End user applications using third-party automated test tools
d. End user applications using manual testing and in-house test tools
2. Your professional experience debugging, developing test cases and running system tests for developed subsystems
and features is:
a. N/A - I do not have experience in these areas.
b. I have this experience on 1 to 3 commercial product launches or product integrations.
c. I have this experience on 4 to 6 commercial product launches or product integrations.
d. I have this experience on 7 to 10 or more commercial product launches or product integrations.
3. You have personally created the following number of test plans or test cases:
e. N/A - I would be new to creating test plans or test cases
f. For 1 to 3 product releases
g. For 4 to 6 product releases
h. For 7 to 10 product releases
4. What is an advantage of black box testing over white box testing:
i. Tests give confidence that the program meets its specifications
j. Tests can be done while the program is being written instead of waiting until it is finished
k. It insures that every piece of code written is tested in some way
l. Tests give confidence that every part of the code is working

34
 5. What is an advantage of white box testing over black box testing:
m. Tests can discover that some code is missing
n. Tests can be done while the program is being written instead of waiting until it is finished
o. Tests can be designed before a program is written
p. Tests give confidence that the program meets its specifications
6. Your experience with Programming within the context of Quality Assurance is:
q. N/A - I have no programming experience in C, C++ or Java.
r. You have done some programming in my role as a QA Engineer, and am comfortable meeting such
requirements in Java, C and C++ or VC++.
s. You have developed applications of moderate complexity that have taken up to three months to complete.
7. Your skill in maintaining and debugging an application is best described as:
t. N/A - You have not participated in debugging a product.
u. You have worked under the mentorship of a team lead to learn various debugging techniques and
strategies.
v. You have both an interest in getting to the root of a problem and understand the steps You need to take to
document it fully for the developer.
w. You am experienced in working with great autonomy on debugging/maintenance efforts and have a track
record of successful projects You can discuss.
a. Why does testing not prove a program is 100 percent correct (except for extremely simple programs)? Because we can only
test a finite number of cases, but the program may have an infinite number of possible combinations of inputs and outputs
a. Because the people who test the program are not the people who write the code
b. Because the program is too long
c. All of the above
d. We CAN prove a program is 100 percent correct by testing
Which statement regarding Validation is correct:
a. It refers to the set of activities that ensures the software has been built according to the customer's
requirements.
b. It refers to the set of activities that ensure the software correctly implements specific functions
Software Quality Assurance Interview Questions only (8)
What is unit testing?
a. A technique to ensure that every unique sequence of commands through a program is executed
b. Testing pieces of a program (usually classes) independently using test drivers and/or stubs
c. Testing using inputs that are derived from a statement of what the program is supposed to do
d. Testing of increasingly more complete versions of a program
Which of the following is used to determine whether all reported bugs have indeed been fixed, and no new ones introduced:
a. Regression
b. Matrix
c. Performance
d. Functional
e. White Box
a) Which of the following is not correct regarding the purpose of testing:
a. To verify that a program works correctly
b. To verify that a program matches the initial specifications
c. To prove a program is 100 percent correct in all cases
35
 d. To uncover bugs that are then fixed via debugging
• Which of the following testing strategies ignores the internal structure of the software?
a. Interface testing
b. Top down testing
c. White box testing
d. Black box testing
e. Sandwich testing

Regarding your experience with XML:

e. N/A - You would be new to using XML.
f. You have a basic understanding of its use.
g. You have experience using XML to transfer and transform data.>
h. ou have significant experience creating XML schema and creating applications for data transfer.
I have the following experience writing SQL queries:
a. You would be new to writing SQL queries.
b. You have written simple SQL queries.
c. You have written medium difficulty SQL queries.
d. You have written complex SQL queries that included joins.
I have the following experience writing Shell Scripts:
a. You would be new to writing Shell Scripts.
b. You have a basic understanding of Shell Scripts.
c. You have experience writing Shell Scripts.
d. You have significant experience creating complex Shell Scripts
Regarding the use of a computer, You am:
a. An expert with computers, the Internet and Windows, and am often asked to help others.
b. New to computers and would need a little help to get started.
c. Comfortable with e-mail and the Internet, but would need help with other applications required for the
position.
d. Comfortable with e-mail and a variety of computer software, but not an expert.
Your knowledge and experience in Linux is:
a. N/A - You have no direct Linux operating system experience. d need help to become functionally proficient.
b. You have a good understanding of Linux and run this OS on Your home PC.
c. You have experience with multiple Linux variants and feel as comfortable with it as most people do working
in Windows.
The highest level of education Youhave attained is:
a. High school diploma
b. Some college experience, but no BS/BA degree, with relevant QA experience.
c. An undergraduate degree in Computer Science or related field.
d. An undergraduate degree in Computer Science or related field, or comparable working experience
Software Quality Assurance Interview Questions only (9)
• Are regression tests required or do you feel there is a better use for resources?
• Our software designers use UML for modeling applications. Based on their use cases, we would like to plan a test
strategy. Do you agree with this approach or would this mean more effort for the testers.
• Tell me about a difficult time you had at work and how you worked through it.
• Give me an example of something you tried at work but did not work out so you had to go at things another way.

36
• How can one file compare future dated output files from a program which has change, against the baseline run
which used current date for input. The client does not want to mask dates on the output files to allow compares. -
Answer-Rerun baseline and future date input files same # of days as future dated run of program with change. Now
run a file compare against the baseline future dated output and the changed programs' future dated output.
• What is the structure of the company?
• Who is going to do the interview-possible background information of interviewer?
• What is the employer's environment (platforms, tools, etc.)?
•
• What are the employer's methods and processes used in software arena?
• What is the employer's philosophy?
• What automating testing tools are you familiar with?
• How did you use automating testing tools in your job?
• Describe some problem that you had with automating testing tool.
• How do you plan test automation?
• Can test automation improve test effectiveness?
• What is Negative testing?
• What was a problem you had in your previous assignment (testing if possible)? How did you resolve it?
• What are two of your strengths that you will bring to our QA/testing team?
• How would you define Quality Assurance?
• What do you like most about Quality Assurance/Testing?
• What do you like least about Quality Assurance/Testing?
• What is the Waterfall Development Method and do you agree with all the steps?
• What is the V-Model Development Method and do you agree with this model?
• What is the Capability Maturity Model (CMM)? At what CMM level were the last few companies you worked?
• What is a "Good Tester"?
• Could you tell me two things you did in your previous assignment (QA/Testing related hopefully) that you are proud
of?
• List 5 words that best describe your strengths.
• What are two of your weaknesses?
• What methodologies have you used to develop test cases?
• In an application currently in production, one module of code is being modified. Is it necessary to re- test the whole
application or is it enough to just test functionality associated with that module?
• Define each of the following and explain how each relates to the other: Unit, System, and Integration testing.
• Define Verification and Validation. Explain the differences between the two.
• Explain the differences between White-box, Gray-box, and Black-box testing.
• How do you go about going into a new organization? How do you assimilate?
• Define the following and explain their usefulness: Change Management, Configuration Management, Version
Control, and Defect Tracking.
• What is ISO 9000? Have you ever been in an ISO shop?
• When are you done testing?
• What is the difference between a test strategy and a test plan?
• What is ISO 9003? Why is it important

37
 • What are ISO standards? Why are they important?
• What is IEEE 829? (This standard is important for Software Test Documentation-Why?)
• What is IEEE? Why is it important?
Software Quality Assurance Interview Questions only 10)
• How do you determine what to test?
• How do you decide when you have 'tested enough?'
• How do you test if you have minimal or no documentation about the product?
• Describe me to the basic elements you put in a defect report?
• How do you perform regression testing?
• At what stage of the life cycle does testing begin in your opinion?
• How do you analyze your test results? What metrics do you try to provide?
• Realising you won't be able to test everything - how do you decide what to test first?
• Where do you get your expected results?
• If automating - what is your process for determining what to automate and in what order?
• In the past, I have been asked to verbally start mapping out a test plan for a common situation, such as an ATM.
The interviewer might say, "Just thinking out loud, if you were tasked to test an ATM, what items might you test plan
include?" These type questions are not meant to be answered conclusively, but it is a good way for the interviewer
to see how you approach the task.
• If you're given a program that will average student grades, what kinds of inputs would you use?
• Tell me about the best bug you ever found.
• What made you pick testing over another career?
• What is the exact difference between Integration & System testing, give me examples with your project.
• How did you go about testing a project?
• What are the limitations of automating software testing?
• What skills needed to be a good test automator?
• How to find that tools work well with your existing system?
• Describe some problem that you had with automating testing tool.
• What are the main attributes of test automation?
• What testing activities you may want to automate in a project?
• How to find that tools work well with your existing system?
• What criteria would you use to select Web transactions for load testing?
• For what purpose are virtual users created?
• Why it is recommended to add verification checks to your all your scenarios?
• In what situation would you want to parameterize a text verification check?
• Why do you need to parameterize fields in your virtual user script?
• What are the reasons why parameterization is necessary when load testing the Web server and the database
server?
• How can data caching have a negative effect on load testing results?
• What usually indicates that your virtual user script has dynamic data that is dependent on you parameterized fields?
• What are the various status reports that you need generate for Developers and Senior Management?
• You have been asked to design a Defect Tracking system. Think about the fields you would specify in the defect
tracking system?
38
 • Write a sample Test Policy?
• Explain the various types of testing after arranging them in a chronological order?
• Explain what test tools you will need for client-server testing and why?
• Explain what test tools you will need for Web app testing and why?
• Explain pros and cons of testing done development team and testing by an independent team?
• Differentiate Validation and Verification?
• Explain Stress, Load and Performance testing?
• Describe automated capture/playback tools and list their benefits?
Software Quality Assurance Interview Questions only (11)
• When should testing start in a project? Why?
• How do you go about testing a web application?
• Difference between Black & White box testing
• What is Configuration management? Tools used?
• What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)
• Would you like to work in a team or alone, why?
• Give me 5 strong & weak points of yours
• Why do you want to join our company?
• When should testing be stopped?
• What sort of things would you put down in a bug report?
• Who in the company is responsible for Quality?

• The top management was feeling that when there are any changes in the technology being used, development
schedules etc, it was a waste of time to update the Test Plan. Instead, they were emphasizing that you should put
your time into testing than working on the test plan. Your Project Manager asked for your opinion. You have argued
that Test Plan is very important and you need to update your test plan from time to time. It’s not a waste of time and
testing activities would be more effective when you have your plan clear. Use some metrics. How you would support
your argument to have the test plan consistently updated all the time.
• The QAI is starting a project to put the CSTE certification online. They will use an automated process for recording
candidate information, scheduling candidates for exams, keeping track of results and sending out certificates. Write
a brief test plan for this new project. The project had a very high cost of testing. After going in detail, someone found
out that the testers are spending their time on software that doesn’t have too many defects. How will you make sure
that this is correct?
• What are the disadvantages of overtesting?
• What happens to the test plan if the application has a functionality not mentioned in the requirements?
• You are given two scenarios to test. Scenario 1 has only one terminal for entry and processing whereas scenario 2
has several terminals where the data input can be made. Assuming that the processing work is the same, what
would be the specific tests that you would perform in Scenario 2, which you would not carry on Scenario 1?
• Your customer does not have experience in writing Acceptance Test Plan. How will you do that in coordination with
customer? What will be the contents of Acceptance Test Plan?
• How do you know when to stop testing?
• What can you do if the requirements are changing continuously?
• What is the need for Test Planning?
• What are the various status reports you will generate to Developers and Senior Management?
• Define and explain any three aspects of code review?
• Why do you need test planning?

39
• Explain 5 risks in an e-commerce project. Identify the personnel that must be involved in the risk analysis of a
project and describe their duties. How will you prioritize the risks?
• Who defines quality?
• What is an equivalence class?
• Is a "A fast database retrieval rate" a testable requirement?
• Should we test every possible combination/scenario for a program?
• What criteria do you use when determining when to automate a test or leave it manual?
• When do you start developing your automation tests?
• Discuss what test metrics you feel are important to publish an organization?
• In case anybody cares, here are the questions that I will be asking:
• Describe the role that QA plays in the software lifecycle.
• What should Development require of QA?
• What should QA require of Development?
• How would you define a "bug?"
• Give me an example of the best and worst experiences you've had with QA.
• How does unit testing play a role in the development / software lifecycle?
• Explain some techniques for developing software components with respect to testability.

40