20110112 - Testing Interview Questions

8/8/2019 20110112 - Testing Interview Questions

1/35

Testing Interview Questions

Define Bug Life Cycle? What is Metrics?

When we find out the bug, we will put into the open status. After fixing the bug developerchange the

status as fixed. Again we will test the fixed part, if there is no bug, change the bug status as

Closed other wise change the bug status as Reopen.A s/w metric defines the a standard method of measuring certain attributes of the process or the

product or the service.

What is the difference between System testing and end to end testing?

System testing is testing conducted on a complete, integrated system to evaluate the systems

compliance with its specified requirements.

end to end testing: here we give real time data

System Testing: One module or part of the system is tested

end-to-end Testing: The entire project, i.e which has many integrated systems, are tested.

How would you test a fast lazer printer?

-Test for power supply

-pc connection test

-printer sample test

-buffer test

-alignment test

-test for clarity

-speed of printing

-performance

Difference between stress testing and load testing?

STRESS TESTING:

for all types of applications deny the resources it needs, like: application is developed for 256MB

Ram or higher. you test on 64Mb Ram see it fails and fails safely

LOAD TESTING:

for client/server applications { 2-tier or higher }

Your request:

5000 users at a time. Check throughput of application, if achieved, load testing for reqd load isdone. If not tune the application developed and/or servers

STRESS TESTING:

estimating the performance of a application under different load levels.

LOAD TESTING:

To estimate the performance of a application when number of concurrent users are accessing at a

time.

STRESS TESTING:

Estimating the performance of server or CPU by applying max load or peak load.


2/35

LOAD TESTING:

Estimating the performance of server or CPU under customer expected configuration load is called

load testing.

STRESS TESTING:

apart from the above information there is more of hardware dependency kind of testing (like: less

CPU, less RAM rtc..)

LOAD TESTING:

focuses on number of user over a certain peroid of time (like normal users, more than normal user,

huge number of users, unbearable number of users etc)

How to write test cases for a search web page like google?

Test Case No.1

Test Data: Enter the URL of the website and press Enter button

Exp Result: Home page of the Website should appears.

TestCase No.2

Test Data: Check all the sub links are enable or disable.

Exp Result: All the sub links must be in enabled state.

TestCase No.3

Test Data: Check whether the Search Button is Enabled or disabled.

Exp Result: Search Button should be in Enabled state.

TestCase No.2

Test Data: Check whether the search Text box takes all data or not.

Exp Result: It should take all types of data (like, Numeric,Characters,special Characters etc).

What is the difference between use case, test case and test plan?

Use Case:

It is prepared by Business analyst in the Functional Requirement Specification (FRS), which is

nothing but steps which are given by the customer.

Test cases: It is prepared by test engineer based on the use cases from FRS to check the

functionality of an application thoroughly.

Test Plan: Team lead prepares test plan, in it he represents the scope of the test, what to test and

what not to test, scheduling, what to test using automation etc.

How can we design the test cases from requirements? Do the requirements, representexact functionality of AUT?

Yes, requirements should represent exact functionality of AUT.

First of all you have to analyze the requirements very thoroughly in terms of functionality. Then we

have to thing about suitable test case design technique [Black Box design techniques like

Equivalence Class Partitioning (ECP), Boundary Valve Analysis (BVA),Error guessing and Cause Effect

Graphing] for writing the test cases.

By these concepts you should design a test case, which should have the capability of finding the

absence of defects.


3/35

How to launch the test cases in Test Director and where it is saved?

You create the test cases in the test plan tab and link them to the requirements in the requirement

tab. Once the test cases are ready we change the status to ready and go to the Test Lab Tab and

create a test set and add the test cases to the test set and you can run from there.

For automation, in test plan, create a new automated test and launch the tool and create the script

and save it and you can run from the test lab the same way as you did for the manual test cases.The test cases are sorted in test plan tab or more precisely in the test director, lets say quality

centers database test director is now referred to as quality center.

What is the deference between a bug and a defect?

When tester verifies the test cases, all failed test cases are recorded as bugs directed for necessary

action and recorded in defected reports. As a testing point of view all fail test cases are defects as

well as found bugs. While development point of view if product doesnt meet the software

requirement specifications or any other features that is to be required, it is defect in the system.

Who found this feature is not meeting his requirements, he call it is bug in that product.

How can we explain a bug, which may arrive at the time of testing. Explain?

First check the status of the bug, then check whether the bug is valid or not then forward the same

bug to the team leader and then after confirmation forward it to the concern developer.

What do you mean by reproducing the bug? If the bug was not reproducible, what is the

next step?

Reproducing a bug is as simple as reproducing a defect. If you find a defect, for example click the

button and the corresponding action didnt happen, it is a bug. If the developer is unable to find this

behavior he will ask us to reproduce the bug.

In another scenario, if the client complaints a defect in the production we will have to reproduce it in

test environment.

How can you know bug is reproducible or not?

A bug is reproducible if we can reproduce it, If we cannot reproduce it, it is not reproducible in which

case we will do further testing around it and if we cannot see it we will close it, and just hope it

would never come back ever again.

On what basis we give priority and severity for a bug and give one example for highpriority and low severity and high severity and low priority?

Always the priority is given by our team leader. Tester will never give the priority.

For example,

Highseverity:hardware bugs application crash

Lowseverity:User interface bugs.

High priority: Error message is not coming on time, calculation bugs etc.

Low priority:Wrong alignment, final output wrong.


4/35

How is traceability of bug follow?

The traceability of bug can be followed in so many ways.

1. Mapping the functional requirement scenarios (FS Doc) - test cases (ID) - Failed test cases (Bugs)

2. Mapping between requirements (RS Doc) - Test case (ID) - Failed test cases.

3. Mapping between test plans (TP Doc) - test case (ID) - failed test cases.

4. Mapping between business requirements (BR Doc) - test cases (ID) - Failed test cases.

5. Mapping between high level design (Design Doc) - test cases (ID) - Failed test cases.Usually the traceability matrix is mapping between the requirements, client requirements, function

specification, test plan and test cases.

What will be the role of tester if bug is reproduced?

When ever the bug is reproduced, tester can send it back to the developer and ask him to fix it

again. If the developer cannot fix the bug once again and if the tester sends the bug back to the

developer, the third time the tester can make the bug as deferred i.e. he can reject the build (.exe)

How many functional testing tools are available? What is the easiest scripting language

used?

There might be a lot but mostly used are Win runner , silk Test, Rational Robot, QTP These are the

functional Testing tools.

What are the types of functional tests available?

There are four types of function to test a system.

1. Functional testing

2. Performance testing

3.integration testing

4. System testing

What is the major difference between Web services & client server environment?

The major difference between them are:

Web Services:

Its more towards the internet side. When we talk about web services it could mean from the java side

(deployed on Apache) or Windows side (deployed on IIS). Testing web services is totally a different

topic here.

Client Server: The system here involves a client system or a GUI (wherein a user see the front end

by which he can input to the system) and a Server ( a backend usually) where in the data gets

saved via the GUI.

What is Test Procedure?

Test procedure:-document specifying a sequence of actions for the execution of a particular test.

Test Procedure is a part of Test Case document. It comprises of following three steps:

1. To verify the look and feel of AUT through GUI test cases.

2. To verify the positive behavior of AUT through positive test cases.

3. To verify the negative behavior of the AUT through negative test cases.


5/35

Key elements of test plan?

The TestPlan consists of so many things. These are Test scope, Test Strategy, Testing Schedule,

Resource planning, What to test and What not to test, What can do in manual and What can do in

Automation, If Automation then which tool is preferred etc.

Test plan is the plan where, the test lead will select how many testers are required for testing for

given application. How to divide the team and test cases.How much time it takes to wind up testing

process.

What is SQA testing and steps of SQA testing?

Software QA involves the entire software development PROCESS, monitoring and improving the

process. Making sure that any agreed-upon standards and procedures are followed and ensuring that

problems are found and dealt with. It is oriented to prevention. The life cycle begins when an

application is first conceived and ends when it is no longer in use. It includes aspects such as initial

concept, requirements analysis, functional design, internal design, documentation planning, test

planning, coding, document preparation, integration, testing, maintenance, updates, retesting,

phase-out, and other specification.

What is the difference between Use Case and Test Case?

Use Case is written in Business Design Document (BDD)by the Business Analyst. It is for

understanding the functionality for the person who is involved in writing the test cases.

USE CASE EXAMPLE Action Response

when OK button is clicked Screen 1 appears

Testcase is different perceptions for a functionality to be tested, usually written by a Test Engineer.

The same person who has written the testcase may execute them or the other person

Above Usecase is converted into TestCase keeping in mind different perceptions (-ve and +ve)

Action Expected Value Actual Value Result

click on Ok screen 1 should appear(+ve perception) screen1 appeared pass

click on ok screen 2 should appear(-ve perception) screen 1 appeared fail

click on ok screen 2 should appear(-ve perception screen 2 appeared pass

Difference between test case and use case is

use case is prepared by High Level Management team but test case is prepared by

Test engineers.

Use case is prepared for validating the applications in terms of Actors, actions and responses but

test case is used to test a specific functionality of an app.

Use case is description of series of events that occur between user and system.

i.e. how system will response when a particular action is taken by user.

Test case:-in use case a generalized scenario is given but in testcase we are more thoroughly testing

the various aspect of that generalized scenario.

What is the difference between System testing and end to end testing?

System testing is testing conducted on a complete, integrated system to evaluate the systems


6/35

compliance with its specified requirements.

end to end testing: here we give real time data

System Testing: One module or part of the system is tested

end-to-end Testing: The entire project, i.e which has many integrated systems, are tested.

What kinds of testing should be considered?

o Black box testing - not based on any knowledge of internal design or code. Tests are based onrequirements and functionality.

o White box testing - based on knowledge of the internal logic of an application's code. Tests arebased on coverage of code statements, branches, paths, conditions.

o 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.

o 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.

o integration testing - testing of combined parts o f an application to determine if they functiontogether 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 anddistributed systems.

o functional testing - black-box type testing geared to functional requirements of an application; thistype 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 o f testing.)

o system testing - black-box type testing that is based on overall requirements specifications; coversall combined parts of a system.

o end-to-end testing - similar to system testing; the 'macro' end of the test scale; involves testing ofa 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.

o sanity testing or smoke testing - typically an initial testing effort to determine if a new so ftwareversion is performing well enough to accept it for a major testing effort. For example, if the newsoftware 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.

o regression testing - re-testing after fixes or modifications of the software or its environment. It canbe 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.

o acceptance testing - final testing based on specifications of the end-user or customer, or based onuse by end-users/customers over some limited period of time.

o load testing - testing an application under heavy loads, such as testing of a web site under a rangeof loads to determine at what point the system's response time degrades or fails.


7/35

o stress testing - term often used interchangeably with 'load' and 'performance' testing. Also used todescribe such tests as system functional testing while under unusually heavy loads, heavy

repetition of certain actions or i nputs, input of large numerical values, large complex queries to a

database system, etc.

o 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.

o usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on thetargeted 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.

o install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes.o recovery testing - testing how well a system recovers from crashes, hardware failures, or other

catastrophic problems.

o failover testing - typically used interchangeably with 'recovery testing'o security testing - testing how well the system protects against unauthorized internal or external

access, willful damage, etc; may require sophisticated testing techniques.

o compatability testing - testing how well software performs in a particularhardware/software/operating system/network/etc. environment.

o exploratory testing - often taken to mean a creative, informal software test that is not based onformal test plans or test cases; testers may be learning the software as they test it.

o ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers havesignificant understanding of the software before testing it.

o context-driven testing - testing driven by an understanding of the environment, culture, andintended use of so ftware. For example, the testing approach for life-critical medical equipment

software would be completely different than that for a low-cost computer game.

o user acceptance testing - determining if software is satisfactory to an end-user or customer.o comparison testing - comparing software weaknesses and strengths to competing products.o alpha testing - testing of an application when development is nearing completion; minor design

changes may still be made as a result o f such testing. Typically done by end-users or others, not by

programmers or testers.

o beta testing - testing when development and testing are essentially completed and final bugs andproblems need to be found before final release. Typically done by end-users or others, not by

programmers or testers.

o mutation testing - a method for determining if a set of test data or test cases is useful, bydeliberately 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.

What are 5 common problems in the software development process?

o poor requirements - if requirements are unclear, incomplete, too general, and not testable, therewill be problems.

o unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.o inadequate testing - no one will know whether or not the program is any good until the customer

complains or systems crash.

o featuritis - requests to pile on new features after development is underway; extremely common.o miscommunication - if developers don't know what's needed or customer's have erroneous

expectations, problems are guaranteed.


8/35


9/35

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:

o minimize or eliminate use of global variables.o 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.

o use descriptive variable names - use both upper and lower case, avoid abbreviations, use as manycharacters as necessary to be adequately descriptive (use of more than 20 characters is not out of

line); be consistent in naming conventions.

o function and method sizes should be minimized; less than 100 lines of code is good, less than 50lines is preferable.

o function descriptions should be clearly spelled out in comments preceding a function's code.o organize code for readability.o use whitespace generously - vertically and horizontallyo each line of code should contain 70 characters max.o one code statement per line.o coding style should be consistent throught a program (eg, use of brackets, indentations, naming

conventions, etc.)

o in adding comments, err on the side of too many rather than too few comments; a common rule ofthumb is that there should be at least as many lines o f comments (including header blocks) as lines

of code.

o no matter how small, an application should include documentaion of the overall program functionand flow (even a few paragraphs is better than nothing); or if possible a separate flow chart and

detailed program documentation.

o make extensive use of error handling procedures and status and error logging.o for C++, to minimize complexity and increase maintainability, avoid too many levels of inheritance

in class heirarchies (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.)

o for C++, keep class methods small, less than 50 lines of code per method is preferable.o for C++, make liberal use of exception handlers

What is 'good design'?

'Design' could refer to many things, but often refers to 'functional design' or 'i nternal design'. Good

internal design is indicated by software code whose overall s tructure 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 thathave a user interface, it's often a good idea to assume that the end user will havelittle computer knowledge and may not read a user manual or even the on-line help; some common

rules-of-thumb include:

o the program should act in a way that least surprises the usero it should always be evident to the user what can be done next and how to exito the program shouldn't let the users do something stupid without warning them.


10/35

What is SEI? CMM? CMMI? ISO? IEEE? ANSI? Will it help?

o SEI = 'Software Engineering Institute' at Carnegie-Mellon University; initiated by the U.S. DefenseDepartment to help improve so ftware development processes.

o CMM = 'Capability Maturity Model', now called the CMMI ('Capability Maturity Model Integration'),developed by the SEI. It's a model of 5 levels of process 'maturity' that determine effectiveness in

delivering quality software. It is geared to large organizations such

as large U.S. DefenseDepartment contractors. However, many of the QA processes involved are appropriate to any

organization, and if reasonably applied can be helpful. Organizations can receive CMMI ratings by

undergoing assessments by qualified auditors.

Level 1 - characterized by chaos, periodic panics, andheroic efforts required by individuals to successfully complete projects. Few if any

processes in place; successes may not be repeatable. Level 2 - software project tracking, requirements management, realistic

planning, and configuration management processes are in place; successful practices can be repeated. Level 3 - standard software

development and maintenance processes are integrated throughout an organization; a Software Engineering Process Group is is in

place to oversee software processes, and training programs are used to ensure understanding and compliance.L

evel 4 - metrics areused to track productivity, processes, and products. Project performance is predictable, and quality is consistently high. Level 5 - the

focus is on continouous process improvement. The impact of new processes and technologies can be predicted and effectively

implemented when required. Perspective on CMM ratings: During 1997-2001, 1018 organizations were assessed. Of those, 27%

were rated atLevel 1, 39% at 2, 23% at 3, 6% at 4, and 5% at 5. (For ratings during the period 1992-96, 62% were atLevel 1, 23%

at 2, 13% at 3, 2% at 4, and 0.4% at 5.) The median size of organizations was 100 software engineering/maintenance personnel;

32% of organizations were U.S. federal contractors or agencies. For those rated atLevel 1, the most problematical key process area

was in Software Quality Assurance.

o ISO = 'International Organisation for Standardization' - The ISO 9001:2000 standard (whichreplaces the previous standard of 1994) concerns quality systems that are assessed by outsideauditors, and it applies to many kinds of production and manufacturing organizations, not just

software. It covers documentation, design, development, production, testing, installation, servicing,

and other processes. The full set o f standards consists of: (a)Q9001-2000 - Quality Management

Systems: Requirements; (b)Q9000-2000 - Quality Management Systems: Fundamentals and

Vocabulary; (c)Q9004-2000 - Quality Management Systems: Guidelines for Performance

Improvements. To be ISO 9001 certified, a third-party auditor assesses an organization, and

certification is typically good for about 3 years, after which a complete reassessment is required.

Note that ISO certification does not necessarily indicate quality products - it indicates only that

documented processes are followed.

Also see http://www.iso.ch/ for the latest information. In the U.S. the standards can be purchased

via the ASQ web site athttp://e-standards.asq.org/

o IEEE = 'Institute of Electrical and Electronics Engineers' - among other things, creates standardssuch as 'IEEE Standard for Software Test Documentation' (IEEE/ANSI Standard 829), 'IEEE

Standard of Software Unit Testing (IEEE/ANSI Standard 1008), 'IEEE Standard for Software Quality

Assurance Plans' (IEEE/ANSI Standard 730), and others.

o ANSI = 'American National Standards Institute', the primary industrial standards body in the U.S.;publishes some software-related standards in conjunction with the IEEE and ASQ (American Society

for Quality).

o Other software development/IT management process assessment methods besides CMMI and ISO9000 include SPICE, Trillium, TickIT, Bootstrap, ITIL, MOF, and CobiT.


11/35

What is the 'software life cycle'?

The life cycle begins when an application is first conceived and ends when it is no longer in use. It

includes aspects such as initial concept, requirements analysis, functional design, internal design,

documentation planning, test planning, coding, document preparation, integration, testing,

maintenance, updates, retesting, phase-out, and ot

her aspects.

Will automated testing tools make testing easier?o 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.

o A common type of automated tool is the 'record/playback' type. For example, a tester could clickthrough 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 might then be

retested by just 'playing back' the 'recorded' actions, and comparing the logging results to check

effects of the changes. T

he problem wit

hsuc

htools is t

hat if t

here are continual c

hanges to t

hesystem being tested, the 'recordings' may have to be changed so much that it becomes very time-

consuming to continuously update the scripts. Additionally, interpretation and analysis 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.

o Another common type of approach for automation of functional testing is 'data-driven' or 'keyword-driven' automated testing, in which the test drivers are separated from the data and/or actions

utilized in testing (an 'action' would be something like 'enter a value in a text box'). Test drivers

can be in the form of automated test tools or custom-written testing software. The data and actions

can be more easily maintained - such as via a spreadsheet - since they are separate from the test

drivers. The test drivers 'read' the data/action information to perform specified tests. This approach

can enable more efficient control, development, documentation, and maintenance of automated

tests/test cases.o Other automated tools can include:

code analyzers - monitor code complexity, adherence to standards, etc. coverage analyzers - thesetools check which parts of the code have been exercised by a test, and may be o riented 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.

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.

What is Accessibility Testing?


12/35

Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

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.

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.

What is Application Binary Interface (ABI)?

A specification defining requirements for portability of applications in binary forms across defferent

system platforms and environments.

What is Application Programming Interface (API)?

A formalized set of software calls and routines that can be referenced by an application program inorder to access supporting system or network services.

What is Automated Software Quality (ASQ)?

The use of software tools, such as automated testing tools, to improve software quality.

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.

What is Backus-Naur Form?

A metalanguage used to formally describe the syntax of a language.

What is Basic Block?

A sequence of one or more consecutive, executable statements containing no branches.

What is Basis Path Testing?

A white box test case design technique that uses the algorithmic flow of the program to design tests.

What is Basis Set?

The set of tests derived using basis path testing.

What is Baseline?


13/35

The point at which some deliverable produced during the software engineering process is put under

formal change control.

What is Beta Testing?

Testing of a rerelease of a software product conducted by customers.

What is Binary Portability Testing?

Testing an executable application for portability across system platforms and environments, usually forconformation to an ABI specification.

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.

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.

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).

What is Bug?

A fault in a program which causes the program to perform in an unintended or unanticipated manner.

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.

What is Branch Testing?

Testing in which all branches in the program source code are tested at least once.

What is Breadth Testing?

A test suite that exercises the full functionality of a product but does not test features in detail.

What is CAST?

Computer Aided Software Testing.


14/35

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.

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.

What is Cause Effect Graph?

A graphical representation of inputs and the associated outputs effects which can be used to design test

cases.

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.

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.

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 commonprogramming errors, and analyzing its compliance with coding standards.

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.

What is Coding?

The generation of source code.

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.

What is Component?

A minimal software item for which a separate specification is available.


15/35

What is Component Testing?

See the question what is Unit Testing.

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.

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.

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 valueof that information to the organization right now.

What is Conversion Testing?

Testing of programs or procedures used to convert data from existing systems for use in replacement

systems.

What is Cyclomatic Complexity?

A measure of the logical complexity of an algorithm, used in white-box testing.

What is Data Dictionary?

A database that contains definitions of all data items defined during analysis.

What is Data Flow Diagram?

A modeling notation that represents a functional decomposition of a system.

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.

What is Debugging?

The process of finding and removing the causes of software failures.

What is Defect?

Nonconformance to requirements or functional / program specification

What is Dependency Testing?


16/35

Examines an application's requirements for pre-existing software, initial states and configuration in

order to maintain proper functionality.

What is Depth Testing?

A test that exercises a feature of a product in full detail.

What is Dynamic Testing?

Testing software through executing it. See also Static Testing.

What is Emulator?

A device, computer program, or system that accepts the same inputs and produces the same outputs as

a given system.

What is Endurance Testing?

Checks for memory leaks or other problems that may occur with prolonged execution.

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.

What is Equivalence Class?

A portion of a component's input or output domains for which the component's behaviour is assumed to

be the same from the component's specification.

What is Equivalence Partitioning?

A test case design technique for a component in which test cases are designed to execute

representatives from equivalence classes.

What is Exhaustive Testing?

Testing which covers all combinations of input values and preconditions for an element of the software

under test.

What is Functional Decomposition?

A technique used during planning, analysis and design; creates a functional hierarchy for the software.

What is Functional Specification?

A document that describes in detail the characteristics of the product with regard to its intended

features.

What is Functional Testing?

Testing the features and operational behavior of a product to ensure they correspond to its


17/35

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.

See also What is Black Box Testing.

What is Glass Box Testing?

A synonym for White Box Testing.

What is Gorilla Testing?

Testing one particular module, functionality heavily.

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.

What is High Order Tests?

Black-box tests conducted once the software has been integrated.

What is Independent Test Group (ITG)?

A group of people whose primary responsibility is software testing,

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).

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.

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.

What is Load Testing?

See Performance Testing.

What is Localization Testing?

This term refers to making software specifically designed for a specific locality.


18/35

What is Loop Testing?

A white box testing technique that exercises program loops.

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.

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.

What is Negative Testing?

Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

What is Path Testing?

Testing in which all paths in the program source code are tested at least once.

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".

What is Positive Testing?

Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.

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.

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.

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.


19/35

What is Quality Control?

The operational techniques and the activities used to fulfill and verify requirements of quality.

What is Quality Management?

That aspect of the overall management function that determines and implements the quality policy.

What is Quality Policy?

The overall intentions and direction of an organization as regards quality as formally expressed by top

management.

What is Quality System?

The organizational structure, responsibilities, procedures, processes, and resources for implementing

quality management.

What is Race Condition?

A cause of concurrency problems.Multiple accesses to a shared resource, at least one of which is awrite, with no mechanism used by either to moderate simultaneous access.

What is Ramp Testing?

Continuously raising an input signal until the system breaks down.

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 powerout conditions.

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.

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).

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.

What is Scalability Testing?

Performance testing focused on ensuring the application under test gracefully handles increases in work

load.


20/35

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.

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.

What is Soak Testing?

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.

What is Software Requirements Specification?

A deliverable that describes all data, functional and behavioral requirements, all constraints, and allvalidation requirements for software/

What is Software Testing?

A set of activities conducted with the intent of finding errors in software.

What is Static Analysis?

Analysis of a program carried out without executing the program.

What is Static Analyzer?

A tool that carries out static analysis.

What is Static Testing?

Analysis of a program carried out without executing the program.

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.

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.


21/35

What is Structural Testing?

Testing based on an analysis of internal workings and structure of a piece of software. See also White

Box Testing.

What is System Testing?

Testing that attempts to discover defects that are properties of the entire system rather than of its

individual components.

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.

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.

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.

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.

What is Test Driver?

A program or test tool used to execute a tests. Also known as a Test Harness.

What is Test Environment?


22/35

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.

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.

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?

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 is Test Harness?

A program or test tool used to execute a tests. Also known as a Test Driver.

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. Ref IEEE Std 829.

What is Test Procedure?


23/35

A document providing detailed instructions for the execution of one or more test cases.

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.

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.

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.

What is Test Tools?

Computer programs used in the testing of a system, a component of the system, or its documentation.

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.

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.

What is Total Quality Management?

A company commitment to develop a process that achieves high quality product and customer

satisfaction.

What is Traceability Matrix?

A document showing the relationship between Test Requirements and Test Cases.

What is Usability Testing?

Testing the ease with which users can learn and use a product.


24/35

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.

What is Unit Testing?

Testing of individual software components.

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

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.

What is Volume Testing?

Testing which confirms that any values that may become large over time (such as accumulated counts,

logs, and data files), can be accommodated by the program and will not cause the program to stop

working or degrade its operation in any manner.

What is Walkthrough?

A review of requirements, designs or code characterized by the author of the material under review

guiding the progression of the review.

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.

What is Workflow Testing?

Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by

the end-user.


25/35

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

7HVWLQJ4XHVWLRQVDQG$QVZHUV

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

:KDWPDNHVDJRRGWHVWHQJLQHHU"

:KDWPDNHVDJRRGVRIWZDUH4$HQJLQHHU"

:KDWPDNHVDJRRG4$RU7HVWPDQDJHU"

:KDWVWKHUROHRIGRFXPHQWDWLRQLQ4$"

:KDWVWKHELJGHDODERXWUHTXLUHPHQWV"

:KDWVWHSVDUHQHHGHGWRGHYHORSDQGUXQVRIWZDUHWHVWV"

:KDWVDWHVWSODQ"

:KDWVDWHVWFDVH"

:KDWVKRXOGEHGRQHDIWHUDEXJLVIRXQG"

:KDWLVFRQILJXUDWLRQPDQDJHPHQW"

:KDWLIWKHVRIWZDUHLVVREXJJ\LWFDQWUHDOO\EHWHVWHGDWDOO"

+RZFDQLWEHNQRZQZKHQWRVWRSWHVWLQJ"

:KDWLIWKHUHLVQWHQRXJKWLPHIRUWKRURXJKWHVWLQJ"

:KDWLIWKHSURMHFWLVQWELJHQRXJKWRMXVWLI\H[WHQVLYHWHVWLQJ"

:KDWFDQEHGRQHLIUHTXLUHPHQWVDUHFKDQJLQJFRQWLQXRXVO\"

:KDWLIWKHDSSOLFDWLRQKDVIXQFWLRQDOLW\WKDWZDVQWLQWKH

UHTXLUHPHQWV"

+RZFDQ6RIWZDUH4$SURFHVVHVEHLPSOHPHQWHGZLWKRXWVWLIOLQJ

SURGXFWLYLW\"

:KDWLIDQRUJDQL]DWLRQLVJURZLQJVRIDVWWKDWIL[HG4$SURFHVVHV

DUHLPSRVVLEOH"

+RZGRHVDFOLHQWVHUYHUHQYLURQPHQWDIIHFWWHVWLQJ"

+RZFDQ:RUOG:LGH:HEVLWHVEHWHVWHG"

+RZLVWHVWLQJDIIHFWHGE\REMHFWRULHQWHGGHVLJQV"

:KDWLV([WUHPH3URJUDPPLQJDQGZKDWVLWJRWWRGRZLWKWHVWLQJ"

:KDWPDNHVDJRRGWHVWHQJLQHHU"

"$JRRGWHVWHQJLQHHUKDVDWHVWWREUHDNDWWLWXGHDQDELOLW\WR

WDNHWKHSRLQWRIYLHZRIWKHFXVWRPHUDVWURQJGHVLUHIRUTXDOLW\

DQGDQDWWHQWLRQWRGHWDLO

"7DFWDQGGLSORPDF\DUHXVHIXOLQPDLQWDLQLQJDFRRSHUDWLYH

UHODWLRQVKLSZLWKGHYHORSHUVDQGDQDELOLW\WRFRPPXQLFDWHZLWKERWK

WHFKQLFDOGHYHORSHUVDQGQRQWHFKQLFDOFXVWRPHUVPDQDJHPHQW

SHRSOHLVXVHIXO

"3UHYLRXVVRIWZDUHGHYHORSPHQWH[SHULHQFHFDQEHKHOSIXODVLW

SURYLGHVDGHHSHUXQGHUVWDQGLQJRIWKHVRIWZDUHGHYHORSPHQWSURFHVV

JLYHVWKHWHVWHUDQDSSUHFLDWLRQIRUWKHGHYHORSHUVSRLQWRIYLHZ

DQGUHGXFHWKHOHDUQLQJFXUYHLQDXWRPDWHGWHVWWRROSURJUDPPLQJ

"-XGJHPHQWVNLOOVDUHQHHGHGWRDVVHVVKLJKULVNDUHDVRIDQ

DSSOLFDWLRQRQZKLFKWRIRFXVWHVWLQJHIIRUWVZKHQWLPHLVOLPLWHG

:KDWPDNHVDJRRGVRIWZDUH4$HQJLQHHU"

"7KHVDPHTXDOLWLHVDJRRGWHVWHUKDVDUHXVHIXOIRUD4$HQJLQHHU

"$GGLWLRQDOO\WKH\PXVWEHDEOHWRXQGHUVWDQGWKHHQWLUHVRIWZDUH

GHYHORSPHQWSURFHVVDQGKRZLWFDQILWLQWRWKHEXVLQHVVDSSURDFKDQG

JRDOVRIWKHRUJDQL]DWLRQ

"&RPPXQLFDWLRQVNLOOVDQGWKHDELOLW\WRXQGHUVWDQGYDULRXVVLGHVRI

LVVXHVDUHLPSRUWDQW

",QRUJDQL]DWLRQVLQWKHHDUO\VWDJHVRILPSOHPHQWLQJ4$SURFHVVHV

SDWLHQFHDQGGLSORPDF\DUHHVSHFLDOO\QHHGHG

"$QDELOLW\WRILQGSUREOHPVDVZHOODVWRVHHZKDWVPLVVLQJLV

LPSRUWDQWIRULQVSHFWLRQVDQGUHYLHZV

:KDWPDNHVDJRRG4$RU7HVWPDQDJHU"


26/35

"$JRRG4$WHVWRU4$7HVWFRPELQHGPDQDJHUVKRXOG

"EHIDPLOLDUZLWKWKHVRIWZDUHGHYHORSPHQWSURFHVV

"EHDEOHWRPDLQWDLQHQWKXVLDVPRIWKHLUWHDPDQGSURPRWHDSRVLWLYH

DWPRVSKHUHGHVSLWHZKDWLVDVRPHZKDWQHJDWLYHSURFHVVH J

ORRNLQJIRURUSUHYHQWLQJSUREOHPV

"EHDEOHWRSURPRWHWHDPZRUNWRLQFUHDVHSURGXFWLYLW\

"EHDEOHWRSURPRWHFRRSHUDWLRQEHWZHHQVRIWZDUHWHVWDQG4$HQJLQHHUV

"KDYHWKHGLSORPDWLFVNLOOVQHHGHGWRSURPRWHLPSURYHPHQWVLQ4$

SURFHVVHV

"KDYHWKHDELOLW\WRZLWKVWDQGSUHVVXUHVDQGVD\QRWRRWKHU

PDQDJHUVZKHQTXDOLW\LVLQVXIILFLHQWRU4$SURFHVVHVDUHQRWEHLQJ

DGKHUHGWR

"KDYHSHRSOHMXGJHPHQWVNLOOVIRUKLULQJDQGNHHSLQJVNLOOHGSHUVRQQHO

"EHDEOHWRFRPPXQLFDWHZLWKWHFKQLFDODQGQRQWHFKQLFDOSHRSOH

HQJLQHHUVPDQDJHUVDQGFXVWRPHUV

"EHDEOHWRUXQPHHWLQJVDQGNHHSWKHPIRFXVHG

:KDWVWKHUROHRIGRFXPHQWDWLRQLQ4$"

"&ULWLFDO1RWHWKDWGRFXPHQWDWLRQFDQEHHOHFWURQLFQRW

QHFHVVDULO\SDSHU

"4$SUDFWLFHVVKRXOGEHGRFXPHQWHGVXFKWKDWWKH\DUHUHSHDWDEOH

"6SHFLILFDWLRQVGHVLJQVEXVLQHVVUXOHVLQVSHFWLRQUHSRUWV

FRQILJXUDWLRQVFRGHFKDQJHVWHVWSODQVWHVWFDVHVEXJUHSRUWV

XVHUPDQXDOVHWFVKRXOGDOOEHGRFXPHQWHG

"7KHUHVKRXOGLGHDOO\EHDV\VWHPIRUHDVLO\ILQGLQJDQGREWDLQLQJ

GRFXPHQWVDQGGHWHUPLQLQJZKDWGRFXPHQWDWLRQZLOOKDYHDSDUWLFXODU

SLHFHRILQIRUPDWLRQ

"&KDQJHPDQDJHPHQWIRUGRFXPHQWDWLRQVKRXOGEHXVHGLISRVVLEOH

:KDWVWKHELJGHDODERXWUHTXLUHPHQWV"

"2QHRIWKHPRVWUHOLDEOHPHWKRGVRILQVXULQJSUREOHPVRUIDLOXUH

LQDFRPSOH[VRIWZDUHSURMHFWLVWRKDYHSRRUO\GRFXPHQWHG

UHTXLUHPHQWVVSHFLILFDWLRQV

"5HTXLUHPHQWVDUHWKHGHWDLOVGHVFULELQJDQDSSOLFDWLRQV

H[WHUQDOO\SHUFHLYHGIXQFWLRQDOLW\DQGSURSHUWLHV

"5HTXLUHPHQWVVKRXOGEHFOHDUFRPSOHWHUHDVRQDEO\GHWDLOHG

FRKHVLYHDWWDLQDEOHDQGWHVWDEOH $QRQWHVWDEOHUHTXLUHPHQWZRXOG

EHIRUH[DPSOHXVHUIULHQGO\WRRVXEMHFWLYH

"$WHVWDEOHUHTXLUHPHQWZRXOGEHVRPHWKLQJOLNHWKHXVHUPXVWHQWHU

WKHLUSUHYLRXVO\DVVLJQHGSDVVZRUGWRDFFHVVWKHDSSOLFDWLRQ

"'HWHUPLQLQJDQGRUJDQL]LQJUHTXLUHPHQWVGHWDLOVLQDXVHIXODQG

HIILFLHQWZD\FDQEHDGLIILFXOWHIIRUWGLIIHUHQWPHWKRGVDUH

DYDLODEOHGHSHQGLQJRQWKHSDUWLFXODUSURMHFW

"0DQ\ERRNVDUHDYDLODEOHWKDWGHVFULEHYDULRXVDSSURDFKHVWRWKLVWDVN

"&DUHVKRXOGEHWDNHQWRLQYROYH$//RIDSURMHFWVVLJQLILFDQW

FXVWRPHUVLQWKHUHTXLUHPHQWVSURFHVV

"&XVWRPHUVFRXOGEHLQKRXVHSHUVRQQHORURXWDQGFRXOGLQFOXGH

HQGXVHUVFXVWRPHUDFFHSWDQFHWHVWHUVFXVWRPHUFRQWUDFWRIILFHUV

FXVWRPHUPDQDJHPHQWIXWXUHVRIWZDUHPDLQWHQDQFHHQJLQHHUV

VDOHVSHRSOHHWF

"$Q\RQHZKRFRXOGODWHUGHUDLOWKHSURMHFWLIWKHLUH[SHFWDWLRQV

DUHQWPHWVKRXOGEHLQFOXGHGLISRVVLEOH

"2UJDQL]DWLRQVYDU\FRQVLGHUDEO\LQWKHLUKDQGOLQJRIUHTXLUHPHQWV

VSHFLILFDWLRQV

",GHDOO\WKHUHTXLUHPHQWVDUHVSHOOHGRXWLQDGRFXPHQWZLWK


27/35

VWDWHPHQWVVXFKDV7KHSURGXFWVKDOO

"'HVLJQVSHFLILFDWLRQVVKRXOGQRWEHFRQIXVHGZLWKUHTXLUHPHQWV

GHVLJQVSHFLILFDWLRQVVKRXOGEHWUDFHDEOHEDFNWRWKHUHTXLUHPHQWV

",QVRPHRUJDQL]DWLRQVUHTXLUHPHQWVPD\HQGXSLQKLJKOHYHOSURMHFW

SODQVIXQFWLRQDOVSHFLILFDWLRQGRFXPHQWVLQGHVLJQGRFXPHQWVRULQ

RWKHUGRFXPHQWVDWYDULRXVOHYHOVRIGHWDLO

"1RPDWWHUZKDWWKH\DUHFDOOHGVRPHW\SHRIGRFXPHQWDWLRQZLWK

GHWDLOHGUHTXLUHPHQWVZLOOEHQHHGHGE\WHVWHUVLQRUGHUWRSURSHUO\

SODQDQGH[HFXWHWHVWV

":LWKRXWVXFKGRFXPHQWDWLRQWKHUHZLOOEHQRFOHDUFXWZD\WR

GHWHUPLQHLIDVRIWZDUHDSSOLFDWLRQLVSHUIRUPLQJFRUUHFWO\

:KDWVWHSVDUHQHHGHGWRGHYHORSDQGUXQVRIWZDUHWHVWV"

7KHIROORZLQJDUHVRPHRIWKHVWHSVWRFRQVLGHU

"2EWDLQUHTXLUHPHQWVIXQFWLRQDOGHVLJQDQGLQWHUQDOGHVLJQ

VSHFLILFDWLRQVDQGRWKHUQHFHVVDU\GRFXPHQWV

"2EWDLQEXGJHWDQGVFKHGXOHUHTXLUHPHQWV

"'HWHUPLQHSURMHFWUHODWHGSHUVRQQHODQGWKHLUUHVSRQVLELOLWLHV

UHSRUWLQJUHTXLUHPHQWVUHTXLUHGVWDQGDUGVDQGSURFHVVHVVXFKDV

UHOHDVHSURFHVVHVFKDQJHSURFHVVHVHWF

",GHQWLI\DSSOLFDWLRQVKLJKHUULVNDVSHFWVVHWSULRULWLHVDQG

GHWHUPLQHVFRSHDQGOLPLWDWLRQVRIWHVWV

"'HWHUPLQHWHVWDSSURDFKHVDQGPHWKRGVXQLWLQWHJUDWLRQ

IXQFWLRQDOV\VWHPORDGXVDELOLW\WHVWVHWF

"'HWHUPLQHWHVWHQYLURQPHQWUHTXLUHPHQWVKDUGZDUHVRIWZDUH

FRPPXQLFDWLRQVHWF

"'HWHUPLQHWHVWZDUHUHTXLUHPHQWVUHFRUGSOD\EDFNWRROVFRYHUDJH

DQDO\]HUVWHVWWUDFNLQJSUREOHPEXJWUDFNLQJHWF

"'HWHUPLQHWHVWLQSXWGDWDUHTXLUHPHQWV

",GHQWLI\WDVNVWKRVHUHVSRQVLEOHIRUWDVNVDQGODERUUHTXLUHPHQWV

"6HWVFKHGXOHHVWLPDWHVWLPHOLQHVPLOHVWRQHV

"'HWHUPLQHLQSXWHTXLYDOHQFHFODVVHVERXQGDU\YDOXHDQDO\VHVHUURU

FODVVHV

"3UHSDUHWHVWSODQGRFXPHQWDQGKDYHQHHGHGUHYLHZVDSSURYDOV

":ULWHWHVWFDVHV

"+DYHQHHGHGUHYLHZVLQVSHFWLRQVDSSURYDOVRIWHVWFDVHV

"3UHSDUHWHVWHQYLURQPHQWDQGWHVWZDUHREWDLQQHHGHGXVHU

PDQXDOVUHIHUHQFHGRFXPHQWVFRQILJXUDWLRQJXLGHVLQVWDOODWLRQJXLGHV

VHWXSWHVWWUDFNLQJSURFHVVHVVHWXSORJJLQJDQGDUFKLYLQJ

SURFHVVHVVHWXSRUREWDLQWHVWLQSXWGDWD

"2EWDLQDQGLQVWDOOVRIWZDUHUHOHDVHV

"3HUIRUPWHVWV

"(YDOXDWHDQGUHSRUWUHVXOWV

"7UDFNSUREOHPVEXJVDQGIL[HV

"5HWHVWDVQHHGHG

"0DLQWDLQDQGXSGDWHWHVWSODQVWHVWFDVHVWHVWHQYLURQPHQWDQG

WHVWZDUHWKURXJKOLIHF\FOH

:KDWVDWHVWSODQ"

$VRIWZDUHSURMHFWWHVWSODQLVDGRFXPHQWWKDWGHVFULEHVWKH

REMHFWLYHVVFRSHDSSURDFKDQGIRFXVRIDVRIWZDUHWHVWLQJHIIRUW

7KHSURFHVVRISUHSDULQJDWHVWSODQLVDXVHIXOZD\WRWKLQNWKURXJK

WKHHIIRUWVQHHGHGWRYDOLGDWHWKHDFFHSWDELOLW\RIDVRIWZDUH

SURGXFW7KHFRPSOHWHGGRFXPHQWZLOOKHOSSHRSOHRXWVLGHWKHWHVW

JURXSXQGHUVWDQGWKHZK\DQGKRZRISURGXFWYDOLGDWLRQ ,WVKRXOG


28/35


29/35

"$WHVWFDVHLVDGRFXPHQWWKDWGHVFULEHVDQLQSXWDFWLRQRUHYHQW

DQGDQH[SHFWHGUHVSRQVHWRGHWHUPLQHLIDIHDWXUHRIDQDSSOLFDWLRQ

LVZRUNLQJFRUUHFWO\

"$WHVWFDVHVKRXOGFRQWDLQSDUWLFXODUVVXFKDVWHVWFDVHLGHQWLILHU

WHVWFDVHQDPHREMHFWLYHWHVWFRQGLWLRQVVHWXSLQSXWGDWD

UHTXLUHPHQWVVWHSVDQGH[SHFWHGUHVXOWV

"1RWHWKDWWKHSURFHVVRIGHYHORSLQJWHVWFDVHVFDQKHOSILQG

SUREOHPVLQWKHUHTXLUHPHQWVRUGHVLJQRIDQDSSOLFDWLRQVLQFHLW

UHTXLUHVFRPSOHWHO\WKLQNLQJWKURXJKWKHRSHUDWLRQRIWKHDSSOLFDWLRQ

)RUWKLVUHDVRQLWVXVHIXOWRSUHSDUHWHVWFDVHVHDUO\LQWKH

GHYHORSPHQWF\FOHLISRVVLEOH

:KDWVKRXOGEHGRQHDIWHUDEXJLVIRXQG"

7KHEXJQHHGVWREHFRPPXQLFDWHGDQGDVVLJQHGWRGHYHORSHUVZKRFDQ

IL[LW

$IWHUWKHSUREOHPLVUHVROYHGIL[HVVKRXOGEHUHWHVWHGDQG

GHWHUPLQDWLRQVPDGHUHJDUGLQJUHTXLUHPHQWVIRUUHJUHVVLRQWHVWLQJWR

FKHFNWKDWIL[HVGLGQWFUHDWHSUREOHPVHOVHZKHUH ,ID

SUREOHPWUDFNLQJV\VWHPLVLQSODFHLWVKRXOGHQFDSVXODWHWKHVH

SURFHVVHV$YDULHW\RIFRPPHUFLDOSUREOHPWUDFNLQJPDQDJHPHQW

VRIWZDUHWRROVDUHDYDLODEOH 7KHIROORZLQJDUHLWHPVWREH

FRQVLGHUHGLQWKHWUDFNLQJSURFHVV

"&RPSOHWHLQIRUPDWLRQVXFKWKDWGHYHORSHUVFDQXQGHUVWDQGWKHEXJ

JHWDQLGHDRILWVVHYHULW\DQGUHSURGXFHLWLIQHFHVVDU\

"%XJLGHQWLILHUQXPEHU,'HWF

"&XUUHQWEXJVWDWXVH J5HOHDVHGIRU5HWHVW1HZHWF

"7KHDSSOLFDWLRQQDPHRULGHQWLILHUDQGYHUVLRQ

"7KHIXQFWLRQPRGXOHIHDWXUHREMHFWVFUHHQHWF ZKHUHWKHEXJ

RFFXUUHG

"(QYLURQPHQWVSHFLILFVV\VWHPSODWIRUPUHOHYDQWKDUGZDUHVSHFLILFV

"7HVWFDVHQDPHQXPEHULGHQWLILHU

"2QHOLQHEXJGHVFULSWLRQ

")XOOEXJGHVFULSWLRQ

"'HVFULSWLRQRIVWHSVQHHGHGWRUHSURGXFHWKHEXJLIQRWFRYHUHGE\D

WHVWFDVHRULIWKHGHYHORSHUGRHVQWKDYHHDV\DFFHVVWRWKHWHVW

FDVHWHVWVFULSWWHVWWRRO

"1DPHVDQGRUGHVFULSWLRQVRIILOHGDWDPHVVDJHVHWF XVHGLQWHVW

")LOHH[FHUSWVHUURUPHVVDJHVORJILOHH[FHUSWVVFUHHQVKRWVWHVW

WRROORJVWKDWZRXOGEHKHOSIXOLQILQGLQJWKHFDXVHRIWKHSUREOHP

"6HYHULW\HVWLPDWHDOHYHOUDQJHVXFKDV RU

FULWLFDOWRORZLVFRPPRQ

":DVWKHEXJUHSURGXFLEOH"

"7HVWHUQDPH

"7HVWGDWH

"%XJUHSRUWLQJGDWH

"1DPHRIGHYHORSHUJURXSRUJDQL]DWLRQWKHSUREOHPLVDVVLJQHGWR

"'HVFULSWLRQRISUREOHPFDXVH

"'HVFULSWLRQRIIL[

"&RGHVHFWLRQILOHPRGXOHFODVVPHWKRGWKDWZDVIL[HG

"'DWHRIIL[

"$SSOLFDWLRQYHUVLRQWKDWFRQWDLQVWKHIL[

"7HVWHUUHVSRQVLEOHIRUUHWHVW

"5HWHVWGDWH

"5HWHVWUHVXOWV

"5HJUHVVLRQWHVWLQJUHTXLUHPHQWV

"7HVWHUUHVSRQVLEOHIRUUHJUHVVLRQWHVWV


30/35

"5HJUHVVLRQWHVWLQJUHVXOWV

$UHSRUWLQJRUWUDFNLQJSURFHVVVKRXOGHQDEOHQRWLILFDWLRQRI

DSSURSULDWHSHUVRQQHODWYDULRXVVWDJHV

)RULQVWDQFHWHVWHUVQHHGWRNQRZZKHQUHWHVWLQJLVQHHGHG

GHYHORSHUVQHHGWRNQRZZKHQEXJVDUHIRXQGDQGKRZWRJHWWKHQHHGHG

LQIRUPDWLRQDQGUHSRUWLQJVXPPDU\FDSDELOLWLHVDUHQHHGHGIRUPDQDJHUV

:KDWLVFRQILJXUDWLRQPDQDJHPHQW"

&RQILJXUDWLRQPDQDJHPHQWFRYHUVWKHSURFHVVHVXVHGWRFRQWURO

FRRUGLQDWHDQGWUDFNFRGHUHTXLUHPHQWVGRFXPHQWDWLRQSUREOHPV

FKDQJHUHTXHVWVGHVLJQVWRROVFRPSLOHUVOLEUDULHVSDWFKHVFKDQJHV

PDGHWRWKHPDQGZKRPDNHVWKHFKDQJHV

:KDWLIWKHVRIWZDUHLVVREXJJ\LWFDQWUHDOO\EHWHVWHGDWDOO"

7KHEHVWEHWLQWKLVVLWXDWLRQLVIRUWKHWHVWHUVWRJRWKURXJKWKH

SURFHVVRIUHSRUWLQJZKDWHYHUEXJVRUEORFNLQJW\SHSUREOHPVLQLWLDOO\

VKRZXSZLWKWKHIRFXVEHLQJRQFULWLFDOEXJV 6LQFHWKLVW\SHRI

SUREOHPFDQVHYHUHO\DIIHFWVFKHGXOHVDQGLQGLFDWHVGHHSHUSUREOHPV

LQWKHVRIWZDUHGHYHORSPHQWSURFHVVVXFKDVLQVXIILFLHQWXQLW

WHVWLQJRULQVXIILFLHQWLQWHJUDWLRQWHVWLQJSRRUGHVLJQLPSURSHUEXLOGRUUHOHDVHSURFHGXUHVHWF PDQDJHUVVKRXOGEHQRWLILHGDQG

SURYLGHGZLWKVRPHGRFXPHQWDWLRQDVHYLGHQFHRIWKHSUREOHP

+RZFDQLWEHNQRZQZKHQWRVWRSWHVWLQJ"

7KLVFDQEHGLIILFXOWWRGHWHUPLQH 0DQ\PRGHUQVRIWZDUHDSSOLFDWLRQV

DUHVRFRPSOH[DQGUXQLQVXFKDQLQWHUGHSHQGHQWHQYLURQPHQWWKDW

FRPSOHWHWHVWLQJFDQQHYHUEHGRQH &RPPRQIDFWRUVLQGHFLGLQJZKHQWR

VWRSDUH

"'HDGOLQHVUHOHDVHGHDGOLQHVWHVWLQJGHDGOLQHVHWF

"7HVWFDVHVFRPSOHWHGZLWKFHUWDLQSHUFHQWDJHSDVVHG

"7HVWEXGJHWGHSOHWHG"&RYHUDJHRIFRGHIXQFWLRQDOLW\UHTXLUHPHQWVUHDFKHVDVSHFLILHGSRLQW

"%XJUDWHIDOOVEHORZDFHUWDLQOHYHO

"%HWDRUDOSKDWHVWLQJSHULRGHQGV

:KDWLIWKHUHLVQWHQRXJKWLPHIRUWKRURXJKWHVWLQJ"

8VHULVNDQDO\VLVWRGHWHUPLQHZKHUHWHVWLQJVKRXOGEHIRFXVHG

6LQFHLWVUDUHO\SRVVLEOHWRWHVWHYHU\SRVVLEOHDVSHFWRIDQ

DSSOLFDWLRQHYHU\SRVVLEOHFRPELQDWLRQRIHYHQWVHYHU\GHSHQGHQF\

RUHYHU\WKLQJWKDWFRXOGJRZURQJULVNDQDO\VLVLVDSSURSULDWHWR

PRVWVRIWZDUHGHYHORSPHQWSURMHFWV

7KLVUHTXLUHVMXGJHPHQWVNLOOVFRPPRQVHQVHDQGH[SHULHQFH ,I

ZDUUDQWHGIRUPDOPHWKRGVDUHDOVRDYDLODEOH

&RQVLGHUDWLRQVFDQLQFOXGH

":KLFKIXQFWLRQDOLW\LVPRVWLPSRUWDQWWRWKHSURMHFWVLQWHQGHGSXUSRVH"

":KLFKIXQFWLRQDOLW\LVPRVWYLVLEOHWRWKHXVHU"

":KLFKIXQFWLRQDOLW\KDVWKHODUJHVWVDIHW\LPSDFW"

":KLFKIXQFWLRQDOLW\KDVWKHODUJHVWILQDQFLDOLPSDFWRQXVHUV"

":KLFKDVSHFWVRIWKHDSSOLFDWLRQDUHPRVWLPSRUWDQWWRWKHFXVWRPHU"

":KLFKDVSHFWVRIWKHDSSOLFDWLRQFDQEHWHVWHGHDUO\LQWKH

GHYHORSPHQWF\FOH"


31/35

":KLFKSDUWVRIWKHFRGHDUHPRVWFRPSOH[DQGWKXVPRVWVXEMHFWWR

HUURUV"

":KLFKSDUWVRIWKHDSSOLFDWLRQZHUHGHYHORSHGLQUXVKRUSDQLFPRGH"

":KLFKDVSHFWVRIVLPLODUUHODWHGSUHYLRXVSURMHFWVFDXVHGSUREOHPV"

":KLFKDVSHFWVRIVLPLODUUHODWHGSUHYLRXVSURMHFWVKDGODUJH

PDLQWHQDQFHH[SHQVHV"

":KLFKSDUWVRIWKHUHTXLUHPHQWVDQGGHVLJQDUHXQFOHDURUSRRUO\

WKRXJKWRXW"

":KDWGRWKHGHYHORSHUVWKLQNDUHWKHKLJKHVWULVNDVSHFWVRIWKH

DSSOLFDWLRQ"

":KDWNLQGVRISUREOHPVZRXOGFDXVHWKHZRUVWSXEOLFLW\"

":KDWNLQGVRISUREOHPVZRXOGFDXVHWKHPRVWFXVWRPHUVHUYLFHFRPSODLQWV"

":KDWNLQGVRIWHVWVFRXOGHDVLO\FRYHUPXOWLSOHIXQFWLRQDOLWLHV"

":KLFKWHVWVZLOOKDYHWKHEHVWKLJKULVNFRYHUDJHWRWLPHUHTXLUHG

UDWLR"

:KDWLIWKHSURMHFWLVQWELJHQRXJKWRMXVWLI\H[WHQVLYHWHVWLQJ"

&RQVLGHUWKHLPSDFWRISURMHFWHUURUVQRWWKHVL]HRIWKHSURMHFW

+RZHYHULIH[WHQVLYHWHVWLQJLVVWLOOQRWMXVWLILHGULVNDQDO\VLVLV

DJDLQQHHGHGDQGWKHVDPHFRQVLGHUDWLRQVDVGHVFULEHGSUHYLRXVO\LQ

7KHWHVWHUPLJKWWKHQGRDGKRFWHVWLQJRUZULWHXSDOLPLWHGWHVW

SODQEDVHGRQWKHULVNDQDO\VLV

:KDWFDQEHGRQHLIUHTXLUHPHQWVDUHFKDQJLQJFRQWLQXRXVO\"

$FRPPRQSUREOHPDQGDPDMRUKHDGDFKH

":RUNZLWKWKHSURMHFWVVWDNHKROGHUVHDUO\RQWRXQGHUVWDQGKRZ

UHTXLUHPHQWVPLJKWFKDQJHVRWKDWDOWHUQDWHWHVWSODQVDQGVWUDWHJLHV

FDQEHZRUNHGRXWLQDGYDQFHLISRVVLEOH

",WVKHOSIXOLIWKHDSSOLFDWLRQVLQLWLDOGHVLJQDOORZVIRUVRPH

DGDSWDELOLW\VRWKDWODWHUFKDQJHVGRQRWUHTXLUHUHGRLQJWKH

DSSOLFDWLRQIURPVFUDWFK

",IWKHFRGHLVZHOOFRPPHQWHGDQGZHOOGRFXPHQWHGWKLVPDNHVFKDQJHVHDVLHUIRUWKHGHYHORSHUV

"8VHUDSLGSURWRW\SLQJZKHQHYHUSRVVLEOHWRKHOSFXVWRPHUVIHHOVXUH

RIWKHLUUHTXLUHPHQWVDQGPLQLPL]HFKDQJHV

"7KHSURMHFWVLQLWLDOVFKHGXOHVKRXOGDOORZIRUVRPHH[WUDWLPH

FRPPHQVXUDWHZLWKWKHSRVVLELOLW\RIFKDQJHV

"7U\WRPRYHQHZUHTXLUHPHQWVWRD3KDVHYHUVLRQRIDQ

DSSOLFDWLRQZKLOHXVLQJWKHRULJLQDOUHTXLUHPHQWVIRUWKH3KDVH

YHUVLRQ

"1HJRWLDWHWRDOORZRQO\HDVLO\LPSOHPHQWHGQHZUHTXLUHPHQWVLQWRWKH

SURMHFWZKLOHPRYLQJPRUHGLIILFXOWQHZUHTXLUHPHQWVLQWRIXWXUH

YHUVLRQVRIWKHDSSOLFDWLRQ

"%HVXUHWKDWFXVWRPHUVDQGPDQDJHPHQWXQGHUVWDQGWKHVFKHGXOLQJLPSDFWVLQKHUHQWULVNVDQGFRVWVRIVLJQLILFDQWUHTXLUHPHQWV

FKDQJHV7KHQOHWPDQDJHPHQWRUWKHFXVWRPHUVQRWWKHGHYHORSHUVRU

WHVWHUVGHFLGHLIWKHFKDQJHVDUHZDUUDQWHGDIWHUDOOWKDWVWKHLU

MRE

"%DODQFHWKHHIIRUWSXWLQWRVHWWLQJXSDXWRPDWHGWHVWLQJZLWKWKH

H[SHFWHGHIIRUWUHTXLUHGWRUHGRWKHPWRGHDOZLWKFKDQJHV

"7U\WRGHVLJQVRPHIOH[LELOLW\LQWRDXWRPDWHGWHVWVFULSWV

")RFXVLQLWLDODXWRPDWHGWHVWLQJRQDSSOLFDWLRQDVSHFWVWKDWDUHPRVW

OLNHO\WRUHPDLQXQFKDQJHG

"'HYRWHDSSURSULDWHHIIRUWWRULVNDQDO\VLVRIFKDQJHVWRPLQLPL]H


32/35

UHJUHVVLRQWHVWLQJQHHGV

"'HVLJQVRPHIOH[LELOLW\LQWRWHVWFDVHVWKLVLVQRWHDVLO\GRQH

WKHEHVWEHWPLJKWEHWRPLQLPL]HWKHGHWDLOLQWKHWHVWFDVHVRUVHW

XSRQO\KLJKHUOHYHOJHQHULFW\SHWHVWSODQV

")RFXVOHVVRQGHWDLOHGWHVWSODQVDQGWHVWFDVHVDQGPRUHRQDGKRF

WHVWLQJZLWKDQXQGHUVWDQGLQJRIWKHDGGHGULVNWKDWWKLVHQWDLOV

:KDWLIWKHDSSOLFDWLRQKDVIXQFWLRQDOLW\WKDWZDVQWLQWKH

UHTXLUHPHQWV"

,WPD\WDNHVHULRXVHIIRUWWRGHWHUPLQHLIDQDSSOLFDWLRQKDV

VLJQLILFDQWXQH[SHFWHGRUKLGGHQIXQFWLRQDOLW\DQGLWZRXOGLQGLFDWH

GHHSHUSUREOHPVLQWKHVRIWZDUHGHYHORSPHQWSURFHVV

,IWKHIXQFWLRQDOLW\LVQWQHFHVVDU\WRWKHSXUSRVHRIWKH

DSSOLFDWLRQLWVKRXOGEHUHPRYHGDVLWPD\KDYHXQNQRZQLPSDFWVRU

GHSHQGHQFLHVWKDWZHUHQRWWDNHQLQWRDFFRXQWE\WKHGHVLJQHURUWKH

FXVWRPHU

,IQRWUHPRYHGGHVLJQLQIRUPDWLRQZLOOEHQHHGHGWRGHWHUPLQHDGGHG

WHVWLQJQHHGVRUUHJUHVVLRQWHVWLQJQHHGV

0DQDJHPHQWVKRXOGEHPDGHDZDUHRIDQ\VLJQLILFDQWDGGHGULVNVDVD

UHVXOWRIWKHXQH[SHFWHGIXQFWLRQDOLW\

,IWKHIXQFWLRQDOLW\RQO\HIIHFWVDUHDVVXFKDVPLQRULPSURYHPHQWVLQ

WKHXVHULQWHUIDFHIRUH[DPSOHLWPD\QRWEHDVLJQLILFDQWULVN

+RZFDQ6RIWZDUH4$SURFHVVHVEHLPSOHPHQWHGZLWKRXWVWLIOLQJ

SURGXFWLYLW\"

%\LPSOHPHQWLQJ4$SURFHVVHVVORZO\RYHUWLPHXVLQJFRQVHQVXVWR

UHDFKDJUHHPHQWRQSURFHVVHVDQGDGMXVWLQJDQGH[SHULPHQWLQJDVDQ

RUJDQL]DWLRQJURZVDQGPDWXUHVSURGXFWLYLW\ZLOOEHLPSURYHGLQVWHDG

RIVWLIOHG3UREOHPSUHYHQWLRQZLOOOHVVHQWKHQHHGIRUSUREOHP

GHWHFWLRQSDQLFVDQGEXUQRXWZLOOGHFUHDVHDQGWKHUHZLOOEH

LPSURYHGIRFXVDQGOHVVZDVWHGHIIRUW $WWKHVDPHWLPHDWWHPSWVVKRXOGEHPDGHWRNHHSSURFHVVHVVLPSOHDQGHIILFLHQWPLQLPL]H

SDSHUZRUNSURPRWHFRPSXWHUEDVHGSURFHVVHVDQGDXWRPDWHGWUDFNLQJDQG

UHSRUWLQJPLQLPL]HWLPHUHTXLUHGLQPHHWLQJVDQGSURPRWHWUDLQLQJDV

SDUWRIWKH4$SURFHVV +RZHYHUQRRQHHVSHFLDOO\WDOHQWHG

WHFKQLFDOW\SHVOLNHVUXOHVRUEXUHDFUDF\DQGLQWKHVKRUWUXQ

WKLQJVPD\VORZGRZQDELW $W\SLFDOVFHQDULRZRXOGEHWKDWPRUHGD\V

RISODQQLQJDQGGHYHORSPHQWZLOOEHQHHGHGEXWOHVVWLPHZLOOEH

UHTXLUHGIRUODWHQLJKWEXJIL[LQJDQGFDOPLQJRILUDWHFXVWRPHUV

:KDWLIDQRUJDQL]DWLRQLVJURZLQJVRIDVWWKDWIL[HG4$SURFHVVHV

DUHLPSRVVLEOH"

7KLVLVDFRPPRQSUREOHPLQWKHVRIWZDUHLQGXVWU\HVSHFLDOO\LQQHZ

WHFKQRORJ\DUHDV7KHUHLVQRHDV\VROXWLRQLQWKLVVLWXDWLRQRWKHUWKDQ

"+LUHJRRGSHRSOH

"0DQDJHPHQWVKRXOGUXWKOHVVO\SULRULWL]HTXDOLW\LVVXHVDQG

PDLQWDLQIRFXVRQWKHFXVWRPHU

"(YHU\RQHLQWKHRUJDQL]DWLRQVKRXOGEHFOHDURQZKDWTXDOLW\PHDQV

WRWKHFXVWRPHU

+RZGRHVDFOLHQWVHUYHUHQYLURQPHQWDIIHFWWHVWLQJ"


33/35

&OLHQWVHUYHUDSSOLFDWLRQVFDQEHTXLWHFRPSOH[GXHWRWKHPXOWLSOH

GHSHQGHQFLHVDPRQJFOLHQWVGDWDFRPPXQLFDWLRQVKDUGZDUHDQGVHUYHUV

7KXVWHVWLQJUHTXLUHPHQWVFDQEHH[WHQVLYH :KHQWLPHLVOLPLWHGDV

LWXVXDOO\LVWKHIRFXVVKRXOGEHRQLQWHJUDWLRQDQGV\VWHPWHVWLQJ

$GGLWLRQDOO\ORDGVWUHVVSHUIRUPDQFHWHVWLQJPD\EHXVHIXOLQ

GHWHUPLQLQJFOLHQWVHUYHUDSSOLFDWLRQOLPLWDWLRQVDQGFDSDELOLWLHV

7KHUHDUHFRPPHUFLDOWRROVWRDVVLVWZLWKVXFKWHVWLQJ

+RZFDQ:RUOG:LGH:HEVLWHVEHWHVWHG"

:HEVLWHVDUHHVVHQWLDOO\FOLHQWVHUYHUDSSOLFDWLRQVZLWKZHE

VHUYHUVDQGEURZVHUFOLHQWV &RQVLGHUDWLRQVKRXOGEHJLYHQWRWKH

LQWHUDFWLRQVEHWZHHQKWPOSDJHV7&3,3FRPPXQLFDWLRQV,QWHUQHW

FRQQHFWLRQVILUHZDOOVDSSOLFDWLRQVWKDWUXQLQZHESDJHVVXFKDV

DSSOHWVMDYDVFULSWSOXJLQDSSOLFDWLRQVDQGDSSOLFDWLRQVWKDWUXQ

RQWKHVHUYHUVLGHVXFKDVFJLVFULSWVGDWDEDVHLQWHUIDFHVORJJLQJ

DSSOLFDWLRQVG\QDPLFSDJHJHQHUDWRUVDVSHWF

$GGLWLRQDOO\WKHUHDUHDZLGHYDULHW\RIVHUYHUVDQGEURZVHUV

YDULRXVYHUVLRQVRIHDFKVPDOOEXWVRPHWLPHVVLJQLILFDQWGLIIHUHQFHV

EHWZHHQWKHPYDULDWLRQVLQFRQQHFWLRQVSHHGVUDSLGO\FKDQJLQJ

WHFKQRORJLHVDQGPXOWLSOHVWDQGDUGVDQGSURWRFROV

7KHHQGUHVXOWLVWKDWWHVWLQJIRUZHEVLWHVFDQEHFRPHDPDMRU

RQJRLQJHIIRUW

2WKHUFRQVLGHUDWLRQVPLJKWLQFOXGH

":KDWDUHWKHH[SHFWHGORDGVRQWKHVHUYHUH JQXPEHURIKLWVSHU

XQLWWLPH"DQGZKDWNLQGRISHUIRUPDQFHLVUHTXLUHGXQGHUVXFKORDGV

VXFKDVZHEVHUYHUUHVSRQVHWLPHGDWDEDVHTXHU\UHVSRQVHWLPHV

":KDWNLQGVRIWRROVZLOOEHQHHGHGIRUSHUIRUPDQFHWHVWLQJVXFKDV

ZHEORDGWHVWLQJWRROVRWKHUWRROVDOUHDG\LQKRXVHWKDWFDQEH

DGDSWHGZHEURERWGRZQORDGLQJWRROVHWF "

":KRLVWKHWDUJHWDXGLHQFH":KDWNLQGRIEURZVHUVZLOOWKH\EH

XVLQJ":KDWNLQGRIFRQQHFWLRQVSHHGVZLOOWKH\E\XVLQJ"$UHWKH\

LQWUDRUJDQL]DWLRQWKXVZLWKOLNHO\KLJKFRQQHFWLRQVSHHGVDQG

VLPLODUEURZVHUVRU,QWHUQHWZLGHWKXVZLWKDZLGHYDULHW\RI

FRQQHFWLRQVSHHGVDQGEURZVHUW\SHV"

":KDWNLQGRISHUIRUPDQFHLVH[SHFWHGRQWKHFOLHQWVLGHH JKRZ

IDVWVKRXOGSDJHVDSSHDUKRZIDVWVKRXOGDQLPDWLRQVDSSOHWVHWF

ORDGDQGUXQ"

":LOOGRZQWLPHIRUVHUYHUDQGFRQWHQWPDLQWHQDQFHXSJUDGHVEH

DOORZHG"KRZPXFK"

":KDWNLQGVRIVHFXULW\ILUHZDOOVHQFU\SWLRQVSDVVZRUGVHWF

ZLOOEHUHTXLUHGDQGZKDWLVLWH[SHFWHGWRGR"+RZFDQLWEHWHVWHG"

"+RZUHOLDEOHDUHWKHVLWHV,QWHUQHWFRQQHFWLRQVUHTXLUHGWREH"$QG

KRZGRHVWKDWDIIHFWEDFNXSV\VWHPRUUHGXQGDQWFRQQHFWLRQ

UHTXLUHPHQWVDQGWHVWLQJ"

":KDWSURFHVVHVZLOOEHUHTXLUHGWRPDQDJHXSGDWHVWRWKHZHEVLWHV

FRQWHQWDQGZKDWDUHWKHUHTXLUHPHQWVIRUPDLQWDLQLQJWUDFNLQJDQG

FRQWUROOLQJSDJHFRQWHQWJUDSKLFVOLQNVHWF "

":KLFK+70/VSHFLILFDWLRQZLOOEHDGKHUHGWR"+RZVWULFWO\":KDW

YDULDWLRQVZLOOEHDOORZHGIRUWDUJHWHGEURZVHUV"

":LOOWKHUHEHDQ\VWDQGDUGVRUUHTXLUHPHQWVIRUSDJHDSSHDUDQFH

DQGRUJUDSKLFVWKURXJKRXWDVLWHRUSDUWVRIDVLWH""

"+RZZLOOLQWHUQDODQGH[WHUQDOOLQNVEHYDOLGDWHGDQGXSGDWHG"KRZ

RIWHQ"

"&DQWHVWLQJEHGRQHRQWKHSURGXFWLRQV\VWHPRUZLOODVHSDUDWH

WHVWV\VWHPEHUHTXLUHG"+RZDUHEURZVHUFDFKLQJYDULDWLRQVLQ


34/35

EURZVHURSWLRQVHWWLQJVGLDOXSFRQQHFWLRQYDULDELOLWLHVDQG

UHDOZRUOGLQWHUQHWWUDIILFFRQJHVWLRQSUREOHPVWREHDFFRXQWHGIRU

LQWHVWLQJ"

"+RZH[WHQVLYHRUFXVWRPL]HGDUHWKHVHUYHUORJJLQJDQGUHSRUWLQJ

UHTXLUHPHQWVDUHWKH\FRQVLGHUHGDQLQWHJUDOSDUWRIWKHV\VWHPDQG

GRWKH\UHTXLUHWHVWLQJ"

"+RZDUHFJLSURJUDPVDSSOHWVMDYDVFULSWV$FWLYH;FRPSRQHQWVHWF

WREHPDLQWDLQHGWUDFNHGFRQWUROOHGDQGWHVWHG"

"3DJHVVKRXOGEHVFUHHQVPD[XQOHVVFRQWHQWLVWLJKWO\IRFXVHGRQ

DVLQJOHWRSLF ,IODUJHUSURYLGHLQWHUQDOOLQNVZLWKLQWKHSDJH

"7KHSDJHOD\RXWVDQGGHVLJQHOHPHQWVVKRXOGEHFRQVLVWHQWWKURXJKRXW

DVLWHVRWKDWLWVFOHDUWRWKHXVHUWKDWWKH\UHVWLOOZLWKLQDVLWH

"3DJHVVKRXOGEHDVEURZVHULQGHSHQGHQWDVSRVVLEOHRUSDJHVVKRXOG

EHSURYLGHGRUJHQHUDWHGEDVHGRQWKHEURZVHUW\SH

"$OOSDJHVVKRXOGKDYHOLQNVH[WHUQDOWRWKHSDJHWKHUHVKRXOGEHQR

GHDGHQGSDJHV

"7KHSDJHRZQHUUHYLVLRQGDWHDQGDOLQNWRDFRQWDFWSHUVRQRU

RUJDQL]DWLRQVKRXOGEHLQFOXGHGRQHDFKSDJH

+RZLVWHVWLQJDIIHFWHGE\REMHFWRULHQWHGGHVLJQV"

:HOOHQJLQHHUHGREMHFWRULHQWHGGHVLJQFDQPDNHLWHDVLHUWRWUDFH

IURPFRGHWRLQWHUQDOGHVLJQWRIXQFWLRQDOGHVLJQWRUHTXLUHPHQWV

:KLOHWKHUHZLOOEHOLWWOHDIIHFWRQEODFNER[WHVWLQJZKHUHDQ

XQGHUVWDQGLQJRIWKHLQWHUQDOGHVLJQRIWKHDSSOLFDWLRQLV

XQQHFHVVDU\ZKLWHER[WHVWLQJFDQEHRULHQWHGWRWKHDSSOLFDWLRQV

REMHFWV,IWKHDSSOLFDWLRQZDVZHOOGHVLJQHGWKLVFDQVLPSOLI\WHVW

GHVLJQ

:KDWLV([WUHPH3URJUDPPLQJDQGZKDWVLWJRWWRGRZLWKWHVWLQJ"

([WUHPH3URJUDPPLQJ;3LVDVRIWZDUHGHYHORSPHQWDSSURDFKIRUVPDOO

WHDPVRQULVNSURQHSURMHFWVZLWKXQVWDEOHUHTXLUHPHQWV

,WZDVFUHDWHGE\.HQW%HFNZKRGHVFULEHGWKHDSSURDFKLQKLVERRN([WUHPH3URJUDPPLQJ([SODLQHG

7HVWLQJH[WUHPHWHVWLQJLVDFRUHDVSHFWRI([WUHPH3URJUDPPLQJ

3URJUDPPHUVDUHH[SHFWHGWRZULWHXQLWDQGIXQFWLRQDOWHVWFRGHILUVW

EHIRUHWKHDSSOLFDWLRQLVGHYHORSHG

7HVWFRGHLVXQGHUVRXUFHFRQWURODORQJZLWKWKHUHVWRIWKHFRGH

&XVWRPHUVDUHH[SHFWHGWREHDQLQWHJUDOSDUWRIWKHSURMHFWWHDPDQG

WRKHOSGHYHORSVFHQDULRVIRUDFFHSWDQFHEODFNER[WHVWLQJ

$FFHSWDQFHWHVWVDUHSUHIHUDEO\DXWRPDWHGDQGDUHPRGLILHGDQGUHUXQ

IRUHDFKRIWKHIUHTXHQWGHYHORSPHQWLWHUDWLRQV

4$DQGWHVWSHUVRQQHODUHDOVRUHTXLUHGWREHDQLQWHJUDOSDUWRIWKH

SURMHFWWHDP

'HWDLOHGUHTXLUHPHQWVGRFXPHQWDWLRQLVQRWXVHGDQGIUHTXHQW

UHVFKHGXOLQJUHHVWLPDWLQJDQGUHSULRULWL]LQJLVH[SHFWHG

functional requirement: A requirementthatspecifiesafunctionthatacomponentorsystemmust

perform.


35/35

functional testing: Testingbasedonananalysisofthespecificationofthefunctionalityofacomponent

orsystem.

specification: A documentthatspecifies...therequirementsdesignbehaviororothercharacteristicsofa

componentorsystemandoftentheproceduresfordetermining whethertheseprovisionshavebeen

satisfied. [IEEE 610]

functionality: Thecapabiltyofthesoftwareproducttoprovidefunctions whichmeetstatedandimpliedneeds whenthesoftwareisusedunderspecifiedconditions.

functionality testing: Theprocessoftestingtodeterminethefunctionalityofasoftwareproduct.

20110112 - Testing Interview Questions

Documents

Transcript of 20110112 - Testing Interview Questions