sdlc is software development life cycle.
1. Requirements gathering phase.
2. Analysis phase.
3. Design phase
4. Development phase.
5. Testing phase
6. maintenance phase

i hope this is correct answer. 

1)Whether the password correctly encrypting into ourdatabase.
2)Authentication test.It contains whether the user is valid
or not.
3)Page navigations its.suppose i am transaction page,i want
to back another page using navigation buttons.

always know the precondition of the test module.

in this case a tester should know the balance amount in the
person 1 account.

It is the primary testing after which further testing 
should be done. It helps reduce the time of testers. 
For eg in a LOGIN window, if it does not allow you to LOGIN 
no point in logging in,so we can go ahead with Basic 
Testing. This is also called Sanity Testing.

Conceptually Smoke testing and sanity testing both are same
but perception ally these are different.Smoke testing:Smoke
testing is conducted with negative perception it is the
testing in which all the functionality are available are not
is tested to proceed for further overall testing.Sanity
testing: This is also test for to check whether all the
functionality are available are not.But this testing is
conducted with positive perception.

some companies will say the sanity and smoke testing 
are same,but some companies will say just before releasing 
the build the developers will check whether the build is 
proper detailed testing(or)not.that is smoke testing
      once the build is released the test engineers will 
check the build is proper for detailed checking(or)not.that 
is sanity testing.

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
    * A Smoke test is designed to touch every part of the
application in a cursory way. It's shallow and wide.
    * Smoke testing is conducted to ensure whether the most
crucial functions of a program are working, but not
bothering with finer details. (Such as build verification).
    * Smoke testing is normal health check up to a build of
an application before taking it to testing in depth.

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.
    * A Sanity test is used to determine a small section of
the application is still working after a minor change.
    * 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.
    * Sanity testing is to verify whether requirements are
met or not, checking all features breadth-first.

equivalence testing

Equivalence partitioning

Boundary value analysis

Quick Test Professional (QTP) is an automated functional Graphical User Interface (GUI) testing tool that allows the automation of user actions on a web or client based computer application.
It is primarily used for functional regression test automation. QTP uses a scripting language built on top of VBScript to specify the test procedure, and to manipulate the objects and controls of the application under test.

Integration testing is testing different modules with in a
software system at once,,ieall the modules are tested as a
one whle software system

end-to-end testing is nothing but testing a product as and
end user to ensure whether it meets all requirements of end
user.

It defines about the bugs found by client to bugs found by 
tester

The no of defects identified in a component or system
divided by the size of the component of the system.

Defect Density can be defined as the no. of defects found 
in a particular section of code.
Defect Density=No. of Defect found/Total number of lines of 
code.