What is the need of smoke test even when unit test is done
by developers?
- 6 Answers
- 7579 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / bhagwat
i Agree with vaishali's answer, however, there is a subtal
difference which I thoght.Unit/module/component testing is
a type of testing that is done by developer, where smoke
testing is the checking of final build before proceeding
for regreesion testing.Mostly smoke testing is done by QA
and if it passed then Build is accepted for further
testing. After completion of smoke testing BAR(build
acceptance report) is prepare. In smoke testing all major
functionalities of application are verified and if 65%-70%
of the functionality is working properly then Build is
accepted for further testing.
| Is This Answer Correct ? | 6 Yes | 0 No |
Answer / melbourne bala
Unit testing.
it is used to check the single component or program.It is
usually done by software developer or white box tester.Each
and every lines should check atleast one time.the
programming knowledge is must.It is based on code.the
developer should check the loops ,arrays,etc.
Smoke testing
It is for test engineer work.after deployed the build from
software development team.He should check the higher
priority of function check,the very important functions not
working,he will send back the build to software
developer.sanity testing and smoke testing is not
different.advantage of the test is we can find the serious
issues and defect at early stage.
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / nagendra
I agree the ans what nani is provided. But, this is not the
correct ans for the ques.
Unit testing is done by the Developers after completion of
the Developing the code. They will think that, what they
are doing is correct. So, there may be a chance of missing
any functionlities. That missing functionality defects will
be caught in the Smoke testing which will be done by the
Testers.
Developers will think in the perspective of their side.
They never said that they are doing wrong. Even Nobody
accept this... :)
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / vaishali
Unit test and smoke test are quite different terminology.
Unit test is something for testing the modules/components
independently. Smoke test is for checking the final build
(may be written on the CD/DVD)for verifying that build is
installing properly on the standalone machine.so smoke
testing is to be done on completion of the testing process
and before handing over the release/system to the customer
| Is This Answer Correct ? | 3 Yes | 2 No |
Answer / saff
unit testing is done by developer in developing enivronment
he will check wheather code is working or not in dev
enivorment so purpose of smoke testing is to test the aplln
in testing environment
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / n@n!
hi Ashwini,
unit testing and smoke testing both r different.
unit testing was done developeres.
after unit testing was completed the product never release
in the market.
unit testing is initial stage of testing after coading was
release.
smoke testing was done by test engineers.
after smoke testing was completed then only the application
was release in the market.
| Is This Answer Correct ? | 1 Yes | 3 No |
What is the need for testing?What is the Outcome of Testing? What is the Purpose of Testing? When to start and Stop Testing?
what methods will u follow to prepare testcases in ur org?
WHAT IS COMPATABILITY TESTING
Deep structure testing is not designed to Option 1 examine object behaviors Option 2 exercise communication mechanisms Option 3 exercise object dependencies Option 4 exercise structure observable
What is the meaning of incident in testing?
Can you explian $ pillar of Agile
How can you define state tanstion testing aswell decesion testing with examples.how you can differ them too??
what is compliance testing?
please give me the template of tracebility matrix ? i need whicch is commanly used in real time...
what is manual testing process
what is different Between Risk and Issue ?
Defect Migration "Defect Migration" means that error is early project documents lead to errors in later documents. For example, an incorrect requirement leads to an incorrect set of speacifications, which leads to design errors, which leads to coding errors, which lead to failures when we test against user expectations. a. How will you prevent Defect Migration? b. Why do you think preventing Defect Migration is important?
Automation Testing 
