Testing Methodology
We begin the testing process by developing a comprehensive
plan to test the general functionality and special features
on a variety of platform combinations. Strict quality
control procedures are used. The process verifies that the
application meets the requirements specified in the system
requirements document and is bug free. At the end of each
testing day, the team prepares a summary of completed and
failed tests. Our programmers address any identified issues,
and the application is resubmitted to the testing team until
every item is resolved. All changes and retesting are
tracked through spreadsheets available to both the testing
and programming teams. Applications are not allowed to
launch until all identified problems are fixed. A report is
prepared at the end of testing to show exactly what was
tested and to list the final outcomes.

Our software testing methodology is applied in three
distinct phases: unit testing, system testing, and
acceptance testing.

    * Unit Testing?The programmers conduct unit testing
during the development phase. Programmers can test their
specific functionality individually or with other units.
However, unit testing is designed to test small pieces of
functionality rather than the system as a whole. This allows
the programmers to conduct the first round of testing to
eliminate bugs before they reach the testing staff.
    * System Testing?The system is tested as a complete,
integrated system. System testing first occurs in the
development environment but eventually is conducted in the
production environment. Dedicated testers, project managers,
or other key project staff perform system testing.
Functionality and performance testing are designed to catch
bugs in the system, unexpected results, or other ways in
which the system does not meet the stated requirements. The
testers create detailed scenarios to test the strength and
limits of the system, trying to break it if possible.
Editorial reviews not only correct typographical and
grammatical errors, but also improve the system?s overall
usability by ensuring that on-screen language is clear and
helpful to users. Accessibility reviews ensure that the
system is accessible to users with disabilities.
    * Acceptance Testing?The software is assessed against
the requirements defined in the system requirements
document. The user or client conducts the testing in the
production environment. Successful acceptance testing is
required before client approval can be received.


Test Strategy


The test team worked with the project team members to
formulate a test plan, a schedule, and strategies based on
the Small IT Solution scope and identified small business
customer scenarios.

The identified customer scenario, for the solution testing,
is a small business of approximately 50 PCs. The customer
would have in place a peer-to-peer network. They may also
have a limited number of existing Microsoft servers or other
server products not developed by Microsoft. The customer
approach toward migration would be to implement Windows
Small Business Server 2003, Standard Edition on new hardware
and then migrate existing data and configurations to the new
platform.

The development team was expected to have unit tested the
recommendations and configurations provided in the
documentation. This includes verifying the service
recommendations and specifying the correct sequence of steps
to ensure proper configuration. The deployment topology and
architectural choices, regarding the network and servers,
are assumed to have been validated as best practices by the
solution architect and Microsoft product groups relevant to
the solution. The deployment topology, architectural
choices, and the validation results of unit testing were
provided before the solution testing began.

Testing of the Small IT Solution was completed with the
following two distinct focuses:
?	

The primary focus of the solution testing was to validate
the configurations and recommendations provided in the
solution. The results of this testing were reflected in the
test cases and the test case results that were produced by
the test effort.
?	

The secondary focus of the solution testing was to generate
feedback on the relevant Microsoft products. Feedback was
recorded during solution planning, designing, development,
and testing through meetings with the Microsoft product
development teams and through product bugs, filed with the
relevant Microsoft product development teams.

I think test methodologies are 1)static method  2)dynamic 
method and testing techniques are 1) black box testing
2) white box testing 3) grey box testing.
static testing: Here, we wil do testing on the 
documentation not on the app. i.e test case design, review, 
test scenarioes but in dynamic method we wil do testing on 
the app.
black box testing is done by testers here, we wil check the 
functionality of the app.
white box testing is done by developers.
grey box testing means sometimes some code is required to 
test the app. then we go for grey box testing.

 If it is wrong, pls. correct me it is imp. to me also.
 my mail id : mythreyibh@gmail.com

Testing Methodology
	

We begin the testing process by developing a comprehensive
plan to test the general functionality and special features
on a variety of platform combinations. Strict quality
control procedures are used. The process verifies that the
application meets the requirements specified in the system
requirements document and is bug free. At the end of each
testing day, the team prepares a summary of completed and
failed tests. Our programmers address any identified issues,
and the application is resubmitted to the testing team until
every item is resolved. All changes and retesting are
tracked through spreadsheets available to both the testing
and programming teams. Applications are not allowed to
launch until all identified problems are fixed. A report is
prepared at the end of testing to show exactly what was
tested and to list the final outcomes.

Our software testing methodology is applied in three
distinct phases: unit testing, system testing, and
acceptance testing.

    * Unit Testing?The programmers conduct unit testing
during the development phase. Programmers can test their
specific functionality individually or with other units.
However, unit testing is designed to test small pieces of
functionality rather than the system as a whole. This allows
the programmers to conduct the first round of testing to
eliminate bugs before they reach the testing staff.
    * System Testing?The system is tested as a complete,
integrated system. System testing first occurs in the
development environment but eventually is conducted in the
production environment. Dedicated testers, project managers,
or other key project staff perform system testing.
Functionality and performance testing are designed to catch
bugs in the system, unexpected results, or other ways in
which the system does not meet the stated requirements. The
testers create detailed scenarios to test the strength and
limits of the system, trying to break it if possible.
Editorial reviews not only correct typographical and
grammatical errors, but also improve the system?s overall
usability by ensuring that on-screen language is clear and
helpful to users. Accessibility reviews ensure that the
system is accessible to users with disabilities.
    * Acceptance Testing?The software is assessed against
the requirements defined in the system requirements
document. The user or client conducts the testing in the
production environment. Successful acceptance testing is
required before client approval can be received.

Methodology is the process we follow
and Technique is the procedure.

Let me explain briefly

Testing are of two types
1. Static Testing
2. Dynamic Testing

Methodology are 
1. Unit Testing
2. Integration Testing
3. System Testing
4. User Acceptance Testing.


Methodology----------------------Techniques

1. Unit Testing-------------a. Code coverage
                            b. unit/code functional testing
                            c. Code COmplexity
  for code coverage we have techniques like statement
coverage, path coverage, loop coverage.


2. Integration Testing-------a. Top Down approach
                             b. bottom up approach
                             c. sandwich approach
            for all these approach we need some small
program which we call it as stub and drivers.

3.  System Testing -------a. FUnctional testing
                          b. Non-Functional Testing

 Functional Testing-------a. Error Handling Testing
                          b.Guess Testing
                          c. Input Domain testing(BVA & ECP)
                          d. Compactability testing
                          e. State transition testing
                          f. parallel testing
                          g. inter operatability testing
                          h. configuration testing

4. User Acceptance testing---a. Beta testing
                             b. alpha testing
                             c. Business scenario (BRS)


if i am wrong please do correct.

sameer_800720@yahoo.co.in