HI, CAN ANY ONE PLZ EXPLAIN IN SIMPLE WORD WHEN WE DO
SANITY TESTING AND SMOKE TESTING AND WHY ?
and differance between this two ?
- 4 Answers
- 4528 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / nitin sharma
Smoke Testing: To check the cruicial functionalities of the
application are working properly or not,Generally done by
the Dev Team so that the test team can go ahead with the
application.
Sanity Testing:To Check the small sections or basic
functionalities of application,Generally done by the test
team to ensure whether the build is acceptable or not.
May this could help you..
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / pratik
HI NITIN THANKS FOR REPLY....
one more thing i want to ask is i read some where that
smoke test is done before the product release and some
where said that it is to check weather to go for further
test or not ? so which is true .?
and when we do sanity in testing life cycle ?
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / nitin sharma
@Pratik
Before product release genrally we do the UAT(User
Acceptance Testing)which is the last phase in Testing,Smoke
is done to check the high level funcionalities and it
depends on company to company,somewhere smoke and sanity
done by the tester itself and somewhere smoke by developers.
If smoke pass then it is not necessary that santy will also
be pass it could be reject because in sanity we check the
small sections in modules,smoke is just only to ensure that
tester can go ahead with the application for further test
So don't be confused.May this will clear your doubt.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / pradeep
Hi Nitin,
can you give example for sanity testing..
| Is This Answer Correct ? | 0 Yes | 0 No |
What is CDB?
Why can be tester dependent on configuration management?
Define the notion of transaction and deadlock ?
Please some one answer these Q's 1.Modules in Pension Domains ? 2.What Should we Test on Pension Domain.? Thanks in Advance Stewie
which testing we do during requirements? a. white box testing b. black box testing c.both testing d.none
What Kinds of Testing should be followed for an web application while Manual Testing . Ie., Regression , Integration , Alpha , Beta , Performance , Stress ,Load , Back End(database)...etc What is the serial way to follow the above Testing Kinds in manual testing of any application. Plz clear my doubt.
Most of my QA team members work offsite. So collaboration between the team members is an issue that has been affecting our work badly. Does anyone have a solution for this?
In "V" model of SDLC which phase correspond to integration testing: 1. Requirements 2. Analysis 3. Design 4. Coding
test scenarios for downloading a file
what is the difference between verification and validation ?
What is class level methods?
What is Software reliability?
Automation Testing 
