The relationship between test cases and requirements is shown with the help of a document. This document is
known as traceability matrix.

Equivalence partitioning testing is a software testing technique which divides the application input test data
into each partition at least once of equivalent data from which test cases can be derived. By this testing
method it reduces the time required for software testing.

Automation is the integration of testing tools into the test environment in such a manner that the test execution,
logging, and comparison of results are done with little human intervention. A testing tool is a software
application which helps automate the testing process. But the testing tool is not the complete answer for
automation. One of the huge mistakes done in testing automation is automating the wrong things during
development. Many testers learn the hard way that everything cannot be automated. The best components to
automate are repetitive tasks. So some companies first start with manual testing and then see which tests are the
most repetitive ones and only those are the automated.
As a rule of thumb do not try to automate:

• Unstable software: If the software is still under development and undergoing many changes automation testing

will not be that effective.

• Once in a blue moon test scripts: Do not automate test scripts which will be run once in a while.
• Code and document review: Do not try to automate code and document reviews; they will just cause trouble.

The following figure shows what should not be automated.

          SHOULD INSERT PICTURE

All repetitive tasks which are frequently used should be automated. For instance, regression tests are prime
candidates for automation because they're typically executed many times. Smoke, load, and performance
tests are other examples of repetitive tasks that are suitable for automation. White box testing can also be
automated using various unit testing tools. Code coverage can also be a good candidate for automation.

White box testing technique involves selection of test cases based on an analysis of the internal structure
(Code coverage, branches coverage, paths coverage, condition coverage etc.) of a component or system. It is
also known as Code-Based testing or Structural testing. Different types of white box testing are :

• Statement Coverage
• Decision Coverage

The following are the important steps used to define a testing policy in general. But it can change
according to your organization. Let's discuss in detail the steps of implementing a testing policy in an
organization.

   SHOULD INSERT PICTURE

Definition: The first step any organization needs to do is define one unique definition for testing within the
organization so that everyone is of the same mindset.
How to achieve: How are we going to achieve our objective? Is there going to be a testing committee, will
there be compulsory test plans which need to be executed, etc?.

Evaluate: After testing is implemented in a project how do we evaluate it? Are we going to derive metrics
of defects per phase, per programmer, etc. Finally, it's important to let everyone know how testing has
added value to the project?.

Standards: Finally, what are the standards we want to achieve by testing? For instance, we can say that more
than 20 defects per KLOC will be considered below standard and code review should be done for it.

It helps prevent defects from being introduced into the code.

Risk-based testing is the term used for an approach to creating a test strategy that is based on prioritizing
tests by risk. The basis of the approach is a detailed risk analysis and prioritizing of risks by risk level.
Tests to address each risk are then specified, starting with the highest risk first.

Preventative tests are designed early; reactive tests are designed after the software has been produced.

In white box testing following steps are verified.

• Verify the security holes in the code
• Verify the incomplete or broken paths in the code
• Verify the flow of structure according to the document specification
• Verify the expected outputs
• Verify all conditional loops in the code to check the complete functionality of the application
• Verify the line by line coding and cover 100% testing

a) Static testing: During Static testing method, the code is not executed and it is performed using the
software documentation.

b) Dynamic testing: To perform this testing the code is required to be in an executable form.

There are four test levels

• Unit/component/program/module testing
• Integration testing
• System testing
• Acceptance testing

Integration testing is a level of software testing process, where individual units of an application are
combined and tested. It is usually performed after unit and functional testing.

Test design, scope, test strategies , approach are various details that Test plan document consists of.

• Test case identifier
• Scope
• Features to be tested
• Features not to be tested
• Test strategy & Test approach
• Test deliverables
• Responsibilities

Configuration management is the detailed recording and updating of information for hardware and software
components. When we say components we not only mean source code. It can be tracking of changes for
software documents such as requirement, design, test cases, etc.
When changes are done in adhoc and in an uncontrolled manner chaotic situations can arise and more
defects injected. So whenever changes are done it should be done in a controlled fashion and with proper
versioning. At any moment of time we should be able to revert back to the old version. The main intention
of configuration management is to track our changes if we have issues with the current system.
Configuration management is done using baselines.

System Testing: System testing is finding defects when the system under goes testing as a whole, it is also
known as end to end testing. In such type of testing, the application undergoes from beginning till the end.

UAT: User Acceptance Testing (UAT) involves running a product through a series of specific tests
which determines whether the product will meet the needs of its users.

While doing testing on the actual product, the code coverage testing tool is run simultaneously. While the
testing is going on, the code coverage tool monitors the executed statements of the source code. When the
final testing is completed we get a complete report of the pending statements and also get the coverage
percentage

Error condition hiding another error condition.

COTS - Commercial off The Shelf.

The purpose of which is allow specific tests to be carried out on a system or network that resembles as
closely as possible the environment where the item under test will be used upon release.

In traditional testing methodology testing is always done after the build and execution phases. But that's a
wrong way of thinking because the earlier we catch a defect, the more cost effective it is. For instance,
fixing a defect in maintenance is ten times more costly than fixing it during execution.
In the requirement phase we can verify if the requirements are met according to the customer needs.
During design we can check whether the design document covers all the requirements. In this stage we can
also generate rough functional data. We can also review the design document from the architecture and the
correctness perspectives. In the build and execution phase we can execute unit test cases and generate
structural and functional data. And finally comes the testing phase done in the traditional way. i.e., run the
system test cases and see if the system works according to the requirements. During installation we need to
see if the system is compatible with the software. Finally, during the maintenance phase when any fixes are
made we can retest the fixes and follow the regression testing. Therefore, Testing should occur in
conjunction with each phase of the software development.

It depends on the risks for the system being tested. There are some criteria bases on which you can stop
testing.

• Deadlines (Testing, Release)
• Test budget has been depleted
• Bug rate fall below certain level
• Test cases completed with certain percentage passed
• Alpha or beta periods for testing ends
• Coverage of code, functionality or requirements are met to a specified point

The main purpose of the integration strategy is to specify which modules to combine when and how many
at once.

Semi-random test cases are nothing but when we perform random test cases and do equivalence
partitioning to those test cases, it removes redundant test cases, thus giving us semi-random test cases.1
test for statement coverage, 2 for branch coverage

Black box testing is the software testing method which is used to test the software without knowing the
internal structure of code or program. This testing is usually done to check the functionality of an
application. The different black box testing techniques are :

• Equivalence Partitioning
• Boundary value analysis
• Cause effect graphing

Technical Review.

The techniques of equivalence partitioning and boundary value analysis are often applied to specific
situations or inputs. However, if different combinations of inputs result in different actions being taken,
this can be more difficult to show using equivalence partitioning and boundary value analysis, which tend
to be more focused on the user interface. The other two specification-based techniques, decision tables and
state transition testing are more focused on business logic or business rules. A decision table is a good way
to deal with combinations of things (e.g. inputs). This technique is sometimes also referred to as a
'cause-effect' table. The reason for this is that there is an associated logic diagramming technique called
'cause-effect graphing' which was sometimes used to help derive the decision table

By testers.

The design phase is more error prone than the execution phase. One of the most frequent defects which
occur during design is that the product does not cover the complete requirements of the customer. Second
is wrong or bad architecture and technical decisions make the next phase, execution, more prone to defects.
Because the design phase drives the execution phase it's the most critical phase to test. The testing of the
design phase can be done by good review. On average, 60% of defects occur during design and 40%
during the execution phase.

In experience-based techniques, people's knowledge, skills and background are a prime contributor to the
test conditions and test cases. The experience of both technical and business people is important, as they
bring different perspectives to the test analysis and design process. Due to previous experience with similar
systems, they may have insights into what could go wrong, which is very useful for testing.

Inspection

Yes, because both help detect faults and improve quality. To test a function, what has to write a
programmer, which calls the function to be tested and passes it test data.

The IEEE Std. 829-1998 defines a test log as a chronological record of relevant details about the execution
of test cases. It's a detailed view of activity and events given in chronological manner.

Entry and exit criteria are a must for the success of any project. If you do not know where to start and
where to finish then your goals are not clear. By defining exit and entry criteria you define your
boundaries. For instance, you can define entry criteria that the customer should provide the requirement
document or acceptance plan. If this entry criteria is not met then you will not start the project. On the
other end, you can also define exit criteria for your project. For instance, one of the common exit criteria in
projects is that the customer has successfully executed the acceptance test plan.

  SHOULD INSERT PICTURES

Verification is a review without actually executing the process while validation is checking the product
with actual execution. For instance, code review and syntax check is verification while actually running the
product and checking the results is validation.

a) Security Testing

Testing where in we subject the target of the test , to varying workloads to measure and evaluate the
performance behaviors and ability of the target and of the test to continue to function properly under these
different workloads?

b) Load Testing

Testing activity which is performed to expose defects in the interfaces and in the interaction between
integrated components is?

A process area is the area of improvement defined by CMMI. Every maturity level consists of process
areas. A process area is a group of practices or activities performed collectively to achieve a specific
objective. For instance, you can see from the following figure we have process areas such as project
planning, configuration management, and requirement gathering.

Random testing often known as monkey testing. In such type of testing data is generated randomly often
using a tool or automated mechanism. With this randomly generated input the system is tested and results
are analyzed accordingly. These testing are less reliable; hence it is normally used by the beginners and to
see whether the system will hold up under adverse effects.

Provide developers and other parties with feedback about the problem to enable identification, isolation
and correction as necessary.

• Provide ideas for test process improvement.
• Provide a vehicle for assessing tester competence.
• Provide testers with a means of tracking the quality of the system under test.

Websites have software called a web server installed on the server. The user sends a request to the web
server and receives a response. So, for instance, when you type www.google.com the web server senses it
and sends you the home page as a response. This happens each time you click on a link, do a submit, etc.
So if we want to do load testing you need to just multiply these requests and responses "N" times. This is
what an automation tool does. It first captures the request and response and then just multiplies it by "N"
times and sends it to the web server, which results in load simulation.

So once the tool captures the request and response, we just need to multiply the request and response with
the virtual user. Virtual users are logical users which actually simulate the actual physical user by sending
in the same request and response. If you want to do load testing with 10,000 users on an application it's
practically impossible. But by using the load testing tool you only need to create 1000 virtual users.

Testing the end to end functionality of the system as a whole is defined as a functional system testing.

The product has to be used by the user. He is the most important person as he has more interest than
anyone else in the project.

SHOULD INSERT IMAGE

From the user we need the following data:

The first thing we need is the acceptance test plan from the end user. The acceptance test defines the entire
test which the product has to pass so that it can go into production. We also need the requirement
document from the customer. In normal scenarios the customer never writes a formal document until he is
really sure of his requirements. But at some point the customer should sign saying yes this is what he
wants.

The customer should also define the risky sections of the project. For instance, in a normal accounting
project if a voucher entry screen does not work that will stop the accounting functionality completely. But
if reports are not derived the accounting department can use it for some time. The customer is the right
person to say which section will affect him the most. With this feedback the testers can prepare a proper
test plan for those areas and test it thoroughly.
The customer should also provide proper data for testing. Feeding proper data during testing is very
important. In many scenarios testers key in wrong data and expect results which are of no interest to the
customer.

Because configuration management assures that we know the exact version of the test ware and the test
object.

A software development model that illustrates how testing activities integrate with software development
phases.

Triggered by modifications, migration or retirement of existing software

In order to understand testing methodology we need to understand the workbench concept. A Workbench
is a way of documenting how a specific activity has to be performed. A workbench is referred to as phases,
steps, and tasks as shown in the following figure.

SHOULD INSERT IMAGE

There are five tasks for every workbench:

Input: Every task needs some defined input and entrance criteria. So for every workbench we need defined
inputs. Input forms the first steps of the workbench.
Execute: This is the main task of the workbench which will transform the input into the expected

Check: Check steps assure that the output after execution meets the desired result.
Production output: If the check is right the production output forms the exit criteria of the workbench.
Rework: During the check step if the output is not as desired then we need to again start from the execute
step.

  SHOULD INSERT IMAGE

Defect cascading is a defect which is caused by another defect. One defect triggers the other defect. For
instance, in the accounting application shown here there is a defect which leads to negative taxation. So the
negative taxation defect affects the ledger which in turn affects four other modules.

SHOULD INSERT IMAGE

When we install the application at the end client it is very possible that on the same PC other applications
also exist. It is also very possible that those applications share common DLLs, resources etc., with your
application. There is a huge chance in such situations that your changes can affect the cohabiting software.
So the best practice is after you install your application or after any changes, tell other application owners
to run a test cycle on their application.

Is it really a test if you put some inputs into some software, but never look to see whether the software
produces the correct result? The essence of testing is to check whether the software produces the correct
result, and to do that, we must compare what the software produces to what it should produce. A test
comparator helps to automate aspects of that comparison. Who is responsible for document all the issues,
problems and open point that were identified during the review meeting

The difference between pilot and beta testing is that pilot testing is nothing but actually using the product
(limited to some users) and in beta testing we do not input real data, but it's installed at the end customer to
validate if the product can be used in production.

The moderator (or review leader) leads the review process. He or she determines, in co-operation with the
author, the type of review, approach and the composition of the review team. The moderator performs the
entry check and the follow-up on the rework, in order to control the quality of the input and output of the
review process. The moderator also schedules the meeting, disseminates documents before the meeting,
coaches other team members, paces the meeting, leads possible discussions and stores the data that is
collected.

The moderator (or review leader) leads the review process. He or she determines, in co-operation with the
author, the type of review, approach and the composition of the review team. The moderator performs the
entry check and the follow-up on the rework, in order to control the quality of the input and output of the
review process. The moderator also schedules the meeting, disseminates documents before the meeting,
coaches other team members, paces the meeting, leads possible discussions and stores the data that is
collected.

An input or output ranges of values such that only one value in the range becomes a test case.

Normally an application has to be tested with multiple sets of data. For instance, a simple login screen,
depending on the user type, will give different rights. For example, if the user is an admin he will have full
rights, while a user will have limited rights and support if he only has read-only support rights. In this
scenario the testing steps are the same but with different user ids and passwords. In data-driven testing,
inputs to the system are read from data files such as Excel, CSV (comma separated values), ODBC, etc. So
the values are read from these sources and then test steps are executed by automated testing.

SHOULD INSERT IMAGE

During test planning.

There are four major ways of rolling out any project:
Pilot : The actual production system is installed at a single or limited number of users. Pilot basically
means that the product is actually rolled out to limited users for real work.

Gradual Implementation: In this implementation we ship the entire product to the limited users or all
users at the customer end. Here, the developers get instant feedback from the recipients which allow them
to make changes before the product is available. But the downside is that developers and testers maintain
more than one version at one time.
Phased Implementation: In this implementation the product is rolled out to all users in incrementally. That
means each successive rollout has some added functionality. So as new functionality comes in, new
installations occur and the customer tests them progressively. The benefit of this kind of rollout is that
customers can start using the functionality and provide valuable feedback progressively. The only issue
here is that with each rollout and added functionality the integration becomes more complicated.

Parallel Implementation: In these types of rollouts the existing application is run side by side with the
new application. If there are any issues with the new application we again move back to the old
application. One of the biggest problems with parallel implementation is we need extra hardware, software,
and resources.

The purpose of exit criteria is to define when a test level is completed.

The likelihood of an adverse event and the impact of the event determine the level of risk.

Decision table testing is used for testing systems for which the specification takes the form of rules or
cause-effect combinations. In a decision table the inputs are listed in a column, with the outputs in the
same column but below the inputs. The remainder of the table explores combinations of inputs to define
the outputs produced.

As the name suggests, tailoring is nothing but changing an action to achieve an objective according to
conditions. Whenever tailoring is done there should be adequate reasons for it. Remember when a process
is defined in an organization it should be followed properly. So even if tailoring is applied the process is
not bypassed or omitted.

As the name suggests, tailoring is nothing but changing an action to achieve an objective according to
conditions. Whenever tailoring is done there should be adequate reasons for it. Remember when a process
is defined in an organization it should be followed properly. So even if tailoring is applied the process is
not bypassed or omitted.

Six Sigma is a statistical measure of variation in a process. We say a process has achieved Six Sigma if the
quality is 3.4 DPMO (Defect per Million Opportunities). It's a problem-solving methodology that can be
applied to a process to eliminate the root cause of defects and costs associated with it.

Independent testers are unbiased and identify different defects at the same time.

The bulk of the test design work begun after the software or system has been produced.

Acceptance testing checks the system against the "Requirements." It is similar to System testing in that the
whole system is checked but the important difference is the change in focus:
System testing checks that the system that was specified has been delivered. Acceptance testing checks
that the system will deliver what was requested. The customer should always do Acceptance testing and
not the developer.
The customer knows what is required from the system to achieve value in the business and is the only
person qualified to make that judgment. This testing is more about ensuring that the software is delivered
as defined by the customer. It's like getting a green light from the customer that the software meets
expectations and is ready to be used.

Test case specification defines the expected results of a test.

It avoids author bias in defining effective tests.

The exit criteria is determined on the bases of ?Test Planning?.

Rapid Application Development (RAD) is formally a parallel development of functions and subsequent
integration. Components/functions are developed in parallel as if they were mini projects, the
developments are time-boxed, delivered, and then assembled into a working prototype. This can very
quickly give the customer something to see and use and to provide feedback regarding the delivery and
their requirements. Rapid change and development of the product is possible using this methodology.
However the product specification will need to be developed for the product at some point, and the project
will need to be placed under more formal controls prior to going into production.

Testing technique : Is a process for ensuring that some aspects of the application system or unit functions
properly there may be few techniques but many tools.

Testing Tools : Is a vehicle for performing a test process. The tool is a resource to the tester, but itself is
insufficient to conduct testing

Regression testing is used for regression defects. Regression defects are defects occur when the
functionality which was once working normally has stopped working. This is probably because of changes
made in the program or the environment. To uncover such kind of defect regression testing is conducted.
The following figure shows the difference between regression and confirmation testing.

SHOULD INSERT IMAGE

If we fix a defect in an existing application we use confirmation testing to test if the defect is removed. It's
very possible because of this defect or changes to the application that other sections of the application are
affected. So to ensure that no other section is affected we can use regression testing to confirm this.

There are currently seven different agile methodologies, they are :

• Extreme Programming (XP)
• Scrum
• Lean Software Development
• Feature-Driven Development
• Agile Unified Process
• Crystal
• Dynamic Systems Development Model (DSDM)

A ?Test Analysis? and ?Design? includes evaluation of the testability of the requirements and system.

Because testing everything is not feasible.

• Equivalence Partitioning.
• Use Case Testing.
• Data Flow Analysis.
• Exploratory Testing.
• Decision Testing.
• Inspections.

Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use Case Testing, Exploratory
Testing and Decision Testing are dynamic.

In most organizations testing only starts after the execution/coding phase of the project. But if the
organization wants to really benefit from testing, then testers should get involved right from the
requirement phase. If the tester gets involved right from the requirement phase then requirement
traceability is one of the important reports that can detail what kind of test coverage the test cases have.

Because they share the aim of identifying defects but differ in the types of defect they find.

In contrast to informal reviews, formal reviews follow a formal process. A typical formal review process
consists of six main steps:

• Planning
• Kick-off
• Preparation
• Rework
• Follow-up.

Structure-based testing techniques (which are also dynamic rather than static) use the internal structure of
the software to derive test cases. They are commonly called 'white-box' or 'glass-box' techniques (implying
you can see into the system) since they require knowledge of how the software is implemented, that is,
how it works. For example, a structural technique may be concerned with exercising loops in the software.
Different test cases may be derived to exercise the loop once, twice, and many times. This may be done
regardless of the functionality of the software.

After the software has changed or when the environment has changed Regression testing should be
performed.

A negative test is when you put in an invalid input and receives errors. While a positive testing, is when
you put in a valid input and expect some action to be completed in accordance with the specification.

The purpose of test completion criterion is to determine when to stop testing

For example memory leaks

Re-testing ensures the original fault has been removed; regression testing looks for unexpected side
effects.

Lack of Objectivity

The answer depends on the risk for your industry, contract and special requirements.

Because errors are frequently made during programming of the different cases near the ?edges? of the range
of values.

It is led by a trained leader, uses formal entry and exit criteria and checklists.

Variation is the basis of Six Sigma. It defines how many changes are happening in the output of a process.
So if a process is improved then this should reduce variations. In Six Sigma we identify variations in the
process, control them, and reduce or eliminate defects.

Test coverage measures in some specific way the amount of testing performed by a set of tests (derived in
some other way, e.g. using specification-based techniques). Wherever we can count things and can tell
whether or not each of those things has been tested by some test, then we can measure coverage.

Because incremental integration has better early defects screening and isolation ability

It would be before test case designing. Requirements should already be traceable from Review activities
since you should have traceability in the Test Plan already. This question also would depend on the
organisation. If the organisations do test after development started then requirements must be already
traceable to their source. To make life simpler use a tool to manage requirements.

Bottom-up integration

Unit testing : Testing performed on a single, stand-alone module or unit of code.
Integration Tests : Testing performed on groups of modules to ensure that data and control are passed
properly between modules.
System testing : Testing a predetermined combination of tests that, when executed successfully meets
requirements.
Acceptance testing : Testing to ensure that the system meets the needs of the organization and the end
user or customer (i.e. validates that the right system was built).

Metrics from previous similar projects and discussions with the development team.When testing a grade
calculation system, a tester determines that all scores from 90 to 100 will yield a grade of A, but scores
below 90 will not. This analysis is known as:

Equivalence partitioning:

A test manager wants to use the resources available for the automated testing of a web application. The
best choice is Tester, test automater, web specialist, DBA

Send to the detailed information of the bug encountered and check the reproducibility

No an increase in testing does not always mean improvement of the product, company, or project. In real
test scenarios only 20% of test plans are critical from a business angle. Running those critical test plans
will assure that the testing is properly done. The following graph explains the impact of under testing and
over testing. If you under test a system the number of defects will increase, but if you over test a system
your cost of testing will increase. Even if your defects come down your cost of testing has gone up.

Normally black box test cases are written first and white box test cases later. In order to write black box
test cases we need the requirement document and, design or project plan. All these documents are easily
available at the initial start of the project. White box test cases cannot be started in the initial phase of the
project because they need more architecture clarity which is not available at the start of the project. So
normally white box test cases are written after black box test cases are written.Black box test cases do not
require system understanding but white box testing needs more structural understanding. And structural
understanding is clearer i00n the later part of project, i.e., while executing or designing. For black box
testing you need to only analyze from the functional perspective which is easily available from a simple
requirement document.

  SHOULD INSERT IMAGE

A type of integration testing in which software elements, hardware elements, or both are combined all at
once into a component or an overall system, rather than in stages.

Big-Bang Testing

Which technique can be used to achieve input and output coverage? It can be applied to human input, input
via interfaces to a system, or interface parameters in integration testing.

Equivalence partitioning

Conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not
be used. For example, the tester may decide to use boundary value analysis but will think through and test
the most important boundary values without necessarily writing them down. Some notes will be written
during the exploratory-testing session, so that a report can be produced afterwards.

In order to identify and execute the functional requirement of an application from end to finish "use case"
is used and the techniques used to do this is known as "Use Case Testing"

The complete Verification and Validation of software is done in SDLC, while STLC only does Validation
of the system. SDLC is a part of STLC.

Software reviews works as a filter for the software process. It helps to uncover errors and defects in
software. Software reviews enhance the quality of software. Software reviews refine software, including
requirements and design models, code, and testing data.

A formal technical review (FTR) is a software quality control activity. In this activity, software developer
and other team members are involved. The objectives of an FTR are:

Uncover the errors.

Verify that the software under technical review meets its requirements.

To ensure that the software must follow the predefined standards.

To make projects more manageable.

The FTR includes walkthroughs and inspections. Each FTR is conducted as a normal meeting. FTR will be
successful only if it is properly planned, and executed.

The following are the attributes of good test case.

• A good test has a high probability of finding an error. To find the maximum error, the tester and developer

should have complete understanding of the software and attempt to check all the conditions that how the
software might fail.

• A good test is not redundant. Every test should have a different purpose from other, otherwise tester will

repeat the testing process for same condition.

• A good test should be neither too simple nor too complex. In general, each test should be executed

separately. If we combine more than one test into one test case, it might be very difficult to execute.
Sometimes we can combine tests but it may hide some errors.

Cyclomatic complexity is a software metric that measure the logical strength of the program. It was
developed by Thomas J. McCabe. Cyclomatic complexity is calculated by using the control flow graph of
the program. In the flow graph, nodes are represented by circle. Areas bounded by edges and nodes are
called regions. When counting regions, we also include the area outside the graph as a region.

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

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.

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

A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality.

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.

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

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

A specification defining requirements for portability of applications in binary forms across different system
platforms and environments.

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

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.

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.

Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are
stress tests).

Verification is a review without actually executing the process while validation is checking the product
with actual execution. For instance, code review and syntax check is verification while actually running the
product and checking the results is validation.

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

If software misses some feature or function from what is there in requirement it is called as defect.

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

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

The Alpha Testing is conducted at the developer sites and in a controlled environment by the end user of
the software

Testing the application after the installation at the client place.

Testing of individual software components (Unit 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.

Computer Aided Software Testing.

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.

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

The generation of source code.

Testing whether software is compatible with other elements of a system with which it should operate, e.g.
browsers, Operating Systems, or hardware.

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

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

Examines an application's requirements for pre-existing software, initial states and configuration in order
to maintain proper functionality.

There are five methodologies most frequently used:
A)Top down according to budget
B)WBS (Work Breakdown Structure)
C)Guess and gut feeling
D)Early project data
E)TPA (Test Point Analysis)

In database testing, we can check the integrity of database field values.

There are two types of testing-
Functional- Black Box Testing
Structural- white Box Testing

Cyclomatic complexity is likely the most widely used complexity metric in software engineering. It
describes the complexity of a procedure by measuring the linearly independent paths through its source
code.

Interoperatability:-To check if the software can co exist with other supporting softwares in the system
Compatibility:-To check if the software runs on different types of operating systems according to customer
requirements.

1) Stress testing
2) Security testing
3) Recovery testing
4) Beta testing

A set of test inputs, execution, and expected result developed for a particular objective.

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

There are two types of approaches used-
Bottom-Up
Top-Down

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

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

A synonym for White Box Testing.

Testing one particular module, functionality heavily.

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.

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.

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.

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.

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

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.

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

A deliverable that describes all data, functional and behavioral requirements, all constraints, and all
validation requirements for software.