What is a software testing?

Testing is executing a system. It can identify errors, bugs, gaps or missing in contrary to the
actual requirements. Testing defined according to ANSI/IEEE 1059 standard; A process of
analyzing a software item to detect the differences between existing and required conditions
and to evaluate the features of the software item.

What are the things found when software testing?

Error, Fault and Failure
A programmer makes an error (mistake), which results in a defect (fault, bug) in the
software source code. If this defect is executed, in certain situations the system will
produce wrong results, causing a failure.

Explain the PDCA cycle and where testing fits in?

Plan: Identifying and analyzing the problem.

DO: Developing and testing a potential solution.
Check: Measuring how effective the test solution was, and analyzing whether it could be
improved in any way.
Act: implementing the improved solution fully.
The PDCA cycle origin in 1950. It create by Dr. W. Edwards Deming. He is a lecture in
Japan. This presentation will move from the 1600s with Galileo and the philosophy of
science through the evolution of the scientific method and the science of improvement.
Walter Stewart in 1939 applied the scientific method with his cycle: specification-production
inspection. W. Edwards Deming in 1950 modified the Stewart cycle: design of the product,
make it, put it on the market, test it through market research, then redesign the product. The
Japanese interpretation of the Deming wheel in Dr. Demings lectures of 1950 and 1951
lead to the plan-do-check-action or PDCA cycle. This cycle was integral to the Japanese QC,
TQC, and QC circle activities. Deming introduced his Stewart cycle for learning and
improvement in the USA in 1986. Dr. Deming introduced a more abbreviated PDSA cycle in
1993. In 1994, the PDSA cycle was accompanied by three questions to aid in the planning
step of the PDSA Cycle. In 1996 and 2009 publications, the PDSA cycle was broadened to
include strategies and methods to develop, test, and implement changes that would result in
improvement. This version was called the Model for Improvement. As an introduction to a

framework for improvement, the model for improvement has been found to support
improvement efforts in a full range from the very informal to the most complex.

What is a software process?

In contrast to software life cycle models, software process models often represent a
networked sequence of activities, objects, transformations, and events that embody strategies
for accomplishing software evolution. Such models can be used to develop more precise and
formalized descriptions of software life cycle activities. Their power emerges from their
utilization of a sufficiently rich notation, syntax, or semantics, often suitable for
computational processing. Software process networks can be viewed as representing multiple
interconnected task chains.
Develop an informal narrative specification of the system.
Identify the objects and their attributes.
Identify the operations on the objects.
Identify the interfaces between objects, attributes, or operations.
Implement the operations.

Why is testing important?

We can identify errors, faults, bugs and failure in software with software testing. So we can
give good product for our client. We can overcome loss money and harmful environment.

What is software bugs?

A software bug is an error, flaw, failure, or fault in a computer program or system that causes
it to produce an incorrect or unexpected result, or to behave in unintended ways. Most bugs
arise from mistakes and errors made by people in either a program's source code or its design,
or in frameworks and operating systems used by such programs, and a few are caused
by compilers producing incorrect code. A program that contains a large number of bugs,
and/or bugs that seriously interfere with its functionality, is said to be buggy or defective.
Reports detailing bugs in a program are commonly known as bug reports, defect reports, fault
reports, problem reports, trouble reports, change requests, and so forth.
Bugs trigger errors that can in turn have a wide variety of ripple effects, with varying levels
of inconvenience to the user of the program. Some bugs have only a subtle effect on the

program's functionality, and may thus lie undetected for a long time. More serious bugs may
cause the program to crash or freeze. Others qualify as security bugs and might for example
enable a malicious user to bypass access controls in order to obtain unauthorized privileges.

What are the factors testing can involve?

Planning: A good planner is an achiever. But when it comes to real-time planning, believe
me, its not easy. You have to consider everything Your strength and your weaknesses,
teams capabilities and tools availability, requirements and constraints, approach and
obstacles.
Communication: Transparent communication is a key point for any project. Whether its client
communication, internal team communication, communication with management or
communication with third party, it plays an important part in success of the project.
Skills and knowledge: This is by default the most important part of any project. No matter
how good you plan and how best tools are available, if you do not have required skills in the
team, nothing can work. Updating oneself with current trends is very important.
Tools: Specific tools can make your project timeline achievable. Only manual efforts do not
work in the fast world of today. Even if that is the only option, it should be supported with
scripting knowledge, reporting tools, bug tracking, and project management tools. With this,
automation tools are popping up like anything and having knowledge about specific tools and
ability to select right tool as per requirements is expected at every level of testing.

Explain the software testing team key players and their roles?
Business sponsor and partners: Provides funding. Specifies requirements and deliverables.
Approves changes and some test results.
Project manager Plans and manages the project Software developer: Designs, codes, and
builds the application. Participates in code reviews and testing. Fixes bugs, defects, and
shortcomings.
Testing Coordinator: Creates test plans and test specifications based on the requirements and
functional and technical documents.
Tester: executes the tests and documents results.

Who does the testing?

Software tester
Software developer
Project lead/ Manager
End user

Write short description for following topics

Error

The word error entails different meanings and usages relative to how it
is conceptually applied. The concrete meaning of the Latin word "error" is "wandering" or
"straying". Unlike an illusion, an error or a mistake can sometimes be dispelled through
knowledge. For example, a person who uses too much of an ingredient in a recipe and has a
failed product can learn the right amount to use and avoid repeating the mistake. However,
some errors can occur even when individuals have the required knowledge to perform a task
correctly. Examples include forgetting to collect change after buying chocolate from a
vending machine, forgetting the original document after making photocopies, and forgetting
to turn the gas off after cooking a meal. Some errors occur when an individual is distracted by
something else.
Bug
A software bug is an error, flaw, failure, or fault in a computer program or system that causes
it to produce an incorrect or unexpected result, or to behave in unintended ways. Most bugs
arise from mistakes and errors made by people in either a program's source code or its design,
or in frameworks and operating systems used by such programs, and a few are caused
by compilers producing incorrect code. A program that contains a large number of bugs,
and/or bugs that seriously interfere with its functionality, is said to be buggy or defective.
Reports detailing bugs in a program are commonly known as bug reports, defect reports, fault
reports, problem reports, trouble reports, change requests, and so forth.
Fault
In computing and operating systems, a trap, also known as an exception or a fault, is
typically a type of synchronous interrupt typically caused by an exceptional condition. A trap
usually results in a switch to kernel mode, wherein the operating system performs some
action before returning control to the originating process. A trap in a system process is more
serious than a trap in a user process, and in some systems is fatal. In some usages, the
term trap refers specifically to an interrupt intended to initiate a context switch to a monitor
program or debugger.
Failure
A failure occurs when a faulty piece of code is executed leading to incorrect state that f
propagates to the programs output. The following figure tells us how Error made by human
will result in failure of the software.