Answer / varshab

Smoke testing is basically perform to asure software is
stable enough to consider it for further testing.It is
shallow & wide as we navigate through all options of
application without going into much deep.In this we are
more concern about major functions without much bothering
about minor ones.e.g.It is more useful in configuration
(hardware) testing.

Sanity testing is cursory testing.When new build is
released from development team with minor changes, in this
case instead of performing through regression testing
sanity testing is more appropriate to ascertain indeed
rectifications are done.It is narrow & deep.It is subset of
regression testing.

Answer / sj

Take one example To test Word Doc::

In word doc we have different option available like File
Menu,Edit Menu,View Menu,Insert Menu,Tool Menu,Table Menu
etc.......
For Smoke Testing We check whether when we click in file
menu or in insert menu etc we get all options present in
that menu or not i.e Smoke Testing..


For Sanity testing After clicking on File menu we check its
sub menu whether or not they r working fine or not i.e
Sanity Testing ...........


with the help of example i think u understand the 2 Testing

Answer / deepa

Smoke Test:

When a build is received, a smoke test is run to ascertain
if the build is stable and it can be considered for further
testing.



Smoke testing can be done for testing the stability of any
interim build.



Smoke testing can be executed for platform qualification
tests.



Sanity testing:

Once a new build is obtained with minor revisions, instead
of doing a through regression, a sanity is performed so as
to ascertain the build has indeed rectified the issues and
no further issue has been introduced by the fixes. Its
generally a subset of regression testing and a group of
test cases are executed that are related with the changes
made to the app.



Generally, when multiple cycles of testing are executed,
sanity testing may be done during the later cycles after
through regression cycles.

Answer / akhil kumar

Hey guys are u going mad.First thing is that if u dont know
about the thing that please dont put your foot in that as
little knowledge is a very dangerous thing.This is very
simple thing which I m describing briefly:-

Sanity testing :- It is just to test the basic
functionalities of a software product and application.it is
done by testers.

smoke testing :-it is a form of regression testing.when a
application made some new changes to modules or added new
modules to a application then a smoke test is performed that
it is working fine or not.it can be done by both developers
and testers.

I hope this might have clear your doubts.

If anyone of has some queries regarding manual testing and
automation tools and quality assurance u can ask me freely.
my email id is akhil_25683@yahoo.co.in.

Thanks & Regards,
akhil

Answer / sridhar

Sanity Testing: sanity test is a very brief run-through of
the functionality of a computer program, system,
calculation, or other analysis, to assure that the system or
methodology works as expected

Smoke Testing: smoke testing is a preliminary to further
testing, i.e when the release is given to the test team -
need to do smoke testing for each and every link - in order
to verify that the next pages are displayed and the further
testing can be done.

Answer / rajkumar

Smoke Testing- Also called as Build Verification Testing.
This type of testing is done to check the stability of the
build that most of the crucial function are present and can
be accessed and to evaluate the build is ready for further
levels of testing. e.g. All menu options are present, all
forms can be navigated properly. This is a shallow and wide
approch

Sanity Testing- This is a cursory testing in which we will
check a functionality in detail rather than going for
overall build. Approach is narro & deep.

Answer / naveen

Smoke testing is a wider\broad approach in which we test the
stability of build. Whether build deployed to testing
environment functioning without any issues or not..Here the
main functionalities is tested(such as we are able to login
to the application without any issues)

Sanity testing is a narrow regression testing where we test
indepth functionalities are working as expected or
not(basically a touch test of all applications)

-Naveen

Answer / a.sameer

Smoke testing is done by developers before the build is
released to testers.

Sanity testing is done by testers to verify whether to
accept a build for further testing or not.

In both the same the way of technique used to test is the
same, both are for checking for minimal functionality of the
application only difference is done departments are different.

Answer / viji

smoke testing-Checking the functionality
Sanitary-opposite to smoke testing.checking in depth of
functionality of the process

Answer / silpa

sanity testing and smoke testing is same.
here we wil check the basic functionalities of our build.
we are using +ve data for sanity testing
but in smoke testing we are using -ve data .

What is the main purpose of having Equivalence Class Particition & Boundary value analysis in Testing?

6 Answers   Tavant Technologies,

hi... guys can any one pls help me out.... I m civil engg graduate i want to come into s/w field... i have decided to do manual testing course. i know its not sufficient.. which r the other coures shall i do with this.. suggest me good atomation tool and SAP courses... thanks in advance.. i wil be thankfull to u all

0 Answers  

Hi I want to prepare for ISTQB Foundation level. Can any body mail me some sample papers for preparation. My mail id is sanjaysachdeva2008 @gmail.com

1 Answers  

in your organization in what way(phases) s/w is developed and in what way testing will be conducted?

4 Answers  

What r the attribute of good software test?

1 Answers  

What is the bigbang approach in integration testing?

14 Answers   CarrizalSoft Technologies, TCS,

What is srs and brs document?

0 Answers  

hi iam keeping 2+ fake exp here is my project plz tell me wt kind of Q's can be posed on it. Blue room acts as the central repository for all project information – providing detailed view into the operations of entire services of the organization. Blue room provides access to different levels of users based on their role like CEO, client, project managers, project leader and team members. Each will have permissions to access different functionality of the tool. Blue room gives access to higher management like CEO, VP or Project managers to real-time data including project completion percentages, gross margin, remaining engagement time, budget vs. actual, and profitability analysis. Through this extensive visibility, services professionals gain a better understanding of the overall performance of their services organization and are able to make faster and more effective strategic business decisions. Upload and download your Project files into Blue room from anywhere, making the latest project plans available to all participants via the Internet. n 1 more project also: Cable Network Management System (CNMS) efficiently handles customer information, billing and also effectively monitors the services provided. CNMS mainly consists of two modules. Cable Network Information (CNI) and Customer Accounts (CA). CNI maintains customer's information, employee information, service areas and tariff. CA is completely an accounting package, which helps to handle all accounting transactions of the company. The CA module is an important module and it includes account type, login information, and payment methods etc. Each customer account is linked in the system with a specific services offered to a customer, and the customer will be billed depends on his usage of these services. Customer account belongs to specific account type, which is related to some price plans and discounts. The billing process involves receiving billing records from various networks, determining the billing tariff associated with the area, calculating the bill for each customer on monthly basis, aggregating these records periodically to generate customer bills, sending bills to the customer, and collecting payments received from the customer and adjust customers balances accordingly. Up to Date Balance sheet, Import and Export feature, Network Compatible and user friendly, Rescue data through Recovery system and Dynamic Report Generation are other important features. can any 1 plz tell wt kind of test cases will be asked on dis.

3 Answers  

work break down structure in manual testing

3 Answers  

Suppose u have a ICICI Home Page & there is a option link "Bill Payments" so once u click this link then new child window will be open where u have a 1. "amount(Text box)" 2.Auto Debit monthly (check box) & 3. "OK" & "Cancel" Button. Please write the test cases for this Integration Test cases also.

3 Answers  

In a system designed to work out the tax to be paid: An employee has £4000 of salary tax free. The next £1500 is taxed at 10% The next £28000 is taxed at 22% Any further amount is taxed at 40% To the nearest whole pound, which of these is a valid Boundary Value Analysis test case? The options provided are a)£1500 b)£32001 c)£33501 d)£28000

5 Answers  

diff betn buddy and pair testing

1 Answers