**define software testing (Bug, Errors, Faults, Failure)

**Explain Nature of errors

/Software Bug:
• A software bug is the common term used to describe an error, flaw, mistake,
failure or fault in a computer program or system that produces an incorrect or
unexpected result, or which causes the program to perform in an un-intended manner.
1. Errors: An error is a mistake, misconception or misunderstanding on the part of
a software developer. It might be typographical error, a misleading of
specifications, or a misunderstanding of what a subroutine does.
2. Faults: For example, a developer might misunderstand a user-interface
requirement and therefore create a design that includes misunderstanding.
3. Failure: A fault (bug) can go undetected until a failure occurs, which is when a
user or tester perceives that the system is not delivering the expected service
.
**Explain Goals of software testing
1. Immediate Goals: These goals are also called as short term goals. These testing
goals are the immediate result after testing. These goals contain:
(i) Bug discovery: This is the immediate goal of software testing to find errors at
any stage of software development. Numbers of the bugs are discovered in the early
stage of testing.
(ii) Bug prevention: This is the resultant action of bug discovery.
2. Long Term Goals: These testing goals affect the software product quality in the
long term. These include:
(i) Quality: This goal enhances the quality of the software products.
(ii) Customer satisfaction: This goal verifies the customer’s satisfaction for
developed software product.
3. Post Implemented Goals: These goals are important after the software product
released. Some of them are listed below:
(i) Reduce maintenance cost: Post-released errors are costlier to fix and
difficult to identify.
(ii) Improved software testing process: These goals improve the testing process for
future use of software projects. These goals are known as postimplementation goals

**Explain Principal of testing

1. Testing shows the presence of errors:
Testing an application can only disclose one or more defects that exist in the
application, however, testing alone cannot prove that the application is error
free.
2. Exhaustive testing is impossible:
• Unless the application under test (UAT) has a very simple logical structure and
limited input, it is not possible to test all possible combinations of data and
scenarios.
4. Defect clustering:
• During testing, it can be observed that most of the reported defects are related
to a small number of modules within a system i.e. a small number of modules contain
most of the defects in the system.
5. The Fading effectiveness:
• If you keep running the same set of tests over and over again, there chances are
that no more new defects will be discovered by those test cases. Because as the
system evolves, many of the previously reported defects will have been fixed and
the old test cases do not apply anymore.

**write a note on reviews

• Review is the name given to a testing technique done by people. It is a people
based static technique in which one or more people are involved in examining
certain activity or activities. There are a variety of ways in which reviews can be
carried out across different organizations
Software review method include following techniques:
o Formal Review / Technical Review / Peer Review.
o Informal Review.
o Walkthrough.
o Inspection.
o Audit

**explain inspection in details

Inspection is a "formal evaluation technique in which software requirements,
design, or code are examined in detail by a person or group other than the author
to detect faults, violations of development standards, and other problems" (IBM)

**explain walkthrough in details

Walkthroughs can be viewed as presentation reviews in which a review participant,
usually the developer of the software being reviewed, narrates a description of the
software and the remainder of the review group provides their feedback throughout
the presentation These are referred to as presentation reviews because the bulk of
the feedback usually only occurs for the material actually presented at the level
it is presented.

**what is Debugging strategies

Debugging is the activity which is carried out by the development team (or
developer), after getting the test report from the testing team about defect(s)
(defects can also be reported by the client). The developer then tries to find the
causes of the defect. Developer may need to go through lines of code and find which
part of code is having
defects.

** What is white box testing? Explain types of white box testing

White Box Testing (WBT) is also known as Code-Based Testing or Structural Testing
White box testing is the software testing method in which internal structure is
known as the tester who is going to test the software. types- Unit Testing,
Integration Testing

**what is black box testing? explain types of black box testing

Black Box Testing, also known as Behavioral Testing, is a software testing method
in which the internal structure/design/implementation of the item being tested is
not known to the tester.

** what is gray box testing

Gray Box Testing is a software testing method which is a combination of Black Box
Testing method and White Box Testing method. In Black Box Testing, the internal
structure of the item being tested is unknown to the tester and in White Box
Testing the internal structure is known.

** list out non functional system testing

Non-functional testing involves testing the product’s quality factors such as
reliability, scalability etc Non-functional testing requires the expected results
to be documented in qualitative and quantifiable terms types-Usability Testing,
Recovery Testing, Installation Testing, Security Testing, Stress Testing.
** what is Acceptance Testing? explain criteria
Acceptance Testing is often the final step before rolling out the application. It
is performed to determine whether system meets user requirements or not Usually the
end users, who will be using the application, test the application
before‘accepting’ it explain criteria- Product Acceptance, Procedure Acceptance,
Service Level Agreements

**VALIDATION AND VERIFICATION

VALIDATION
Validation testing is the process of evaluating a system or component during or at
the end of the development process to determine whether it satisfies specified
requirements or not
VERIFICATION
Verification is the process of evaluating work-products of a development phase to
determine whether they meet the specified requirements. This process ensures that
the product is built according to the requirements and design specifications

** big bang approach non incremental testing

In this type, all components are combined at once to form a program. That is, test
all components in isolation and then mix them all together The non-incremental
approach is also known as "Big-Bang" testing.
• This approach is great with smaller systems, but it can end up taking a lot of
time for larger, more complex systems. However, this approach is not recommended as
both drivers and stubs are required

** load testing
Load testing is a software testing technique used to examine the behavior of a
system under the normal and extreme expected load conditions. This testing is
generally performed under controlled laboratory conditions in order to distinguish
between two different systems. This is a type of non-functional testing

** smoke testing
A smoke test is reduced version of regression testing. Smoke testing is the initial
testing process exercised to check whether the software under test is ready for
further processing. The term smoke testing originated in the hardware industry.
After a part of hardware or a hardware component (For example: transformer) was
changed or repaired, the
equipment was simply powered-up. If there was no smoke, the component passed the
test

**SANDWICH APPROACH
This approach is also called as "Bi-directional integration testing". Sandwich
testing defines testing into two parts and follows both parts starting from both
ends, i.e., top down approach and bottom-up approach either simultaneously or one
after another. In top-down approach, testing can start only after the top-level
modules have been coded and unit tested. Similarly, bottom-up testing can start
only after the bottom
level modules are ready.