subhash ingale


{ City } pune
< Country > india
* Profession * software testing eng.
User No # 73007
Total Questions Posted # 0
Total Answers Posted # 2

Total Answers Posted for My Questions # 0
Total Views for My Questions # 0

Users Marked my Answers as Correct # 1
Users Marked my Answers as Wrong # 5
Questions / { subhash ingale }
Questions Answers Category Views Company eMail




Answers / { subhash ingale }

Question { Cognizant, 8608 }

difference between sanity testing and smoke testing?


Answer

1. Sanity Testing or Build Verification testing or Build
acceptance testing.

It is type of testing in which one will conducted overall
testing and the release the build in order to conform
whether the build is proper or not for conducting detil
testing.

To do the same one will check the following.
1.Whether the build can installed in to Environment proper
or not.
2.whether one can navigate to all the pages of the
application or not.
3.whether all the objects are available and properly
arranged or not.
4.whether the required connection are properly established
or not.


Smoke Testing :-
some compines this type of testing also called as smoke
testing but in some compines just before releasing the
build is proper or not that is known as smoke testing and
once the build is release the test Eng. will check whether
the build is proper or not . that is known as build
acceptance testing ,build verification testing.

Is This Answer Correct ?    0 Yes 0 No

Question { Wipro, 5957 }

Integrating Testing Own example


Answer

In this stage the
developer will develop the “interface” in order to
integrate the module the white box testers will test within
those interface are working fine or not.
The developers may fallow any one of the following
approach while integrating the module.
1. Top – down – approach. (TDP)
2. Bottom – up – approach. (BUA)
3. Sandwich approach or hybrid approach or mixed
approach.
4. Big-bang approach.

1. top-down- approach:-
In this approach
one will develop parent module 2222first and then they will
develop related child module and then integrate.

STUP: - while the integrating the modules in top down
approach if at all any mandtre module are missing than that
module is replaced with a temporary program known as stub.


2. bottom- up- approach:-
In this module the child module will
be develop first and then corresponding parent’s module
will be developed and integrated.
3. Sandwich or hybrid or mixed approach:-
This is mixed approach of both top down
approach and bottom up approach.

4. Big- bang approach:-
In this approach one will wait till the entire
module one developed and then finally integrated then at a
time.

Is This Answer Correct ?    1 Yes 5 No