levels of testing

Answers were Sorted based on User's Feedback



levels of testing..

Answer / venkat

Unit testing: typically done by developers will do this,
code can be tested.
Integration testing: This is can be done by after
completion of unit testing. All dependent modules can be
tested in this level; in here one module output is input to
the next module,
Ex: login page to home page, home page to account transfer
page.
System testing: here all components of the system are
combined together and test it. Here END-END flow of the
system will be tested.
Acceptance testing: the customer does this; client will be
using the system against the business requirements

Is This Answer Correct ?    22 Yes 4 No

levels of testing..

Answer / guest

1)unit testing
2)integration testing
3)system testing
4)user acceptace testing

1)unit testing:
individual software components of appication are tested in
isolation from other part of the program.



bigban testing: individual software components of an
aplivation are combined at once into system .every module i
s first init tested.then the entire sysetm is tested for
communication interfaces between them.


bottom-up testing:
in bottom-up integration testing begins from bottom of
the module hierarchy and work up to the top to simulate
higher level modules .every module is first unit tested
then modules are added in acsending hierarchial order.lower
level modules are tested first then the next set of higher
level modules are tested with previuosly tested lower level
modules.


top-down testing:
begins testing from top of the module hierarchy and
work down to the bottom to simulate lower interfacing
modules.every module is first unit tested then the modules
are added in descending hierarchial order.higher level
modules are tested first then the next set of lower level
modules are tested with previously tested higher level
modules.





















Is This Answer Correct ?    14 Yes 2 No

levels of testing..

Answer / p.moorthi

There are 5 levels of testing.

1) Unite level testing
2) Module level testing
3) Integration level testing
4) System level testing
5) User acceptance level testing
1) Unit level testing

If one performs testing on a unit then that level of testing
is known as unit level testing. It is white box testing
usually developers perform it.
Unit: - It is defined as a smallest part of an application.

2) Module level testing

If one perform testing on a module that is known as module
level testing. It is black box testing usually test
engineers perform it.


3) Integration level testing

Once the modules are developing the developers will develop
some interfaces and integrate the module with the help of
those interfaces while integration they will check whether
the interfaces are working fine or not. It is a white box
testing and usually developers or white box testers perform it.

The developers will be integrating the modules in any one of
the following approaches.
i) Top Down Approach (TDA)
In this approach the parent modules are developed first and
then integrated with child modules.
ii) Bottom Up Approach (BUA)
In this approach the child modules are developed first and
the integrated that to the corresponding parent modules.
iii) Hybrid Approach
This approach is a mixed approach of both Top down and
Bottom up approaches.
iv) Big Bang Approach
Once all the modules are ready at a time integrating them
finally is known as big bang approach.
STUB
While integrating the modules in top down approach if at all
any mandatory module is missing then that module is replace
with a temporary program known as STUB.

DRIVER
While integrating the modules in bottom up approach if at
all any mandatory module is missing then that module is
replace with a temporary program known as DRIVER.

4) System level testing

Once the application is deployed into the environment then
if one performs testing on the system it is known as system
level testing it is a black box testing and usually done by
the test engineers.

At this level of testing so many types of testing are done.

Some of those are

a) System Integration Testing
b) Load Testing
c) Performance Testing
d) Stress Testing etc….

5) User acceptance testing.

The same system testing done in the presents of the user is
known as user acceptance testing. It s a black box testing
usually done by the Test engineers.

Is This Answer Correct ?    16 Yes 4 No

levels of testing..

Answer / shankaragouda

smoke text is done once build is released to the testing
team, to make sure that all the links are properly working
without fail to move further level of testing

Is This Answer Correct ?    9 Yes 2 No

levels of testing..

Answer / saranya rajaram

Unit testing:
Unit is considered as the smallest module in an
application.A unit contains codes of few lines,which
performs a particular task.
Testing the unit,testing the logic of the code is said
to be unit testing.
For performing this test we need Low level design
document(LLD).And we perform white box testing.And the
testers are called as Unit testers.

Is This Answer Correct ?    7 Yes 2 No

levels of testing..

Answer / balu

1)unit testing
2)Module Testing
3)system and integration testing
4)user acceptace testing

1)unit testing:Unit is considered as the smallest module in
an application.A unit contains codes of few lines,which
performs a particular task. Testing the unit,testing the
logic of the code is said
to be unit testing.

Is This Answer Correct ?    2 Yes 0 No

levels of testing..

Answer / saranya rajaram

Hi Purni,

Can u pls tel me what is a smoke test.For what
purpose it is used?

Is This Answer Correct ?    2 Yes 2 No

levels of testing..

Answer / deepu

level of testing
unit testing
integration testing
system testing
acceptance testing
unit testing:
it is done on a unit
this testing is an initial testing
this testing is done by the developers
integration testing:
this testing is checking the interface between all the units
combing all the units in this level of testing
developer as well as tester involve
system testing:
checking the entire system
acceptance testing:
done by the user
tester also involve in this

Is This Answer Correct ?    0 Yes 0 No

levels of testing..

Answer / sravan

Levels of testing:

System Integration Testing
User Acceptance Testing
Pre-Production Testing
Production Validation Testing
These are the levels of testing...

Unit Testing, Integration testing, system testing etc are all come under major types of testing.....

Is This Answer Correct ?    1 Yes 1 No

levels of testing..

Answer / deepak parida

Levels of Testing:
There are five levels of testing
1. Unit Level Testing
2. Module Level Testing
3. Integration Level Testing
4. System Level Testing
5. User Acceptance Testing (U.A.T)
1.Unit Level Testing: -
It is a level of testing in which one will perform testing on the units. It is a white box testing and usually developers or white box testers will perform.
2.Module Level Testing: -
Module: Module is defined as a group of related functionalists to perform a major task
It is a level of testing in which one will perform testing on the modules. It is a black box testing and usually test engineers perform it.
3.Integration Level Testing: -
It is a level of testing in which the developers will develop some interfaces to integrate the modules and test whether the interfaces are working fine or not. It is a white box testing usually developers or white box tasters perform.
The developers may follow one of the following approaches while integrating the modules.
1.Top-down approach
2.Bottom –up approach
3.Hybrid or Sandwich approach
4.Big-bang approach
1.Top-down approach: - In this approach one will develop the parent modules first and then integrate them with the related child modules
2.Bottom-up approach: - In this approach one will develop the child modules first and integrate them to the parent modules
3.Hybrid approach Or Sandwich approach:- This is a mixed approach of both the top down and bottom up approaches
4.Big bang approach:-In this approach one will wait till all the modules are ready and finally they will integrate all the modules at a time
STUB: - While integrating the modules in top down approach if at all any mandatory module is missing (not completed) then that module is replace with a
DRIVER: -While integrating the modules in bottom up approach. If at all any mandatory module is missing (not completed) then that module is replaced with a temporary program known as DRIVER
4. System Level Testing:
It is a level of testing in which one will install the complete application in to the environment and then perform testing on it. At this level different types of testing will be done one among those is system integration testing.
5. System integration Testing: -
It is a type of testing in which once the complete application is developed one will perform an action at one module and checks for the reflections at the corresponding modules. It is a black box testing and usually test engineers perform.

6. User- Acceptance Testing: -
It is the level of testing in which one will perform the same system testing in the presence of the user in order to make him accept the application. It is a black box testing and usually Test engineer performs it.
Environment: - Environment is a combination of three layers (e.g.: Yahoo)
a. Presentation layer
b. Business layer
c. Data base Layer
System: The application installed in to an environment combinable called as system.
a. Presentation Logic: The logic that is used for viewing application is known as presentation logic
b. Business Logic: - The logic that is used for performing the operations on the application is known as business logic.
c. Data Base Logic: - The logic that is used for sharing and retrieving the data is known as database logic.

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Manual Testing Interview Questions

1.how to check or test the image ?

4 Answers  


what is bottleneck of application?

1 Answers  


Test cases for google home page, yahoo signin page, elavator, traffic signals. And can anybody post the some other testcase(on like pen,keyboard....) as interview point of view.

4 Answers   CTS,


I Have 2 Yrs Experience in Manual I appiled in Job Portals still i m not getting any calls plz help me wat i need to do guide me please ?

1 Answers  


Comparison testing is typically done to test two competing products as part of customer market analysis prior to product release. Is it true.explain comparision testing

1 Answers  






Name some bug tracking tools???

3 Answers  


What is diff between equialence partioning and boundary value analysis

4 Answers   TCS,


can u pls explain me what is boundary value analasys and equivalent partitioning

4 Answers  


send the senario template

0 Answers  


If you found any high priority bug before release product then what will you do as tester if you only tester in team??

1 Answers   Persistent,


At Evening 6'o clock they will release the new build to you.what will u do on that time.

7 Answers   QA,


Can anyone give me the example of High Priority and Low severity defect. Please dont give me answers like Spelling mistakes or logo missing something like that. Give me some real time example from your application. Please ignore the earline question which i have posted.Thanks in Advance.

2 Answers   Qwest,


Categories