Interested to Buy Any Domain ? << Click Here >> for more details...
Difference between smoke testing and sanity test ?????????
- 14 Answers
- 22638 Views
- CTS, I also Faced
- E-Mail Answers
Answer Posted / samiran bose
Smoke Testing:-
1. Area of smoke testing is so big.
2. Smoke testing is not a formal testing.
3. Before the build is released Smoke testing is done by
developers or by testers before accepting a build for
further testing.
Sanity testing:-
1. Particular functionality is tested in Sanity testing.
2. sanity testing is formal testing.
3. At the beginning and ending of each phase of Software
Development Life Cycle sanity testing is performed.
Usually tester and Developer perform Sanity testing.
| Is This Answer Correct ? | 1 Yes | 1 No |
Post New Answer View All Answers
Why are you in qa?
How do you define a format of writing a good test case?
Questions for role of a QC engineer at NDS,Bangalore 1st round is written 20 questions on aptitude and 10 question on testing Aptitude--problems on time and distance,tap problem,ages,time and work,probability, Testing 1.Difference Between QA & QC 2.Any 4 types of SDLC models with diagram. Also Pros and cons of each model 3.What is application Testing And embedded testing 4.Qualities of a good tester 5.Test cases for registering user. One field for user name,2 fields for password,"ok" and "cancel" button 6.What is a bug,explain Bug life cycle 7.Difference between priority and severity? 8.Some question on software design
Describe the dimensions of the risk in qa?
Mention what are the test artifacts involved in qa?
How you will begin to improve the QA process?
Tell me some key points to consider while writing a bug report.
what is difference between smoke testing and sanity testing?
What is the basis for choosing the sdlc model for development of software?
how we apply cmmi and iso in oyr testing or qa do it have some specifuc format
Enlist the priority of the testing tasks defined by the qa team in product development.
What is basis set?
What is a cause effect graph?
What if there is not enough time for thorough testing?
why do not u try to get job in your core side(example :-eee)?
