Interested to Buy Any Domain ? << Click Here >> for more details...
What is the difference b/w Smoke Testing and Sanity Testing
with Example...
- 2 Answers
- 5812 Views
- Cap Gemini, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / sania
Smoke testing is the surface level testing to certify that
build provided by development to QA is ready to accept for
further testing.smoke testing only checks the major
functionality of the software.
For example we are working in a small project named
Employee Management System and in this project there are
four modules like New Employee Module, Existing Employee
Module, Admin Module, User Module etc. So firstly in this
four modules development team performs the Smoke Testing by
executing all the major functionality of modules like New
Employee is able to login or not and after login new
employee can seen the record of the existing employee or
not, and employee that is created can also be edited,
deleted or not.
| Is This Answer Correct ? | 3 Yes | 1 No |
What are the structure-based (white-box) testing techniques?
Whether networking knowledge is essential for a testing professional?
Write a function Occurrences() in a language of your choice that takes in two strings. The first is a search string, and the second is a sentence. For example, running the function: Running Occurrences ("o", "Red Gate Software - Ingeniously Simple Tools") will output: Occurrences of 'o': 4 Occurrences ("at", "The cat sat on the mat") will output: Occurrences of 'at': 3 Sample Question 2: 2)Below is Notepad's File/Save dialog. a) If you were asked to test this dialog, how would you go about it? b) List various inputs you might place into the "File name" text field to test it.
what are the daily activities of a software tester ie the activities carried out by the tester from the time he/she enters the office till the time he/she leaves the office
What is difference between JBOD and RAID?
How will you define a critical bug?
What is branch coverage?
Why we perform stress-testing, resolution-testing and cross- browser testing?
What is sei - software engineering institute?
What is oo function testing?
What is test plan and explain its contents?
26). how will know do written test cases are sufficient to validate application of functionality? 27). how will you prepare test data to validate input object? 28). explain defect status? 29). how will know whether the developer accepted you defects or not? 30). explain acceptance test? 31). explain when we stop testing? 32). explain scope of your project? 33). in which module you conducted testing? 34). explain defects which you found in that module? 35). if defect is not reproducible then what information you will provide to developer 36). if developer is not accepted your defect then what you will do?
Automation Testing 
