Answer
Client server application: In this type of architecture,
the entier application has to be installed on client
machine, and whenever you do any changes in your code,
again it has to be installed on all the client machines.
Web based application:Core application resides on the
server and client can be thin client( browser).whatever
changes you do, you have to install the application in
server, NO need to worry about the clients,bcoz u will not
install anything on client machine
1)Client server applcation directly we can launch
where as for launching the web based applcations we need
start database server,web server and by using internet
explorer (URL) we can launch web based application
2)Client server applications are menu driven where as web
based applications are liks driven to get the next page.
3)Client server application will contain less content, and
with less images
when compared to web based applications
web applications will contain more content with more images
Tuesday, March 30, 2010
What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)
Answer
>I would like to see myself as a Test Lead taking one step ahead.
>I would like to see myself contributing positively to the Organization which i'll working-I will develop new skills and techniques.
> I like to more responsibilities because i think that results in your personal growth and development.
>I want to get/complete few Software Certifications in Testing.
>I would like to see myself as a Test Lead taking one step ahead.
>I would like to see myself contributing positively to the Organization which i'll working-I will develop new skills and techniques.
> I like to more responsibilities because i think that results in your personal growth and development.
>I want to get/complete few Software Certifications in Testing.
What is Entry and Exit criteria explain in detail?
Entry and Exit criteria's tells:
For each level of testing like Intergration , System and
User acceptance testing, before and after what we need to
do.
Entry criteria for Integration Testing :
1. Testing environment should be ready.
1. All the Unit Test cases should be passed.
2. High level design document should be ready.
2. All the integration Test cases should be ready.
Exit criteria for Integration Testing :
1. All the Defects found during integration testing should
be fixed.
2. All the Integration Test cases should be passed.
For each level of testing like Intergration , System and
User acceptance testing, before and after what we need to
do.
Entry criteria for Integration Testing :
1. Testing environment should be ready.
1. All the Unit Test cases should be passed.
2. High level design document should be ready.
2. All the integration Test cases should be ready.
Exit criteria for Integration Testing :
1. All the Defects found during integration testing should
be fixed.
2. All the Integration Test cases should be passed.
What is metrics? type of metrics?
Answer
The test metrics are basically the measurement of
quality,judging the performance of tester and to detect the
problem in process. This is usually maintained by Quality
Lead. Even the coverage includes Test Coverage and
efficiency.
The test metrics are basically the measurement of
quality,judging the performance of tester and to detect the
problem in process. This is usually maintained by Quality
Lead. Even the coverage includes Test Coverage and
efficiency.
Difference between SDLC and STLC
# 1 Waterfall model comes uder SDLC while V model comes under
STLC,in waterfall model testing is done after completion of
project but in v model testing starts from first phase i.e
from requirement.In Waterfall model no correction or
changes is done and in v model after acceptance testing the
changes can be done.
# 2 water fall model goes in step by step means can't back to
the prevoius step...generally used in development of a
SDLC..
while V model belongs to the STLC that is a part of
SDLC .
STLC,in waterfall model testing is done after completion of
project but in v model testing starts from first phase i.e
from requirement.In Waterfall model no correction or
changes is done and in v model after acceptance testing the
changes can be done.
# 2 water fall model goes in step by step means can't back to
the prevoius step...generally used in development of a
SDLC..
while V model belongs to the STLC that is a part of
SDLC .
Monday, March 29, 2010
difference between product based company and service/project based company
Product - impact on groups(Requirement gathered from market
study)
Project - impact on users(requirement from users)
Product based company:
The company which will have their own products .These products are used by the other companies by paying money to this companies.
Service Based Company:
These companies depend on the clients.Means that,they will develop a product or an application for the other companies. Ex:Sapient corporation,Accenture,TCS etc....
study)
Project - impact on users(requirement from users)
Product based company:
The company which will have their own products .These products are used by the other companies by paying money to this companies.
Service Based Company:
These companies depend on the clients.Means that,they will develop a product or an application for the other companies. Ex:Sapient corporation,Accenture,TCS etc....
Thursday, March 25, 2010
Difference between Sessions and Cookies
The main difference between cookies and sessions is that cookies are stored in the user's browser, and sessions are not. This difference determines what each is best used for.
A cookie can keep information in the user's browser until deleted. If a person has a login and password, this can be set as a cookie in their browser so they do not have to re-login to your website every time they visit. You can store almost anything in a browser cookie. The trouble is that a user can block cookies or delete them at any time. If, for example, your website's shopping cart utilized cookies, and a person had their browser set to block them, then they could not shop at your website.
Sessions are not reliant on the user allowing a cookie. They work instead like a token allowing access and passing information while the user has their browser open. The problem with sessions is that when you close your browser you also lose the session. So, if you had a site requiring a login, this couldn't be saved as a session like it could as a cookie, and the user would be forced to re-login every time they visit
A cookie can keep information in the user's browser until deleted. If a person has a login and password, this can be set as a cookie in their browser so they do not have to re-login to your website every time they visit. You can store almost anything in a browser cookie. The trouble is that a user can block cookies or delete them at any time. If, for example, your website's shopping cart utilized cookies, and a person had their browser set to block them, then they could not shop at your website.
Sessions are not reliant on the user allowing a cookie. They work instead like a token allowing access and passing information while the user has their browser open. The problem with sessions is that when you close your browser you also lose the session. So, if you had a site requiring a login, this couldn't be saved as a session like it could as a cookie, and the user would be forced to re-login every time they visit
Subscribe to:
Posts (Atom)
