Answer Posted / ramyab.mca@gmail.com
Hai....
• Black box testing - not based on any knowledge of
internal design or code. Tests are based on requirements
and functionality.
• White box testing - based on knowledge of the internal
logic of an application's code. Tests are based on coverage
of code statements, branches, paths, conditions.
• 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.
• 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.
• integration testing - testing of combined parts of an
application to determine if they function together
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 and distributed systems.
• functional testing - black-box type testing geared to
functional requirements of an application; this type 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
of testing.)
• system testing - black-box type testing that is based on
overall requirements specifications; covers all combined
parts of a system.
• end-to-end testing - similar to system testing;
the 'macro' end of the test scale; involves testing of 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.
• sanity testing or smoke testing - typically an initial
testing effort to determine if a new software version is
performing well enough to accept it for a major testing
effort. For example, if the new software 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.
• regression testing - re-testing after fixes or
modifications of the software or its environment. It can be
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.
• acceptance testing - final testing based on
specifications of the end-user or customer, or based on use
by end-users/customers over some limited period of time.
• load testing - testing an application under heavy loads,
such as testing of a web site under a range of loads to
determine at what point the system's response time degrades
or fails.
• stress testing - term often used interchangeably
with 'load' and 'performance' testing. Also used to
describe such tests as system functional testing while
under unusually heavy loads, heavy repetition of certain
actions or inputs, input of large numerical values, large
complex queries to a database system, etc.
• 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.
• usability testing - testing for 'user-friendliness'.
Clearly this is subjective, and will depend on the targeted
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.
• install/uninstall testing - testing of full, partial, or
upgrade install/uninstall processes.
• recovery testing - testing how well a system recovers
from crashes, hardware failures, or other catastrophic
problems.
• security testing - testing how well the system protects
against unauthorized internal or external access, willful
damage, etc; may require sophisticated testing techniques.
• compatability testing - testing how well software
performs in a particular hardware/software/operating
system/network/etc. environment.
• exploratory testing - often taken to mean a creative,
informal software test that is not based on formal test
plans or test cases; testers may be learning the software
as they test it.
• ad-hoc testing - similar to exploratory testing, but
often taken to mean that the testers have significant
understanding of the software before testing it.
• user acceptance testing - determining if software is
satisfactory to an end-user or customer.
• comparison testing - comparing software weaknesses and
strengths to competing products.
• alpha testing - testing of an application when
development is nearing completion; minor design changes may
still be made as a result of such testing. Typically done
by end-users or others, not by programmers or testers.
• beta testing - testing when development and testing are
essentially completed and final bugs and problems need to
be found before final release. Typically done by end-users
or others, not by programmers or testers.
• mutation testing - a method for determining if a set of
test data or test cases is useful, by deliberately
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.
K,Byeeee...
Thanks & Regards
B.Ramyasri
| Is This Answer Correct ? | 14 Yes | 0 No |
Post New Answer View All Answers
How does compatibility testing differ while testing in Internet explorer and testing in Firefox?
What is unit level testing?
State a generalized process for load test? Or explain how you did it previously.
Write the test cases for yahoo home page
1. Give me an example of something you tried at work but did not work out so you had to go at things another way. can somebody give a real time example
what could be the (realtime)bugs you come across in job portal and health care projects in terms of 1. high severity n low priority 2. high severity n high priority 3. low severity n low priority 4. low severity n low priority? pls its very urgent thanks n in advance n lukin forward for reply
What is pesticide paradox? How to overcome it?
How do you know the code has met specifications?
Explain the procedure & path of s/w in testing?
hi everybody, iam Adi Durga, i complited my bsc(computers) in 2008.I have experience in finacial and bpo companys(mnc). but iam intersted on s/w role.I have the technical skills c, c++, Oracle 9i and manual testing. But i dont know hoe to strat my career in s/w. Every company offering on financial/bpo side. In this I attended nearly 10 companies,I selected in 8. All those are bpo and finacial, But i cant get any opportunities on s/w side.plz help how to get opportunites on s/w side. Actually I am interested on testing side. But every company offering for only experienced persons. plz help me. this is my mailid.... adi.durga19@gmail.com
What was a problem you had in your previous assignment (testing if possible)? How did you resolve it?
need answer interviewer will ask me about all project which i mention in resume or presently i'm working??please reply tomorrow is my interview
What is Dynamic Binding and Dynamic Loss?
types of reviews?Advantages of reviews? Diff between process and procedure? diff b/w verification and validation? diff b/w cmm,cmmi? exp tqm,gqm,iso,ieee? Roles and responsibilities of tester? Ricks,types of ricks? what r Quality factors?
Define brain stromming and cause effect graphing?
