What is the difference between smoke and sanity testing?
and when we perform smoke testing and when we perform
sanity testing?
- 6 Answers
- 8836 Views
- I also Faced
- E-Mail Answers
Answer Posted / raj_rex
SMOKE TEST :
Smoke testing is considerd as
built level test.Each time the test team receives a new
build(new version of program),an initial test is performed
to determine that the most crucial functions of the program
works and the build is stable enough and can be considered
for further testing.
SANITY TEST :
Sanity testing is considered as
release level testing.When software is ready to be shiped
to client and we want to finally cheek if everything is
fine and working as per requirement.It's a sub set of
Regressing testing -a group of test cases are executed to
cheek it is indeed working according to specification
(requirement).
I hope this will do.But somebody may not agry with me as
this defination will vary company to company... but i think
this is the basic defination...
| Is This Answer Correct ? | 0 Yes | 4 No |
Post New Answer View All Answers
from where do u collect test data if u miss some data what will happen
What r all the security problems u r facing & the measures taken to solve.
Artifacts in design phase of SDLC ?
What is a maturity level?
What is change request, how you use it?
What is bottom-up approach?
In simple steps how will you do unit testing using VSTS?
You may undergone many projects. Do all the projects match up with customer’s expectations?
What is your Approach when you find 10 Sev-1 bugs in 50 test cases?
Wat type of questions ll be asked in interview for an 1-2 yrs. experinced persond and i need some database concept question in testing.
Describe your experiences with code analyzers.
Explain some techniques for developing software components with respect to testability.
Hi Friends, This is Chennamsubbaraidu.i Have 2+ Years Realtime Exp in Manual Testing.Am Looking to Shift From My Present Company.Please if u Have Any Openings in Your Company's, Please Let Me Know.Any Location Prefer.Thanks.
There is only requirements document. You have 10 days and 8 resources to release the system.At the end of the 8th day u tell ur TL that system is ready for release. How will you proceed with the testing process or in other words what all approach you will follow once you get requirements
How will u decide test data to see that evey feature is thoroughly tested
