1. In sanity testing is it necessary to write test cases?
Actually I heard that Smoke testing is scripted one and Sanity is not scripted one. What type of scripts we have to generate in Smoke testing. In Smoke testing tester has to test environment also like software & hardware with build. How he has to test the environment (What type of test cases he has to generate)
2. What is the role of test engineer in Alpha testing (acceptance), What does he do in Alpha testing.
Total Answers and Comments: 6
Last Update: October 26, 2006 Asked by: ravikaanthe
First of all, must tell you that sanity Testing and smoke testing is used interchangeably in some org and some not. Actually sanity testing is done ideally at the begining always. This testing is done just to ensure that application whioch we will be testing is present before we begin out detailed system integration testing. If the application is not present, we will not be able to test. e.g., in order to do the functionality testing, usability testing of a LIFT, you need to first ensure that the lift is actually there in order to test.
Smoke testing is basically done when we are moving the project/product in the PROD environment, just to check that the major functionalities of an application works as intended by the user.
WE can write just one or two sanity test cases, if required (or a norm exists in the org), for each module of an application. Smoke test cases are generally written whil performing the smoke testing and it';s test case can be derived from the system integration test cases (functionality test cases) which we had written earlier.
To answer your other part of the question, Alpha Testing is that phase of the testing which is done before the product is shifted to PROD and generally done by the in house developers or a separate testing team at the developers site (customer location) just to be very much sure on the number of bugs in the application before it is finally delivered.
Thanks and Regards,
Nikhar
Above answer was rated as good by the following members: NiharikaVaish
RE: 1. In sanity testing is it necessary to write test...
It is not at all necessary to write test cases for sanity and smoke testing. This depends from org to org and their policies. There are few test cases which just check the flow/functionality of application which are run for sanity/smoke testing.
Alpha testing or Acceptance testing- Here the tester tests the functionality of the application. He tests for all critical flows, dependencies, most visible part etc for the application.
RE: 1. In sanity testing is it necessary to write test...
HI All,
First of all, must tell you that sanity Testing and smoke testing is used interchangeably in some org and some not. Actually sanity testing is done ideally at the begining always. This testing is done just to ensure that application whioch we will be testing is present before we begin out detailed system integration testing. If the application is not present, we will not be able to test. e.g., in order to do the functionality testing, usability testing of a LIFT, you need to first ensure that the lift is actually there in order to test.
Smoke testing is basically done when we are moving the project/product in the PROD environment, just to check that the major functionalities of an application works as intended by the user.
WE can write just one or two sanity test cases, if required (or a norm exists in the org), for each module of an application. Smoke test cases are generally written whil performing the smoke testing and it';s test case can be derived from the system integration test cases (functionality test cases) which we had written earlier.
To answer your other part of the question, Alpha Testing is that phase of the testing which is done before the product is shifted to PROD and generally done by the in house developers or a separate testing team at the developers site (customer location) just to be very much sure on the number of bugs in the application before it is finally delivered.
1 
0