What is Software Testing?

Ans:
Software testing can be stated as the process of validating and verifying that a
softwareprogram/application/product:Meets the business and technical requiremen
ts that guided its design and development; works asexpected; and can be implemen
ted with the same characteristics.
166. What is a bug?Ans:
Bug is found before the application goes into hands of the customer. (realese).
Generally found bythe testers.
167. What is a defect?Ans
: Defect is found after the application goes into the hands of customer(realese)
. Generally found bythe users of application.
168
.
What is functional testing?Ans
: Functional testing refers to activities that verify a specific action or funct
ion of the code. These areusually found in the code requirements documentation,
although some development methodologieswork from use cases or user stories. Func
tional tests tend to answer the question of "can the user dothis" or "does this
particular feature work".
169. What is non-functional testing?Ans:
Non-functional testing refers to aspects of the software that may not be related
to a specificfunction or user action, such as scalability or security. Non-func
tional testing tends to answer suchquestions as "how many people can log in at o
nce".
170. What is scalability?Ans
: Scalability is a desirable property of a system, a network, or a process, whic
h indicates its ability toeither handle growing amounts of work in a graceful ma
nner or to be enlarged.
171. What is security?Ans:
Security means the collective processes and mechanisms by which sensitive and va
luableinformation and services are protected from publication, tampering or coll
apse by unauthorizedactivities or untrustworthy individuals and unplanned events
respectively.
172. What is non-functional testing?Ans:
Non-functional testing refers to aspects of the software that may not be related
to a specificfunction or user action, such as scalability or security. Non-func
tional testing tends to answer suchquestions as "how many people can log in at o
nce".
173. What is static testing?Ans:
Reviews, walkthroughs, or inspections are considered as static testing.
174. What is dynamic testing?Ans:
Actually executing programmed code with a given set of test cases is referred to
as Dynamictesting.
175. Can static testing be omitted?Ans:
Static testing can be (and unfortunately in practice often is) omitted.
176. When can the dynamic testing be started?Ans:
Dynamic testing takes place when the program itself is used for the first time (
which is generallyconsidered the beginning of the testing stage). Dynamic testin
g may begin before the program is 100%complete in order to test particular secti
ons of code (modules or discrete functions). Typical techniquesfor this are eith
er using stubs/drivers or execution from a debugger environment.
177. What is software verification?Ans:
Verification: Have we built the software right? (i.e., does it match the specifi
cation).
178. What is software validation?Ans:
Validation: Have we built the right software? (i.e., is this what the customer w
ants).
179. What is White Box Testing?Ans:
White box testing is when the tester has access to the internal data structures
and algorithmsincluding the code that implement these