difference between smoke test and sanity test
difference between exploratory test and adhoc test
Answers were Sorted based on User's Feedback
Answer / anil nakhate,
Smoke test:- to check the basic functionality of that
application is working properly or not.
Ex: Login functionality, If login functionality is working
properly then build accept for further testing process.
It is also called as build verification test(BVT).
Sanity Testing:- sanity testing is a subset of regression test,
it is deep & narrow testing.
Ex:Suppose we want to test money transfer functionality, to
conc. on all available option for money transfer
functionlity, this call deep testing
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / swapn
smoke test we check the availability it is a test for
availability
sanity test is also a test for availability but they are
conceptually same but perception opposite
smoke test is positive perception sanity negative perception
some companies call smoke and some say sanity
exploratory testing has no test case document and business
document
adhoc testing has business document
better than exploratory
| Is This Answer Correct ? | 0 Yes | 7 No |
what are the examples for web based applications and Client Server Applications
5 Answers ASD Lab, CFCI, College School Exams Tests, GXS,
what is tracebility matrix and what will be there in tracebility matrix?tell me details like idno, discription....etc.pls any one answer this question?
what is testing?
what is the priority for fixing bug?
Name three reasons why the tester may choose to record in Context Sensitive mode.
IN V-Model, from where a tester involves and from where a developer will involve???
why feature not to be tested in test plan
When test plan will be prepared in v-model?
for example, we have old password,confirmed password, new password followed by submit button. what are the test cases written for that?
As there are different builds for every version & any build can release to the client.I m using Excell sheet for Test Case writting. Then Am I write Version No/build No.newly added feature test cases. Because when that build again release for testing I can understand that this build have that feature.
what are test cases for edit,add,delete,save,preview and main buttons and test scenarios
What are the different strategies for rollout to end users?