hi tell me different testing methodologies
- 7 Answers
- 8515 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / anjali
There are three types of testing methodologies;
WHITE BOX TESTING-Testing structural part of an application.
BLACK BOX TESTING-testing functionality of an application
GREY BOX TESTING-mixture of WBT & BBT
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / murali
scrum,crystal,test driven method,extreme(xp)and etc....
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / hgtrtr
methedologies is white black and gray
where as models are fish,v..................
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / jj
Waterfall, Spiral, V-Model, Incremental model are some of the test methodologies.
White box and Black box are testing techniques used to cover Structural and Functional testing respectively.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / shridatt
Hi the different types of software testing are
Black box testing - Internal system design is not
considered in this type of testing. Tests are based on
requirements and functionality.
White box testing - This testing is based on knowledge of
the internal logic of an application’s code. Also known as
Glass box Testing. Internal software and code working
should be known for this type of testing. Tests are based
on coverage of code statements, branches, paths, conditions.
Unit testing - Testing of individual software components or
modules. Typically done by the programmer and not by
testers, as it requires detailed knowledge of the internal
program design and code. may require developing test driver
modules or test harnesses.
Incremental integration testing - Bottom up approach for
testing i.e continuous testing of an application as new
functionality is added; Application functionality and
modules should be independent enough to test separately.
done by programmers or by testers.
Integration testing - Testing of integrated modules to
verify combined functionality after integration. Modules
are typically 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 - This type of testing ignores the
internal parts and focus on the output is as per
requirement or not. Black-box type testing geared to
functional requirements of an application.
System testing - Entire system is tested as per the
requirements. 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, 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 - Testing to determine if a new software
version is performing well enough to accept it for a major
testing effort. If application is crashing for initial use
then system is not stable enough for further testing and
build or application is assigned to fix.
Regression testing - Testing the application as a whole for
the modification in any module or functionality. Difficult
to cover all the system in regression testing so typically
automation tools are used for these testing types.
Acceptance testing -Normally this type of testing is done
to verify if system meets the customer specified
requirements. User or customer do this testing to determine
whether to accept application.
Load testing - Its a performance testing to check system
behavior under load. 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 - System is stressed beyond its
specifications to check how and when it fails. Performed
under heavy load like putting large number beyond storage
capacity, complex database queries, continuous input to
system or database load.
Performance testing - Term often used interchangeably
with ’stress’ and ‘load’ testing. To check whether system
meets performance requirements. Used different performance
and load tools to do this.
Usability testing - User-friendliness check. Application
flow is tested, Can new user understand the application
easily, Proper help documented whenever user stuck at any
point. Basically system navigation is checked in this
testing.
Install/uninstall testing - Tested for full, partial, or
upgrade install/uninstall processes on different operating
systems under different hardware, software environment.
Recovery testing - Testing how well a system recovers from
crashes, hardware failures, or other catastrophic problems.
Security testing - Can system be penetrated by any hacking
way. Testing how well the system protects against
unauthorized internal or external access. Checked if
system, database is safe from external attacks.
Compatibility testing - Testing how well software performs
in a particular hardware/software/operating system/network
environment and different combination s of above.
Comparison testing - Comparison of product strengths and
weaknesses with previous versions or other similar products.
Alpha testing - In house virtual user environment can be
created for this type of testing. Testing is done at the
end of development. Still minor design changes may be made
as a result of such testing.
Beta testing - Testing typically done by end-users or
others. Final testing before releasing application for
commercial purpose
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / meenakshi
V-Model,Fish Model,Scrum Model,BigBang Model,Waterfall Model
| Is This Answer Correct ? | 0 Yes | 1 No |
what type of report that you print it out from your defect tracking too when you go for the bug triage meetings? Thanks
What are the various black box and white box testing techniques?
How the test plan is a tool and the product?
What is the difference between Build Management and Release Management ?
What is the difference between Sleep and wait in winrunner what is integration testing and types of testing present what is system testing what is data driven testing what is functionality testing if requirements are given to you then how do you write the test cases for it Account number = Ok cancel For above given form the valid account number starts from 1 to 1000 so is it necessary to input the 1,2,3 ….998,999,1000 test cases to check the conditions of valid account numbers I,e is it compulsory to write 1000 test cases for the above form
What is the difference between integration and system testing?
What is a test log?
how many types of functions in qtp
How to prepare traceability matrix?
What is the deference between regression testing and re-testing?
How do ensure that we prepared Test cases for all the requiremets.. or how do we ensure that we didn't missed out any requirments...do we prepare any Tracebility matrix.. can anybody answer this question...
How Requirement is linked with traceability matrix. Give proper example
Automation Testing 
