Answer / 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

Answer / rakesh nelapati

Very good reply... keep it up and help who ever needs good
material.
All the best for ur bright future.
tc bye

I am pranu(frm hyderabad) new commer for this site? I have some doubt's pls clarify it..... I finished my B.Tech 2003 pased out(ECE),(pranati_434@yahoo.co.in) and S/w Testing Course Now iam serarching a job in Testing, I did not have any experience in real time projects. Any body can send me the sample Testcases,Srs,Matrix for Banking,ERP Projects etc.,. 3.5 yrs gap , consultancy..,

2 Answers  

---

Any body can tell what are the contents RTM(Requirements Tracebility Matrix)

2 Answers  

---

Can anyone give me a sample bug report, Iam right now taking training on Testing Tools.

5 Answers  

---

What is difference between Regression and Restesting?

13 Answers   Verisoft,

---

are you ready to work on new domain but you dont have any body to take help or suggestion (seniors).you are the initiator?how will you work in such cases?

2 Answers   Logica CMG,

---

---

What is the difference between GUI Testing,UI testing and Usability TEsting

0 Answers   TCS,

---

What is the difference b/n Testing Methodology and Testing methods?

5 Answers  

---

What is there in the final Test Summary Report

3 Answers   GE,

---

what is advantages and disadvantages of the Waterfall Model and V-Model ?

1 Answers   Crea,

---

Would u provide the exact differences of test case and test conditon 2)test case and use case 3)test suite and test scenara

4 Answers  

---

First window is registertion window where u will be having the fields to entering the name,password and confirm password and Ok button.After hitting the OK button it will take u to 2nd window, wel come window for the user with the msg welcome user. 3rd window will be login screen where u will be entring the user name and password with out any mistake in case and spell (i.e u entered correctly)and 4th window it shows that user does not exits .What will be reasons? Other then data base not connected.

10 Answers   AZTEC,

---

What do u do if the bug that u found is not accepted by the developer and hez saying its not reproducable.Note:The developer is in the onsite location

6 Answers   AZTEC,

---