what are the definitions of smoke , sanity and dry run
testing ?
Answers were Sorted based on User's Feedback
Answer / rahul singh
1.Smoke testing---
Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
2.sanity test---
A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
A sanity test is usually unscripted.
3.Dry run test---
Test or check performed on a computer, hardware, or electrical equipment. This test is generally run to test the performance or stability of a particular product before it is made available.
Is This Answer Correct ? | 7 Yes | 1 No |
SMOKE TESTING:
--------------
Smoke testing originated in the hardware testing
practice of turning on a new piece of hardware for the first
time and considering it a success if it does not catch fire
and smoke. In software industry, smoke testing is a shallow
and wide approach whereby all areas of the application
without getting into too deep, is tested.
A smoke test is scripted, either using a written set of
tests or an automated test.
SANITY TESTING:
--------------
A sanity test is a narrow regression test that focuses
on one or a few areas of functionality. Sanity testing is
usually narrow and deep.
A sanity test is usually unscripted.
Is This Answer Correct ? | 0 Yes | 0 No |
how can u map SDLC With STLC
what is impact analysis
what do u mean by Functional testing?
Hello, Currently we are doing manual testing for PHP& .NET Projects. We are planning to automate it.Kindly suggest which automation testing tool is appropriate for it. Thanks
If you open a bug in build -1 and that get closed in build-2 . Again the same bug a raised in build -3. Then what state will you give to that?
What is the difference between quality assurance and quality control?
what is accessibility testing?
Hi! pl. suggest a good book for manual testing..to attend interviews in manual testing with 3+ yrs of experience
Work flow in testing in your company?
wat is da differnce between test stratagy and tedt plan?
We can check many things in one test case, then Is it necessary to write separate test case for checking each functionality? Example : For Login Window --> Test Case is---> 1) Enter valid user id & password --> For this expected result --> 1) User should login. My question --> while executing above valid test case, we can expect more than one result such as "Visibility of password should be as ****" So Should I have to write separate test case for "Visibility of Password" OR Not? Please guide me properly.
Can v prepare Test cases only from BRS from Tester point of view?