Answer / nitin verma hcl

Hi,

Smoke Testing:- 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.
Smoke testing can be done for testing the stability of any
interim build. Smoke testing is done by developers before
the build is released or by testers before accepting a build
for further testing.

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 application.

Plz correct me if i m wrong..
Regards..
nitin9360@gmail.com

Answer / ravindhar

Smoke testing is to find out the 'Testability' of the build
by ensuring the crucial functionalities of the application
have been delivered. This will done once build released to
QA.
Sanity testing: It is cursory testing, can be done any time
to ensure that application is working properly. mainly
focus on GUI checking, database connectivity, printer
connectivity
So both are have their own nature.

Answer / sharman

Thousand mind, mounth and million different thoughts....

Answer / sunil reddy

Both are validating 4 whether basic functionality of build
is stable or not for further testing

Answer / naganath

Smoke testing is done whenver a new build comes to TCOE
team.if the smoke test pass then only teasting team proceds
for further testing i.e. basic testing done by the testing
team.

Sanity Testing:the world sanity means FRIEND whenever the
developer develops any code he do the testing by
himself.but he is not sure for what he coded so he colegie
i.e. friend developer do the testing of that code is called
sanity. actully sanity testing done by the development team.

Answer / shrish mahajan

Smoke Testing:
The testing process in which we execute maximum number of test cases with minimum number of test data to ensure the system is ready for testing and is stable. It is done by Testers. A smoke testing is just a cursory examination of all the basic components of a s/w under test to ensure that they work.

Sanity Testing:
The testing process in which we execute maximum number of test cases with minimum number of test data to ensure that system is ready to deploy in the production environment. It is done by the Business Analysts.

Answer / sriram

Sanity testing is nothing but Bredth level testing that
means we will touch all the functionalities we will not go
into deep, where as Smoke testing is depth testing we will
go in deep to test each and everything w.r.t the
functionality.

Answer / sudhir

Sanity Test:Every time when a new build comes to the
testing team then firstly sanity testing is done.Sanity
consists of testing the basic functionalities of the
application.Now if any major issue is reported then the
build is rejected and sanity fails.

Now in the next build the testing is done on the reported
issue and other features are smoked out.This is smoke
testing.

Answer / selvaa

Sanity : first conduct the sanity testing,then only go to
further testing,its means to check the basic
functionalities...

Smoke: its final testing,the particular build is going to
realease,if its capable of live environment....
kayessor Blr

I don't know about testing, I want to learn about Teasting. What kind of books I should read? Can anyone help me? (Like manual, automated testing) lots of things are there. from where I should start?

2 Answers  

Hi, My name is Dinesh.I want to prepare for ISTQB certification , So can anyone please email me the syllabus of it and what is criteria for giving exam.Please email me answers at: dinesh0323@live.com

2 Answers  

Can you explain exploratory testing?

0 Answers  

What is mean by incident logging system ?

0 Answers  

How do we validate cerdit cards in billing project

2 Answers   HCL,

Difference between spiral model and proto type in sdlc?

4 Answers   ciit, CSS,

What is a defect?

0 Answers  

what are the different testing methodologies and testing techniques? Am asked in interview that what is the defect age? I replied that the time gap between the defect reporting and defect resolving. then the interviewer asked me if at all the defect is not resolved then what is the defect age of that particular defect? can anybody answer this?

3 Answers  

please make me understand what is client server and web application?

1 Answers   HCL,

What is fuzz testing?

0 Answers  

Written Paper at Net Solutions: 1) Difference between Smoke Testing and Sanity Testing. 2) Bug life cycle. 3) Write the steps followed in STLC in your company. 4) Define: 1) BVA (Boundary Value Analysis) 2) ECP (Equivalence Class Partitioning) 5) Write test cases for a login screen with following fields/buttons: Username: Password: Login (Button) Cancel (Button)

2 Answers   Net Solution,

(urgent)hi all can any one answer to following questions.i have an interview tomorrow.it will be a great help if any one answer to this questions.thanks all. 1.when ever we get a build do we need to do smoke test is it compulsory,and how much do they spend for test. 2.generally all the testcases are stored in which place in real time.is there tool used to store that testcases and test plan,suppose we are using test director can we store all our test cases in it, and where does entire application test cases and test plan is stored assuming that company is using test director. 3.and when we file a bug,and it gets fixed after that do we need to do regressing testing only on that test case or any other test cases also.how the process will be there in real time. 4.when ever a new feature is added to the application do all the test cases to be re executed. 5. can we use toad, winaql in oracle database to access sql queries.

8 Answers   Instill,