Bug ID is assigned by the Defect tracking tool which u r 
using. 
About Bug Version Id, I don't what it means. Sry.

Bug id & bug version id is same.when u found the bug then u
fixed a bugid of that bug.when bug is fixed then applicatin
is moved in new version .if u found new bug then u assign
bugid version.this is a fixed number.

Bug ID and Bug Version ID are entirely different. As u 
said, Bug ID will generate Automatically by the Bug 
Tracking Tool. When the Tester is reporting a Bug, he need 
to mention that it was reproducing in which Version. It is 
nothing but the Bug Vesion ID. For Eg : Bug Id 2021 is 
reproducing in Version 1.1.9_12082008.(i.e Version 1.1.9 
dated 12th August,20008).

In my guess it is black box phase where the system testing 
activities are done in that phase.

Its the Functionality and sysyem testing

Which is coming under Black box Phase.

It always in Validation (The dynamic part)side in a SDLC

Smoke Testing and Sanity Testing are the processes of 
checking the basic functionality of the application. These 
testing are done before the application is cleared for in 
depth testing. 
There is no point of testing further if the basic 
functionality are not working properly.

Hi


   Smoke & Sanity Testing are performed to check whether the
Application is sane enough to proceed  for Major 
Functionality .



sun_ramprasad@yahoo.com

Smoke testing::Development team Tests the build is suitable
for conducting Testing or not and the is accepting Customer
expected vlues or not.

Sanity testing:After getting the initial build from
development team.testing team find out whether is is
accepting input keyboard values or not & other objects are
responding properly or not is called sanity testing

Both smoke testing and sanity tesing are build verification 
tests.Difference between these is smoke testing will 
perform with a new build while sanity testing will perform 
with regression testing
Build verification test whilch performed with a new build 
is smoke testing.The same with regression testing is sanity 
testing

When u got new build

smoke and sanity are performed on build. ist we perfotm 
smoke testing after that sanity. smoke is for test minimal 
most feature available. and sanitity for availabilty of 
minimal most operational features.

After release the build we wiil check all the
functionality's are test or not ----smoke

After complete the smoke then we will test main 
functionality's of the build ----sanity


If any doughts or suggestions pls send me mail 
skmohinuddin786@gmail.com
9052076761
Hyderabad

The documents required for the testing are
1. SRS
2. FUNCTIONAL SPECIFICATIONS

SRS
Test Plan
Tracibility MATRIX

FRS,BRS,SRS

software requirement specification is required to do 
testing.

FRS,SRS,BRS are all same but the reqirement are pronounced 
diffrently from company to company......

sorry ajaya.

FRS and SRS is not same
SRS includes (FRS + NON-FRS).Then answer of above question is 

1.SRS
2.TestPlan document
3.Test Design Document(Test Scenarios & Test Cases)

yes you are right santhoshnathan..

Thank q for correcting me
regards,
Ajay

Both Smoke & Sanity testing are same in one way that is, 
its a build verification testing. When a particular module 
is developed then developer will do smoke testing in order 
to test whether the developed module is stable (which means 
the basic functionalities must work) then in turn it will 
be given for testing.

Now the testers will also do the build verification testing 
where we call that as Sanity testing

smoke testing is a non-exhaustive testing where as sanity 
testing is a cursory testing,This level of testing is a 
subset of regression testing . So I dont think smoke 
testing is also called sanity testing

its not right to say that smoke testing and sanity testing 
is same. both are different in some context. sanity testing 
comes first and then smoke testing. sanity testing is the 
initial level of testing required if the functionality 
which is being tested passes through this test then it will 
go for the next level of testing.
THE BASIC DIFFERENCE BETWEEN THEM ARE :
(1)
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. 
 
WHERE AS 

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.

(2)
A smoke test is scripted--either using a written set of 
tests or an automated test

WHERE AS 

A sanity test is usually unscripted

(3)
A Smoke test is designed to touch every part of the 
application in a cursory way. It's is shallow and wide.

WHERE AS 

A Sanity test is used to determine a small section of the 
application is still working after a minor change.

(4)
Smoke testing will be conducted to ensure whether the most 
crucial functions of a program work, but not bothering with 
finer details. (Such as build verification). 

WHERE AS 

Sanity testing is a cursory testing; it is performed 
whenever a cursory testing is sufficient to prove the 
application is functioning according to specifications. 
This level of testing is a subset of regression testing.

SO THESE ARE THE GENERAL DIFFERENCE

a)	Sanitary testing is nothing but the build is stable 
or not complete to testing is called sanitary testing.  
b)	Sanitary testing is also known as testers 
acceptation testing (TAT), or builds verification testing 
(BVT).
c)	Now check the lock and fell, that telephone have 
the connection or not, if connection have that is which 
type, all numbers are work or not, that size, this type of 
all testing apply the telephone.


My name is k.chandra sekhar,
My phone no are 9246540049 65880049, Hyderabad.
My mail id is ndra_143@yahoo.co.in 
I am taking the class for projects and interview trips if 
you interest contact

Sanity testing is done whenever the new build release. we 
have to test for the major functionality of the application 
which could stop our testing part continuation.

If it fails, then we  should not continue with our testing 
part. For the eg of telephone, If we check the 
functionality like while lifting the receiver, it should 
give the dial tone. if it fails, then its waste of time to 
continue with the testing phase.

Also called as smoke testing.

sanity testing is a test  which tests the build came from 
the developers is stable or not for testing that is it 
fufils all the requirements of the customer or not.
 also developers develops all the functionalities or not.
 coming to telephone  its phone working or not.
its phone has std r not
its phone havingn isd or n ot
its working properly or not
keypad of the phone is perfectly pressing r not

sanity testing is a 0 level tesing or intial testing or 
smoke testing. It is done to test that whether the build is 
stable for further testing or not.
for sanity testing of telephone
1. check that phone has dial tone or not.
1. check all the key of phone is pressing.

whenever the tester founds the bug, he will inform to the 
developers about the bug and to fix it. the developer than 
fixes the bug and sends to the tester, this process of 
fixing the bug and sending the new version to the tester is 
called Build. 
the tester has to test whether the major functionality of 
the application is working good or stopping us from testing 
is called as sanity testing.

example of telephone is common and u may refer from above 
examples.

         thank you.

A subset of all defined/planned test cases that cover the 
main functionality of a component or system, to 
ascertaining that the most crucial functions of a program 
work,but not bothering with finer details. A daily build 
and smoke test is among industry best
practices

I think it is test Bed and not belt u r mistaken

Test bed 
An environment is created for testing purpose.  A test bed 
may refer to software only or both hardware and software.

Conventional testing means the testing done by the test
engineers in the testing phase of SDLC on the application ,
whereas unconventional testing is done by the QA pplto each
and every otcome document of each phase right from the
intial phase of the SDLC