What is the need of smoke test even when unit test is done
by developers?
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 will you do when you were given two diffrent projects and asked to complete them at same time?
How you will test pen
6 Answers Accenture, Digital Mesh,
What does entry and exit criteria mean in a project?
suppose i received 3 build b1, b2, b3 on which build i will do regression testing
How to test the below code and write test case? Prove that this code is wrong? int add(int a ,int b) {return a+b; }
what are the scenarios and test cases for online banking proj ..ex; fixed deposit, loginh into an account, checking an account, savings deposit
How many bugs occured will be considerd appropriate over 1000 steps when inspecting software? Describle an approriate Bug value.
Can you tell me some thing about source code testing tools?
Requirement is given : 1) The Login screen should require with 2 fields "Login" & "Password" 2) After successful login Success Message will display. 3) For Invalid login Error Message will display. 4) "Login" & "Password" both fields are case insensitive. 5) The Application should be Dialog application. What are the test cases for above requirements?
how to deploye the build when the developers give the source code..?
You're in the execution phase and after executing many test cases..you're not able to find any defect..not even a single defect. What will you do?
What is User Acceptance testing and when u'll do this and who will do this testing. If u got any bug while doing UAT what would be the status of Severity and Priority?