two tier archtecture is client server and three tier 
architecture is web based application.

Two tier architecture means: 

        Client server application. Client acts as Front End 
and Server acts as Backend like databases.


Three tier Architecture Means:  
     Three tier architecure means N tier architecture like 
Yahoo , gmail, and or Web Applications. Having Number of 
Users or Customers or 
Clients.                                                    
       M  Dora Babu   S O N T A S O F T W A R E     
BANGLORE     Mail me @  mdorababum@gmail.com

hi i m swapnil
Two-tier architecture is a client/server architecture , 
where a request to do some task is sent to the server and 
the server responds by performing the task.where as a three-
tier or a multi tier architecture  has client, server and 
database. Where the client request is sent to the server 
and the server in turn sends the request to the database. 
The database sends back the information/data required to 
the server which inturn sends it to the client.

two tier means two layer available.three tier means three
layer available.

web based application testing is 3 tire testing which 
contain business layer,presentation layer and enviroment 
layer.

read throughly the requirements eg: SRS

The initial stage of testing starts with the study phase..
i.e. Understanding the scope of the project.
In this phase you clear your assumptions and questions with 
dev.This is very important.
Note: Not only the project knowledge but the other 3rd 
party products involved(for ex. your product may interact 
with MS Sharepoint or exchange Server so that knowledge is 
also necessary).

2.After understanding the scope of the project you need to 
write test Plan.

3. In parallel develop Test outline ->test scenarios ->test 
cases.

4.Review the Test Plan and Test Cases (Peer review) and do 
the rework if any.

5. Freeze the Test Plan and Test Cases. If you have any 
repository like TD or QC then upload your Test Cases.

6. Map your Test Cases with Requirements you alredy fed in 
the repository.

7. Prepare the Test Environment Setup and Data Setup.

8. Prepare your documents need from testing like 
Trackers,etc..,

9. Start Testing.

Testing initiation : during this testing phase project
manager  will prepares  project level document. here he
concentrates on below factors.
  
             1. type of project
             2. scope and involves
             3. risk analysis

Quality - With respect to IT we can say “deliverables 
working as it suppose to be for the customers in the first 
time after installation with no errors”. Usually Quality is 
maintained in a company by group called "SQA Group". They 
are responsible to define and structure the company 
process. It will have member from HR, Finance, Facility, 
Security, Reception, Development, Testing teams. 

Ex: SQA team might decide how the offer letter format of a 
company should look like? How the pay slip format should 
look like? Where the developers should check in the code? 
What kind of templates should be used to develop project 
plan and test plan? 

The belief is following a quality process, the output (that 
is the software deliverables) will also be in high quality. 
That is where SQA comes in the picture.


Where as testing is “executing an application with the 
intention to find bug(s)”. It’s a team not a group like SQA.

Tests focused on ensuring the target-of-test data (or
systems) are accessible only to those actors for which they
are intended.

Test the application against unauthorised access.

SECURITY TESTING :

The process of testing which is done to ensure the security 
of the application or the system or the product is 
recognised as Security Testing

It is done by various ways like

1.Intrusion Detection
2.Passward Protection
3.Encryption-Decryption
4.Restriction on Unauthorised Access etc

Security Testing is a very important aspect of 
Testing,sometime involves a lot of cost.

ad hoc testing is an unplanned testinng of a perticular 
issue or issues. When ever a requiest comes test team has 
to manage the resource to perform the task and plan the 
delivarables as commited.

Test the application Randomly.

It is a informal testing. It means testing is done by 
randomly.

doing a short cut way, doesn't follow sequencial order.
           1.due to lack of time
           2.due to lack of skills
           3.due to lack of documentation or information
           4.due to lack of resource 
                           over to these come risks testing 
team concentrate on ad-hoc testing.

Adhoc testing doesn't have proper plan,probably it may 
carried out at the end of testing where all the testcases 
are executed.

The main aim is to check the application randomly.

It is mostly done when the application has lesser delivery 
time.

Smoke Testing: Executing the application to check whether it
is free from errors or not. It should be done as soon as we
receive the Build from the developer.

Smoke Testing: Testing the application to know whether the 
application is eligible to test is called smoke testing. It 
means there should some piece of code should be working for 
the testers to test and proceed further. This testing is 
done many times to check does the application meet 
acceptance criteria to start testing.

Ex: There might be a case "dll not found error" seen when 
you launch the application after installing. What testing 
can you do when you cannot launch the application?

Its an early stage of testing process. We carry out smoke 
testing for checking the stability of the build. Whether 
the build is ready for testing or not.If smoke testing is 
failed then the build is rejected.

The minimum requirement to start testing:-
   Build.
   Test envirnoment.
   Test Case.

The minimum requirements to start testing are
1).Test cases should be prepared and reviewed.
2).Testing environment should be ready.
3).Build should be released

Hi i am ashok from Perot Systems,
The Following are the Minimam Reqqirement to start testing
1. Receive build from development team
2. Reviewed testcases design document
3. Requirements of the customer

Following listed points should have been completed in order 
to say go for testing:
1)Build has been received from development team & 
configuration team has deployed it on QA box.

2)Test environment setup completed & test bed is prepared.

3)Tester has done his analysis on the clients requirement & 
specification.

4)Test cases are reviewed completely.